The ADC kernel drivers throw errors when reading multiple channels, you can either deal with it or fix the driver. So far, I've just dealt with it, ignoring the resource unavailable error and just continuing on:
Python code example: https://github.com/cdsteinkuehler/linuxcnc/blob/MachineKit-ubc/configs/ARM/BeagleBone/BeBoPr-Bridge/ReadTemp.py#L303 The resource unavailable error is thrown in a consistent pattern, but the pattern changes depending on which channels you're actually reading. Also, the errors are not time sensitive. I get the same patten of errors when performing reads by hand (using cat at the command line, with _seconds_ between reads) as I do reading via a program with a 50 mS delay. I'm hoping they finally fixed this in the newer kernels. On 2/23/2014 11:01 AM, Ben Mitch wrote: > Hi guys - have any of you reached a resolution on this? I've been getting > it intermittently since the start with my BBB, 3.8.13, but just now as I > start to use more of the AIN pins I've started seeing what is reported > here, that it locks up and I have to reboot to recover access to the AIN > pins. I quickly lose access again, making my BBB kind of not fit for this > particular purpose, which is frustrating :). Any info gratefully received, > any requested further info happily posted. > > Cheers > > On Monday, 2 December 2013 12:56:11 UTC, [email protected] wrote: >> >> I am getting resource temporary unavailable when I tried to read ADC pins >> from BeagleBone Black -- Charles Steinkuehler [email protected] -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
