• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 54 subscribers
  • Views 668 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.

LAUNCHXL-CC26X2R1: Creating a single production image for On chip OAD solution

Sandeep Sonawane
Prodigy 175 points

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH, CC2642R

Hi everyone,

I am working on On-chip OAD feature. As we know for On-chip OAD we need to flash 3 file at a time :- 

1) BIM file --> in .hex form

2)Persistent application --> in .bin form

3)User application --> in .bin format 

using Uniflash into our cc2642R controller.

So after flashing successfully we are using BTOOL for OAD feature and we have successfully updated our new firmware using the option OVER THE AIR DOWLOAD provided in BTOOL.

This not our concern , but our concern is that in production line we need use single image (*_oad.bin or .hex file) and here during ON-chip OAD process we are flashing 3 file which we need to combined into single image or file (i.e .bin or .hex) and we have created single image (.hex) which combination of BIM file and User application (.bin) using SRECORD TOOL but as we know persistent application also needed in On-chip OAD feature, which is must because whenever OAD_RESET command is send it will boot either user application or persistent application, but as the image does not contain persistent application , hence BIM is not able to boot new image and also i think it is not able trace the user image in memory which earlier we have combined and created using SRECORD TOOL . We also tried combine persistent application but it did not worked.

So my question are :-

1) How can we create a single image for ON-chip OAD (because it requires 3 file stated above and we need combined it into single image), which tool we need to use and what is the process please explain it. Is it possible or not.

2) If we use our single image which is combination of BIM file (.hex) and User application (oad.bin) created using SRECORD which I stated above than we try to perform OAD using BTOOL so while sending new firmware it first reset the device due which it needs to boot new file but it is not able to find/trace the user application (oad.bin) file and later connection is disconnected and our earlier firmware is also erased according to me (please correct me if I am wrong). So by this I conclude that persistent application (.bin) is a necessary file to perform ON-chip OAD right ?

3) can we combine all 3 file needed for on-chip OAD using SRECORD but my query is how the BIM will know the memory address of persistent application and user application, means how it will load or boot when reset command is send by peer device using BTOOL ? (because when we flash persistent application using Uniflash we write 0x38000 address beside it .i.e referred the training module for OAD by TI )

4) What is oad_image_tool provided in sdk tool . How to use it ?

Thanks & Regards

Sandeep