• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 1144 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28377D: TMS320F28377D CPU2 connecting problem

Sang-il Nam
Expert 2820 points

Part Number: TMS320F28377D
Other Parts Discussed in Thread: TMS320F28388D

Hi, 

I'm debugging the TMS320F28377D controller using the XDS200 emulator. (I'm use CCS V10)

A strange error has occurred, I asking what the cause is :

CPU1 is connected well and there is no problem.

No problem at program loading and executing in CPU1, but when I try to connect with CPU2, I get an error like attached below.

C28xx_CPU2: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.0.00002)

Interestingly, the above problem does not occur in TMS320F28388D.

What is the cause of the problem and what parts should I look for?

Thanks in advance.

  • 0
    TI__Guru** 117201 points

    Hi,

    Is it fresh device or you have programmed some code into it ?

    When you are connecting to CPU2, CPU1 is halted or running ?

    One thing you can try is after connecting to CPU1, issue reset to CPU1 (from CCS) and then click on run. Once CPU1 halts (if it does not halt, halt it manually via CCS halt button) and then  try to connect to CPU2.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2820 points

    Hi,

    Is it fresh device or you have programmed some code into it ?

    >> It is fresh device.

    When you are connecting to CPU2, CPU1 is halted or running ?

    >> CPU1 is halted when connecting to CPU2.

    One thing you can try is after connecting to CPU1, issue reset to CPU1 (from CCS) and then click on run. Once CPU1 halts (if it does not halt, halt it manually via CCS halt button) and then  try to connect to CPU2.

    >> I've tested the method you mentioned, but I get the same error.

    >> Connecting to CPU1 --> Reset CPU1 --> Resume CPU1 --> (CPU1 Halted) --> Connecting to CPU2 --> The same error occurred.

    If you ignore the error and repeat the connection attempt, the connection is made with the following error message.
    However, CPU2 does not operate normally. Only the connection is made.

    C28xx_CPU2: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU2: Failed CPU Reset: (Error -1041 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
    C28xx_CPU2: GEL: Error while executing OnTargetConnect(): Reset failed: retcode=-1
    at GEL_Reset() [f28377d_cpu2.gel:98]
    at OnTargetConnect()
    C28xx_CPU2: Flash Programmer: Warning: The configured device (TMS320F28377D), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.

    Regards,

    Sang-il, Nam

  • 0 in reply to Vivek Singh
    Expert 2820 points

    Additionally, The error I mentioned above occurs in TMS320F28377D, but not in TMS320F28388D.

    If you compare the f28377d_cpu1.gel and f28388d_cpu1.gel, there are differences like the attached image, and I wonder if it is related to this problem.

    (In the case of the f28377d_cpu1.gel file, the process for CPU2 is not included when connecting or resetting the chip.)

  • 0 in reply to Sang-il Nam
    TI__Guru** 117201 points

    Hi,

    I don't see any issue in Gel file. The difference you are seeing is because of some hardware changes/enhancement on F28388 device. We as well as many customers are using same Gel file with out any issue.

    Do you see this issue on multiple device ? Can you take a picture of the chip (top view) and post it.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2820 points

    Thanks for the quick answer.

    It's difficult to attach a picture because I can't have a camera inside the company. Instead I attach the LOT number of the chip I tested.

    * TMS320F28377DZWTT YFA 3BATZYW

    * TMS320F28377DZWTT YFC 64A3LQW

    Of the various 28X chips I have, the problem only occurs on the F28377D. (CPU1 is connectable, CPU2 is not connectable)

    F28335, F280049, F28388D, etc. all have no connectivity problems.

    And, not all boards with the F28377D chip have this problem. Some boards work normally, and some boards have this problem.

    If there is a problem with the reliability of the PCB JTAG trace on the board I designed, can this happen?

    Is there any possibility of improving the PCB JTAG trace design to solve the problem?

    Thanks in advance.

  • 0 in reply to Sang-il Nam
    TI__Guru** 117201 points

    Hi,

    If you have some boards working and some not then this does seem like a board issue but it's difficult to say where is the issue. You could observe the power supply and see if there is any dip in power supply when you connect CPU2.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2820 points

    Thank you for the quick and friendly answer.

    I'll check the power regulation stability when connecting to CPU2.