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.

CCS/UNIFLASH: Please add Forced Mass Erase for cc13x2

Part Number: UNIFLASH
Other Parts Discussed in Thread: CC1312R

Tool/software: Code Composer Studio

In our application, we lock down all the debug interfaces so that the binary firmware, and other sensitive information, stored in on-chip flash cannot be read out.

On cc13xx, we can (must) perform a "Forced Mass Erase" on the device in SmartRF Flasher 2. This application doesn't support cc13x2 yet. UniFlash does support cc13x2, but to my knowledge not a Forced Mass Erase on said device.

Of course, I can temporarily disable the read-out protection, but that is but a temporary solution.

Can you add "Forced Mass Erase" support to UniFlash (including the command line tools)? Alternatively (actually preferred), add cc13x2 support to SmartRF Flasher 2?

Best,

Marcus

  • Marcus,

    By mass erase you mean your device is locked and you need to recover it? If so, can you try the option below? 

    (I don't have my board here with me to test this, but I recall it should work without the need to connect).

      

    At the moment, however, the CLI interface does not yet have a mass erase option.

    Regarding the CC1312 Support by the SmartRF Flasher, please check your original thread at: 

    https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/p/672568/2479397#2479397

    Hope this helps,

    Rafael 

  •  Hi!

    Hm, sorry, I missed that I got an answer on the other thread. It doesn't however resolve my issue.

    I have two CC1312r Launchpad boards, one that I have programmed with my locked binary and one that is vanilla, just unpacked. The vanilla one can be erased without error, but the other one get's an error, shown in the pic attached. I don't use custom cxmls for them, just let Uniflash autodetect this.

    The error indicates that it can't connect to a router subpath, which I guess is one of the TAP/DAPs in the jtag part of the chip, hence why I assumed the lock I flashed it with is the culprit. I inspected the binary, and it does indeed lock down the TAP/DAPs and serial bootloader, but I think I didn't set the ERASE_CONF_CHIP_ERASE_DIS_N (have to double check). But if that was set, would that disable even forced mass erase?

  • Hi,

    If you have locked  ERASE_CONF_CHIP_ERASE, you will not be able to perform "mass erase" (Chip erase and Mass erase is the same thing).

    The "Erase entire flash" button in Uniflash issues a mass erase - if it's not working, it may be a bug in Uniflash. What version of Uniflash are you using? If it's not the latest, please try using that.

    TIABO

  • Martin,

    The error on the Uniflash interface seems to indicate the device itself is locked indeed.

    One question: did you try to unlock it using the newer version of the SmartRF Flasher mentioned in the other thread? If this operation is not successful, then I really suspect the device is in a different type of lock and I would ask you to follow up on the other thread, as the device experts will be able to provide you additional ideas on how to properly unlock the device.

    If the issue is concentrated only on Uniflash, I will follow up with the Uniflash dev team here.

    Regards,
    Rafael
  • Martin,

    It's been several days since your last reply to this thread and we suspect you may have found the source of the problem. This thread will be closed, but please feel free to return to it if there are any pending issues.

    Regards,
    Rafael