Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
sko:
If I connect my e250v2 to the computer the clock is set to Sep 23 2017 00:00 after disconnecting. If I set the right date/time it is correct until I connect it to the computer again. Is this the normal behavior until now?
saratoga:
--- Quote from: epithetless on March 01, 2009, 11:41:23 AM --- Does the progress that's been made so far with the Fuze also apply to the newer v2 Fuzes, or just the original (now v1) Fuzes?
--- End quote ---
Not much is known about the V2 hardware. If its based on the AS353X, then some of the V1 hardware is probably present, and also the mkamsboot code will likely work. However, until someone starts working on a port, I don't think we'll know for sure.
epithetless:
--- Quote from: saratoga on March 01, 2009, 03:18:06 PM ---Not much is known about the V2 hardware. If its based on the AS353X, then some of the V1 hardware is probably present, and also the mkamsboot code will likely work. However, until someone starts working on a port, I don't think we'll know for sure.
--- End quote ---
Thanks, saratoga. I suspected as much, but it's good to get confirmation on that front.
Hillshum:
--- Quote from: sko on March 01, 2009, 03:00:01 PM ---If I connect my e250v2 to the computer the clock is set to Sep 23 2017 00:00 after disconnecting. If I set the right date/time it is correct until I connect it to the computer again. Is this the normal behavior until now?
--- End quote ---
The OF and Rockbox fight for control of the RTC. The OF's "default" time is Sep 23....
I've been getting that too.
bertrik:
The RTC in the sansas is basically just a second counter. Earlier sansas keep the time in seconds since January 1st, 1980.
My theory is as follows:
in the e200v2 series the OF keeps the time in seconds since January 1st, 1970 (unix time) and has a check for invalid second values. One such check could be that the time is not before the build date of the firmware itself, which could be September 23rd, 2007. If the RTC is set to a date in 2009 in rockbox (using 1980 as second 0), the OF will interpret this as a date 10 years earlier, in 1999 (using 1970 as second 0). The OF concludes this is an invalid date because it is before the OF build date and sets the RTC to the OF build date, which is September 23, 2007. Back in Rockbox, this value of the RTC counter is interpreted as 10 years later which is 23 September 2017.
To test this theory, we should find out if the build date of the firmware is indeed around sept 23, 2007. It would be nice to know if earlier original firmwares reset the date to a different (earlier) date. Also try to find out if dates after sept 23, 2017 are not reset back to sept 23, 2017.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version