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

CC1352R: Debug interface is locked even after Forced Mass Erase

Nate Ihle
Prodigy 20 points
Part Number: CC1352R


I have been using a __ramfunc to write a firmware binary to the program flash memory. In doing so I have accidentally overwritten the CCFG portion and possibly disabled the bootloader and JTAG. In order to recover I used the SmartRF Flash Programmer 2 CC26xx/cc13xx Mass Erase function. This worked for me once, but recently it has not been successfully re-enabling the debug interface. I tried another board to make sure it's not an issue with the uC being damaged and I'm still having the same issue. Here are screenshots of the successful Mass Erase and subsequent failure to communicate:

  • 0
    TI__Expert 4425 points

    Hi,

    The modifications to CCFG might have disallowed performing a mass erase. Please refer to the Technical Reference Manual section 11.2.1.14 (field CHIP_ERASE_DIS_N). Other fields might also have been modified preventing you from performing the mass erase.

    Nate Ihle said:
    I tried another board to make sure it's not an issue with the uC being damaged and I'm still having the same issue.

    Is this a board where the same issue (accidentally overwriting CCFG) has occurred? 

    Regards,
    Nikolaj

  • 0 in reply to Nikolaj_G
    Prodigy 20 points

    Hey Nikolaj,

    Thanks for the reference. It looks like I may have disabled the CHIP_ERASE_DIS_N bit as well as some of the TAP/DAP settings. Do you know if there is any way to recover from here? 

    Yes the 2nd board also had the CCFG overwritten in the same manner.

    I now skip over the CCFG portion of flash (0x57FA8 - 0x58000) in my __ramfunc, so this shouldn't happen to my other boards. However it would be nice to recover these 2 if possible.

  • +1 in reply to Nate Ihle
    TI__Expert 4425 points

    Hi Nate,

    I am afraid that you will not be able to recover the devices, if chip erase (also referred to as mass erase) has been disabled through normal means.

    If however your application on your devices is still functioning correctly and if it provides a way to erase the CCFG sector, (maybe triggered through another interface) then you might have a chance to recover the device.

    Regards,
    Nikolaj