• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 226 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.

TMS320F28377S: Error debugging in CCS 11.2.0

Ganesh Shanbhag
Prodigy 10 points
Part Number: TMS320F28377S


Tool/software:

I recently began debugging using the XDS110 debug probe (Firmware Version: 3.0.0.38) and CCS (Version: 11.2.0.00007) encountered an error. I'm using the JTAG interface with a CTI-20 to TI 14-pin adapter, and I've connected it to the target device using jumper wires. The target is a custom board that gets flashed during production. Since we've observed some issues post-flashing, I need to debug it to identify the root cause. I've attached an image showing the error in a debug session.

PS: I’ve double checked all the JTAG connections and verified continuity using a digital multimeter, since I’m using jumper cables for the setup. Everything appears to be connected properly, and there are no open or misrouted lines. And made sure that target is powered properly (3.28V) by checking the VTREF with GND.

  • 0
    TI__Mastermind 21085 points

    Hi Ganesh,

    Are you able to test your target configuration on  another device to ensure the CCXML is not at fault here. I will recommend you double check the JTAG settings in your target configuration file. You can launch and select the Advanced tab at the bottom left of the window to see advanced options.

    Regards,

    Ozino

  • 0 in reply to Ozino Odharo
    Prodigy 10 points

    Hi ,

    Thanks for your reply.

    I found that the target device is locked using DCSM. I need to unlock it before starting a debug session. I am working on exploring and writing a small piece of code to unlock it before stating the program loop.

  • 0 in reply to Ganesh Shanbhag
    Prodigy 10 points

    Hi ,

    I’m unlocking the DCSM using the same function (that uses a 128-bit password) that’s used during firmware upgrades over UART to unlock flash before erasing/writing. However, I’m still encountering the same error.

    What else can go wrong?

  • 0 in reply to Ganesh Shanbhag
    TI__Mastermind 21085 points

    HI  can you confirm if you are only using DCSM passwords or do you have JTAG lock enables as well? Your target configuration file (ccxml) will need to have the passwords for the JTAG and DCSM saved if you want to connect to the device via a debugger. You can set these values using the On-chip Flash tool within CCS. Connect to the target configuration file, connect to the device open the on-chip tool-> flash settings.

    Regards,

    Ozino

  • 0 in reply to Ozino Odharo
    Prodigy 10 points

    Hi ,

    Your target configuration file (ccxml) will need to have the passwords for the JTAG and DCSM saved if you want to connect to the device via a debugger

    I checked for password option within the ccxml file. And couldn't find one.

    You can set these values using the On-chip Flash tool within CCS.

    I couldn't find On-chip Flash tool option within the CCS version I am using. It seems integrated with Debug.

  • 0 in reply to Ganesh Shanbhag
    Prodigy 10 points

    Issue Identified:
    The root cause of the setup problem was the jumper wires, which introduced significant noise into the system.

    Key Takeaway:
    As highlighted in the datasheet, ensure the JTAG cable length does not exceed 6 inches to maintain signal integrity and avoid noise related issues.

    Refer to the attached image for further clarification.

  • 0 in reply to Ganesh Shanbhag
    TI__Mastermind 21085 points

    Ganesh,

    Thank you for the feedback. Glad to hear your got this resolved.

    Regards,

    Ozino