• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 121 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6414T: Error connecting to the target

IWS
Prodigy 190 points
Part Number: TMS320C6414T

Tool/software:

Dear Support-Team,

I urgently need to make a tiny change within an old project for TMS320C6414T.

I installed ccs_setup_7.2.0.00013.exe 

but when I try to connect to the target I get the following error:

Error connecting to the target:
(Error -1146 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
(Emulation package 6.0.628.3)

The 6414T is in a chain with another DSP which I can connect to and load a program into...

Any hints for me?

Thanks, Wolfgang

P.S.:

- CCS is on Windows

- CCS -> Target Configuration -> Test Connection works.

- Debugger is a Blackhawk USB560v2 System Trace Emulator
(Driver date: 02.08.2018 - far behind the DSP in question)

- The "target" is "mature" and not in question of hardware issues.

- The debugger is in use with CCS 12.50 on linux on an other device and works fine.

  • 0
    TI__Guru**** 442001 points

    Hello,

    IWS said:
    Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.

    Please see the below document for more details on the error. See section called "Invalid device ID"

    IWS said:
    - The "target" is "mature" and not in question of hardware issues.

    The same CCS version and debug prove was used successfully in the past with the same target?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 190 points

    Hi Ki, 

    Thanks for fast answer.

    Ähm, which "below document"?

    To be honest: Same CCS with same target: No.


    As the JTAG-Chain works and I can load the other dsp in the chain and the dsp is actually loading, running and operating fine I strongly suggest this to be a kind of software issue... 

    Regards, Wolfgang


    P.S.: Despite this I'm fascinated that the debugger (USB560v2) is quite the same than 20 years ago. In new multi-core devices I thought debugging would also run faster (e.g. LVDS).

  • 0 in reply to IWS
    TI__Guru**** 442001 points
    IWS said:
    Ähm, which "below document"?

    Sorry, here is the link:

    https://dev.ti.com/tirex/explore/node?node=A__ANoamrIZPWD2-6T-NDDWGg__ccs_devtools__FUz-xrs__LATEST

    IWS said:
    As the JTAG-Chain works and I can load the other dsp in the chain and the dsp is actually loading, running and operating fine I strongly suggest this to be a kind of software issue... 

    The JTAG scan chain sound fine. The error indicates that the debugger is unable to communicate with that particular device. It could be a hardware issue or some configuration issue. What is the other DSP in the chain? Another C6414?