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: problem when reverting a LPSTK-CC1352R to factory image

Part Number: CC1352R
Other Parts Discussed in Thread: , UNIFLASH, CC2652R

Hi Team,

May I ask for your help and expertise? Our customer have a concern as stated below:

"I'm dealing with a problem when reverting a LPSTK-CC1352R to factory image. I've followed the instructions in some of your older posts but I am unable to revert the image

I've read this post:
https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1032328/launchxl-cc1312r1-easylink-cc13x2-create-and-store-factory-image-to-external-flash 

And this one:
https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1004167/cc1352r-change-factory-image-on-external-flash 

I will be pleased to give you any more information of the problem if necessary."

I hope you can help us with this. Thank you so much.

Kind regards,
Gerald

  • Hi Yikai,

    Thank you for your response. I got a response from our customer as stated below:

    "I'm going to elaborate my problem a bit more, because the linked referenced from the reply was my first try.

    I'm trying to overwrite the factory image, so that if I press and hold BTN1 while I reset the LPSTK it boots up with a new application. For that, I erased the flash by loading the erase_storage_offchip_cc13x2lp.hex file on the CC1352R. I found it weird when, after loading it and performing a factory reset the led started blinking red and green, until it freezes in yellow. I don't know where that blinking comes from if the flash is erased... Anyway, I then loaded two images: bim and an application. I understand the application needs to be of the kind oad.bin, for instance application_oad.bin, in order for it to boot with bim (onchip or offchip?), but I am not sure if any other type of application image (without OAD) can be used. I would also appreciate you clarifying this."

    I hope you can further help us with this.

    Kind regards,
    Gerald


  • Hi Gerald,

    1) Can you ask them which specific oad application they loaded?

    2) Which version of the SimpleLink CC13x2/26x2 SDK are they using?

    3) Can you ask them to go through the SimpleLink Academy lab on OAD, and specifically the last part about debugging?

    https://dev.ti.com/tirex/explore/node?node=AIixxGE2y6tnPJ7cm65SFQ__pTTHBmu__LATEST

    Cheers,

    Marie H.

  • Hi Marie H,

    Thank you for your response. Kindly see details below:

    1) I am loading the simple_peripheral_oad_offchip_CC13X2R1_LAUNCHXL_tirtos_ccs_oad.bin
    2) SDK version: 5.20.00.52
    3) I followed the steps from the SimpleLink Academy you mentioned but it seems I cannot debug the bim. I attach a capture of what I see when I perform a board reset with the debugger, because I find it strange, and besides, the breakpoints are disabled and I cannot find a way to enable them. I am programming the simple peripheral, and the bim_offchip_CC1352R1_LAUNCHXL_nortos_css.out from Uniflash, in Windows, and I am using a CC2652R in between the CC1352R and the PC to debug the application.


    Kind regards,
    Gerald

  • Hi Gerald,

    I think you should still be able to run the code even if it look like the device is in HIB. 

    BTW the device is reset as part of the debug script in CCS, so you don't need to do another board reset. 

    Did you see the example readme? It explains how to enter debug mode at runtime and create a factory image.

    https://dev.ti.com/tirex/explore/node?node=AF2j9NOAWj9I-2l4lmj4lg__pTTHBmu__LATEST

    Cheers,

    Marie H.

  • 1) I am loading the simple_peripheral_oad_offchip_CC13X2R1_LAUNCHXL_tirtos_ccs_oad.bin

    This is for the launchpad and not for LPSTK.

    I suggest you erase the entire flash using SmartRF Flash Programmer 2. Then flash the cc13x2r1lp_bim_offchip.hex. After that flash the multi sensor hex file.

    -kel

  • Hi,

    I got response from our customer as shown below:

    "I've been trying to perform the steps from the responses without any luck until today, when I found a way that seems to be working. However, I still have some doubts, that I would like to solve if possible.

    I followed these steps:

    1) Erase flash with Smart Flash Programmer 2 (all unprotected pages, keep CCFG)
    2) Program with Uniflash:
    - cc13x2r1lp_bim_offchip.hex
    - multi_sensor:CC13x2r1_LAUNCHXL_tirtos_ccs.out
    The hex file did nothing apparently, it did not boot.
    3) Flash project_zero_CC13X2RF_LAUNCHXL_tirtos_ccs.out

    In this case, from what I see, I assume project_zero.out file needs a bim to boot. As there is no bim flashed, the factory image is the one booted, that's why the multisensor app is the one started. If, on the other hand, I flash a bim as well, project zero boots up. That's supposed to happen if I am right.

    However, with multi_sensor+cc13x2r1lp_bim on the external flash and project_zero+bim on the internal I cannot boot from multi_sensor by pressing BT1/off/on/BT1, it starts project_zero. Isn't it possible to boot from the factory image even if there's a valid one on the internal flash?

    I would like to know if I am trying something that is not possible or I am performing the steps the wrong way.
    Thank you so much."

    I hope you can further advise us.

    Kind regards,
    Gerald

  • Hello,

    The factory image is the multi sensor example program. Do not flash any launchpad example programs to the LPSTK-CC1352R, like the project zero. I am suggesting to re-flash the multi sensor example program to start fresh.

    The bim hex file is in this folder location:

    C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC1352R1_LAUNCHXL\ble5stack\hexfiles\bim_offchip\Release

    The multi_sensor hex file is in the release folder after you rebuild all.

    C:\ti\ccsv103workspace\CC1352Rv510\multi_sensor_CC13X2R1_LAUNCHXL_tirtos_ccs\Release

    Use SmartRF Flash Programmer version 1.8.0. Flash the bim hex file. Then the multi sensor hex file. You can also do a mass erase first using the wrench icon. The blue led should blink after flashing.

    -kel

  • Hi,

    I got response from our customer as shown below:

    "Ok, I got it, I can now reflash the factory image but I don't know how to boot from it if I flash something else afterwards. If the new image is wrong, the factory image boots up, but I would like to boot from factory image it even if the new one is right. Isn't it possible? Doing BT1/off/on/BT1 always starts the new image, not the factory one."

    I hope you can further help us.

    Kind regards,
    Gerald

  • Hi Gerald,

    The point of the factory image is to be a safe guard in case the application image is corrupted. 

    If they want to boot into factory image they will need to re-write the application accordingly.

    Cheers,

    Marie H.