**** BEGIN LOGGING AT Tue Dec 19 03:00:02 2017
Dec 19 04:47:30 <blabla> help
Dec 19 04:47:57 <blabla> hello
Dec 19 04:48:39 <blabla> join
Dec 19 04:48:44 <blabla> \join
Dec 19 04:48:49 <blabla> help
Dec 19 04:48:55 <blabla> help
Dec 19 05:54:01 <zmatt> ... no help for you
Dec 19 07:33:53 <fisal> #bbb
Dec 19 07:34:14 <fisal> Hello
Dec 19 07:36:01 <fisal> I have the latest debian image for BBB .. It's been 3 days trying to enable the  7 inch cape  from NewHaven displays with no success
Dec 19 07:37:03 <zmatt> fisal: you're sure it's compatible?
Dec 19 07:37:06 <fisal> As it's not offically supported in the debian image provided by beaglboard.org .. is there a way to add support for this screen?
Dec 19 07:37:37 <zmatt> probably, although the first question would be: why isn't it supported?
Dec 19 07:37:51 <fisal> Yes. it's compatible because the image that's provided by newhaven displays is working with screen enabled.
Dec 19 07:38:30 <fisal> I don't want to use their image because it's not documented like theoffical image by beagleboard.org
Dec 19 07:40:09 <zmatt> okay
Dec 19 07:41:36 <zmatt> assuming it has a cape identification eeprom, it should work automatically once a suitable overlay for it has been added to /lib/firmware
Dec 19 07:42:02 <zmatt> beagleboard.org maintains a large collection of these that are automatically installed to ensure capes work "out of the box"
Dec 19 07:45:53 <zmatt> if the manufacturer of your cape doesn't provide an overlay, one will need to be made based either on the schematics or on the known-working image
Dec 19 07:46:16 <zmatt> anyway, I'm afk, I need a bit more sleep
Dec 19 15:22:30 <mouha1> hi, I'm using a BBB on SD with "bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img" and I'm fighting to be able to have the max of GPIO on P8 by disabling HDMI.
Dec 19 15:23:50 <mouha1>  When I decomment uEnv.txt "disable_ubtoot_overlay_video=1" reboot and "echo 70 > /sys/class/gpio/export" + "echo 0 > /sys/class/gpio/gpio48/value" I'm rejected
Dec 19 15:37:10 <mouha1> nobody ?
Dec 19 15:44:52 <zmatt> mouha1: probably you're not using u-boot overlays because the bootloader on eMMC is being used and it's too old
Dec 19 15:45:28 <zmatt> you can verify this theory by bypassing the eMMC bootloader by powering on while holding down the S2 button (you can release the button once the power led turns on)
Dec 19 15:45:39 <zmatt> that will result in the bootloader on SD card being used
Dec 19 16:23:50 <mattvenn> zmatt: it's about 40mv pk to pk
Dec 19 16:23:52 <mattvenn> very short spikees
Dec 19 16:27:55 <mattvenn> I'm using a lab psu for the supply at the moment, pretty quiet, not switched mode
Dec 19 16:30:02 <mattvenn> spikes are 16ms apart
Dec 19 16:30:49 <zmatt> ms? us you mean?
Dec 19 16:31:04 <zmatt> since you said 33 kHz, not 33 Hz
Dec 19 16:31:37 <zmatt> actually, that would 30us
Dec 19 16:31:44 <zmatt> so uhh, which is it?
Dec 19 16:32:15 <mattvenn> and zoomed in on a spike, it's made of about 12 spikes that are about 32ns long each, separated by 26us
Dec 19 16:34:16 <zmatt> odd
Dec 19 16:35:00 <mattvenn> yeah
Dec 19 16:35:07 <mattvenn> today it looks a bit different
Dec 19 16:36:30 <mattvenn> ok, just connected the usb from the beaglebone  and got the  33khz back
Dec 19 16:37:19 <mattvenn> regarding  your question about j sysnc freq  on the panel,  can  I look that up easialy out of xorg.conf or something?
Dec 19 16:37:44 <zmatt> having said that, 40 mV of noise on a 5V supply is not that much... if the teensy requires a much more stable supply, it should probably take care of that itself
Dec 19 16:38:40 <mattvenn> I've tried to build a very quiet supply on the ADC board, and currently runniing the  teensy off that.
Dec 19 16:38:56 <mattvenn> I've removedd the fuse on the teensy so the 5v noise froom the bbb isn't so bad
Dec 19 16:38:56 <freemor> Could it be ingrassing from a cellular transmitter or wifi?
Dec 19 16:39:06 <mattvenn> yes, I was thinking that freemor
Dec 19 16:39:24 <mattvenn> III've got about 3 esp8266s around here
Dec 19 16:39:27 <zmatt> uhh, I'm not sure what the easiest way to determine that frequency is... though it's easy enough to determine if the display is causing this: disconnect it
Dec 19 16:39:57 <mattvenn> zmatt: yes I'll give that a go
Dec 19 16:40:30 <mattvenn> it's not that easy in my case because the screen breaks out the unused header pins, and I'm using them for spi/reset etc
Dec 19 16:40:46 <mattvenn> but I can at least check the supply
Dec 19 16:40:51 <mattvenn> I'll do it now
Dec 19 16:41:21 <zmatt> it's a CAPE rather than a hdmi display?
Dec 19 16:42:12 <mattvenn> yyep
Dec 19 16:42:30 <zmatt> (also, I just realized, there is actually an easy way to determine hsync frequency, namely by measuring the hsync pin on the beaglebone with a scope.  however the fact that you've got different interference patterns under different circumstances already makes that guess of mine a bit irrelevant)
Dec 19 16:45:23 <mattvenn> https://imagebin.ca/v/3lFHIH9Opv9C
Dec 19 16:46:21 <mattvenn> https://imagebin.ca/v/3lFHZlAhlT65
Dec 19 16:46:39 <mattvenn> 1st is zoomed out showing 16ms periodic pulses
Dec 19 16:46:57 <mattvenn> 2nd is zoomed in on a pulse showing it's actually a set of pulses
Dec 19 16:47:08 <mattvenn> will unplug the screen now
Dec 19 16:49:02 <zmatt> and what did you do to change the pattern between this and the 33 kHz ?
Dec 19 16:50:22 <mattvenn> riight now I'm guessing that I had the trigger set a bit higher so I was only catching every other oone
Dec 19 16:50:29 <mattvenn> I think it was always there
Dec 19 16:51:18 <zmatt> so you mean 33 Hz then?
Dec 19 16:51:22 <zmatt> not kHz ?
Dec 19 16:52:25 <mattvenn> sorry I'm being confusing
Dec 19 16:52:26 <zmatt> 16 ms means about 60 Hz... sounds like something plausibly display-related
Dec 19 16:52:54 <zmatt> or numerous other things I guess
Dec 19 16:53:20 <zmatt> hmm, scope says 67.8 Hz though...
Dec 19 16:53:27 <mattvenn> I'm really at the beginning of tracking this down and sttartiing to characterize the noise.
Dec 19 16:53:46 <mattvenn> Yes, best to believe the scope ;)
Dec 19 16:54:17 <mattvenn> with hthe screen unplugged that noise is looking different
Dec 19 16:54:37 <mattvenn> I'm still getting a similar looking pattern, but it's a lot slower now
Dec 19 16:54:49 <zmatt> you're very very sure it's not the power supply?
Dec 19 16:54:59 <mattvenn> pulses separated by 1ms, and then 500ms between sets of pulses
Dec 19 16:56:17 <zmatt> since it sounds like the pattern might be changing depending on power consumption
Dec 19 16:58:02 <mattvenn> youre right
Dec 19 16:58:12 <mattvenn> same pattern with the bbb off
Dec 19 16:58:24 <zmatt> :)
Dec 19 16:58:27 <mattvenn> now I feel like an idiot -- sorry!
Dec 19 17:00:29 <mattvenn> iit's a 3 channel psu and someone else is using another channel
Dec 19 17:00:42 <mattvenn> turning that off has stopped it
Dec 19 17:02:44 <freemor> mattvenn: we've all chased our tails at one point or another. it why other eyes are so useful
Dec 19 17:02:49 <zmatt> mattvenn: hah
Dec 19 17:03:06 <zmatt> yup
Dec 19 17:04:37 <mattvenn> however, the screen is very noisy
Dec 19 17:05:08 <mattvenn> just posting a new pic
Dec 19 17:07:52 <mattvenn> screen runniing app https://imagebin.ca/v/3lFNzDIEWBVT
Dec 19 17:08:25 <mattvenn> screen blank: https://imagebin.ca/v/3lFNnLhv1zQ4
Dec 19 17:09:03 <mattvenn> so that's on the 5v line of the usb socket of the bbb
Dec 19 17:09:39 <zmatt> the power supply is still within +/-1%
Dec 19 17:09:43 <mattvenn> and what was happening yesterday was that every now and then the spike would coincide with the teensy generating the dac pulse
Dec 19 17:09:57 <mattvenn> and that would make the ADC under test faill
Dec 19 17:10:19 <mattvenn> zmatt: it's because this is a low noise application
Dec 19 17:10:37 <mattvenn> I'm trying to keep the noise at the ADC to below 1mv
Dec 19 17:10:59 <zmatt> so then the mistake is using 5v from an usb plug as low-noise analog supply with inadequate filtering
Dec 19 17:11:15 <mattvenn> yuup
Dec 19 17:11:45 <mattvenn> running the teensy from the adc psu is much cleaner
Dec 19 17:14:06 <mattvenn> so thanks for your eyes!
Dec 19 17:14:34 <zmatt> np :)
Dec 19 17:15:35 <mattvenn> I really appreciate the opportunity to talk these things over. We have a hackerspace here but not too many people are using bbb
Dec 19 18:46:56 <deadprogram> hello, all
Dec 19 18:47:27 <deadprogram> anyone run into any trouble with update_kernel.sh --bone-kernel --lts-4_14 ?
Dec 19 18:48:40 <deadprogram> seems like it ran, but after reboot, now my BBG does not appear to be starting. usr0 is doing heartbeat, but usr2 is lit all the time
Dec 19 19:05:20 <deadprogram> was knocked off IRC for some reason
Dec 19 19:06:02 <deadprogram> anyone have trouble with the update_kernel.sh with not booting after update?
Dec 20 02:17:38 <onio> need help with u-boot not reading uEnv.txt file on the beaglebone black
**** ENDING LOGGING AT Wed Dec 20 03:00:02 2017