Zigbee OTA application

[deepanrajanbara]

Hi,

We are using nxp Zigbee device as co-ordinator which is flashed with control bridge application.

Please let us know how to generate .ota file for the 3rd party sensor so that we can update the sensor from nxp coordinator.

Also with reference to ZWGUI tool we have implemented source code to do the OTA process. 

When we do OTA with the ZWGUI tool to the end sensor it takes around 20 mins to complete. but the same thing we have implemented in which it takes around 1hr to complete the OTA and the end device is not updated with the latest firmware also.

Once after the OTA is complete we receive the end response. But as soon as we receive the end response we get the OTA Block response from the end device and the whole process begin again.

Is there any command to stop the OTA process from the end sensor or the co-ordinator to identify not to send response.

Please let us debug this issue.Provide your feedback

Thank you,

Deepanraj

[mario_castaneda]

Hi Deepanraj,

As you tested this OTA update requires the same OTA cluster in the end device, in this case. Look at the E_SL_MSG_BLOCK_SEND routine in the app_Zns_cmds.c  file

Please look at the commands that you could send to the Control Bridge.

    /* OTA Cluster */
    E_SL_MSG_LOAD_NEW_IMAGE                                     =  0x0500,
    E_SL_MSG_BLOCK_REQUEST                                      =  0x8501,
    E_SL_MSG_BLOCK_SEND                                         =  0x0502,
    E_SL_MSG_UPGRADE_END_REQUEST                                =  0x8503,
    E_SL_MSG_UPGRADE_END_RESPONSE                               =  0x0504,
    E_SL_MSG_IMAGE_NOTIFY                                       =  0x0505,
    E_SL_MSG_SEND_WAIT_FOR_DATA_PARAMS                          =  0x0506,
    E_SL_MSG_SEND_RAW_APS_DATA_PACKET                           =  0x0530,
‍‍‍‍‍‍‍‍‍

hope it helps.

Regards,

Mario

[deepanrajanbara]

Hi,

After OTA is complete the End request status is 0x95. Please let us know what could be the cause of this issue. 

What could be the reason for the end device to returns 0x95. 

[mario_castaneda]

Hi Deepanraj,

Is it possible that you could provide your sniffer log of all of this process? I know that it could be very long, but it will help us to debug your issue.

Regards,

Mario

[deepanrajanbara]

Hi Mario,

Thanks for the support, Actually due to the lockdown we do not have the sniffer setup with us. Please let us know, whether this issue is related to the timeout value while waiting for block response. Also how to increase the timeout value in this case. Does the timeout value need to be increased in the co-ordinator or end device side.

Thank you,

Deepanraj.A

[mario_castaneda]

Hi Deepanraj,

Do you have a USB JN516x Dongle? However, you could program one of your JN devices with the sniffer SW that we provide. C:\NXP\bstudio_nxp\sdk\JN-SW-4170\Tools\JennicSniffer

Note: The JN Sniffer only works with the Ubiqua Software

We have to be sure what is happening, and the sniffer could provide a better reference.

Regards,

Mario

[deepanrajanbara]

Hi Mario,

Please find the sniffer logs attached and below is the transport key.

Trust Centre Key

5a6967426565416c6c69616e63653039

Transport Keys

f1029f587d1e0bd4c9fa3710d596230c

3643acc192ef684dae5be4998a8720a5

Thank you,

Deepanraj.A

[mario_castaneda]

Hi Deepanraj Anbarasan,

Please let me know if you still facing the OTA issue.

Regards,

Mario

[deepanrajanbara]

Hi Mario,

The issue is fixed it was due to some bytes mismatch.

Thank you,

Deepanraj.A

[mario_castaneda]

Hi Deepanraj,

I am sorry, I think the sniffer log has some issues, I can not see the packets correctly, could you please share it again?

Regards,

Mario

[deepanrajanbara]

Actually we are following the same and the end device also supports OTA cluster. Our issue is that it takes longer time to complete the update. Also after the update is complete the END OTA Request status is as 0x95 which corresponds to ABORT. Also let us know, How to generate the .ota file since we are only able to generate .zigbee file.

Please help us know what is the reason for this ABORT status code and how can we correct this.

Thank you,

Deepanraj