• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 56 subscribers
  • Views 1166 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OAD cc2530 problem

Franz Gustav Niederheitmann
Intellectual 895 points
Other Parts Discussed in Thread: Z-STACK, CC2530, CC2530EM

Hi,

 

we are trying to develop OAD in an CC2530 with Z-Stack 2.3.0-1.4.0 and ZOAD.

we can conect the devices in ZOAD and send the .bin to them, but when we restart the CC2530 (via software and via hardware), it still has the old stack in memeory.

with the osciloscope, we watch the memory in the SmartRF05 1.71 and we saw that it is writing in the external flash.. we believe that when we reset, it is not writing in the cc2530 memory. we dont know if it cant read from external flash, or some othe problem.

does anyone has this problem?

we also try to use Daintree SNA to send the images, but it dont start to upload it.

 

Thanks,

 

Franz - LACTEC

  • 0
    TI__Mastermind 19350 points

    Hello Franz -

    I can assure you that OAD works in the Z-Stack 2.3.0-1.4.0 with ZOAD for the CC2530EM on the SmartRF05EB v1.7.1 or later. If you have an earlier EB, the external flash is not big enough - only 128k vice 256k. If you have custom H/W, communication with the external NV would definitely be suspect and should be verified with your own H/W unit test S/W. Are you waiting long enough? After selecting the target device in the ZOAD window and pressing the "Restart Device" button, it will take over 2 minutes before the device comes back up with the new image. For device restarting, you will see the ZOAD send out a status request and get a resonse with data like this:

    01 04 00

    81 04 14 01 00 ....

    The the ZOAD sends out the ZLMSGID_CODE_ENABLE  but gets no immediate response:

    05 05 06 ...

    Then in about a minute you'll see the target device send a response (that's how long it takes to calculate the CRC over the downloaded image):

    85 05 02 01 00

    Then the target device has to program that downloaded image to the run code image area and calculate the CRC again, so it will be over a minute until it comes back up on the network running the new image.

    -DH

     

  • 0 in reply to Dirty Harry
    Intellectual 895 points

    Hi Dirty Harry,

    It works. We were restarting before it does the CRCs.  Our mistake. Thanks for your tips.

    i would like to know if there is any avaliable source code form the ZOAD? we would like to do an aplication for uploading the devices, but we like to send the image in broadcast (for all the network), and this version of ZOAD can't do this.

    just another question, do you still have the magnum .44 from tv?

     

  • 0 in reply to Franz Gustav Niederheitmann
    TI__Mastermind 19350 points

    Good news, Franz.

    OAD by broadcast will be very, very tricky - it is not trivial because of the rebroadcast required by ZigBee spec, the holding time of broadcasts to not re-use a re-broadcast (10 seconds) and the max broadcasts held (6) so the OTA push rate will be slow - 6 or less every 10 seconds. I strongly advise you to get your OAD image onto a device (preferably a router), and then make that device serve the image to all instead of the dongle via ZOAD. You can use a script with Z-Tool to command one device at a time to go get the image from the router. You will see that the OTA transfer in this peer-to-peer is very fast - so fast that you may not want to take on the significant technical challenge of OAD by broadcast.

    About my Avatar - it is not so much because I bring a .44 to work (I don't, and good thing, since I would probably go through several computers per year) but because I get stuck with all of the dirty work, just like the character in that movie.

     

  • 0 in reply to Dirty Harry
    Prodigy 135 points

    Hi All

     

    I´m looking for the source code of ZOAD, it´s available?

     

    Thanks JVELL

  • 0 in reply to JVELL
    TI__Mastermind 19350 points

    Hey JVELL -

    Someone else is too:

    http://e2e.ti.com/support/low_power_rf/f/158/p/35481/124271.aspx#124271

    The source code for Z-Tool is not available for everyone. However, if you need the source code for Z-Tool, please submit a request to lpwsupport@ti.com

  • 0 in reply to JVELL
    TI__Expert 5255 points

    No, the source code for ZOAD is not available.

  • 0 in reply to xyzzy
    Intellectual 895 points

    After 6 mouth i finally got an official answer from Texas Instruments (lpwsupport@ti.com)

    "We do not provide the source code for the Windows applications ZOAD and Z-Tool."

    Ok, but why do I need to wat six mounth to receive this?

    Regards,

     

     

  • 0 in reply to Dirty Harry
    Prodigy 50 points

    hi Dirty Harry,    and all the guys  are reading this .

    I don't know if you can give me any suggestion about my cc2530 OAD problem: 

    I am using a few network elements running  the stack: 2.3.0.1.4.0   The elements are: one coordinator, one end node on which there is a

    external NV eeprom. Before starting to run ZOAD app's I have carried many RD/WR test with the enternal NV  and I succesfully restart the node even by the

    same image copied from the internal cc2530 flash , on external NV . 

    I am quite confident the OAD code modified to work with external NV is working properly.  

    I am using a dongle and ZOAD application to try to send *.img file to end node.

    I succesfuly join the network and find the device to update and also start the download of the new image file. 

    But I find the image transfer very slow : it takes over an Hour to transfer a 300K  size image.  

    Unfortunatly, at nearly 90%  download  in progress,  I didn't  end the  download process  because the ZOAD stops 

    with timeout error which I can't guess which network element is responsible for.

    Do you think the transfer is too much slow to be OK?  I saw the packet with the sniffer and they goes to the

    coordinator and then to the node. Maybe The packet are not huge in size and the transfer rate is not so fast , at a glance. 

    I find a post where they talk about  minutes of image transfer, May the OAD trasnsfer performance depend on the

    dongle version or is it possible to speed up  the transfer  setting some zigbee network parameter  on coordinator

    or on the end node? 

     

     

    Any tips are welcome

     

    Thank you

  • 0 in reply to roberto pileri
    TI__Mastermind 19350 points

    Hello -

    I remember that there had been a slowness bug in one of the Z-Stack releases, but I didn't remember which one, so I searched this forum for "OAD slow" and found a lot of threads that mention that the slowness bug is in 2.3.0 and is fixed in 2.3.1 or later.

    I would recommend you to upgrade to the latest release, 2.4.0.

    Cheers,