• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 1004 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to debug U-boot on EVM8168 using CCSv5 for windows

Alessandro Schembri
Prodigy 170 points
We are developing a new card with Integra TMS320CA8168. We have also the EVM8168 with ti-ezsdk_c6a816x-evm_5_00_00_56 environment. I made some changes for u-boot and I was able to generate the u-boot image on ubuntu 10.04. Now I'd like to debug this new image using CCSv5 for windows because the linux version doesn't support the BH-USB-560M jtag. What is the best procedure to create CCSv5 project starting from the u-boot makefile? Before to debug the new card I'd like to debug u-boot on the evalution board. Thanks in advance
  • 0
    TI__Guru**** 171779 points

    Hi,

    In order to perform debugging in any makefile-based project (including linux kernel and u-boot), CCSv5 has the concept of Standard Makefile (or Unmanaged) project, a specific type of project that simply requires an existing Makefile and all required source/include files in the same directory structure. It differs from the traditional CCS (Managed) project as it only allows control of the parameters passed to the make (or gmake) tool - all compiler and linker parameters are entirely contained in the Makefile.

    Therefore, to debug the u-boot source code in a Windows machine you will need access to the u-boot source directory (typically via samba share) and the u-boot binary with debug symbols (file <u-boot> if I am not mistaken). You will also have to create a Standard Makefile project to allow CCS to properly correlate the memory address in the target with the correct source code in the u-boot tree.

    The process of creating a standard make project and loading the symbols is very similar to performing Linux kernel debug. Check the section Stop Mode debug of the following page:

    http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5

    Hope this helps,

    Rafael