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.

CC1352P: Bootloader power consumption

Part Number: CC1352P

We are building a board with a CC2642 main processor and a CC1352P co-processor, our intention is to eventually use to CC2642 to flash the CC1352 with firmware when needed however we initially won't be using the 1352. 

If we produce boards and leave the 1352 in it's default state without a valid image then it will sit in boot loader mode until some future date when we want to use it, when it's in this state does it use much power? i.e. will it be asleep most of the time?

We are trying to decide if we can leave it that way or if we need to put some minimal code on it that puts the processor to sleep.

  • Hi Martin,

    What happens when you boot into an empty/cleared device is the following:

    When the device resets, part of the boot procedure is to check if CCFG_IMAGE_VALID in CCFG contains a valid pointer, which is the flash image vector table. If the address is valid, then the boot procedure jumps to that address. However, if it is invalid then it jumps to the ROM bootloader. In the ROM bootloader it polls the serial ports for any incoming messages forever. In other words, in never goes into standby.

    In order to put the device into sleep you need to flash the device with some minimal code. The simplest would be to use NoRTOS, which in main simply calls the Power driver to put it into shutdown state. Remember to configure the CCFG with the bootloader backdoor enabled, as I assume you are planning to use the bootloader to reprogram the device.

    int main(void)
    {
        // Any required board-specific initialization here.
    
        Power_init();
        Power_shutdown(0, 0);
    
        // Should never return
        while (1);
    }

  • ok got it, thanks for the answer!