Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 856 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.

CCS/TMS320C6474: Black Hawk USB 560v2 System Trace Emulator Error

Surya Paruchuri
Intellectual 650 points
Part Number: TMS320C6474
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hello,

I am trying to debug a custom board with TI 6474 SoC on it. I am using Black Hawk USB 560v2 STM Emulator with

CCS 4.2.1.00004,

SysBIOS 6.30.2.42

DSPBios 5.41.7.24

RTSC 3.20.3.63

OS: Win-7 64 bit;

Compiler tool chain listed under product Configuration are:  (c200)5.2.6, (c5400) 4.2.0, (c5500)4.3.6,(c6000) 7.0.2;

Black Haw Driver : 4.2.1.206;(Updated from some older version).

I am able to open a debug session, but when I try to connect to target, I get the following error:

Error connecting to the target:
Error 0x80000244/-1265
Fatal Error during: Register, Initialization, OCS,
The TAP ID for the DAP, read as 0x00000000, does not match with the default ID or the one provided in the board file.

I have tried to test the same board with a borrowed spectrum digital emulator to test if debugging is functional. And I am able to debug with Spectrum Digital EMU.  Any help on this would be highly appreciated.  Thank you.

  • 0
    TI__Guru**** 169234 points

    Hi,

    The error you are getting is quite unusual and its message changed over the years - code 1265 is now identified as a Device ID, which more properly characterizes the problem.

    The thread below contains a few tips to further debug this problem.

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/325327 

    Given the same hardware works on a different Debug Probe, I would try to match as close as possible the two target configurations. I suspect there may be something not quite correct with the target configuration of the Blackhawk Debug Probe.

    If you are using the C6474 EVM, it has two DSPs in the same scan chain. You will have to create a custom configuration and add the second DSP. If you are using a different board with a single DSP on it, the configuration is pretty straightforward. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 650 points
    Thanks Rafael for your feedback.

    Unfortunately I need to stick to old tool chain for some compatibility issues at my organization. But nevertheless, I have figure out that the configuration on black hawk didn't reflect the spectrum digital one because black hawk's .ccxml file doesn't have the other devices on the scan interface, while spectrum digital one has it. Changing this has fixed this one.

    Thank again for prompt response.