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.

CCS/TMS320DM642: Unable to debug

Part Number: TMS320DM642

Tool/software: Code Composer Studio

Hello,

I am facing problems trying to move our RTSC application from CCS3.3 to CCS4.2. We are using our own custom board with TMS320DM642 DSP, and we are using XDS510USB emulator. In CCS3.3, I can connect to the board, and debug and run the application.

At this point, I just want to be able to connect to the board from CCS4.2. Using the wizard, I created an empty RTSC project with the following parameters:

Device: TMS320DM642
BIOS: 6.32.02.39
Code generation Tools: TI v7.2.3
XDC tools: 3.22.1.21
Target: ti.targets.C64
Platform: ti.platforms.evmDM642


In my target configuration for debugging, I did specified TMS320DM642 as my device, and XDS510USB as my emulator.

With all that in place, I get the following error upon attempting to start debugging:

C64x: Error connecting to the target: Error 0x80000240/-1146 Fatal Error during: Initialization, OCS, Invalid data was scanned by the emulation controller. Verify the board setup to make sure the scan chain is properly defined. If the setup is correct, then RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.

I get this error whether I use standard gel files, which came with CCS4.2, or with our modified gel files, which work in CCS3.3

I would appreciate any clues on what the error means and how to address it.

Thanks!

  • Hello,
    Can you try running a low-level JTAG connectivity test and post the results here:
    dev.ti.com/.../

    Your version of CCS is very old but I think the "test connection" option was still there in CCSv4.

    btw - Is there any reason why you are moving to just v4 and not a more recent version?

    Thanks
    ki
  • Hello Ki,

    Unfortunately the Test Connection button is not present. We are using CCS4.2 since it appears that CCS5 and newer versions of the studio do not support the TMS320DM642 DSP and ti.platforms.evmDM642 platform.

    Alex.
  • Which XDS510USB probe are you using (vendor)? Many of them come with a equivalent low-level diagnostics tool. Spectrum Digital has SdConfigEx for example.

    Current versions of CCS still support the DM642. But supporting software may not (BIOS). Where did you hear that CCSv5+ does not support DM642?
  • Ki,

    The XDS510 USB probe we are using is made by Spectrum Digital. Following your advice, I just ran connection and emulator tests from SdConfigEx, and they succeeded. Here is the output of the Connection Test:

    $$ You are connected to:
    $$ EmuProductName=XDS510USB
    $$ EmuPortAddr=0x510
    $$ EmuPortMode=USB
    $$ ProductId=510
    $$ ProductVersion=84

    Here is the output of the emulator test:

    $$ You are connected to:
    $$ EmuProductName=XDS510USB
    $$ EmuPortAddr=0x510
    $$ EmuPortMode=USB
    $$ ProductId=510
    $$ ProductVersion=84


    ** Checking emulator/eZdsp scan connection

    ** Emulator Test **
    $$ EmuProductName=XDS510USB
    $$ EmuPortAddr=0x510
    $$ EmuPortMode=USB
    $$ ProductId=510
    $$ ProductVersion=84
    ** Emulator Scan Test
    -- Found JTAG IR length of 38
    -- Found 1 JTAG device(s) in the scan chain

    As for why I am not using CCS5+ - the ti.platforms.evmDM642 platform we've been using is not among those supported by the Studio. So even though TMS320DM642 DSP is supported by it, there is no a clear path to migration of my project to that version of the studio. So, for now here is the list of questions/problems I am facing:

    1. Provided I decide to use CCS4.2, what would be the approach to address the original communication problem considering that tests ran from SdConfigEx succeed?

    2. If CCS5 is a better option than CCS4, how do I overcome the absence of support for the ti.platforms.evmDM642 platform for RTSC projects in that version of the studio? I've tried to create bare-bone TMS320DM642 -supporting CCS5 RTSC projects using the wizard choosing either ti.platforms.generic or ti.platforms.sim6xxx platforms, but failed to even build the resulting projects.

    3. I've also tried to import my bare-bone CCS4 RTSC project (which fails to connect to the board) to CCS5, but the import failed due to missing IPC package.

    I'd appreciate any help you can provide.

    Thanks.

  • Based on the output of SDConfig, your low level JTAG connection seems ok.

    Alex Shkiler said:
    1. Provided I decide to use CCS4.2, what would be the approach to address the original communication problem considering that tests ran from SdConfigEx succeed?

    Try checking you emulator configuration, specifically the JTAG TCLK setting. Try lowering it:

    https://www.youtube.com/embed/mKxaztkCsYw

    Note that for SD XDS510USB, the setting will look different than the video above. But there should still be something for TCLK frequency.

    Alex Shkiler said:

    2. If CCS5 is a better option than CCS4, how do I overcome the absence of support for the ti.platforms.evmDM642 platform for RTSC projects in that version of the studio? I've tried to create bare-bone TMS320DM642 -supporting CCS5 RTSC projects using the wizard choosing either ti.platforms.generic or ti.platforms.sim6xxx platforms, but failed to even build the resulting projects.

    3. I've also tried to import my bare-bone CCS4 RTSC project (which fails to connect to the board) to CCS5, but the import failed due to missing IPC package.

    Questions 2 & 3 are best answered by the experts in the DM64x DaVinci forums. They can recommend the best versions of the various tools for your device.

    Thanks

    ki

  • Hello,
    I haven’t heard back from you, I’m assuming you were able to resolve your issue. If not, please post a reply with an update below (or create a new thread).

    thanks,
    ki
  • Ki,

    I indeed managed to make it work. I started "from scratch" and let Composer Studio import my legacy 3.3 project. I also made sure that the Studio uses our custom gel file. 

    Thank you for your help!

    Alex.