• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 262 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2652R: CC2652 Zigbee OTA firmware upgrade

CC2340R5: How to use the otaServer tool to start an OTA upgrade?

senjin
Intellectual 260 points
Part Number: CC2340R5
Other Parts Discussed in Thread: CC2652P, CC1352P, , UNIFLASH

Tool/software:

testing environment

ZC, cc2652p,  zc_ota_server_CC1352P_2_LAUNCHXL_tirtos7_ticlang, sdk:simplelink_cc13xx_cc26xx_sdk_7_41_00_17

ZED, CC234R5, onoff_switch_ota_client_onchip_LP_EM_CC2340R5_freertos_ticlang, sdk:simplelink_lowpower_f3_sdk_8_40_02_01

I have now set up the network for ZC and added ZED to the network. I have catched the relevant packets through packet capture tools. I am now using the OtaServer tool to upgrade, but I do not know how to do it. I did not find any relevant guidance in the document /docs/zigbee/html/zigbee/ota_upgrade.html. 

In addition, considering that my application will consume more flash space than ota_client, I plan to increase its image size instead of using the method where custom APP and ota_client each occupy half of the space.  When the custom application receives an upgrade notification, reset the device and then jump to ota_client image to perform the upgrade operation.  I would like to ask if this method is feasible and what operations my APP should do.

  • 0
    TI__Guru**** 214197 points

    Hi Senjin,

    Please follow the Zigbee OTA SimpleLink Academy Lab for instructions with using OtaServer.  Use a sniffer to confirm that your ZED has joined the network and is requesting OTA image update information.  Let me know if you encounter any trouble with using the guidance provided.

    TI is developing further options for Zigbee OTA software updates to save on additional user application memory, please reach out offline to further discuss these.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 260 points

    Hi Ryan,

    I know from the academy document that when ZED joins the network, there is no need to do anything, just wait for the OTA to start.  However, I found that the OTA never started. I observed in LOG that ZED sent query next image request, but ZC did not respond. Also, I observed 'Image Found' in the OtaServer tool, indicating that the upgrade file can be identified. I have added sniffer log to the attachment.

    I don't know which operation is wrong to cause this problem, can you help me analyze it, thank you.

    OTA LOG.zip

  • +1 in reply to senjin
    TI__Guru**** 214197 points

    Hi Senjin,

    I just re-tested the SimpleLink F3 SDK v8.40.02.01 Zigbee on-chip OTA to confirm that everything is correct.  The OTA upgrade begins without any errors after following the SLA.  Please note that MCUBoot settings are slightly different than noted in the SLA, which is to be expected given that the SLA does not update for every SDK release.

    The ZED's Next Image Request packet contents are exactly like I would expect, however the ZC does not provide a Response (ignore this Image Size as this is a reference from another off-chip example).

    Thus there is an issue either with the ZC OTA server project (I tested with the same SDK using a default configuration) or the candidate image (BEBE-2340-0000000X.zigbee).  I have provided the candidate I used in my test for you to try (assuming you are using the same MCUBoot settings, the Zigbee OTA on-chip project from the F3 SDK v8.40.02.01, and loading both in Uniflash correctly).  Make sure the flash memory is erased on both devices before programming the respective images for the test.

    BEBE-2340-00000002.zigbee

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 260 points

    Thanks, Thank you for your guidance. The problem is solved. In the mcuboot project, I chose the wrong upgrad mode.  In addition, when I was using the serial port tool, I mistakenly enabled the flow control function.