I have recently been going through this same problem. I also have a working U-Boot so I didn't bother with any DRAM initialization in my BDI2000 config file but found I couldn't see my boot ROM code or get the target started properly from the BDI2000.

The key for me ended up being the MMAP command to get access to the boot ROM address range. For example

MMAP 0xFFF00000 0xFFF7FFFF

Once I had that I could see the U-Boot code again using 'md 0xfff00100' and start the target running using 'go'.

Hope this helps.

Carolyn

-----Original Message----- From: Demke, Torsten [mailto:Torsten.Demke@fci.com] Sent: Tuesday, July 01, 2003 10:06 AM To: U-Boot Mailing List (E-mail) Subject: [U-Boot-Users] u-boot debugging using gdb and BDI2000

Hallo all,

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 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? 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?

Thanks for your help. Torsten

---

This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061 203_01/01 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users