[U-Boot-Users] Debug with Abatron BDI2000 on 405EP evaluation board

[llandre]

>Dear llandre,
>
>in message <5.1.1.6.0.20030310192644.02f86d88 at dns.struinfo.it> you wrote:
> >
> > I have a couple questions about it:
> > 1) The BDI2000 is shipped with a script file for the 405GP evaluation 
> board
> > (evb405gp.cfg) that is is very similar to 405EP board. In the [INIT]
> > section, several initializations are performed in order to debug
> > application code in SDRAM. Since the boot loader is executed out of reset,
> > to debug U-Boot from the SRAM, I think these initializations must be
> > removed. In other words the [INIT] section must be empty, because U-Boot
> > itself will initialize the microcontroller. Is it correct?
>
>This is correct. The [INIT] section should contain only  the  minimum
>of  necessary  initializations,  like turning off any hardware watch-
>dogs, etc. SDRAM initialization should be removed, so tha the  U-Boot
>code finds a virgin system, as it does without the BDI2000 attached.
>
>
> > 2) In the bdiGDB User Manual they say to load the application code with 
> the
> > LOAD command in the [HOST] section of the script file. Is it equivalent to
> > use the load command from GDB shell?
>
>Since you don;t initialize the SDRAM, you will normally have  to  use
>the  "prog"  command  to  program  the  U-Boot image to flash. Do you
>really have SRAM connected as boot device?

Yes. The default configuration is:
Flash: 0xFFF8:0000 - 0xFFFF:FFFF
SRAM:  0xFFF0:0000 - 0xFFF7:FFFF
but there is a switch that exchanges the address spaces of the two memories 
in order to debug easily the boot code:
Flash: 0xFFF0:0000 - 0xFFF7:FFFF
SRAM:  0xFFF8:0000 - 0xFFFF:FFFF.





llandre