Migrating nRF53 Zigbee project to nRF54 results in ZBOSS errors

[Kampino]

Hi,

I try to migrate a working nRF53 Zigbee project from SDK 2.7 to the latest SDK and an nRF54. As described here, I also switched to Zigbee R23. The project structure is shown below.

But the build exit with the error message

C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:16:32: error: 'PM_ZBOSS_NVRAM_SIZE' undeclared here (not in a function); did you mean 'PM_SRAM_SIZE'?
   16 | #define ZBOSS_NVRAM_PAGE_SIZE (PM_ZBOSS_NVRAM_SIZE / CONFIG_ZIGBEE_NVRAM_PAGE_COUNT)
      |                                ^~~~~~~~~~~~~~~~~~~
C:/Users/konta/Desktop/BeeLight/firmware/zephyr/include/zephyr/toolchain/gcc.h:87:52: note: in definition of macro 'BUILD_ASSERT'
   87 | #define BUILD_ASSERT(EXPR, MSG...) _Static_assert((EXPR), "" MSG)
      |                                                    ^~~~
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:18:15: note: in expansion of macro 'ZBOSS_NVRAM_PAGE_SIZE'
   18 | BUILD_ASSERT((ZBOSS_NVRAM_PAGE_SIZE % PHYSICAL_PAGE_SIZE) == 0,
      |               ^~~~~~~~~~~~~~~~~~~~~
C:/Users/konta/Desktop/BeeLight/firmware/zephyr/include/zephyr/toolchain/gcc.h:87:51: error: expression in static assertion is not an integer
   87 | #define BUILD_ASSERT(EXPR, MSG...) _Static_assert((EXPR), "" MSG)
      |                                                   ^
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:18:1: note: in expansion of macro 'BUILD_ASSERT'
   18 | BUILD_ASSERT((ZBOSS_NVRAM_PAGE_SIZE % PHYSICAL_PAGE_SIZE) == 0,
      | ^~~~~~~~~~~~
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c: In function 'zb_osif_nvram_init':
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:39:31: error: 'PM_ZBOSS_NVRAM_ID' undeclared (first use in this function)
   39 |         ret = flash_area_open(PM_ZBOSS_NVRAM_ID, &fa);
      |                               ^~~~~~~~~~~~~~~~~
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:39:31: note: each undeclared identifier is reported only once for each function it appears in
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:45:31: error: 'PM_ZBOSS_PRODUCT_CONFIG_ID' undeclared (first use in this function)
   45 |         ret = flash_area_open(PM_ZBOSS_PRODUCT_CONFIG_ID, &fa_pc);
      |                               ^~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c: In function 'zb_get_nvram_page_length':
C:/Users/konta/Desktop/BeeLight/firmware/ncs-zigbee/subsys/osif/zb_nrf_nvram.c:55:1: warning: control reaches end of non-void function [-Wreturn-type]
   55 | }
      | ^
[449/492] Building C object modules/nrfxlib/nrf_802154/nrf_802154/driver/CMakeFiles/nrf-802154-driver.dir/src/nrf_802154_trx_dppi.c.obj

What causes this issue and how can I fix it?

[AHaug]

Hi,

Did you also follow the steps in the migration guides from 2.7.0 and incrementally up to 3.0.1 i.e https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration_guides.html with emphasis on https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_sysbuild.html if you're coming from child/parent images?

If you're unsure about the sysbuild migration, what does your project folder look like? Are you using child images or sysbuild? https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/ 

Kind regards,
Andreas

[Kampino]

Hi,

thanks to the answer. The project is built with Sysbuild and when removing Zigbee from the project, the build runs smoothly.

I´ve pushed the latest version of the project to my GitHub so you can see the structure:

github.com/.../firmware

[Kampino]

Hi Andreas,

Another update:
I´ve got everything working so far (BSEC, NCS 3.0.1, Zigbee), and I´ve changed the directory structure to this.

Now I have to work on the west.yml file for my application to initialize everything correctly.

[AHaug]

Hi again,

I see that you've had some progress here with customizing, but I may have some news that could either be good or bad for you. 

I had a chat with one of the Zigbee devs and I might have a few pointers.

The idea behind the addon is to an extension to NCS, but it is not flexible in a sense that you can whatever ncs version you would like to. You will have to use a certain NCS release together with the Addon that is only meant to be compatible with a given  ZBOSS stack version and NCP host version. There may be options to customize this more later, but for now what we support is only what is mentioned here: https://docs.nordicsemi.com/bundle/addon-zigbee-r23-latest/page/release-notes.html 

This means that the support for v3.0.1 is not within the supported list of SDK versions that we support fwith R23. This does also mean that taking an addon from NCS v3.0.1 will most likely not compile or work together with R23 out of the box.

I'm sorry for not mentioning this earlier. The addon-system is also relatively new for me.

In other words, the first item that I was recommended to relay to you is to make sure that you're using compatible versions of the SDK, addon and to follow the setup steps there.

The second item is to continue with the Zigbee Template sample and to add your application step by step on top of the template for your board.

Kind regards,
Andreas

[Kampino]

Hi Andreas,

thanks for the effort. I will try it with v2.9.0 now, at least until I got Zigbee running (I also have this issue: nRF54L Zigbee R23 production configuration understanding issues . The sensor drivers doesn´t care for now because I have to patch the light sensor driver anyway, so I can use a patch to add it.

But the code is compiling without any issues now. So I think the structure of the project is good. I´ve created the structure based on the template project by adding my code as an additional template and then moving everything around and changing the configuration files accordingly. The result was always the same.

[Kampino]

Hi Andreas,

update: Thanks to Marte (see the other thread), flashing of the Zigbee config is successful now, and this results in a successful join attempt (the data aren´t correct atm, but doesn´t care for now):

The device is leaving the network after a short time. I think because of the wrong data...

[AHaug]

Kampino said:

I will try it with v2.9.0 now,

Allright, let me know if there's still any issues and we'll have a look

Kampino said:

But the code is compiling without any issues now. So I think the structure of the project is good. I´ve created the structure based on the template project by adding my code as an additional template and then moving everything around and changing the configuration files accordingly. The result was always the same.

Great! Glad to hear that

Kind regards,
Andreas

[Kampino]

Hi Andreas,

my device is reporting this when connecting with Zigbee2Mqtt:

00> [00:06:02.442,995] <inf> zigbee_app_utils: Unimplemented signal (signal: 56, status: 0

Signal 56 is documented as "ZB_SIGNAL_JOIN_DONE 56U" and I´m curious why this signal is missing. I can´t get my device to stay in the network. It always joining and leaving the network.

[Kampino]

Hi AHaug 

I found the issue. I must add the install code to Zigbee2Mqtt, but for some reason I can´t add a 16 byte code (I did it wrong probably...). So I disabled the install code in the config

# Enable channel 11 and 16
channel_mask: 0x10800
#install_code: 83FED3407A939723A5C639B26916D505
extended_address: 86D79AC5BAE41FA3
tx_power: 9
app_data: 01ABCD

Can you tell me what this means?

app_data: 01ABCD

Does this number has a specific function or is it a dummy from the template?

[Kampino]

Hi AHaug ,

FYI: My firmware is working now (except the sensors), so I decided to test it with NCS 3.0.1. This version ends with a "Network steering was not successful" error. After switching back to NCS 2.9.0, the error is gone.