On Fri, Oct 13, 2017 at 12:58 PM, Steven Napolitano <[email protected]> wrote: > Thanks Robert. I'm running the 3.8.13-bone86 kernel now. I apologize > because this questions is probably below your pay grade but...do I have to > compile a custom overlay to get ADC working on this kernel? I'm confused > because our legacy BBB are running 3.8.13-bone70 and the uEnv.txt is simply
Hi Steven, So a lot with 3.8.13, i honestly just don't remember. ;) > this: > #dtb= > cmdline=quiet init=/lib/systemd/systemd > > ##Example > #cape_disable=capemgr.disable_partno= > cape_enable=capemgr.enable_partno=BB-UART4 Just tested this: cape_enable=capemgr.enable_partno=BB-UART4,BB-ADC debian@beaglebone:~$ uname -r 3.8.13-bone80 debian@beaglebone:~$ cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART4 8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-ADC debian@beaglebone:~$ cat /sys/bus/iio/devices/iio\:device0/*_raw 3687 2991 3486 1993 1419 1569 1680 3839 > > Somehow ADC is working. When I use that uEnv.txt on kernel 3.8.13-bone86 i > get the dreaded "RuntimeError: Unable to setup ADC system. Possible causes > are: > - A cape with a conflicting pin mapping is loaded > - A device tree object is loaded that uses the same name for a fragment: > helper" > when using the AdaFruit BBIO library. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYi1Jmo2RNiaeYaFkJWXvGq1Oe5aGPa%2BBokDvLY5OjNR8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
