Skip to contentSkip to conversation

debug u-boot with BDI2000

U-Boot-Users Hinko Kocevar 4 participants 5 messages Feb 2, 2005

lore
Share & tools
lore
#0 lore raw

Hi,

After solving early problem with target reset (cable fault) I'm ready to do some real work!
I order to debug u-boot startup and so on, do I have to enable/provide some additional options when compiling u-boot for my target?

I've read the Debugging section in dulg manual, but it doesn't mention anything like that - Just to make sure...

regards,
hk

Signature · 5 lines
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]
#1 lore raw
Quoted 7 lines · Hinko Kocevar

Hi,

After solving early problem with target reset (cable fault) I'm ready to do some real work!
I order to debug u-boot startup and so on, do I have to enable/provide some additional options when compiling u-boot for my target?

Quoted 5 lines

I've read the Debugging section in dulg manual, but it doesn't mention anything like that - Just to make sure...

regards,
hk

Just the standard ones for debugging: -g for symbolic support.

You may want to use -O0 to turn off optimization. The linux kernel won't link when compiled with -O0 because the expected inlining doesn't happen (symptom: linking gives missing symbols) -- I don't recall if u-boot has that limitation too.

gvb

#2 lore raw
Quoted 1 line · Jerry Van Baren

Just the standard ones for debugging: -g for symbolic support.

You also have to be careful of processor initialization code that initializes debug control registers. Proper processor set up requires you do this, but of course the BDI2000 is also trying to use these registers to assist with the debug process. You may have to disable this debug register initialization in the code, depending upon the processor, or find some other way of working around this.

	-- Dan
#3 lore raw
Quoted 8 lines · Dan Malek

You also have to be careful of processor initialization code that initializes debug control registers. Proper processor set up requires you do this, but of course the BDI2000 is also trying to use these registers to assist with the debug process. You may have to disable this debug register initialization in the code, depending upon the processor, or find some other way of working around this.

Hmm, I'm using intel pxa255 A0 processor here. BDI2000 came with some setup files for this processor. I'll check out that stuff, thanks for the tip.

regards,
hk

Signature · 5 lines
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]
#4 lore raw
In reply to Jerry Van Baren
Quoted 2 lines · In message <[email protected]> you wrote:

Just the standard ones for debugging: -g for symbolic support.

This is default for U-Boot, so no change needed.

Quoted 1 line

You may want to use -O0 to turn off optimization. The linux kernel

We never do this. You get used to see what the optimizer is doing - and actually this my be very important to know. We've been hunting a couple of problems (like missing "volatile" atributes) when switching from older versions of GCC to GCC-3.3 - turning off -O0 ould have made this impossible.

Best regards,

Wolfgang Denk

Signature · 4 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Actual war is a very messy business. Very, very messy business.
	-- Kirk, "A Taste of Armageddon", stardate 3193.0