[U-Boot] RTC value corruption on QIL-A9G20 startup

[William C. Landolina <wcl@techatl.com>]

> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Albin Tonnerre
> Sent: Tuesday, August 25, 2009 12:49 PM
> To: u-boot at lists.denx.de
> Subject: Re: [U-Boot] RTC value corruption on QIL-A9G20 startup
>
> On Tue, Aug 25, 2009 at 08:51:56AM -0400, Stephen Caudle wrote :
> > Hello Eric,
> > 
> > On Tue, Aug 25, 2009 at 5:38 AM, Eric B?nard<eric@eukrea.com> wrote:
> > > isn't the RTC connected to the SPI chip select that the internal 
> > > firmware toggle on boot to probe for a SPI Flash ?
> > 
> > That is certainly possible.  This problem went away for me when I >
> > upgraded to the "next" branch.  Could the SPI dataflash code have been 
> > removed between
> > v2009.06 and "next"?  I'll look into this some more.  Thanks for the hint!
>
> Using the "next" branch doesn't help here. Anyway, the code Eric is referring to is the firmware code the CPU > executes from its internal ROM very early in the boot process, so you likely won't find anything remotely related to > this in U-Boot.
>
> Regards,
> --
> Albin Tonnerre, Free Electrons
> Kernel, drivers and embedded Linux development, consulting, training and support.
> http://free-electrons.com

Has there been any resolution on this?  From what I can see (with scope and logic analyzer) the RTC seems to be corrupted by the DataFlash boot code built into the chip.  [The Calao board doesn't have the DataFlash memory and used the chip select for its RTC instead...]

Has anyone found a smoking gun inside U-Boot or will we have to wait for Calao to make boards with the RTC on a different chip select?

Thanks,
Bill Landolina
Technology Atlanta Corporation
500 Sugar Mill Road, Suite 202A
Atlanta, GA 30350

(404) 303-0446 (Voice)
(404) 303-0448 (FAX)
(678) 596-3625 (Cell)
wcl at techatl.com