Create Thread Network and Start OTA Download

Nikunj Panchani

Other Parts Discussed in Thread: CC1352R, UNIFLASH

I followed below link to create thread border router in linux-host (cc1352r).

https://hpssjellis.github.io/particle.io-photon-high-school-robotics/a17-particle-mesh/openthread/install-openthread.html

NCP device is end-device, Thread-cli example working as leader.Temp sensor is joiner device in my thread network.

was that method right to create thread network?

Now, I want to test thread mesh network demo, provide me a way to test that.

Now for OTA server, I followed this README_TTOAD.html and successfully created "ttoad-server".

In my project there is no meshcop folder as in shown above image.

Do we have any other cmd to start OTA download?

Thanks and Regards,

NIkunj Panchani

over 4 years ago

0 Toby Pan over 4 years ago

TI__Mastermind 28230 points

Hi,

The network setup you have seems fine to me.

Can you detail what you mean by "test thread mesh network demo"?

The file structure may have changed, as noted by this post.
Doing a search in the repo, otbr-commissioner is built with files in in ot-br-posix/src/commissioner. You should see otbr-commissioner there after it has built.
Note that the purpose of this command is to commission the other device (eg. doorlock) in the network, and that there are other methods to do this. The OTA download would be triggered after the device has joined the network in this case.

Regards,
Toby

0 Nikunj Panchani over 4 years ago in reply to Toby Pan

Intellectual 560 points

Hi,

I run the OAD sever using following command,

can you suggest what is wrong with server?

Why OAD is not completed successfully it only shows above logs continuously.

Thanks and Regards

Nikunj

0 Toby Pan over 4 years ago in reply to Nikunj Panchani

TI__Mastermind 28230 points

Since the NCP + linux host is used to implement the border router (and consequently the OAD server), I would recommend using the NCP as a router device rather than an end device.

Also, consider using the doorlock_oad example, since it includes the necessary changes to enable OAD. Other OAD-enabled examples are listed here.
Feel free to use them as a reference for adding OAD to the temp_sensor example.

0 Nikunj Panchani over 4 years ago in reply to Toby Pan

Intellectual 560 points

Hello community,

Now successfully downloaded image but I can't able to update new firmware

In doorlock example where I want to change version number to new version (changed #define MY_APP_SOFTWARE_VER { '0', '0', '0', '2' }).

Is this correct way to change version number??

0 Toby Pan over 4 years ago in reply to Nikunj Panchani

TI__Mastermind 28230 points

Yes, changing the version number like that should be fine.

What happens when you reset the device after the OTA?

0 Nikunj Panchani over 4 years ago in reply to Toby Pan

Intellectual 560 points

Hello Toby,

After reset older version application runs not newer that is updated through OTA

0 Toby Pan over 4 years ago in reply to Nikunj Panchani

TI__Mastermind 28230 points

"Download complete" should indicate a successful OTA.

Did you make any other modifications between the old and new images (other than MY_APP_SOFTWARE_VER) ? To verify that the new image is running?

0 Nikunj Panchani over 4 years ago in reply to Toby Pan

Intellectual 560 points

Hello Toby,

Before OTA there is string that prints "door initialized" , after OTA it changes to "Temperature sensor initialized"

0 Toby Pan over 4 years ago in reply to Nikunj Panchani

TI__Mastermind 28230 points

So you used the same doorlock_oad_secure for both images and only changed the string that was printed?

0 Nikunj Panchani over 4 years ago in reply to Toby Pan

Intellectual 560 points

Hello Toby,

Exactly I just changed string and version number only.

Any other changes required?

Thanks,

Nikunj

0 Toby Pan over 4 years ago in reply to Nikunj Panchani

TI__Mastermind 28230 points

I successfully used OAD to update device to a newer version.

Here are the steps:

In Uniflash, flash the CC26x2r1lp_bim_offchip.hex and initial binary at same time (ie. have them both selected).
1. bim can be found in <SDK>\examples\rtos\CC26X2R1_LAUNCHXL\easylink\hexfiles\offChipOad
2. initial binary, for example, will be doorlock_oad_secure_v1.bin (make sure to use the .bin)
Change version number, and anything else you'd like in the project, then rebuild.
Use the .bin from this newly built project (eg. doorlock_oad_secure_v2.bin) for ttoad-server.
Start ttoad-server, then join the device (which is loaded with doorlock_oad_secure_v1.bin).

In general, for OAD projects, use the .bin file instead of the .hex file.
For more information on OAD, refer to http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/thread/html/thread-guide/oad-index.html

Zigbee & Thread

Zigbee & Thread forum

Create Thread Network and Start OTA Download