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.

CC2530: Some issues about CC2530 SBL upgrade firmware.

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

Hi team,

Here's the request from the customer:

Requirements: Updating the firmware of the CC2530 via serial port, current protocol stack version is 2.5.1a. Customer planned to achieve free switching of Z STACK between 3.0.2 and 2.5.1a by the host machine.

Progress: Refer to the document " Serial Boot Loader for CC2530 ", the ability to write firmware using the serial port was successfully implemented using the SerialBootTool and confirm with flash programmer that there is no problem with the writing data.

Problem Points: The program used to work normally, but after writing into the chip through the above scheme, it is found that the chip cannot work normally. (Taking ROUTER as an example, it is found that it cannot connect to the network normally after it is powered on.) It is now certain that the program was successfully jumped from boot to app, but the app is not working properly. Customer thinks that the modification is done strictly by reference to the document, is there a similar case to discuss? In addition to the program offset, are there other offsets that need to be set? Through online simulation, it is found that the program is stuck in "HAL_BOARD_INIT" After trun off interrupts, it will not run.

In addition, the hex generated from the above document is burned directly into the chip using the flash programr without stitching the boot section.Does it work?

Could you help check this case? Thanks.

Best Regards,                                                        

Nick

  • Hi Nick,

    Based on the description it appears that the Serial Boot Loader design is operating as intended.  Has the customer evaluated a default Z-Stack 3.0.2 example without the Boot Loader?  Are they attempting a fresh join to a Zigbee 3.0 network or trying to rejoin a 2.5.1a network?  The latter will not be possible because of security incompatibility.  Rejoins after upgrades are most possible when using the same Zigbee protocol version.  From my perspective, HAL_BOARD_INIT does not turn off interrupts so I am not certain where their program is stuck.  Can they provide code snippets and point to the exact line where they believe the code freezes?  I recommend retaining the flash Serial Boot Loader on both versions, as the Boot Loader cannot erase itself and to support further serial firmware change options.

    Regards,
    Ryan