• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 222 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.

TMS320F280025: Application issues of chips

Tonyx.wu
Genius 4435 points
Part Number: TMS320F280025
Other Parts Discussed in Thread: UNIFLASH

After using the DCSM module to encrypt the flash of 280025, the jtag cannot be connected again, and uniflash is also useless

I have configured the zone per linkpoint section in the DCSM module ZONE1, and set a password (not all zeros) to transfer all sectors of flash to zone 1 protection, without configuring ZONE2. After the configuration is completed, build the project, connect the development board, burn the program, and then use the MEMERY browser to view the memory. At this time, the console will output security: true

Later, I used tool-on chip flash to unlock, and the console displayed security: false. I clicked program xx again (the option next to unlock, lock) to exit the debug state and connect again. An error was reported indicating that the device is in low power state. Do you want to forcibly wake it up

I encrypted through configuring the DCSM GUI interface without writing a program

I tried to enter the password, uniflash, and modify the. gel file in the debug, but still couldn't connect. The technical manual mentioned that I can enter the wait boot mode for JTAG connection, but I don't know how to operate [cover my face]. Is there a specific operation manu

The following is an error prompt

  • 0
    TI__Genius 15080 points

    Hi Tony,

    This seems related to the ECSL logic for the device cutting off the emulation connection. I'll bring in one of the DCSM experts for more information.

    Thanks and regards,

    Charles

  • 0 in reply to Charles Roberson
    Genius 4435 points

    Please help confirm as soon as possible. It's a bit urgent, thank you!

  • 0 in reply to Tonyx.wu
    TI__Mastermind 28310 points

    Hi Tony,

    Are you able to connect to the target at all? Aka Launch the target configuration in your project, right click on CPU and click connect to target? Does this work?

    There is a checkbox in the On-Chip Flash tool to reset the device before programming flash, you may need to uncheck this to resolve this issue. If that does not resolve it, Wait boot will need to be used, but I will need to consult with other DCSM experts to get clarification on how this is performed.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Genius 4435 points

    I also determined that ECSL was triggered. The checkbox he mentioned is not working and the board cannot be connected now. I have also checked a lot of information, but I did not tell me how to enter waitbootmode. Can you provide me with a detailed explanation of how to enter waitbootmode?

  • 0 in reply to Tonyx.wu
    TI__Mastermind 28310 points

    Hi Tony,

    If you have not changed your boot settings via programming the Zone 1 header in USER OTP, you should be able to select the boot mode by driving the boot mode select pins high or low.

    On F28002x, wait boot mode is selected by pulling GPIO24 low and driving GPIO32 high. Are you able to control the state of these pins?

    Thank you,

    Luke