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/TMS320C6713B: Poor connection

Part Number: TMS320C6713B

Tool/software: Code Composer Studio

I want to connect to TMS320C6713B using CCS.
However, when I try to connect, I get an error.
[Execution procedure]
1.Supply power to the original board on which TMS320C6713B is mounted.
2.Start CCS3.1 and execute [connect].
3.An error occurs.
[Tool]
・CCS3.1
・Blackhawk USB
[Question]
a.Do you see the signal output from DSP when you execute conect using CCS3.1?
b.What is the possible reason why you cannot connect due to the error code?
  • Hello,

    It sounds like you are using a customer board. Is that correct?

    In any case, there was some failure with CCS/emulator communication with the target. But I would like to check that the blackhawk emulator is correctly enumerated on your PC. You can use the Blackhawk Control Panel (see page 23 of: https://www.blackhawk-dsp.com/downloads/docs/appnotes/BH-Troubleshooting-UG-03.pdf). If that looks ok, please try running a basic scan as mentioned in page 34. If that also passes, then it seems like low level connectivity is ok. 

    Also, have you been able to connect to this board in the past using the same setup?

    Thanks

    ki

  • Thanks ki

    It sounds like you are using a customer board. Is that correct?

    answer:Yes. That's right.I have implemented TMS320C6713B on the customer board.

    Also, have you been able to connect to this board in the past using the same setup?

    answer:Yes.I made 10 customer boards and only one error occurred.In some cases, the board with the error can be connected.

    Error code 1070 is "Cannot connect to emulator (time out)".I think that the solder on the customer board is defective.
    What signal is the timeout error seeing from TMS320C6713B?
  • user5199444 said:
    In some cases, the board with the error can be connected.

    It could be an unstable connection. First, can you try lowering the TCLK frequency to legacy 10.368MHz limit?