Part Number: LAUNCHXL-CC1350
Other Parts Discussed in Thread: CC1350, CC2640R2L, CC2640R2F, CC2640
Tool/software:
Hello, I am in the proccess of migrating all of the work my company had on code composer studio 11 to VScode, as CCS 20 feels quite slow and doesn't have Github Copilot at the moment. I've been able to create commands to build and flash on terminal with the CCS CLI succesfully. But I can't get to debug using the official TI Extension.
We currently use CC2640R2 microcontrollers on our PCBs and we have always program/debug them through any version of CCS or Flash programmer using a CC1350 Launchpad as an interface. The Launchpad has all jumpers removed except the one where it says XDS110 power which is connecting to the upper pin where Vsense is written, and has cables going from GND, 3,3V, RX, TX, RESET, TMS and TMC directly into our PCBs. We have never used TDI or TDO and we can Debug on CCS like this.
In my vscode launch configuration I have:
Licensed under GNU GPL v2
For bug reports, read
openocd.org/.../bugs.html
CDLiveWatchSetup
jtag
Warn : Interface already configured, ignoring
Warn : Transport "jtag" was already selected
Warn : Transport "jtag" was already selected
cortex_m reset_config vectreset
DEPRECATED! use 'adapter speed' not 'adapter_khz'
adapter speed: 1500 kHz
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Info : XDS110: connected
Info : XDS110: vid/pid = 0451/bef3
Info : XDS110: firmware version = 3.0.0.38
Info : XDS110: hardware version = 0x002b
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 1500 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: cc13x0.jrc: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : starting gdb server for cc13x0.cpu on 50000
Info : Listening on port 50000 for gdb connections
Info : accepting 'gdb' connection on tcp/50000
Error: Target not examined yet
Error executing event gdb-attach on target cc13x0.cpu:
Error: Target not examined yet
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected