Damien, Check the link on TI e2e: http://e2e.ti.com/support/embedded/android/f/509/t/308616.aspx It basically switched the clock source from 32K to 24MHz clock. It eventually fixed my time jump problem. Good luck!
On Tuesday, February 25, 2014 10:34:38 PM UTC-5, Damien wrote: > > Strange ... I checked the commit and found it had been included within the > v2013.04 uboot release .. but my BB board is still experienced with this > time jump issue one/two times per day. Could there be anything else? > Regards. > Damien > > > > On Monday, February 24, 2014 3:23:46 PM UTC+11, RobertCNelson wrote: >> >> Probably.. >> http://git.denx.de/?p=u-boot.git;a=commit;h=000820b5835c2b8b863af992b66dc973dc4bd202 >> On Feb 23, 2014 10:19 PM, "Damien" <[email protected]> wrote: >> >>> Hi Robert, >>> Do you know more detail about the time jump issue in uboot? for example, >>> fix commit number, or some words used for the commit? >>> I am interested to find out what exactly the fixes are, but there are >>> too many commits in uboot and I need some thing to search with. >>> >>> Regards, >>> Damien >>> >>> >>> On Wednesday, November 13, 2013 1:45:37 AM UTC+11, 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. >>> >> -- 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.
