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.

LAUNCHXL-F280049C: CSS scripting doesnt work on CCS 20.4.1

Part Number: LAUNCHXL-F280049C

Hi

I am trying to create a debug enviornment using scripting as specified in https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-scripting.html

I always endup getting following issue. 

PS C:\ti\ccs2041\ccs\scripting> .\run.bat "C:\Users\surendra.nadkarni\workspace_ccstheia\sci_ex3_interrupts_fifo\read_memory.js"
[
  'Texas Instruments XDS110 USB Debug Probe_0/C28xx_CPU1',
  'Texas Instruments XDS110 USB Debug Probe_0/CLA1_0'
]
GEL: C28xx_CPU1: GEL Output:
Memory Map Initialization Complete

GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...

GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...

Target connected. Loading program...
GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...

GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...

GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...

GEL: C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...

C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:196
            throw new TimeoutError();
                  ^

ScriptingTimeoutError: Scripting operation timed out
    at waitForMessage (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:196:19)
    at Object.waitFor (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:204:17)
    at Object.receive (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:345:36)
    at receiveForModule (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:439:25)
    at receiveResponse (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:446:20)
    at execCommand (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:490:23)
    at Object.loadProgram (C:\ti\ccs2041\ccs\scripting\node_modules\scripting\syncAgent.js:557:48)
    at Object.<anonymous> (C:\Users\surendra.nadkarni\workspace_ccstheia\sci_ex3_interrupts_fifo\read_memory.js:12:16)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)

Node.js v18.16.0

I am wondering what is the cause of this issue. Note that I can debug/flash the out file using CCS app. Please find the attached script file. 

const ds = initScripting();

let { cores, nonDebugCores } = ds.configure("C:\\Users\\surendra.nadkarni\\workspace_ccstheia\\sci_ex3_interrupts_fifo\\targetConfigs\\TMS320F280049C_LaunchPad.ccxml");

// Configure a 10 second timeout on all operations (by default there is no timeout)
ds.setScriptingTimeout(10000);
console.log(cores);

const session = ds.openSession('Texas Instruments XDS110 USB Debug Probe_0/C28xx_CPU1');
session.target.connect();
console.log("Target connected. Loading program...");
session.memory.loadProgram("C:\\Users\\surendra.nadkarni\\workspace_ccstheia\\sci_ex3_interrupts_fifo\\CPU1_FLASH\\sci_ex3_interrupts_fifo.out");

console.log("Program loaded. Running target...");
session.target.run();
console.log("Target is running. Waiting for 5 seconds...");
sleep(5000); // Wait for the target to run for a bit before reading memory
console.log("Target is running. Reading memory...");
const symbolAddr = 0x0000a94a;
console.log(`Symbol address: ${symbolAddr}`);


// Example: Read 16 bytes from address 0x00000000
const address = symbolAddr;
const dslocation = address.toString(16) + "@DATA";
const length = 255;
const data = session.memory.read(dslocation, length, 16);
for (let i = 0; i < data.length; i++) {
    console.log(`0x${(address + i).toString(16)}: 0x${data[i].toString(16).padStart(2, '0')}`);
}
console.log(`Data read from 0x${address.toString(16)}:`, data);
session.target.disconnect()
ds.shutdown();

CCXML file

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cla2.xml" id="drivers" xml="tixds510cla2.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="4" id="SWD Mode Settings"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F280049C_0" href="devices/f280049c.xml" id="TMS320F280049C_0" xml="f280049c.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

Second question, is there a possibility to run a GDB server using CCS tools?

Surendra