In message BAY118-W5099133B24D94DCAAA6BEFCFC40@phx.gbl you wrote:
The BDI config file for the Yosemite board on the U-Boot manual doesn't wor k (I can't erase the full range of flash between 0xFC000000 to 0xFFFFFFFF), so I've been using the one provided by AMCC.
I doubt that. The examples in the manual are generated automatically (by running DUTS); it seems to have worked by then.
BTW: Please rstrict your line length to some 70 characters or so.
When I do a reset halt, the PC does get set to 0xFFFFFFFC (please see below ). But GDB still goes straight to 0x00000000.
The BDI config file from the U-Boot manual only allocates 2MB of flash (the re are 64MBs on this board). If I use this config file, the GDB goes to 0xd eadbeef (but the BDI telnet shows the correct 0xFFFFFFFC for the PC after a reset-halt).
I don't understand what the flash mapping has to do with the operation of GDB? As long as all of the U-Boot image is mapped, everything should be fine. Also, I think the provided config file does map 4 MB at 0xFFC00000, doesn't it?
Probably your BDI config file needs adjusting. Try what you see when you use the telnet interface directly, i. e. where do you end up after a "reset halt" ?
Best regards,
...
Please don't top-post / full-quote!
--_a74128a5-4aff-492d-8a22-57e20feb9b73_ Content-Type: text/html; charsetÿindows-1252" Content-Transfer-Encoding: quoted-printable
And please do NOT post HTML here.
Best regards,
Wolfgang Denk