• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1746 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Debug U-Boot with Code Composer Studio in Windows

Sean Moffatt
Intellectual 330 points

Hi,

I am attempting to debug U-Boot on the Beaglebone Black(AM335x) with CCS in Windows using the following tutorial as a guide and have encountered an issue.
processors.wiki.ti.com/.../Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5

My setup is using Virtual Box to host a Linux environment to access the Linux EZ SDK.

Host OS: Windows 7 64
Code Composer Studio Version in Windows : 6.0.1
XDS100v2 USB JTAG Emulator

Guest OS
Virtual Box: 4.3.20
Virttual OS: Ubuntu 12.04
TI Linux EZ SDK : 7.00.00.00 extracted to /home/sitara/ti-sdk-am335x-evm-07.00.00.00

First in the Linux environment I build U-Boot with the following steps.

cd /home/sitara/ti-sdk-am335x-evm-07.00.00.00/board-support/u-boot-2013.10-ti2013.12.01/
export PATH=$PATH:/home/sitara/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- distclean
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am335x_evm_config
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-

I copy the source to the Windows Host OS to C:\ti\u-boot-2013.10-ti2013.12.01

Then in CCS I create a project using the C/C++ Makefile Project with Existing Code for the U-Boot source.
Created a Target Configuration with connection set to Texas Instrument XDS100v2 USB Debug Probe, and the Board set to BeagleBone_Black and then launched the new Target Configuration.
Connected to CortxA8, then loaded the u-boot-spl.bin as Binary for the File Type to Start Address of 0x402F0400. Then Run->Load->Load Symbols.. to load u-boot-spl file.
At this point CCS indicates it cannot fin the file at "/home/sitara/ti-sdk-am335x-evm-07.00.00.00/board-support/u-boot-2013.10-ti2013.12.01/arch/arm/cpu/armv7/start.S", I click the Locate File.. button and select C:\ti\u-boot-2013.10-ti2013.12.01\arch\arm\cpu\armv7\ as the Source Folder.
I can now see the source for the start.S and I can set Hardware Breapoints in the start.S assembly code.

Now when I open the source file at C:\ti\u-boot-2013.10-ti2013.12.01\board\ti\am335x\board.c and attempt to set a Hardware Breakpoint in the am33x_spl_board_init function, they always end up disabled. No matter what source file I attempt to set breakpoints in they are always disabled.

If I select Resume, I can verify I halt on the breakpoints in the start.S code, but I cannot trigger any other breakpoints.

I have tried this same procedure within the Linux VM with CCS running and I can properly set breakpoints anywhere in the source however performance with the XDS100v2 emulator is too slow to be usable.

My questions is how do I associate the source file directory to the symbol file I loaded?

Thanks,
Sean

  • 0
    TI__Guru**** 393215 points

    Moving this to the CCS forum.

  • 0
    TI__Guru**** 450411 points

    Hi Sean,

    Sean Moffatt said:
    Now when I open the source file at C:\ti\u-boot-2013.10-ti2013.12.01\board\ti\am335x\board.c and attempt to set a Hardware Breakpoint in the am33x_spl_board_init function, they always end up disabled. No matter what source file I attempt to set breakpoints in they are always disabled.


    The debugger is unable to associate the copy of the source file you opened with the loaded program. How did you open the source? By double-clicking on it in the Project Explorer?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 330 points

    Hi Ki,

    Sorry for taking so long to reply I was away from work for a few weeks.

    While still in the CCS Debug view I when to File->Open File dialogue in an attempt to open the file.

    Thanks,

    Sean

  • 0 in reply to Sean Moffatt
    TI__Guru**** 450411 points
    Sean,
    It sounds like the source file you are opening is in a different location than the path the debugger has for the source file (it thinks it is a different file). Can you open the source file from the Modules view (View -> Modules)? You can browse the list of source files and double click on them to open it in the editor. If it cannot open it, then it does not have the correct source search path to bring it up.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 330 points

    Hi Ki,


    We have decided instead to use Linux as our Host OS for running Code Composer Studio to eliminate this issue.

    Thanks,

    Sean