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.

RTOS/CC2538: OTA upgrade getting problem

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK

Tool/software: TI-RTOS

Hi,

We are trying to do OTA upgrade in cc2538 between Coordinator and router. Its happening but very slowly. 0.02% per sec it's transferring. The total size of .zigbee file is 145kb.

It's happening till 0.30% to 0.80% only, after that we are getting the below error (Attached Image).

Error: OtaServer Firmware Timeout

if this message appears just after program start

please confirm that the port settings are correct

the com port has been automatically closed

 


how to solve this problem?

Thanks in advance,

shiva

  • Hi shiva,

    Which Z-Stack version are you using? Have you first attempted "Using The Sample OTA Applications" (Section 3) of the Z-Stack OTA Upgrade User's Guide? The added bootloader functionality and preprocessor definitions are very important. Afterwards you've then followed all "Adding Client Functionality to an Application" instructions? Would you be able to provide a sniffer log? e2e.ti.com/.../

    Regards,
    Ryan
  • Hello Ryan,

    we are using Z-stack 3.0. Using The Sample OTA Applications its working fine.

    The definitions and all other functionalities we have completed. Please find the attached sniffer log.

    abcd02.rar

  • Hello shiva,

    What is the private cluster that the router OTA server sends to the coordinator OTA client starting in packet 221? This appears to disrupt OTAServer operation as the MAC ACKs cease and the coordinator becomes unresponsive to router requests. If possible, disable this cluster operation in your application until the OTA completes and see if this fixes the issue.

    Regards,
    Ryan
  • Hello Ryan,

    Thanks for your reply, your suggestion solved our problem between example Coordinator and our own router. But still, the error remaining in our own Coordinator and our own router.

    I have attached the capture file, I didn't get any idea from this capture, so please see the capture and help us. 

    it's stopping at 0.80%. Other than Coordinator code The router code, image A, Image B everything is same. So the problem is with Coordinator only.

    Regards & Thanks,

    Shiva.

  • Hello Shiva,

    What are all the differences between your coordinator and the Z-Stack 3.0 CC2538 OTA Dongle example project? Once the OtaServer GUI starts sending an image then the coordinator should halt other high-level processes until the update finishes. You can now compare sniffer logs and logic analyzer screenshots (of UART communication) between the working and broken instances to debug the issue.

    Regards,
    Ryan
  • Thank you Ryan, 

    The problem has been solved. We are writing our data in UART that's making the problem. We removed those things, now its working fine.

    Now, we built image A with the bootloader (0x00000001  // Image Version), then via OTA, we upgraded image B alone (0x00000002  // Image Version). It's working fine. But,

    After image B upgrade we are trying to upgrade next version of image A (0x00000003  // Image Version). Here we are getting the problem.

    It's not upgrading, it's showing "No image was found for Device". How to solve this?

    If we uncheck "Version check image file" its working fine. So where was the problem?

    Please check the below image: 

    Thanks & Regards,

    Shiva

  • Please see the marked answer in the following: e2e.ti.com/.../680983

    Regards,
    Ryan