CCS/DRA744: PC Trace not working anymore for DRA74x C66 DSP

Hi,

Also I face XDS560V2 STM traveller emulator driver issue. I cannot install the driver or the device manager cannot find the drive in CCS or in blackhack directory.

Regards,

Jeeva

The Error messages when launching Target Configuration file

Manfred,

I have a few questions:

- What is the Debug Probe you are using?
- How are you configuring Trace?

The reason is that I am able to collect DSP ETB Trace information using CCSv6.2.0 with all components upgraded (as mentioned in the attached link you sent) and using both my Blackhawk XDS560v2 STM and my Spectrum Digital XDS560v2 STM.

Jeeva,

Are you the customer Manfred mentioned?

If so, the device driver install is critical to make the Debug Probe work - however, your post evidenced a bit of an issue: the XDS560V2 STM Traveler is from Spectrum Digital and not Blackhawk.

www.spectrumdigital.com/.../

Regards,
Rafael

Hello Rafael,

Yes, it is me, where Manfred was mentioning. And I couldn't find the driver in the spectrum digital website. But this the second issue I think. the first issue is launching the Target configuration error. Shown in screen shot of my previous reply.

I really don't know, how to fix it. I have tried to complete wipe of CCS(clean temp dirs, appdata etc etc) and install it again.

Regards,

Jeeva

Hi Rafael,

After couple of tries. Now I have fixed the 1st error. Now I have to fix the 2nd driver error.

Now I got the error message:

Error initializing emulator:

(Error -2083 @ 0x0)

Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

(Emulation package 6.0.407.3)

this seems to be the Emulator driver issue. Some how it couldn't find the driver inside C:\ti\ or C:\Program Files (x86)\Blackhawk

And I don't know from where to get it.

Regards,

Jeeva

Jeeva,

could you post the solution of your PC Trace problem in this thread? It may help others facing the same issue.

Can you clarify again which emulator you're actually trying to use? There seems to be some confusion. You mentioned the "XDS560V2 STM Traveler" which to my knowledge is only available from Spectrum Digital, but you mentioned Blackhawk as well in connection with the Traveler version of the emulator.

Best regards,

Manfred

Hello Manfred,

The solution for first problem is, there is  an additional SW package we received from TI for DRA7x needs to be copied to c:\TI\ directory.

Sorry for the confusion regarding 2nd problem,

I am using XDS560V2 STM Traveler from Spectrum digital. And in spectrum digital website, the information is very very less and I couldn't find any driver for this debugger. And need some immediate help on this.

Regards,

Jeeva

Jeeva,

The Spectrum Digital device drivers are installed with Code Composer Studio and are typically located at the following directory:

C:\Program Files (x86)\SpectrumDigital

What exactly do you see in the Control Panel? I don't have a Traveller but my full XDS560v2 STM is shown as:

Also, can you get the utlity Sd560v2Cnfg v5 to recognize the probe?

If there is nothing on the Control Panel even after trying to scan for hardware changes, then I suspect the USB connection is faulty - cables, host or emulator port, etc. 

If the Control Panel acknowledges the probe but the utility can't properly find it, I would suspect the probe itself may be faulty. Some troubleshooting tips can be found at the menu Help of this utility. 

Please let me know how these tests go. 

Regards,

Rafael

Hi Rafael,

I am not sure whether the issue is resolved or not. Because at times it was not working when is launch the target configuration.

Issue 1: error message that "CCS cannot reach the port, and aborts the launch"

Solution: manually remove the driver from device manager and reinstall it. and restart the PC

Issue 2: Nothing critical, still it works, for basic operations like read memory etc etc. Attaching the gel file. And Manfred, finds this GEL file is ok.

