The best solution to this problem is (if locally connected) Install Local NTP server and put "service ntp restart" in an infinite loop with sleep time 30 seconds approx. by writing a code in "/etc/init.d/rc.local" file. Reboot system and time will be synchronized with the server computer.
On Tuesday, December 11, 2012 at 12:27:06 PM UTC+1 Džiugas Baltrūnas wrote: > Sorry, I haven't noticed the patch was for u-boot and thanks for pointing > this out. > > I've retested the initial clock selection using u-boot from arago-project > (so with the mentioned patch in place) and I can confirm that the clock > source is always 32 MHz no matter how the board was booted: > > # grep -i clock /var/log/dmesg > [ 0.000000] OMAP clockevent source: GPTIMER2 at 24000000 Hz > [ 0.000000] OMAP clocksource: GPTIMER1 at 32768 Hz > [ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps > every 131071999ms > [ 0.141113] PTP clock support registered > [ 0.143066] Switching to clocksource gp timer > [ 1.395019] clock: disabling unused clocks to save power > [ 1.414581] omap_rtc am33xx-rtc: setting system clock to 2000-01-01 > 00:00:00 UTC (946684800) > > So I'm wondering to know whether the consistence of the initial > clocksource will solve the original problem of the system clock start > ticking to fast, i.e. what are the conditions for system clock not to > change while the system is running? > > Džiugas > > On 10 December 2012 18:36, Robert Nelson <[email protected]> wrote: > >> On Mon, Dec 10, 2012 at 11:25 AM, Džiugas Baltrūnas <[email protected]> >> wrote: >> > Hello, >> > >> > Thanks for the feedback. Indeed, none of the 3.2.x kernels from Robert >> > Nelson's tree >> > (https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2/patches) >> do have >> > the patch you've pointed (it does not even contain arch/arm/cpu/armv7 >> > folder). >> >> Well, Vaibhav's patch does not touch the kernel tree.. It's for the >> bootloader (u-boot), it also happens to be included in the u-boot >> "v2013.01-rc1" release.. >> >> So... If (and only if) you are running my demo images, look at: >> >> /boot/uboot/tools >> >> is there an "update.sh" file? >> if so run "sudo ./update.sh" then.. >> >> sudo ./bootloader_update.sh --use-beta-bootloader >> >> Regards, >> > >> -- >> Robert Nelson >> http://www.rcn-ee.com/ >> >> -- >> For more options, visit http://beagleboard.org/discuss >> >> >> > -- 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/2d8e375d-0ee7-4718-9122-5fdd8d4a1580n%40googlegroups.com.
