[U-Boot-Users] u-boot debugging using gdb and BDI2000

[Wolfgang Denk]

In message <9CFB9DA5261CD611A29B00508B78904804E5945A at ex-deu-munich02.force.de> you wrote:
> 
> we recently purchased a BDI2000 to debug some of our products.
> I have u-boot-0.4.0 running on our board with a MPC8245. For
> a first test I connected the BDI2000 and at the telnet window a can
> see the u-boot code (md 0xfff00100) and can single-step through it.
> 1) general question:
> I removed DRAM etc initialization from the config. file because 

Good idea.

> it will be initialized from the u-boot code. Will it work that way or is
> DRAM
> access needed for proper work of BDI2000/gdb?

Yes, this is exactly what you should do. It will work that way.

> 2) Problem:
> Now I start the gdb and attach it to the BDI2000 
> ((gdb) target remote bdi:2001)
> After that I cannot see the code in flash anymore - md command in 
> telnet window returns all "0". Disassemble in gdb also returns all "0".
> What did I make wrong?

Which commands did  you  enter  at  the  GDB  prompt?  Is  there  any
".gdbinit" file in action? What does it contain?


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Thought for the day: What if there were no hypothetical situations?