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: Issue with ZNP in Zstack 3.0.1

Part Number: CC2530
Other Parts Discussed in Thread: CC2531, , CC2538

I am not able build ZNP hex file from IAR with ZSTACK 3.0. I need to compile the ZNP with custom compile options and the PROD-HEX configuration is removed in this release, Can anyone help with this?

  • This issue is in ZSTACK 3.0.1 release.
  • Which IAR version do you use?
  • I am using IAR version 10.10.1.
  • What error do you see?
  • Hi,

    The configurations were renamed in this release to better reflect what each configuration actually is.

    In the past, Debug would give you an image without the SBL and with the application image starting at the beginning of flash (using the regular linker file, not the cc2530-sb linker file). This image was to be used for debugging or if you wanted to use the CC2530/CC2531 without SBL capabilities.

    ProdHex would give you a .hex image with the SBL included, the idea was you would use this hex file with something like Flash Programmer to program the device initially with both the serial bootloader and with the application image.

    ProdSBL would give you a .bin image that doesn't contain the SBL but does offset the application image by using the cc2530-sb linker file, which means you could use a program like SerialBootTool to upgrade a device that already contains the serial bootloader. i.e., the ProdSBL image is an application-only image that is designed to overwrite the application of a device that is already programmed with the ProdHex image.

    Now we have renamed the workspaces to Debug, ZNP-without-SBL and ZNP-with-SBL. Debug is the same as before, ZNP-without-SBL is the same as ProdSBL, and ZNP-with-SBL is the same as ProdHex. The CC2538 projects have been updated in the same way.