Hello list,
inside the automatic U-Boot patch tracking system a new ticket [DNX#2006040142000704] was created:
<snip>
Wolfgang.
That is very convincing. So for the special case of setting RCW to boot
from lowmem vector, all is well. And I guess there is no great harm in that restriction.
When RCW set to boot from himem vector though, the 83xx maps in the _last_ 8M of the flash chip, not the first, so the remap_flash_by_law* routines end up mapping u-boot out from under us. But OK; we just won't
do that then.
I still stand by by compaint though: if you're going to remap flash according to CFG_FLASH_BASE in start.S, then the 8M hardcoded size is annoying.
back to LAW0 on a builtin assumption of 8M size, placing the starting address thereof to the CFG_FLASH_BASE location (in their case, 0xfe00_0000); then do jumping arithmetic based on that value and TEXT_BASE.
Which works in the Freescale-ADS case, as they have an 8M flash chip.
It also works in case of the TQM8349 board, which uses 32 MB:
U-Boot 1.1.4 (Nov 17 2005 - 00:14:36) MPC83XX
Clock configuration: Coherent System Bus: 266 MHz Core: 533 MHz Local Bus: 33 MHz CPU: MPC83xx, Rev: 1.1 at 533.328 MHz Board: TQM834x PCI1: 32 bit, 33 MHz I2C: ready DTT: 1 is 28 C DRAM: 256 MB FLASH: 32 MB PCI: Bus Dev VenId DevId Class Int In: serial Out: serial Err: serial Net: TSEC0, TSEC1
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 0 => fli
Bank # 1: CFI conformant FLASH (32 x 16) Size: 32 MB in 256 Sectors Erase timeout 16384 ms, write timeout 0 ms, buffer write timeout 4096 ms, buffer size 32 Sector Start Addresses: 80000000 (RO) 80020000 (RO) 80040000 (RO) 80060000 80080000 800A0000 800C0000 800E0000 80100000 80120000 80140000 80160000 80180000 801A0000 801C0000 ...
Best regards,
Wolfgang Denk
</snip>
Your U-Boot support team