CC2652P: On-chip OAD fails using SDK4.3 BIM + SDK4.4 APP

Shuyang Zhong

Part Number: CC2652P
Other Parts Discussed in Thread: UNIFLASH

Hi team,

I noticed a new requirement is added in the chapter "Setting up the BLE OAD Environment" of BLE stack user's guide:

Uniflash must be used to flash the _oad.bin persistent image that is produced by the oad_image_tool or the device will not boot after a reset. When flashing the persistent image .bin file, you must specify the binary load address as the starting address specified in the persistent application project’s linker file. By default, this is at address: 0x00038000.

This leads to a question: if I used the BIM and persistent APP from previous SDK which I did not specify the address during flashing, I was able to perform an OAD to an application image based on SDK4.4. But at this moment, the attemption of performing another OAD with the combination of BIM and Persistent APP from SDK4.3 + application from SDK4.4 will fail. This leads to an inconsistency of the OAD ability between SDKs in the end.

I'm not very clear about the exact reason why the combination of SDK4.3 BIM + SDK4.4 APP would fail, could anyone please help explain? And is there a workaround for the scenario described as above?

Thanks.

BR,

Shuyang

over 5 years ago

0 Jan over 5 years ago

TI__Mastermind 44770 points

Hello Shuyang,

I have assigned an expert to this thread to help with your inquiry.

Sincerely,

Jan

0 Luis M over 5 years ago

TI__Expert 5345 points

Shuyang,

I'm investigating the issue you brought up. Please give me a couple of days to respond.

Thanks,

Luis

0 Luis M over 5 years ago in reply to Luis M

TI__Expert 5345 points

Shuyang,

We don't have an answer from our dev team yet. I'll keep you posted.

-Luis

0 Shuyang Zhong over 5 years ago in reply to Luis M

TI__Expert 5115 points

Hi Luis,

Thanks for keep tracking this. The simplist way to reproduce this is to flash the CC2652 with the persistent_app and BIM_onchip from SDK_4_30_00_54, plus the simple_peripheral_oad_onchip example from SDK_4_40_04_04 (without specify the address for persistent_app). Please try if this helps.

BR,

Shuyang

0 Luis M over 5 years ago in reply to Shuyang Zhong

TI__Expert 5345 points

Hi,

I will try to reproduce the behavior you describe. In the meantime, can you please check carefully if this thread answers your question?

Thank you,

Luis

0 Shuyang Zhong over 5 years ago in reply to Luis M

TI__Expert 5115 points

Hi Luis,

Thanks for reminding me of this post, the problem is exactly the same as mine.

I understand the user needs to manually set the address offset when using SDK4.40, my question is that the SDKs before did not have the requirement, thus the user would not set the offset in old SDKs. But if a customer wants to update their application with OAD from and old SDK to 4.40, the OAD will not success.

Is there a work-around to make the OAD under this condition be backward compatible?

Best regards,

Shuyang

0 Luis M over 5 years ago in reply to Shuyang Zhong

TI__Expert 5345 points

Thanks Shuyang,

I'm trying to find the answer with my team. Please allow me a few days to get the answer.

Thanks,

Luis

Bluetooth®︎

Bluetooth forum

CC2652P: On-chip OAD fails using SDK4.3 BIM + SDK4.4 APP