It could be a power 'level' issue. Most modern sound systems have a built-in kill switch. That if the volume spikes the speakers are turned off to prevent damage.. A similar system is probably in the BBB that prevents it from *receiving* to much power.
It has to be something like that because on a whim I tried to run my BBB before going to bed. In the time it took to get ready for bed (~5min) the BBB had powered down on it's own (no power LED light). Sometimes it runs for days with no issue...other times, like previously mentioned, mere minutes. And this happens on both USB and AC power (adapter is the recommended one by Adafruit). On Monday, November 18, 2013 1:18:54 PM UTC-5, Lei Wang wrote: > > I think Robert is correct. I fetched a snapshot of u-boot (2013.10), build > and dropped it in. It seems that the time jump problem is going away. > > I also did some testing with TI's kernel. I disabled the OPPs at 1G, 720M, > and 600MHz. So the highest OPP is 500MHz. It seems that BBB is running much > more robust. I ran the system overnight without seeing random reboots. > > I wonder if someone has some insight into this random reboot problem. > Why it seems a slower clock helps? > Why a USB connection also seems help (it doesn't seem to decrease the > BogoMIPs)? > What is the main difference between 3.8 kernel and 3.2 kernel? > > Thanks! > > > On Tuesday, November 12, 2013 9:45:37 AM UTC-5, RobertCNelson wrote: >> >> On Tue, Nov 12, 2013 at 8:37 AM, <[email protected]> wrote: >> > I have similar issue. I have (2) versions of BBB (A5A and A5C). They >> both >> > randomly reboot themselves while I am running TI prebuilt BBB android >> image >> > (from a couple hours to ten to fifteen hours). When I plug in the USB >> (DC is >> > still powered) for logging with logcat, the reboot issue seems to >> disappear. >> > >> > I don't have problem with BBB Angstrom image (based on 3.8 kernel). I >> don't >> > have problem with Andrew Henderson's android image (based on 3.8 >> kernel) >> > either. >> > >> > Another issue is that when I run TI BBB android image, the clock >> randomly >> > jumps forward 2^17 seconds. This happens on both of my BBB boards. The >> > problem goes away when I run Angstrom or Andrew's android. >> >> This time 'issue' was fixed in u-boot sometime last year, so I'm >> guessing the TI image has an un-patched u-boot.. >> >> > >> > I suspect it has something to do with the processor, DDR3 (BBB: AM3359 >> 1GHz >> > + 512MB DDR3), the configuration, or apply workaround of errata. We >> have an >> > AM335x EVM kit (AM3359 720MHz + 256MB DDR2). I also loaded TI prebuilt >> > android image. I have run it for several months. It is rock solid. I >> never >> > had problem with it. >> > >> > Here are the links to my other posts in regarding to this issue. >> > >> https://groups.google.com/forum/#!category-topic/beagleboard/advanced/5qSJ4dQdar4 >> >> > http://e2e.ti.com/support/embedded/android/f/509/t/297726.aspx >> > >> >> Regards, >> >> -- >> Robert Nelson >> http://www.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]. For more options, visit https://groups.google.com/groups/opt_out.
