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.
Part Number: CC1350
I am having issue in verifying oad image, before updating OAD.
I have seen that Collector_startFwUpdate() function checks for OAD image header of 8 bytes length.
Everytime i am getting : Not a unified OAD image.
When i dig into code i found that Collector_startFwUpdate() function compares string from a .bin file with the already defined CC26X2_OAD_IMG_ID_VAL in oad_image_header.h file.
In that file i found the following #defines :
#define CC26X2_OAD_IMG_ID_VAL "CC26x2R1"#define CC13X2_OAD_IMG_ID_VAL "CC13x2R1"#define OAD_IMG_ID_VAL "OAD IMG "
i didn't found anything for CC13X0 device family.
Can anybody help me, what is the purpose of having this string compare and further more how to add CC13X0, because i want to use OAD on CC1350.
Please first refer to the following resources:
To better aid the community, please click on the "This Resolved my issue" button whenever a post answers your question!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Ryan Brown1:
Thanks for your quick response.
I went through all of the above links but couldn't find my answer.
Can you suggest some thing else more deep for OAD in BBB based collector.
In reply to Pratik Bhagat:
What issues do you experience when executing the collector CLI?
Thanks again for your reply.
Actually i am able to do OAD from collector to node, But what i found suspicious is every time in my logs i found that :" Not a unified oad image".
I want to know what is Unified image and as i am working on CC13X0 devices what i need to change in oad_image_header.h file.
kindly find the attached screenshot of my logs :
The SIMPLELINK-CC13X2-CC26X2-SDK supports multiple OAD image files due to the device's expanded flash memory and can operate through analysis of the OAD header's Image ID: http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_10_01_11/docs/ti154stack/html/ti154stack/oad-transport.html#support-for-multiple-oad-files
The SIMPLELINK-CC13X0-SDK does not have this similar feature or OAD image header structure which thus causes the notification, however it is of no concern and I am glad to hear that you have OAD operating on your devices.
Thank you so much for all your support.
Thanks for clearing my doubt.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.