Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1199 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.

gdb_agent_console not working with CC1310 launchpad on Linux

Andrew G
Intellectual 900 points
Other Parts Discussed in Thread: CC1310, UNIFLASH

I am having a difficult time getting gdb_agent_console to work with the CC1310 launchpad on Linux. I am running emulation package version 6.0.228.0 and have upgraded XDS110 firmware to the latest available version (2.3.0.1).

Uniflash is able to connect to the board and program binaries without issues, implying that this is not a hardware / connectivity issue.

I am using a board .dat file generated by CSS, attached below. After starting gdb_agent and connecting to the GDB server with a recent version of arm-none-eabi-gdb, I usually get the following error:

./uniflash_3.4/ccs_base/common/uscif/gdb_agent_console ~/cc1310/ccs.dat
Successfully configured cc1310/ccs.dat
CPU Name Port
-------- ----
cortex_m3_0 :55000

Starting all cores
CPU Name Status
-------- ------
cortex_m3_0 Waiting for client
cortex_m3_0 Client connected...Connecting to Target
FAILED! GTI_CONNECT(hpid=0x8c50d88)=-1
(Error -2062 @ 0x0)
Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 6.0.228.0)

Connection failed...exiting

I can work around this by first initializing the board in uniflash (via File -> New Configuration). It appears that maybe gdb_agent_console does not initialize the target correctly on its own. However, as soon as I set a breakpoint in gdb, I get another error:

cortex_m3_0 - Target device is connected
Target connected...Starting server
FAILED! GTI_SETBP_EX(hpid=0x9ee0d88,addr=0x144e,type=0,count=1,access=0)=ffffffff
(Error -1066 @ 0x144E)
Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory.
(Emulation package 6.0.228.0)

ERROR: set_breakpoint() backend call returned 64

Has anyone else had luck with gdb_agent_console + gdb + CC13XX / CC26XX launchpads, and if so, what configuration worked for you?

ccs.dat

  • 0
    Intellectual 900 points
    I should also point out that I tried lower clock settings as suggested in the error messages, to no avail.
  • 0 in reply to Andrew G
    TI__Intellectual 1170 points

    Andrew,

    Sorry for the delay.

    The connection error may have been due to outdated firmware on the xds110.  The gdb agent is not currently updating the firmware when it is necessary.  It is possible that the uniflash took care of the update for you.

    The error you are seeing when setting a breakpoint is common if GDB is requesting a software breakpoint be set in flash memory.  If possible try using the 'hbreak' GDB command instead of 'break' and see if that works.

    Regards,

    Craig