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

Re-flashing a locked Picollo device.

Traver Gumaer1
Intellectual 320 points

Is there no way to just connect a debugger and reflash a device that is locked (using the csm code of course)? I am aware I can ground one of the boot pins and get it to connect, but this is a serious issue for production when they have to perform an additional step to connect to each device before being able to program.

Is there any other way to just reprogram a locked device, or am I stuck shorting the boot pins on each device I need to re-flash?

  • 0
    TI__Guru 61235 points
    Traver,

    Once the device makes an access to secure memory, the ECSL (emulation code security logic) will disconnect JTAG. So the basic answer is no, you cannot connect a debugger to the device once the ECSL is triggered. Changing the bootmode to "Wait" mode (by shorting the bootmode pin you mentioned) keeps the device from making an access to secure memory.

    You say this is a problem in production, but if the device has not yet been programmed the CSM should not be locked and therefore there should be no reason to have to put the device into "Wait" bootmode. What am I missing here?

    Regards,
    David
  • 0 in reply to David M. Alter
    Intellectual 320 points
    In development, many times we have hundreds of already flashed and locked units that need to be re-flashed to address issues found in initial development and production.

    Not only do the boot pins have to be shorted, but they must be accessible by adding a pin header to the design. This is what we will need to do, but I was wondering if there was an easier way. It sounds like once the chip is locked, there is no choice but to make the boot pins accessible to a pin jumper, add a jumper to each device to short the pins, reprogram, and remove the jumper from the device.
  • 0 in reply to Traver Gumaer1
    Intellectual 320 points
    I was also thinking that TDO (GPIO37 the other boot pin) could be used to hold the device from executing code. That would put the device in boot to SCI. The problem is that the debugger firmware would have to be written to do this.