topic Re: CW & u-boot debug in CodeWarrior for QorIQ

CW & u-boot debug

Igor — Wed, 30 Apr 2008 16:17:26 GMT

Hi all,
I have installed CW Dev Studio (Power architecture, Professional edition & Linux Application edition, v8.8, Build 70921) on a WinXp based computer. Secondly, on a Fedora core based host computer, I have cross compiled u-boot 1.1.6 for mpc8313rdb board (toolchain gcc-4.0.2+e30c3/glibc-2.3.6).

The issue is that I want to debug u-boot using CW (and USB TAP) but breakpoints "do not work".

This is what I've done:
Within CW, I have done a "File | Open" on the u-boot elf image.
CW has created a project for that elf file (it has not found libgcc2.c file so it gives me a "warning" message).
Once the project is created I have set the target CPU type in the EPPC Debugger Settings panel and a register init file (8313RDB_uboot_init_Linux.cfg).

Any Advice? Do I have to compile u-boot in a particular manner?
Thanks a lot in advance,

Igor

Re: CW & u-boot debug

J2MEJediMaster — Thu, 01 May 2008 21:22:50 GMT

Consult the Pro & Linux App Edtion Targeting Manual in CodeWarrior's Hlpe directory. In ths manual's Working with the Debugger chapter, locate the section, Debugging the U-boot Bootstrap Firmware, and follow its directions. It describes in detail what you must do to build the U-boot code and download it. HTH,

---Tom

Re: CW & u-boot debug

huangxianguo — Wed, 25 Mar 2009 17:06:15 GMT

I encounted the same issue-- lack of libgcc2 and breakpoint unreachable, and don't know how to resolve. i have operated with the instructor step by step, but that's useless still. lgor, whether you have resolved this issue? can you give me some tutorial?

Re: CW & u-boot debug

Igor — Wed, 25 Mar 2009 17:58:22 GMT

Some time has passed...Sorry but the only thing I remember is that I religiously followed the document's procedure.

Igor

Re: CW & u-boot debug

AshishAgarwal — Wed, 01 Apr 2009 08:00:01 GMT

I am using MPC8536DS Evaluation environment.

nowhow i was able to get working configuration [JTAG] file for the 8536.

i too facing same problem.

when i compile the u-Boot over ltib tool as described in "Pro & Linux App Edition Targeting Manual.pdf" => Debugging the U-Boot Bootstrap Firmware

step by step following of guide still not working for me

1 point i am not sure about is 【manuaｌ Note】

"NOTE If you are using an LTIB BSP, you may need to change the optimization flag of
the U-Boot CFLAGS argument in this file: install/ltib/config/platform/boardName/.config file."

what i have to set there and with which flag?

i.e there is Flag named as

CONFIG_TOOLCHAIN_CFLAGS=""

becuase this is a auto genereted file from ltib config tool, so i changed this from that tool as "-O2"

is it wrong anywhere or i loosing something @?@;

here what i have to do otherwise?

please help me out if anybody resolved this issue anyhow. :

u-Boot code compiled successfully but when i tried to open elf file in the C, it is giving me warning about "libgcc2.c" file not found.

The command i am using for compiling is

./ltib -m scbuild -p u-boot-1.3.4-mpc8536ds.spec

is it Okie ?

libgcc2.c file does not exists or it may not be genereted.

---

Ashish Agarwal

"There's no ceiling on effort!"

Re: CW & u-boot debug

huangxianguo — Fri, 03 Apr 2009 17:07:20 GMT

Fortunately, i have known how to debug.

If you

1.want to stop at FLASH breakpoint:

a. check the option "use Target Initilization File", and locate the file"Program Files/Freescale/CodeWarrior PA V8.8/PowerPC_EABI_Support/Initialization_Files/PQ2/83xxRDB_init_debug_uboot.cfg"

b. non-check the option "Alternate Load Address"

2.want to stop at RAM breakpoint:

a. non-check the option "use Target Initilization File"

b. check "Alternate Load Address" in terms of the section: " Debugging the U-Boot Bootstrap Firmware" in the document"/Program Files/Freescale/CodeWarrior PA V8.8/Help/Pro_&_Linux_App_Edition_Targeting_Manual.chm

c. set Hardware Breakpoint

other settings follow the .chm file in step.

Re: CW & u-boot debug

AshishAgarwal — Tue, 07 Apr 2009 12:12:28 GMT

Hello huangxianguo

Thanks for your kind reply. it true what you commented, is steps for the debuging of U-boot.

But here i mentioned that i want to debug the MPC8536DS version u-Boot 1.3.4.

and indeed i did the debugging of MPC8544 successsfully before the procedure written abov. but in my case right now i am not able to get rid from "libgcc2.c"file missin.

it is the case when we open ****.elf file. i made sure about the process written there in mannual.

what i am looking is if there is any FLAG setting in the Makefile i am missing that generates "libgcc2.c" file warning. that stops me to halt at breakpoints.

Re: CW & u-boot debug

huangxianguo — Wed, 22 Apr 2009 09:25:55 GMT

I think the libgcc2.c is not neccessary if you have compiled the u-boot. you can skip it. you can find it at the libc source.

Re: CW & u-boot debug

AshishAgarwal — Tue, 12 May 2009 07:16:34 GMT

I receive an answer regarding my Servie request to Freescale is like below.

uboot debugging
------------------
This is not supported for 8536 yet. It will not be supported until the June 22 release (CW EPPC 8.8.3).

Got stuck with in development cycle.

but now one thing we can do is insert printf statements in the u-boot source to debug it..

i know it is hard to compile source every time and write it to the Flash but it is the only way i am doing

if you know any other bright way to do the same ..

v- -v suggest me

Re: CW & u-boot debug

AshishAgarwal — Mon, 18 May 2009 11:50:10 GMT

Freescale support comments :

uboot debugging

----------------

This is not supported for 8536 yet. It will not be supported until the 2009, June 22 release (CW EPPC 8.8.3).