TDA4VM: TDA4VM STarter Kit debugging with external XDS110

so ha

Part Number: TDA4VM

I am trying to debug and load firmware to the tda4vm starter kit evaluation board : www.ti.com/.../SK-TDA4VM

I am following this user guide to debug, using an external xds110 debugger, instead of the xds560 :

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j721e.html

js:> loadJSFile ("/home/user/ti-processor-sdk-rtos-j721e-evm-11_01_00_04/pdk_jacinto_11_01_00_17/packages/ti/drv/sciclient/tools/ccsLoadDmsc/j721e/launch.js")
Could not open session. No devices found matching: .*MCU_Cortex_R5_0 (/home/user/ti-processor-sdk-rtos-j721e-evm-11_01_00_04/pdk_jacinto_11_01_00_17/packages/ti/drv/sciclient/tools/ccsLoadDmsc/j721e/launch.js#91)

launch.js Line 91, is updateScriptVars() function, I commented out line 91 as follows :

function updateScriptVars()

{

//Open a debug session

// dsMCU1_0 = debugServer.openSession( ".*MCU_Cortex_R5_0" );

dsDMSC_0 = debugServer.openSession( ".*DMSC_Cortex_M3_0" );

}

at least I get console logs :

Connecting to DMSC_Cortex_M3_0!

But with the pop up :

Error connecting to the target:
(Error -6305) PRSC module failed to write to a router register.
(Emulation package 20.0.0.3178)

I followed all the steps until : Fig. 7.7 CCS: Scripting Console Output, loading the js file , it struggles with opening a session with the cortex r5 in line 91 of the launch.js script.

Is there any clear way of baremetal program the tda4vm-sk.

3 months ago

0 Anil Dali 3 months ago

TI__Intellectual 2050 points

Hi So Ha,

Are you running the launch.js script file after launching the Target Configuration file from CCS?

Regards,

Anil

0 so ha 3 months ago

Prodigy 120 points

launching it leads to the following error :

Error connecting to the target:
(Error -1170 - (3:24:1))
Unable to access the DAP. 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 20.0.0.3178)

And testing jtag connection is successful

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

/home/soham/.ti/ccs1281/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'Sep 26 2024'.
The library build time was '10:06:50'.
The library package version is '20.0.0.3178'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe]

For newly purchased boards, I wonder if there is one time step that needs to be done before you can load via ccs as for the am64 : software-dl.ti.com/.../EVM_SETUP_PAGE.html

0 Anil Dali 3 months ago in reply to so ha

TI__Intellectual 2050 points

Hi So Ha,

so ha said:
launching it leads to the following error :

Error connecting to the target:

Launching will not give this error ("Error connecting to the target").

After launching the target configuration file (which should be as mentioned in the user guide),
We need to run the launch.js file from the scripting console.

But make sure that xds110 debugger with power supply connected to the EVM before doing these steps.

Regards,

Anil

Processors

Processors forum

TDA4VM: TDA4VM STarter Kit debugging with external XDS110