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: Bootlader and OTA Upgrade

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

Hi All,

We are using CC1352R1F3 IC with sensor OAD firmware. We had one TestJig which tests all the functionalities of CC1352R1F3. In the TesJig we are using MSP430FR5994 and communicate to CC1352R1F3 using UART (TXD13 and RXD12). From the Hardware checks, we are checking all the functionalities like Power,Peripherals, RF communication with another Collector device. 

We had an issue with the Jig. We are using Serial Bootloader to program the CC1352R1F3 we could able to perform flashing but after testing, we could not able to perform TURBO OAD to sensors directly.

Because using test jig we program using serial bootloader with hex file, after complete tests we will release to production. Now after producing these sensors we need to connect to Collector using the pairing process, hereafter in the field if we want to upgrade sensors only Native OAD works with the sensors and Turbo OAD is not working the first time.

Can you suggest any method which after Jig testing the TURBO OAD should work?

  • Hi Haricharan,

    When you are programming through the serial bootloader, you have to make sure the image contains both a valid version of BIM and an oad image with a valid OAD header.

    How are you producing your image?

  • Hi Marie,

    We have taken a hex file from the CCS project workspace and that hex file is given to MSP. From MSP using a serial bootloader, we transferred the file to CC1352R1F3 in the Test Jig.

    After this, the sensor is working fine. Now, if we need to update the sensor using a collector, For this if we provide .bin file we can upgrade but it takes 3 minutes approximately(Native OAD).

    Here there is no chance of sending .dim(Delta image(TURBO OAD))?

  • Hi Haricharan,

    According to your description, you are not programming a BIM (boot image manager) image on the device, thus it will not be able to program new devices. Can you make sure you program this as well, either as part of a merged hex file or individually?

  • Hi Marie,

    We are merging bim.hex and sensorOAD.hex and using MSP we are using serial bootloader application and programming the IC. IF we are not using bim.hex the sensor is not working after restarting.

    After the program is dumped using serial bootloader we tried to pair to the collector and sending messages to and from the collector it was successful after that we restarted the sensor and sent again the messages to and from the collector, this also worked fine.

    Now the problem arises we are transferring OAD delta image(.dim) we could not able to send file to sensor because of CRC mismatch. But, if we transfer .bin file the upgrade is successful.

    How can we overcome the issue?

  • Hi Haricharan,

    I don't understand the logic of programming the dim file through the serial bootloader.

    The dim file is a diff file between the original image (bim file) and your next code version. In order for this file to make sense, the original bim must be running on the application.

  • Dear Marie,

    I don't understand the logic of programming the dim file through the serial bootloader.??

    Sorry, you had mistaken my statements in the above message.

    I will describe my problem in detail

    We followed the process below:

    1. We are manufacturing sensors where Uniflash or other programming tools we could not use to program sensors, the only way is UART. So we choose the Serial bootloader and connecting sensors to MSP430FR5994(HOST IC )and performing programming to CC1352 using Serial Bootloader. We are using both (boot_image_manager)bim.hex and sensorOAD.hex to flash using the serial bootloader. 

    2. After successful programming through serial bootloader we are testing all peripherals of the hardware.

    3. Once we confirm the hardware is working fine we are taking the hardware from the test jig and we are sending the sensors to the customer (in other location) there they will join the sensors to the collector and perform FOTA. 

    Is it Possible to perform a turbo OAD for the very first time after programming the controller with the serial bootloader(using bim.hex and sensorOAD.hex)???

     

    Is there any way to send sensorOAD.bin and bim.hex instead of sensorOAD.hex and bim.hex using a serial bootloader?? 

     

    I had one more query

    When you are programming through the serial bootloader, you have to make sure the image contains both a valid version of BIM and an oad image with a valid OAD header.

    Do we get the valid OAD header from the hex file???

  • Hi Haricharan,

    Sorry for the misunderstanding.

    Let me answer your questions in the opposite order from what you asked:

    Do we get the valid OAD header from the hex file???

    • No, the hex file does not contain a valid OAD image header. You will get a valid header after sending the hex file through the oad image tool. (The result is the sensorOAD.bin file.)
    • BTW the BIM image does not need an OAD header, here you can use the hex file.

    Is there any way to send sensorOAD.bin and bim.hex instead of sensorOAD.hex and bim.hex using a serial bootloader?? 

    • Yes. The simplest might be to use e.g. intelhex to merge the two files and program the merged image with the serial bootloader.

    Is it Possible to perform a turbo OAD for the very first time after programming the controller with the serial bootloader(using bim.hex and sensorOAD.hex)???

    • No
    • If you program the device using the serial bootloader with the BIM hex image and the application bin image, you should be good to go
    • Please double-check that the BIM is able to boot into your application image.
  • Thank you for your response.