%20(2).png "sivatejareddyva"){kind=avatar}
Hello Siva,
Glad to hear you have been progressing with your application.
Yes, Test Tool breaks the file into fragments. Take a look at the following screenshot:
What I've highlighted are the initial bytes that were send when I've initiated the transfer of two different files. The first one was too large for Test Tool (1.2 MB) and broke after the two chunks sent, and the second successfully sent the file with, by adding FF padding to multiple of 1 KB I believe.
Observations:
- Test Tool OTA transfer was not created for regular file transfers; for example it doesn't work for big files (at 1.2 MB it cracked for me)
- you should transmit the size beforehand so that you would know how many bytes you will need: it seems that first 66 bytes (first chunk and 2 bytes from chunk 2) are filled with information about image
- don't forget to add the OTA bootloader on the client (even though you will not use it to rewrite the image, it seems that it OTA client isn't working without it);
- after I gave some thought to OTA transfer, I came to the conclusion that the other approach, with CoAP messages exchange, is better; even though there is more work to do, you can control exactly how you want to send the file;
Best of luck,
Lilian
Hello Siva,
Glad to hear you have been progressing with your application.
Yes, Test Tool breaks the file into fragments. Take a look at the following screenshot:
What I've highlighted are the initial bytes that were send when I've initiated the transfer of two different files. The first one was too large for Test Tool (1.2 MB) and broke after the two chunks sent, and the second successfully sent the file with, by adding FF padding to multiple of 1 KB I believe.
Observations:
- Test Tool OTA transfer was not created for regular file transfers; for example it doesn't work for big files (at 1.2 MB it cracked for me)
- you should transmit the size beforehand so that you would know how many bytes you will need: it seems that first 66 bytes (first chunk and 2 bytes from chunk 2) are filled with information about image
- don't forget to add the OTA bootloader on the client (even though you will not use it to rewrite the image, it seems that it OTA client isn't working without it);
- after I gave some thought to OTA transfer, I came to the conclusion that the other approach, with CoAP messages exchange, is better; even though there is more work to do, you can control exactly how you want to send the file;
Best of luck,
Lilian
Hello Lillian,
Please look at the image below
I have generated a .bin out of my .xml and started OTA with out looking at the register address which has crashed the client as expected. I think i can flash it with original.
Is there any information about setting up new register address ? can Test tool help in modifying that ?
if it is possible, how do i read the transferred data on the client side ?
Regards,
Siva
Hi Siva,
If you want to use the OTA approach you have to modify "OTA_PushImageChunk" function call from "OtaClient_UpgradeImage" function, found in *sdk_folder*\middleware\wireless\nwk_ip_1.2.5\examples\common\app_ota_client.c file.
Your function replacement should take the chunk and send it on serial to the destination computer. The function that helps you do this is "THCI_transmitPayload", found in *sdk_folder*\middleware\wireless\nwk_ip_1.2.5\base\thci\thci.c. Define a new OpCode in "nwkOpCode_t" enum found in *sdk_folder*\middleware\wireless\nwk_ip_1.2.5\base\interface\thci.h, so that you would know what kind of message you will get.
Now you have to reassemble the chunks into the file.xml on the destination computer.
Observations:
- make sure that you have in the project THREAD_USE_THCI enabled on both, the server and the client. (found in .\middleware\wireless\nwk_ip_1.2.5\examples\reed_ota_client\config\config.h)
- you should use "reed_ota_client" from the SDK to receive the file and "hcd_ota_server" to transfer it. More informations about OTA transfer in *sdk_folder*\docs\wireless\Thread\Kinetis Thread Stack Over-the-Air (OTA) Firmware Update User's Guide.pdf
Another approach would be to send COAP messages. Requirements and observations:
- both devices should be host_controlled_device (not necessary, but recommended)
- you can simulate the transmission of chunks with TestTool for debug. See the picture attached bellow. You should create URI path for this type of messages, (name it as you want, e.g. "/xml") and use it when you initialize the COAP instance (see function "APP_SendLedCommand" from *sdk_fldr*\middleware\wireless\nwk_ip_1.2.5\examples\reed_ota_client\src\router_eligible_device_app_ota_client.c so you will make and idea how your function should look like);
- now the continuation is similar to the OTA approach; send on the serial the chunks and reassemble them on the computer, see the details above
I hope the information I provided will be helpful.
Regards,
Lilian
