I personally would not use the AM335x onboard ADC in any form for a production device. There is a known issue (Google FSM_BUSY) where the FSM gets into a hung state that cannot be resolved without POR. I banged my head against that problem for several months before realizing what was happening. My setup involved using a PRU to acquire the data and send it to user space via rpmsg. I've moved on to an ADS1299 based solution on a custom cape.
If you use devmem (or similar) to view the ADC registers (ADCSTAT in particular) during the hung state, you can see that bit 5 and bit 4 will both be set: FSM_BUSY=1 and STEP_ID= idle, which obviously isn't possible, meaning the FSM is hung and can't recover without POR. On Wed, Oct 7, 2020 at 2:41 AM [email protected] < [email protected]> wrote: > Hello beaglebone community, > > This is my first post. > > I used beaglebone to develop a prototype for for a self-cleaning > smoothie machine that we plan to commercialize (see video below). It has > multiple sensors and outputs to run motors/solenoids while ensuring user > safety. > > https://www.youtube.com/watch?v=76XDJK5V0PA&feature=share&; > ab_channel=PascalKriesche > > Right now we have. BBB running a linux OS and running a script we wrote > in JS. One issue we have had was the 1.8V analog sensors losing signal > which required us to reboot the system every tie that occurred. We also had > an issue flashing 2 out of our 4 prototypes with an image that worked > (seems to be a firmware version issue leasing to an incorrect hardware pin > mapping). > > I know eventually we want to use a chip on board, but for the initial > production run we were hoping on sticking to a prebuilt onboard computing > module for the initial 1000 units in order to save time and costs. I was > wondering if anyone in this forum had experience launching a product with > beaglebone and if this instability can be resolved with the correct I/O > filtering on our PCB and software functionality. > > Thanks in advance! > > -- > 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/faf26e97-c403-4dac-adc8-7acede4832b9n%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/faf26e97-c403-4dac-adc8-7acede4832b9n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAMRnUvBQbX5Fnd39y3i0%2BVkJOZhmAyuqMb2oZtOkdDSAD1E%3DEA%40mail.gmail.com.
