CCS/AM5726: Debugging U-boot from CCS

The page you are referring to is for Linux (which is good, I'll want to try that next).
What I am looking right now is debugging u-boot.

Is their an updated wiki for u-boot as well (I searched but couldn't find it)?

Regards,
- David

Hi,

I have a same problem(no symbols defined for 0xFF77???).

David, Let's me know how did you solve this problem.

Thanks.

Best Regards,

TS Lee.

Hi, 

Here are the steps we use internally to debug u-boot using Code Composer:

These 2 links are very useful in getting u-boot debugging to work on the Sitara processor:

• processors.wiki.ti.com/.../Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5
• processors.wiki.ti.com/.../U-boot_Debug_in_CCSv5

Explains how you can debug u-boot using code composer. This video (software-dl.ti.com/.../u-boot_debug_autonomous.html) is a must see before doing anything.

Here is a summary of the steps required to debug u-boot in CCS:

• Create a CCS project with the u-boot sources
  The project must be a C/C++ makefile project with existing sources
  
  
• Create a new Debug launch configuration
  Type must be 'Code Composer Studio - Device Debug'
  
  
• Select a Target Configuration for your device
  
  
• De-select cores that won't be used in the debug session
  In our case, only keep the ARM-A15
  
  
• Give a proper name to the debug configuration
  For example: AM57xx_u-boot
  
  
• Move to the program tab
  
  
• Select the device
  Should be 'Texas Instruments XDS2xx USB Debug Probe_0/CortexA15_0
  
  
• Select the u-boot project
  
  
• Select the u-boot image containing all the symbols
  Normally, this file is called `u-boot` without any extension.
  
  
• Select load symbols only
  
  
• Click apply
  
  
• Disable project build option
  Go in the project reference and select `C/C++ build`in the left menu. Click on the behavior tab and un-scheck `Stop on first build error`, `Build` and `Clean`
  
  
• Boot the sitara board and stop the auto-boot process
  
  
• run bdinfo on the u-boot prompt and remem
  => bdinfo
  ```
  arch_number = 0x00000000
  boot_params = 0x80000100
  DRAM bank = 0x00000000
  -> start = 0x80000000
  -> size = 0x80000000
  DRAM bank = 0x00000001
  -> start = 0x00000000
  -> size = 0x00000000
  eth0name = cpsw
  ethaddr = a4:d5:78:c4:f9:12
  current eth = cpsw
  ip_addr = <NULL>
  baudrate = 115200 bps
  TLB addr = 0xFFFF0000
  relocaddr = 0xFFF5C000
  reloc off = 0x7F75C000
  irq_sp = 0xFEF4BEE0
  sp start = 0xFEF4BED0
  ```
• Start the debug session
  
  
• Load program symbols with data offset and code offset set to relocaddr
  
  
• You should now see a full back trace in code composer! You can create breakpoints now as well. Note that you need to set hardware breakpoints.

Hope this helps!

- David

Hi, David.

"relocaddr" is the key!

It's work. 

Thanks a lot.

Best Regards,

TS Lee.