Hi,
Would like to know if it is at all possible to link BLE projects to a common library that is used by Bootloader (BIM), Image A or Image B?
Cheers,
Jerome
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.
Hi,
Would like to know if it is at all possible to link BLE projects to a common library that is used by Bootloader (BIM), Image A or Image B?
Cheers,
Jerome
Hi Jerome,
I'm not sure what you are asking for but the SensorTag example project have build configurations with common libraries for Image A and Image B. You could potentially do this for other sample applications as well.
Best Regards
Joakim
Hi Joakim,
Sorry I should made myself more clear.
I am aware there are common libraries there used by Image A and Image B that have been packaged by TI. What I was referring to was a common library that belonged to a particular area in flash. Is that possible to have both Image A and Image B to use that same library? I know the NVM can be used as shared memory between the images, but I need more than that (i.e. a custom library).
From my understanding, if Image A and Image B both link to a common library (eg. CC2540_BLE_per.lib), that library is still individually packaged in each Image A and Image B binary. i.e. Image A and Image B both have the binaries of the common library (eg. CC2540_BLE_per.lib). Please correct me if I am wrong.
Cheers,
Jerome
Hi Jerome,
I get your point now. It would be a good solution on the code redundancy introduced with the OAD architecture. However, the solution was created to be able to update the stack version as well as application so those have to be bundled.
For the future we are looking into a solution where the application part can be updated individually.
Best Regards
Joakim