On Tue, 13 Mar 2001, David Beckemeyer wrote:
Hi David, hi all. We've been watching the messages about images over 1Meg
and broken EnVars. We have tracked the problem down to an error made
copying the FLASH sector map for (specifically) the AT49BV1614 1Mx16 FLASH
part from the datasheet. The uCbootstrap is designed to use almost any
AMD compatible FLASH, and not all are CFI compliant so we need to store
the sector map.
For those interested, the error can be seen in the sector map printed on
bootup... The sector map contains an offset of 1Mb for the end of the
last sector, _not_ 2Mb. The values in the AT49BV1614 table were copied
from the Word address table, the code expects Byte addresses.
We'll announce a proceedure to fix this problem by tomorrow morning. We
regret any inconvienence this has caused.
Q. How do I know if I am affected?
A. If your uCsimm or uCdimm has an Atmel FLASH device and the uCbootstrap
Copyright starts with "uCbootstrap v1.04 ..." your module is affected. If
you have AMD, Toshiba or SST FLASH you are not affected.
Q. I tried to FLASH an image larger than 1M. Is my module OK?
A. Yes, the code simply determined that it would write past the end of the
available FLASH sectors and aborted.
Q. I tried to set an Environment Variable. Is my module OK?
A. The hardware is OK. Some corruption of the FLASH contents is likely to
Q. How can I use EnVars or images which cross the 1Mb boundary?
A. You need a bootloader with the bugfix applied. We will send another
mail Wednesday, March 14 2001 with instructions on how to proceed.
D. Jeff Dionne.
> > b) In the other hand, when I try to set the AUTOBOOT environment variable:
> > uCbootstrap v1.04 Copyright (c) 2000 Lineo, Inc.
> > Copyright (c) 1999-2000 Rt-Control Inc.
> > All Rights Reserved.
> > AUTOBOOT not "yes" or greater than 0. Ignored
> > FLASH type 00c0 [AT49BV1614]
> > DP|001000 DP|002000 DP|003000 DP|004000 DP|005000 DP|006000
> > DP|007000 DP|008000 DP|00c000 D-|010000 D-|018000 D-|020000
> > D-|028000 D-|030000 D-|038000 D-|040000 D-|048000 D-|050000
> > D-|058000 D-|060000 D-|068000 D-|070000 D-|078000 D-|080000
> > D-|088000 D-|090000 D-|098000 D-|0a0000 D-|0a8000 D-|0b0000
> > D-|0b8000 D-|0c0000 D-|0c8000 D-|0d0000 D-|0d8000 D-|0e0000
> > D-|0e8000 D-|0f0000 D-|0f8000 D-|100000
> > B$ setenv AUTOBOOT 3
> > .......B$ printenv
> > FACTORY=uCsimm (c) 2001 Lineo Canada Corp
> > REVISION=uCsimm Rev 3.3
> > HWADDR0=00:50:C2:03:6a:c5
> > SERIAL=980437319-01ac5
> > CONSOLE=ttyS0
> > AUTOBOOT=
> > B$
> > The AUTOBOOT variable is NOT set to 3 (or any number!!)
> I'm seeing the same thing with the uCsimm modules I just received
> which have the same uCbootstrap v1.04 and FLASH type 00c0 [AT49BV1614]
> If the bootloader can't set the variables, it's a pretty good guess
> that flashing images won't work. It seems like there must be a problem
> with this rev of uCsimms.
> I still have a number of older uCsimm modules that work fine, so I
> can get by for a while, but I hope Lineo gets a fix for this soon,
> before I run out of the older uCsimms.
> This message resent by the email@example.com list server http://www.uClinux.com/
This message resent by the firstname.lastname@example.org list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:42 EST