- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi,
I am now using the CCSv5.5 with an EVM8168 board. I managed to debug the U-boot in EZSDK via CCSv5. By searching some related issues, I followed the steps in this online video
http://software-dl.ti.com/sdo/sdo_apps_public_sw/CCSv5/Demos/u-boot_debug_autonomous/u-boot_debug_autonomous.html
Sucessfully building the u-boot Linux command line(make u-boot), I copyed the whole folder into my Win7 and built up an make project, just as what the video shows.
However, when I tried to launch the debug session, the CCSv5 cast a error window like this:
And these logs are also printed on the CCS cmd window:
IcePick_D_0: GEL: File: G:\CCS_WorkSpace\u-boot-2010.06-psp04.04.00.01\u-boot Does not match the target endianness, not loaded. Check build options and target configuration file (ccxml).
I have no idea with this issue. I just want to load the symbols, which would help me debugging, into the DM8168.
Could you help me and give me some advices?
Naroah
Dec/25/2013
Hi lyer,
Thank you for your reply.
I have my issue solved. I have reset the project and redo the same procedure again. This time, I could load the symbols into the DM8168.
But I have another question, according to the video, the calling stack showed some functions and entries as soon as the ARM-CortexA8 core was halted:
However, the debug window in my CCS would not like to show the calling stack for me, even I have the program halted:
Could you give me some advices?
Naroah
Dec/25/2013
FYI: It seems a 700K uboot image should be loaded into the DM8168, while my image is merely about 290K
http://processors.wiki.ti.com/index.php/U-boot_Debug_in_CCSv5
