[U-Boot] Debugging u-boot with bdi3000 basics

[Wolfgang Denk <wd@denx.de>]

Dear Mark Fanara,

In message <AANLkTinA8O1OtqI93hyazU2UDG4QbZzRkt3ql3iP9hCN@mail.gmail.com> you wrote:
> As my target board is PowerPC based (and therefore skipping relocation
> is not possible), I need help with my previously enumerated questions.
> 
> 1) In section 10.4, Tips and Tricks, it says "To prevent GDB from
> jumping around in the code when trying to single step, i. e. when it
> seems as if the code is not executing line by line, you can recompile
> your code with the following additional compiler options:
> "-fno-schedule-insns -fno-schedule-insns"
> 
> In the u-boot developer world, what is the best practice for adding
> these compiler options? I see CFLAGS in config.mk and assume that is
> what needs to be modified. However, I need a HOWTODOITRIGHT

There is many ways to do this. You may or mayu not want to compile all
files with this option, so you may add it to the glocal CFLAGS, or
just locally in a subdirectory, or manually provide it on the command
line, or ....

Ther eis no single "right" way.

> 3) The function board_init_f() in board.c makes calls to debug(). I
> cannot determine how to enable debug() output. I saw one reference in
> the manual, but it gave no specifics.

You just "#define DEBUG" before the first #include in that file.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Men will always be men -- no matter where they are.
	-- Harry Mudd, "Mudd's Women", stardate 1329.8