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

TMS320F2800137: DCSM

youjun zhang
Intellectual 570 points
Part Number: TMS320F2800137

Tool/software:

hi expert:

i enable the Password Lock,CSM Passwords of dcsm module,when power on ,the mcu runs normally,started  from flash.

then i enable JTAGLOCK,the mcu not run?why?

i wrtie the password of Password Lock,CSM Passwords,JTAGLOCK,do not debug the mcu?why?ccs errorr as follows:

C28xx_CPU1: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.12.0.00150)
C28xx_CPU1: Error connecting to the target: (Error -6311) PRSC module failed to write to a register. (Emulation package 9.12.0.00150)

  • 0
    TI__Mastermind 23290 points

    Hi Youjun,

    Before enabling JTAGLOCK, did you test the device in standalone mode(no debugger connected)? Did this work as expected? When JTAGLOCK is enabled, you must provide the JTAG passwords to connect to the device again. Are you trying to regain access to the device or test in standalone with JTAGLOCK enabled?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Intellectual 570 points

    hi

    Before enabling JTAGLOCK, did you test the device in standalone mode(no debugger connected)? Did this work as expected?

    Yes

    the ccs verison is 12.4,is a bug in this version?iI saw someone asking this question on the forum as well

  • 0 in reply to youjun zhang
    TI__Mastermind 23290 points

    Hi Youjun,

    After enabling JTAGLOCK, you won't be able to connect to the device again unless you provide the JTAG passwords in the target config file. Let me know if you need assistance with this.

    When the device is running in standalone mode with JTAGLOCK enabled, what behavior do you see that indicates the device is not running? Did you enable any other settings in addition to enabling JTAGLOCK after your last successful test? Enabling JTAGLOCK should have no impact on the device when running in standalone mode.

    Thank you,

    Luke