OTA_boot.bin project

Hi Jason,

firstly for the OTA Boot workspace, I just want to check the firmware should go into the main function, but until now I can't go into the main function, it just stuck at some startup code, I don't know.

secondly, I send the BEBE-2538-BBBB0000.zigbee file compiling from OTAClient-ImageB through OtaServer v2.0.7.

by the way after finishing the OTA process, I don't find the project reset because I set a breakpoint at the main function of the first line.

The OTA boot project is the same in Z-Stack Home 1.2.2a and I attached my boot.bin.

Boot.zip

Attached!

cc2538-icf.zip

Dear Chen,

the issue is still exist, can you help me do the test of project OTA_Boot, in my opinion If we just only download this bootloader project, the program must go into the main function, but I can not arrive the main function.

Can you please do it for me just open the OTA_bin project and download it?

Thank you very much, any information is appiciated.

BR,

8637.Z-Stack OTA Upgrade User's Guide.pdf

Do you read section 2.4.7.1 CC2538 Cortex-M3 SoC?

On the CC2538, downloaded images are not relocated and are instead “run-in-place”, a feature of the Cortex-M3.
The OTA example software for the CC2538 demonstrates how to maintain two images in the on-chip flash. These
are referred to as “Image A” and “Image B”. To accomplish this, the flash storage is allocated as depicted in the
following diagram. Note that a non-OTA memory map is included for comparison:

Note that the Image Boot Manager (OTA boot loader), for CC2538, resides in the Lock Bits page. Also note the
special “Ledger” page. This is used by the Boot Manager to maintain a record of the latest downloaded image and
to determine which image in flash to execute at boot time. A ledger entry consists of two CRCs values for a
particular image (shadow and actual) and a pointer to the top of the image’s Interrupt Vector Table (INTVEC)
which contains, among other things, an initial stack pointer and the list of interrupt handlers including the reset
handler for that image.
Although the default settings are to evenly divide, in half, the flash not used by the NV and the Ledger, this is not
mandator. The Image-A and Image-B code areas can be re-sized as desired by changing the definitions in the boardspecific hal_board_cfg.h file as well as making corresponding changes to the two image linker control files):
Components\hal\target\CC2538\hal_board_cfg.h
Projects\zstack\Tools\CC2538DB\ CC2538-OTA-Image-A.icf
Projects\zstack\Tools\CC2538DB\ CC2538-OTA-Image-B.icf
To program the OTA Image Boot Manager, a combined binary image must be built that integrates the OTA Image
Boot Manager, the OTA Client Application (eg. Z-Stack Home SampleSwitch or Z-Stack Energy SampleApp) and
the optional certificates in the case of an SE OTA Client Application. This process is described in more detail in
section 3.2.2 .

thank you for your so quick reply.
I have checked the section of 2.4.7.1. and most of the work I have done like icf file and hal_board_cfg.h file's modification.
and now I want to know the ledger page, I have checked the source code and it call HalOTARead(HAL_NVIC_OSET,    (uint8 *)ledger.nvicJump, sizeof(((ota_ledger_t *)0)->nvicJump), HAL_OTA_DL); in function HalOTAInvRC() to read the jump address and set the ledger page for the jump address of image for boot to get the jump address after reset, but now I didn't find where to set the jump address, I just want to know how to set the jump address for this?
Thanks and waiting for your reply.

BR,

It's defined as the followings:

in hal_ota.h

#define HAL_OTA_RC_ADDR            HAL_IMG_B_BEG
#define HAL_OTA_DL_ADDR            HAL_IMG_A_BEG

in hal_board_cfg.h

#define HAL_IMG_A_BEG             FLASH_BASE
#define HAL_IMG_B_BEG            (FLASH_BASE + 0x0003E000)

BR,

I cannot see your attachment.

Yes, according to your I change the version to DDDD0000, because now my Run Code version is CCCC0000, it can download again.

but the other question is that after I download the version DDDD0000 ok and I rebuild the imageB source code to change version to EEEE0000, it also can download agagin.

but as we know from the user's guide of OTA:

3.2.2.2 Building Image A/B Sample Applications for CC2538
With the initial Image A OTA client with Bootloader now programmed into the target hardware, your first OTA transfer image must be built as an Image B. When the transfer is complete, the target will reset and boot the new Image B. The next OTA transfer must be an Image A. This ping-ponging between Image A and B is necessary to take advantage of the run-in-place feature of the CC2538.

I was confused about this, can it will be wrong after not according to the A-B-A download order?