CC2538: Connecting OTA Dongle port to OTA server

Raghunandana DS

Mastermind 6385 points

Part Number: CC2538

Hi,

I flashed the OTA Dongle Coordinator code to CC2538 Dev Kit with SmartRF06 EB. Using Z-Stack3.0 in IAR 7.70.2

I am trying to connect the the device OTA Dongle in OTA server with port settings:

Baudrate : 38400

Flow : None

Parity : None

StopBits : 1

DataBit : 8

But on opening I was getting as in attach"OTADonle"

over 6 years ago

0 YiKai Chen over 6 years ago

Guru 735545 points

Try to use baudrate 115200.

0 Ryan Brown1 over 6 years ago

TI__Guru**** 208987 points

Hi Raghunandana,

Have you reset the board with no debugger session? Are you connecting to the correct XDS100v3 Class USB Serial COM Port with the J5 UART back channel jumper populated?

Regards,
Ryan

0 Raghunandana DS over 6 years ago in reply to Ryan Brown1

Mastermind 6385 points

Hi, OTA Dongle is connected to OTA server and showing the Device list.
I am trying to update image with "version check image file"un-checked, I did more than 100 image notify nothing is happening but device is in network .
Trying with "Sample Switch END Device OTA Client Image-A with Bootloader" flashed initially
and trying to do OTA with "Sample Switch END Device OTA Client Image-B" BEBE-2538-BBBB2000.zigbee file

0 Ryan Brown1 over 6 years ago in reply to Raghunandana DS

TI__Guru**** 208987 points

Hi,

Are you seeing something similar in OtaServer? My ZC dongle and ZED OTA client were programmed with IAR EWARM 8.11. Removal of flow control is very important:

Regards, Ryan

0 Raghunandana DS over 6 years ago in reply to Ryan Brown1

Mastermind 6385 points

Yes same as it is

0 Ryan Brown1 over 6 years ago in reply to Raghunandana DS

TI__Guru**** 208987 points

And so it is when starting the image download (right click Client Image Notify or Dongle Broadcast Image Notify) that you experience the issue? Please provide a picture of your OtaServer if possible. It may be worth upgrading IAR versions to what is supported in this stack (8.11.1)

Regards,
Ryan

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

If you can have sniffer log, it should be helpful to check your issue.

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

ota1.rarHi Chen,

Please fin the attach for ubiqua capture, Only notify is happening

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

I see the joined device is a router type in your sniffer log. Are you sure that you "Trying with "Sample Switch END Device OTA Client Image-A with Bootloader" flashed initially" and let it join OTA server?

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

Hi chen,
OTA update is done, it some issue in my application and resolved and I am trying for ZR only. I need some info:
How to change the version number of application?
In case I did OTA with same version number of application and different image which will start run on completion of OTA?
In case my existing application is ZED, can I do OTA with ZR application, is it accept and update fine?

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

1. You can change application version number in the following structure

const preamble_t OTA_Preamble @ ".preamble" =
{
HAL_OTA_RC_MAX, // Default program length of max if not using post-processing tool.
OTA_MANUFACTURER_ID, // Manufacturer ID
OTA_TYPE_ID, // Image Type
0x00000001 // Image Version
};

2. Even you use the same version number on different image, it still starts running on completion of OTA.
3. Yes, you can update a ZED to ZR but the original network might be confused by such device. So, you should remove the device and join again after you do such kind of OTA.

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

2. Even you use the same version number on different image, it still starts running on completion of OTA.
Does is start running older image or new.
Does it auto-start run after OTA update complete

0 Raghunandana DS over 6 years ago in reply to Raghunandana DS

Mastermind 6385 points

Hi Chen,
I did OTA by updating image version as:

const preamble_t OTA_Preamble @ ".preamble" =
{
HAL_OTA_RC_MAX, // Default program length of max if not using post-processing tool.
OTA_MANUFACTURER_ID, // Manufacturer ID
OTA_TYPE_ID, // Image Type
0x00000002 // Image Version
};

But always my device is running the older image.

What I as to do to run the latest OTA updated Image?

Thank you

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

Are you sure OTA process is success?

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

I think so, as Download Complete request and response captured please check the attach

ota2.zip

0 Ryan Brown1 over 6 years ago in reply to Raghunandana DS

TI__Guru**** 208987 points

After the image download is successful as indicated by the OtaServer message, is the node deleted from the Device List and reappears after the updated device completes its OTA image update process? Make sure to carefully follow all of the C/C++ Compiler Preprocessor instructions for Images A & B, including HAL_IMG_AREA and OTA_INITIAL_IMAGE.