IcePick_D: Error adding memory map range: invalid page specified
Cortex_M4_IPU1_C0: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence DONE! <<<---
Cortex_M4_IPU2_C0: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU2_C0: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence DONE! <<<---
Cortex_M4_IPU2_C1: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU2_C1: GEL Output: --->>> DRA7xx Cortex M4 Startup Sequence DONE! <<<---
C66xx_DSP1: GEL Output: --->>> DRA7xx C66x DSP Startup Sequence In Progress... <<<---
C66xx_DSP1: GEL Output: --->>> DRA7xx C66x DSP Startup Sequence DONE! <<<---
C66xx_DSP2: GEL Output: --->>> DRA7xx C66x DSP Startup Sequence In Progress... <<<---
C66xx_DSP2: GEL Output: --->>> DRA7xx C66x DSP Startup Sequence DONE! <<<---
CortexA15_0: GEL Output: --->>> DRA7xx Cortex A15 Startup Sequence In Progress... <<<---
CortexA15_0: GEL Output: --->>> DRA7xx Cortex A15 Startup Sequence DONE! <<<---
CortexA15_1: GEL Output: --->>> DRA7xx Cortex A15 Startup Sequence In Progress... <<<---
CortexA15_1: GEL Output: --->>> DRA7xx Cortex A15 Startup Sequence DONE! <<<---
ARP32_EVE_1: GEL Output: --->>> Configuring EVE Memory Map <<<---
ARP32_EVE_1: GEL Output: --->>> EVE Memory Map Done! <<<---
ARP32_EVE_2: GEL Output: --->>> Configuring EVE Memory Map <<<---
ARP32_EVE_2: GEL Output: --->>> EVE Memory Map Done! <<<---
ARP32_EVE_3: GEL Output: --->>> Configuring EVE Memory Map <<<---
ARP32_EVE_3: GEL Output: --->>> EVE Memory Map Done! <<<---
ARP32_EVE_4: GEL Output: --->>> Configuring EVE Memory Map <<<---
ARP32_EVE_4: GEL Output: --->>> EVE Memory Map Done! <<<---
IcePick_D: GEL Output: --->>> CONFIGURE DEBUG DPLL settings to 1.9 GHZs  <<<---
IcePick_D: GEL: Error while executing OnTargetConnect(): invalid page: data
    at (unsigned int *) 0x80031804@data [DRA7xx_dap_startup.gel:251]
    at dpll_dbgss_config_board() [DRA7xx_dap_startup.gel:192]
    at OnTargetConnect()
DRA7xx_dap_startup.gel

Issue 3: Cannot run the PC traces yet. Needs some resolution.

Get below message when launching the PC trace. And following error message.

CS_DAP_DebugSS: GEL Output: --->>> CONFIGURE DEBUG DPLL settings to 1.9 GHZs  <<<---
CS_DAP_DebugSS: GEL Output: > Setup DebugSS 1.9GHz in progress...
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS Trace export clock (TPIU) to 97MHz
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS PLL Clocking 1.9GHz
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS ATB Clocking 380MHz
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS Trace export clock (TPIU) to 97MHz
CS_DAP_DebugSS: GEL Output: --->>> TURNING ON L3_INSTR and L3_3 clocks required for debug instrumention <<<<<<----
CS_DAP_DebugSS: GEL Output: ---<<< L3 instrumentation clocks are enabled >>>> ---
CS_DAP_DebugSS: GEL Output: --->>> Mapping TIMER supsend sources to default cores <<<<<<----
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS Trace export clock (TPIU) to 135MHz

After clicking OK.

CS_DAP_DebugSS: GEL Output: ---<<< TPIU formatter has been stopped >>>---

And try to run the CORE.

C66xx_DSP1: Can't Run Target CPU: (Error -1060 @ 0x1BC002C) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register PC: (Error -1060 @ 0x0) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register ControlRegisters.CSR: (Error -1060 @ 0x41) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register ControlRegisters.CSR: (Error -1060 @ 0x41) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x876adf8c on Page 0 of Length 0x4: (Error -1060 @ 0x876ADF8C) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x876adf88 on Page 0 of Length 0x4: (Error -1060 @ 0x876ADF88) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x87572950 on Page 0 of Length 0x4: (Error -1060 @ 0x87572950) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Register A4: (Error -1060 @ 0x4) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x876adf8c on Page 0 of Length 0x4: (Error -1060 @ 0x876ADF8C) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x876adf88 on Page 0 of Length 0x4: (Error -1060 @ 0x876ADF88) Device is not responding to the request. 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 7.0.188.0)
C66xx_DSP1: Trouble Reading Memory Block at 0x87572950 on Page 0 of Length 0x4: (Error -1060 @ 0x87572950) Device is not responding to the request. 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 7.0.188.0)

Jeeva,

Please apologize for the delay; I was busy trying to figure out the different part numbers and EVMs of these automotive devices.

Can you confirm that you are using DRA74x or DRA74xP?

The reason is that I was able to properly run Trace on my XC5777X EVM (which corresponds to DRA74x) but for DRA74xP there is an outstanding bug filed for Trace, as reported in my post below:
e2e.ti.com/.../2508600

Regarding the GEL errors during connection, I can only suspect that either these scripts are incompatible with the board/device you are using or you may have code previously running on the target that modifies the hardware status and disrupts the regular GEL operation.

Please let me know if these could be possible scenarios.

Regards,
Rafael

Hi Rafael,

I am using DRA75x, DRA74x Jacinto6.

At the moment I am blocked, and fedup with this tracing debugging. So at the moment using CSL_tscRead(). To profile, still I need that traces for more details about stalls and other stuffs for our optimizations.

Regards,

Jeeva