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.

AM263P4: How to use GDB server and client on command line?

Part Number: AM263P4
Other Parts Discussed in Thread: TMDSCNCD263P

Tool/software:

We are using a 3rd party IDE and I'm trying to set up the debug environment for AM263P4 SoC.

Is there a GDB server and client I can run from windows shell to debug the SoC?  Also if there are documentation or examples using XDS110 probe, that would be very helpful.

I found documentation regarding XDS GDB Agent, but it looks like it is end of life.

Also found documentation saying I can find GDB in CGT folder.  But there was none for ti-cgt-armllvm_4.0.1.LTS


/mnt/c/ti/ccs1281/ccs/tools/compiler/ti-cgt-armllvm_4.0.1.LTS/bin$ ls
generate_syms.js tiarmasm.exe tiarmclang.exe tiarmdem.exe tiarmhex.exe tiarmlnk.exe tiarmobjcopy.exe tiarmofd.exe tiarmreadelf.exe tiarmstrip.exe
tiarmar.exe tiarmclang-tidy.exe tiarmcov.exe tiarmdis.exe tiarmlibinfo.exe tiarmnm.exe tiarmobjdump.exe tiarmprofdata.exe tiarmsize.exe

What GDB server and client does CCS 12.8 use for AM263P4?

Thanks

  • Hello,

    Is there a GDB server and client I can run from windows shell to debug the SoC?

    OpenOCD is an option: https://openocd.org/

    What GDB server and client does CCS 12.8 use for AM263P4?

    CCS does not use GDB. It uses its own proprietary debugger.

    We do have an openOCD + GDB extension for VS Code. However, it does not support AM263x:

    https://marketplace.visualstudio.com/items?itemName=ti-development-tools.ti-embedded-debug

    Thanks

    ki

  • Thanks for the quick response. 

    I tried using openocd with gdb-multiarch and having trouble resetting the cores using "monitor reset halt"

    (gdb) target extended-remote :3334
    Remote debugging using :3334
    0x00007758 in ?? ()
    (gdb) monitor reset halt
    JTAG tap: am263p.cpu tap/device found: 0x1bb9502f (mfg: 0x017 (Texas Instruments), part: 0xbb95, ver: 0x1)
    Deferring arp_examine of am263p.cpu.sysctrl
    Use arp_examine command to examine it manually!
    Deferring arp_examine of am263p.cpu.main0_r5.0
    Use arp_examine command to examine it manually!
    Deferring arp_examine of am263p.cpu.main0_r5.1
    Use arp_examine command to examine it manually!
    Deferring arp_examine of am263p.cpu.main1_r5.0
    Use arp_examine command to examine it manually!
    Deferring arp_examine of am263p.cpu.main1_r5.1
    Use arp_examine command to examine it manually!
    am263p.cpu.main0_r5.0: ran after reset and before halt ...
    am263p.cpu.main0_r5.1: ran after reset and before halt ...
    am263p.cpu.main1_r5.0: ran after reset and before halt ...
    am263p.cpu.main1_r5.1: ran after reset and before halt ...
    (gdb) load
    Loading section .vectors, size 0x40 lma 0x0
    Loading section .text, size 0xae00 lma 0x7004cda0
    Load failed

    Any ideas what might be wrong? or what the proper sequence is to reset the SoC?  

    Are there TI provided OpenOCD board/target configuration files for AM263P4?

    Note: I am able to load and debug the image fine.  But when trying to reset the chip, this happens.  I'd like to find a solution to this so that we don't have to power cycle the board every time we want to restart a test.

    Thank you for the support.  I understand this is a bit out of scope for TI, but we are required to use open source tools and other chips fully support OpenOCD configuration files without any issue.

    Regards

    ===============================================================

    Here are the gory details:

    Board: TMDSCNCD263P Rev E2

    SoC: AM263P4

    gdb-multiarch: GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 12.1

    OpenOCD: 0.12.0 (2023-10-02) 

    Configuration files:  Based on ti_am263_launchpad.cfg, ti_k3.cfg.   (minor mods to support AM263P)  Attached

    Example project: Hello World NoRTOS

    ti_tmdscncd263p.cfgti_k3.cfgOpenOCD_Reset_error_log.txt

  • I will bring this thread to the attention of the device experts.

    Thanks

    ki

  • Thank you, looking forward to a solution to this.

    I forgot to add the fact that the test above uses TI sdk 10.1.0.31 sbl_null.release.tiimage.

  • Hi Huey,

    We do not have GDB debugger support on AM263Px. We have taken it in our back log request. Meanwhile I will request you to use the CCS IDE.

  • Hi Nilabh, it is our company mandate to use opensource (or tools not tied to chip vendor) so CCS IDE is not a preferred option for us.

    Ki mentioned:

    "CCS does not use GDB. It uses its own proprietary debugger."

    Can we get more information on this?  Since CCS is based on eclipse, the debugger is just another app that is called by eclipse.  (is this correct?)

    Is the debugger available for us to use from within our IDE? (CLion in this case)

    Thanks

  • Hi Huey

    We are working on the example, Since we are syncing up weekly let me close this thread for now.