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

Original question:

CC1352R: Flash microcontroller using Raspberry Pi 4 GPIOs to generate TCK, TMS and Reset signals

CC1352R: Erase entire flash without using cable + debugger

Bruno Lau Costa
Prodigy 150 points
Part Number: CC1352R

Hi,

I'm currently using a coprocessor connected to a RPi via UART as the central device of a project. We use the serial bootloader to reflash the coprocessor - and for this the bootloader backdoor pin must be enabled.

Our team is wondering that, if we flash a (wrong) fw that doesn't have the backdoor pin enabled, we would no longer be able to use the serial bootloader.

a. Is there any solution/workaround for this case, so that we avoid a manual intervention? We'd like to avoid the approach cable + debugger, since we don't have access to all our central devices.


b. We verified that erasing the entire flash makes it possible to flash the coprocessors via serial bootloader. Is there a way to erase the entire flash via UART, or other type of communication?

Thanks for helping,

Bruno

  • 0
    Guru 735685 points

    As I know, you cannot erase a chip without debugger.

  • 0 in reply to YiKai Chen
    TI__Guru**** 317180 points

    To flash the device through UART you either have to have an empty flash or use the backdoor pin. Hence UART can't be used to erase the flash if you haven't defined a backdoor pin.

    Could you elaborate on the use case? The serial bootloader is typically used when the firmware needed is "known good" as in tested and verified beforehand. If the bootloader pin is not defined it sounds like you are still in the development phase and connecting a debugger should be possible. 

  • 0 in reply to TER
    Prodigy 150 points

    You're right TER, we're still in development mode and starting to think in production. 

    Some time ago we used a coprocessor firmware where the backdoor pin wasn't enabled (and this old version may still exist somewhere and be used, with a really small probability). That being said, we just wanted to guarantee there was nothing else we could do to reprogram the uC if this old firmware is accidentally flashed. Our product is installed inside people's houses and the less we go there and 'disturb' the customers (first tens of users), the better.

    We are now re-designing our coprocessor pcb, eliminating unnecessary parts, and we wanted to verify this possibility in order to add extra connections/traces to the pcb if there was an alternative way of erasing the flash. 

    Anyways, thanks for your help and responsiveness!

    Bruno