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
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).
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.
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.
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 【manual 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