On 22 sep 2006, at 17.10, Dave Hylands wrote:
> IIRC, there has always been 2 sectors consumed. There was a time, =20
> where the code from u-boot occupied the first sector, and u-boot's =20
> environment was stored in the 2nd sector. However, the code portion =20=
> grew beyond 128K, so now the second sector includes code and =20
> environment. But when you do a saveenv in u-boot, it takes care of =20
> rewriting things properly.
So I found out, but glad that you could confirm.
> I'm not sure if the above is what you're looking for or not. If it =20
> isn't, perhaps you could rephrase?
Sure thing. It turnes out (and I'm actually not that surprised) that =20
my boss (ohh no - not him again!!! ;) told me that I should bother =20
with the 400MHz setting in the target area of buildroot. But, and let =20=
you or someone else confirm/deny this, a boot monitor is dependant on =20=
the cpu frequency when it comes to timers, counters etc. So almost =20
everything worked with 1.1.4 a part from the FLASH business.
But I managed to save that by downloading a new u-boot (1.1.4) with =20
correct cpu frequency setting (200 MHz) to $a2000000 and instantly =20
transfered control to this code which made it possible to write a =20
entirely correct built u-boot into the FLASH. Happy ending.
Tutus Data AB Phone: +46-8-70-995 98 99
Sv=E4rdv=E4gen 11 Fax: +46-8-551 102 39
SE-182 33 DANDERYD