The scanner does not power back on if disconnected. The BBB has to be power cycled before the scanner is usable.
The relevant DMESG entries are below: [15104.176465] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15104.176536] hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s [15104.176555] usb 1-1: USB disconnect, device number 2 [15104.176566] usb 1-1: unregistering device [15104.176579] usb 1-1: unregistering interface 1-1:1.0 [15104.176809] musb-hdrc musb-hdrc.1.auto: shutdown urb df5da6c0 ep1in-intr [15104.177785] usb 1-1: usb_disable_device nuking all URBs [15104.290606] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 [15104.290694] hub 1-0:1.0: hub_suspend [15104.290724] usb usb1: bus auto-suspend, wakeup 1 On Wed, Nov 20, 2013 at 1:13 PM, Ulf Samuelsson <[email protected]>wrote: > What happens if you remove the scanner, and plug it in again? > > Best Regards > Ulf Samuelsson > > > 20 nov 2013 kl. 17:56 skrev Philippe Laurent <[email protected]>: > > Ulf, many thanks for the mention. If I hit the last brick wall, I'll hire > you to make the fix available. > > Meanwhile, some interesting developments. Curious about the grounding > conversation, I removed the BBB from the metal case in which it was > enclosed, and placed it on a non-conductive mat. Powered it on with the > scanner attached, and it works as it should. BUT, I have not had the Babble > Interrupt issue again. Even handling the bare board, the USB wire, the > scanner, all of which might have triggered the interrupt before, the > scanner continues to work. After 2 days, and still no interruption, I > power-cycled the BBB, and again, it has run perfectly with no interruptions > for another 2 days, even with the continued attempts to cause the > interrupts to occur. By now, I would have had easily a dozen Babble > Interrupts with the metal case. > > I'm going to restore the ondemand startup script and power control > settings to 'normal' and continue testing. > > On Saturday, November 16, 2013 12:39:56 AM UTC-5, Ulf Samuelsson wrote: >> >> Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev >> [email protected]: >> > I'm using my Beaglebone Black with a USB temperature sensor. It works >> very well, however I noticed monitoring stopped last night after roughly 35 >> days uptime. This morning I looked more closely into the log file and >> noticed: >> > >> > >> > kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred >> > >> > >> > >> > I wasn't able to successfully reset the USB device and before I was >> able to restart the BBB stopped responding. I power-cycled it and it was >> back to normal again. Any ideas what caused this kernel message? >> >> Work as an independent linux consultant, and I think I can fix this >> problem. >> Offered TI to do this, but they said it would be fixed in 3.12, so no >> interest. >> Well, 3.12 is here and no fix as far as I can see in the code. >> I estimate 2 days work to fix with testing. >> >> /ulf >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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.
