Closed crbn60 closed 4 years ago
Awesome! balenaOS are still using kernel overlays! We gave up on that for beagleboard.org, it's too un-reliable, supporting kernel overlays just ends up being a waste of developer resources...
After the overlay loads, do you get the iio adc driver on that system?
debian@bbb-pwr01-ser09:~$ ls -lha /sys/bus/iio/devices/
total 0
drwxr-xr-x 2 root root 0 May 12 03:01 .
drwxr-xr-x 4 root root 0 May 11 17:23 ..
lrwxrwxrwx 1 root root 0 May 11 17:23 iio:device0 -> ../../../devices/platform/ocp/44e0d000.tscadc/44e0d000.tscadc:adc.0.auto/iio:device0
Regards,
# ls -lha /sys/bus/iio/devices/
total 0
drwxr-xr-x 2 root root 0 May 12 02:48 .
drwxr-xr-x 4 root root 0 May 12 02:48 ..
Doesn't look promising.
Some more digging makes me thing that my issue is most likely system level and not with the Python library.
What can I do to verify the system setup, before further troubleshooting at a higher level?
This page indicates that further setup is required:
I added the following directly to the /mnt/boot/uEnv.txt
file on my development device:
enable_uboot_overlays=1
disable_uboot_overlay_video=1
And ADC.setup()
now succeeds. On to the next challenge.
Thanks for your help.
This appears similar to a variety of issues I see where the library is unable to locate the subsystem, at least that's my interpretation. Running as root using the library installed from master:
I'm running a Beaglebone Green Wireless with balenaOS on top of it. In lieu of the version script:
Some excerpts from
dimes
:Then, after trying to run
ADC.setup()
, this gets output:What else can I determine from the system?
Thank you,
A.