Regarding OTA using Low power RF

Ravindra Kant

Other Parts Discussed in Thread: CC2530, Z-STACK

Hi all,i Just want to ask the application Texas Instruments\Z-Stack Home 1.2.2.42930\Projects\zstack\OTA\Boot\CC2530DB\boot.ewww has to be pre burnt into the cc2530 SoC before OAD or it just has to be added in the application.

over 10 years ago

0 YiKai Chen over 10 years ago

Guru 735695 points

First, you have to build a hex file which contains boot loader and download it to CC2530. Then, the OTA image doesn't have to contain boot loader.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

will it work if i am implementing the OTA using SMART rf technology but not using Z -stack??

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

What do you mean smart RF technology?

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Sir almost all the tutorials given on OTA are implemented on z-stack .

0 Ravindra Kant over 10 years ago in reply to Ravindra Kant

Expert 1825 points

how to extract manufacturer id ,version no,image type if ota image converter is not working???

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

OTA is defined by Zigbee spec so it is implemented in Z-Stack. I still don't understand where your problem is.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Mostly current image file or RC image has manufacturer id ,version no ,image type ,image header
now if new image is coming Over the air or DL image the boot loader will compare the above spec especially version no .My question is how to get those data?version no and all..

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

I don't have source code of OTA server so I don't know how it get those data. If you have to know it, I suggest you to contact TI local representative to sign NDA and SLA to get source code and related information.

0 Sjef de Krijger over 10 years ago

Expert 1405 points

First of all, the bootloader does not use manufacturer ID, version or type. It has no concept of this, it just checks the CRC of an image and if it is correct then it will LJMP to the image to boot it.

The selection of a suitable OTA image file is done by methods built into the ZCL OTA Cluster and those methods are implemented in the application image, not the bootloader (naturally, because requiring a running Zigbee network stack).

The manufacturer ID, version and image type are in the header of a standard Zigbee OTA image file, defined in the specification (ZigBee Document 095264). The image generated by IAR has this data in the fixed address 'PREAMBLE' code section, the address defined in linker config ota.xcl.

0 Ravindra Kant over 10 years ago in reply to Sjef de Krijger

Expert 1825 points

.The bootloader C:\Texas Instruments\Z-Stack Home 1.2.2.42930\Projects\zstack\OTA\Boot\CC2530DB it replaces the current image with the downloaded image.

what it actually do it replaces the hex contents or anything else?

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

It is a boot loader that would bring of the application.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Hello sir,
if i am receiving the hex contents over the air and saved those data into the flash of cc2530 now will bootloader will program the controller with the new hex contents or not.

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

Actually, you would receive binary not hex image over the air and save binary into CC2530 flash. It's your application would save binary into CC2530 flash and restart system.Then, boot loader will start system again with new application.

0 Ravindra Kant over 10 years ago in reply to Ravindra Kant

Expert 1825 points

In that case i just have to provide the page no . at which i have stored the data into the flash or the bootloader will take it automatically??

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

This part is implemented in OTA boot loader.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Sir,
Is it possible to find out at which location in the flash current code or running code is written to?

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

You can refer to dl2rc in hal_ota.c.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Hi All,
how much packet size is allowed while transmitting and receiving data from cc2530 Radio through RF?
problem:I am sending data from one cc2530 module to another but only 51 bytes can be sent and received ,if data goes over 51 bytes the mrfilinkrecv function returns length of data received is 0.

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

I can send around 80 bytes in a single packet when I uses Z-Stack. Do you use Z-Stack?

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

No,sir i am not using Z-stack.
but yes as it is written in the user guide of cc2530 that max RX FIFO can be of 128 bytes still i am unable to send more than 51 bytes?

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

I think there must be something wrong in your code. It should be no problem to send more than 51 bytes.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Sir,
The CODE space in cc2530 is 64 KB and XDATA XBANK has 32 Kb of space .Now is it possible at which location the current firmware is stored and also if possible ,what are the address of pages that are blank.Now if the new data is more than 32 Kb than it is possible to map it on the flash.

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

I don't understand your question well. Can you elaborate?

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

is it possible to find out from which page no my current firmware is started ???

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

If your application use OTA, the code mapping is assigned in ota.xcl which you can have a look.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

What is the meaning of -P(CODE) ,-D(CODE)and -Z (CODE) in the linker files.If i have to update the firmware what line i have to add in the linker file.

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

You can refer to supp.iar.com/.../xlink.ENU.pdf.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

sir,

I am using the SoC cc2530F256 ,while writing the data onto the flash i had given the destination page no from 32 which when i cross checked on the Logical Code memory i get the data is written on the address 28000(at this position Bank 2 Starts).

-D_BANK0_START=0x00000 //0 // Note: Unconventional bank numbering on this part: //value assinged to the symbol option -D
-D_BANK0_END=0x07FFF //15 // "BANK0" is the root bank/common area!
//
-D_BANK1_START=0x18000
-D_BANK1_END=0x1FFFF

Reserved Area

-D_BANK2_START=0x28000
-D_BANK2_END=0x2FFFF

Reserved Area

-D_BANK3_START=0x38000
-D_BANK3_END=0x3FFFF

Reserved Area

-D_BANK4_START=0x48000
-D_BANK4_END=0x4FFFF

Reserved Area

-D_BANK5_START=0x58000
-D_BANK5_END=0x5FFFF

Reserved Area

-D_BANK6_START=0x68000
-D_BANK6_END=0x6FFFF

Reserved Area

