Skip to contentSkip to conversation

Debugging U-Boot with BDI2000

U-Boot-Users Glenson Muthedan 3 participants 3 messages Sep 11, 2003

lore
Share & tools
lore
#0 lore raw

Hello!

I'm quite new to U-Boot and trying to get started with the Bootloader-Stuff for some weeks now. My Board is similar to Accelent IDP or CSB226(PXA250 with 32 MB Strataflash and 32 MB SDRAM). U-Boot seems to crash on my board before it can output something through the serial line. So I wanted step through U-Boot right from the very first instruction using BDI2000 while booting. The problem is that the information the bdi user manual gives, is quite confusing. I tried out various configurations for BDI2000, but really don't know what to do with the vector table in the "Mini IC" and the debug handler stuff. The situation now is as following: The target is in debug mode right from the start and the PC is pointing to 0xffff0004. "go" or "ti" doesn't work because of access to an invalid memory address. (My configuration file now contains a blank [INIT] section and no vector table/debug handler stuff in the [TARGET] part)

I'd be very thankful if someone could answer my questions:

1) Is it possible to debug U-Boot with BDI2000 (Linux host) at all? (eg. step through the instructions)

2) Do somebody have a working configuration file for BDI2000 (Linux host) to be used with a PXA250-target?

Hope, you can give me at least a hint.

Regards,
Glenson Muthedan.

#1 lore raw
Quoted 3 lines · In message <[email protected]> you wrote:

1) Is it possible to debug U-Boot with BDI2000 (Linux host) at all? (eg. step through the instructions)

Yes, of course!!!

Quoted 2 lines

2) Do somebody have a working configuration file for BDI2000 (Linux host) to be used with a PXA250-target?

Configuration files for some targets are included with the BDI2000 firmware - see the floppy disk, or the .zip file you received with the device.

But a configuration file for _some_ PXA250 board is only an EXAMPLE, you cannot use it unchanged on different hardware. You must create a
NEW configuration file which matches exactly the hardware as
implemented on your board.

This is not a trivial task, but the knowledge you need to do this is necessary to successfully port and debug U-Boot anyway.

Best regards,

Wolfgang Denk

Signature · 5 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
If programming was easy, they wouldn't need something as  complicated
as a human being to do it, now would they?
                       - L. Wall & R. L. Schwartz, _Programming Perl_
#2 lore raw
In reply to Glenson Muthedan
Quoted 3 lines · Glenson Muthedan

I'm quite new to U-Boot and trying to get started with the Bootloader-Stuff for some weeks now. My Board is similar to Accelent IDP or CSB226(PXA250 with 32 MB Strataflash and 32 MB SDRAM).

Did you try using U-Boot + one of my -ptx patches? Should work better on PXA than vanilla because of the memory layout problems.

Quoted 6 lines

U-Boot seems to crash on my board before it can output something through the serial line. So I wanted step through U-Boot right from the very first instruction using BDI2000 while booting. The problem is that the information the bdi user manual gives, is quite confusing. I tried out various configurations for BDI2000, but really don't know what to do with the vector table in the "Mini IC" and the debug handler stuff.

I currently use this one:

[TARGET]

CPUTYPE         PXA250          ; the target CPU type
JTAGCLOCK       1               ; use 8 MHz JTAG clock
DBGHANDLER      0xFE000800      ; 
ENDIAN          LITTLE          ; memory model (LITTLE | BIG)
BREAKMODE       HARD            ; SOFT or HARD; HARD does only allow two
                                ; breakpoints, but does work on flash
;VECTOR         CATCH 0xDE      ; trap all vectors
;VTABLO         0xE59FF014      ; Use fixed vectors "ldr pc, [pc, #14]"
Quoted 5 lines

The situation now is as following: The target is in debug mode right from the start and the PC is pointing to 0xffff0004. "go" or "ti" doesn't work because of access to an invalid memory address. (My configuration file now contains a blank [INIT] section and no vector table/debug handler stuff in the [TARGET] part)

I started with the Lubbock config which came with the BDI and it worked quite fine.

Quoted 2 lines

1) Is it possible to debug U-Boot with BDI2000 (Linux host) at all? (eg. step through the instructions)

Yes, works perfectly.

Quoted 2 lines

2) Do somebody have a working configuration file for BDI2000 (Linux host) to be used with a PXA250-target?

I send you my CSB config with separate mail.

Robert

Signature · 5 lines
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hornemannstra?e 12,  31137 Hildesheim, Germany
    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4