Part Number: CC2642R-Q1
Other Parts Discussed in Thread: CC2642R
Hello,
We are trying to replicate the simple link connect Mobile App's OAD firmware update feature on our mobile app for CC2642R. We have used the standard simple peripheral on chip and persistent app firmwares for our development. We had few questions about the same.
Firmware bin file was already generated using the post-build tool of CC26xx SDK. As per our knowledge, we found out that the initial header information size is 44 bytes. After sending the header, we would receive 0x00 (SUCCESS) so that we can now send the firmware in blocks of 16 bytes with the initial 2 bytes allocated for the block number (which has to be copied from the notification data).
However in our implementation of the Mobile App, inspite of sending the first 44 bytes of the header data (fetched from the start of the generated bin file), we are receiving 0x09 which denotes the hardware is rejecting the header.
So can you explain the steps or is there any documentation given which explains how many bytes of data to be sent to which characteristic and how to interpret the responses of the example project.
Eg. What data is to be sent via header, how to send payload and how to reset the program to the new firmware