-D_BANK7_START=0x78000
-D_BANK7_END=0x7FFFF
/

my question is how the page nos are defined and are the reserved area is counted in the pages?

and also if the data gets more than 32 Kb then the upcoming data get directly to the new bank?

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

The default xcl file would works fine. Why do you want to change anything in xcl?

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

#defined HAL_OTA_DL_MAX 0x40000 in the file C:\Texas Instruments\Z-Stack Home 1.2.2.42930\Projects\zstack\OTA\Boot\CC2530DB

I am unable to understand why the maximum size is 0X40000

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

Because the flash size of CC2530 for OTA is 256K.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

hello sir,
I have stored the data onto the flash now i want to replace the current firmware with the downloaded data into the flash,since writing the flash during run time is only possible through RAM.can you suggest how to move forward?

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

Sorry, I don't know how to do this. That's why we use boot loader.

0 Ravindra Kant over 10 years ago in reply to YiKai Chen

Expert 1825 points

Sir,
Continuing the old thread ,thanks for bearing with me,
The 51 bytes i have received over the air is been stored onto the flash.My question is if there is some kind of data loss through the RF ,how would i ensure it?What specific condition i should set in my program so that i could avoid data loss??

0 YiKai Chen over 10 years ago in reply to Ravindra Kant

Guru 735695 points

Z-Stack zcl_ota.c has implemented retry mechanism. You can check "if ( events & ZCL_OTA_BLOCK_RSP_TO_EVT )" in zclOTA_event_loop.

0 embRTS over 9 years ago in reply to YiKai Chen

Expert 1125 points

HI Yikai,

I have done the image writing in the EXTERNAL Flash Memory via SPI using CC2530 and Image downloaded from OTA Dongle ( Coordinator ) is SUCCESSFUL and Node is restarting also,

Now I have edited the f8w2530 config file as per the ota.xclZ-Stack OTA Upgrade User's Guide.pdf

CODE_START - 0x0800 ( earlier it was 0x0000 )

and added CRC Option

I have done the integration of hex files of Boot Code and Node Firmware also as per the steps mentioned in page 44 of the pdf attached here with,

I have found the boot code is not able to execute jump to 0x800 location

then I tried debugging that and TRIED to check the function dl2rc()

and i found if i keep only two things in the boot code

one is dl2rc()

and other one is that JUMP instruction to 0x0800

again the integrated code ( Boot + Node Firmware ) is not working ( it means the boot code is not able to execute Jump Instruction to 0x0800 )

So Finally in the boot code I disabled the function dl2rc() and keep that Ljump instruction ( 0x0800 )

the Running code started working

like the Node Device announce and every thing as usual like the how the node firmware works

what could be the problem ?

0 YiKai Chen over 9 years ago in reply to embRTS

Guru 735695 points

It look like the OTA image on your external memory is broken. You should check this part.

0 embRTS over 9 years ago in reply to YiKai Chen

Expert 1125 points

Hi yikai

But the CRC verification for the downloaded inage after 100 percent download is successful

0 YiKai Chen over 9 years ago in reply to embRTS

Guru 735695 points

If boot loader break from dl2rc, it means the image is incorrect. I can only suggest you to check it. By the way, have you test OTA function successfully in SampleSiwtch example?

0 embRTS over 9 years ago in reply to YiKai Chen

Expert 1125 points

The ota download part is working perfectly i mean that image writing to external flash and then rerarting reading the ota cluster's attributes with the upgraded vesion number and all

0 YiKai Chen over 9 years ago in reply to embRTS

Guru 735695 points

It looks so but boot loader have to read image from your external memory and write it to CC2530 flash. If you think image on external memory is good, you should check read part in boot loader.

0 embRTS over 9 years ago in reply to YiKai Chen

Expert 1125 points

I have simulated halFalshWrite

with reading in halFalshRead and verifying that correct data is written, and that has also been successful

Any settings still am I missing, Please suggest Yiaki

0 YiKai Chen over 9 years ago in reply to embRTS

Guru 735695 points

Run out of idea why you cannot make it work @@

0 embRTS over 9 years ago in reply to YiKai Chen

Expert 1125 points

Hi Yikai

after lot of findings

I have noticed one difference

I created two hex files

1.>< One with Download to RC function >

2.>< one WITHOUT dl2rc function >

and burnt the hex file and READ back the two hex files from MCU to PC using read_flash Option

The header string varies in the two cases

1.> RED COLOUR Pop up - when dl2rc() function is included in the Boot Code

2.> GREEN Colour Po up - WITHOUT dl2rc function

I am running out of idea, what is your Suggestion on this

can it be the reason ?

Please refer the image attached

0 embRTS over 9 years ago in reply to embRTS

Expert 1125 points

HI Yikai

Finally it is working
I have added the config File ota.xcl directly
I have one doubt

In f8w2530.xcl file ( Line 108 ) Z(DATA)VREG+_NR_OF_VIRTUAL_REGISTERS=08-7F

In ota.xcl file (Line 109) - Z(DATA)VREG=08-7F

As this is the only change in this both file and I have used ota.xcl file then it started working

One Problem is also there when using ota.xcl, I am not able to combine the boot code and Node Running code using the test Editor and when I combined and tried to burnt the FLASH Programmer is giving an error ( Memory Exceeded )

**** What I have done for time being ( Used the Node Code <with f8w2530.xcl file and boot code ), then created Node Image file using ota.xcl file and updating the Code via OTA *****

Zigbee & Thread

Zigbee & Thread forum

Regarding OTA using Low power RF