Regards,
Ryan

0 Raghunandana DS over 6 years ago in reply to Ryan Brown1

Mastermind 6385 points

Hi Chen,
The device is deleting from network after OTA update complete. But not re-appearing again.
ImageA_withBootLoader as defined : HAL_IMG_AREA=0 and OTA_INITIAL_IMAGE
ImageB as defined : HAL_IMG_AREA=1 (not defined OTA_INITIAL_IMAGE)
Is it need define OTA_INITIAL_IMAGE in all images

0 Raghunandana DS over 6 years ago in reply to Raghunandana DS

Mastermind 6385 points

Hi Chen,
Initially I downloaded ImageA-with Boot-loader. Then
I defined OTA_INITIAL_IMAGE in ImageB predefined macros, and changed version 0x00000002 so the device is Re-started with running ImageB few seconds after OTA complete. But not appered in the device list this time
Then I tried same steps to do OTA for ImageA (no bootloader), defined OTA_INITIAL_IMAGE with version 0x00000003, this time on calling broadcast notify in front of the device showing "No Image Was Found For Devcie"

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

You only have to define OTA_INITIAL_IMAGE when you build ImageA-with Boot-loader. You cannot define OTA_INITIAL_IMAGE in ImageB. If ImageB is download to device and device is restarted. Do you use sniffer to check what happens over the air?

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

BootAtoB.zip BtoA.rar Hi Chen,

I follwed your steps,

Again ImageA-bootload to ImageB is done

ImageB to ImageA is not happening "No Image Was Found For Devcie"

Please find the attsch's

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

BootAtoB.cubx shows Upgrade End Response and I see OTA router's link status, which means the router restarts and joins OTA server. I suppose OTA from Image A to B is success, right? For BtoA.cubx, the OTA doesn't success, OTA server doesn't respond router's Query Next Image Request after OTA starts a while.

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

So, you mean OTA server is not responding. Can know the possibilities for the issue. How can I resolve

0 YiKai Chen over 6 years ago in reply to Raghunandana DS

Guru 735545 points

I don't have OTA sever source code so I cannot guess.

0 Raghunandana DS over 6 years ago in reply to YiKai Chen

Mastermind 6385 points

Hi Chen,
At the run-time from the application can I check what Image and Version is running ? How.
At the run-time can I change the Image to be running? Eg: ImageA is running this time can I start running ImageB irrespective of version? How.
Is it possible maintain the version of application 1.0.0, 1.0.1, 1.0.2 etc like this?
How to vary Image version on every update from AtoB or BtoA, is it enough to +1 on every new is enough?

Thank you

0 Ryan Brown1 over 6 years ago in reply to Raghunandana DS

TI__Guru**** 208987 points

Raghunandana,

The value of the string version ("BBBB1000", "AAAA0000", etc. provided in Project Options -> Build Actions -> Post-build -v command) must be larger than that which was previously loaded for the download to begin without the "No Image Was Found For Device" error. For example, rename "AAAA0000" to "BBBB2000" and it will most likely work. The other option is to clear the "Version Check Image File" box in the Options menu of OtaServer but you must take caution as leaving the port open will cause continual OTA downloads of the same image.

Regards,
Ryan

0 Raghunandana DS over 6 years ago in reply to Ryan Brown1

Mastermind 6385 points

Hi Ryan,
I tried you logic its not worked, made like
""$PROJ_DIR$\..\..\..\..\tools\OTA\OtaConverter\Release\OtaConverter.exe" "$PROJ_DIR$\EndDevice - OTAClient - ImageA\Exe\EndDevice-OTAClient-ImageA.bin" -o"$PROJ_DIR$\EndDevice - OTAClient - ImageA\Exe" -t0x2538 -m0xBEBE -vBBBB2000 -pCC2538"

But "BEBE-2538-BBBB2000.zigbee" not exist in directory. So I tried with the existing "BEBE-2538-AAAA0000.zigbee" not worked same issue
again I create one file in the directory"BEBE-2538-BBBB000.zigbee" again build it and tried with ""BEBE-2538-BBBB2000.zigbee", this time also not worked
In both the case I did "UNCHECK" of "Version File Image Check"

0 Ryan Brown1 over 6 years ago in reply to Raghunandana DS

TI__Guru**** 208987 points

Try cleaning the project before rebuilding. When you say it did not work, with either the new name or check box, do you mean that you still get the "No Image Was Found For Device" warning after opening the COM Port? Try re-building and flashing all of your projects and boards as I have this system working on my end.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2538: Connecting OTA Dongle port to OTA server