From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Caudle <stephen@doceme.com>
Date: Thu, 27 Aug 2009 21:57:25 -0400
Subject: [U-Boot] RTC value corruption on QIL-A9G20 startup
In-Reply-To: <657FC3AB549C7F4DB01F4397232ED733643383734D@Exchange2007.techatl.com>
References: <c2b149fd0908241901u50208fahb987b2c8349d182d@mail.gmail.com>
	<20090825083729.GA10327@pc-ras4041.res.insa>
	<4A93B0F8.80409@eukrea.com>
	<c2b149fd0908250551t1cead6c7sb95a6d1ff2e2656b@mail.gmail.com>
	<20090825164845.GF10327@pc-ras4041.res.insa>
	<657FC3AB549C7F4DB01F4397232ED733643383734D@Exchange2007.techatl.com>
Message-ID: <c2b149fd0908271857p429511fet4a095c83f7f74ea7@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Thu, Aug 27, 2009 at 1:48 PM, William C. Landolina<wcl@techatl.com> wrote:
> 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...]

No resolution here.  I am still seeing the problem (even on the next
branch).  This definitely seems to be caused by the processor boot
ROM.

> 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?

I believe a hardware change is the only way to fix this problem.

Regards,
Stephen