SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Thu, 06 Feb 2025 12:33:37 GMT

Great to hear we were able to solve the undefined references. Don't hesitate to create another ticket in future if there is any question

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Wed, 05 Feb 2025 23:44:18 GMT

The errors related to i2c_nrfx_twim was fixed by removing "CONFIG_I2C_LOG_LEVEL_OFF=y". I was able to build the nRF5340 firmware using the SDK 2.9.0.

Thanks for the support.

Regards,

Leiser

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Wed, 05 Feb 2025 18:03:49 GMT

Sorry for the delay, I was working in other assignment.

Looks like adding the CONFIG_NRFX_GPPI on the boards files works. No more undefined reference to `nrfx_gppi_channel_alloc'.

The error now is related to i2c_nrfx_twin.

\main_app\build\zephyr && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe -E true""
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim_common.c.obj): in function `i2c_nrfx_twim_configure':

C:/ncs/v2.9.0/zephyr/drivers/i2c/i2c_nrfx_twim_common.c:71: undefined reference to `log_const_i2c_nrfx_twim'

c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim_common.c.obj): in function `i2c_nrfx_twim_msg_transfer':

C:/ncs/v2.9.0/zephyr/drivers/i2c/i2c_nrfx_twim_common.c:103: undefined reference to `log_const_i2c_nrfx_twim'

C:/ncs/v2.9.0/zephyr/drivers/i2c/i2c_nrfx_twim_common.c:140: undefined reference to `log_const_i2c_nrfx_twim'

I think you can close this one. If I will not able to find a solution for that error I will open other case for that.

Thanks!

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Wed, 22 Jan 2025 14:42:46 GMT

As it seems like the error has changed from the app core to net core. I think the best soulution will be to add the CONFIG_NRFX_GPPI to the following files

https://github.com/nrfconnect/sdk-zephyr/blob/v3.4.99-ncs1-rc1/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig

https://github.com/nrfconnect/sdk-zephyr/blob/v3.4.99-ncs1-rc1/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig

and rebuild the application

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Wed, 22 Jan 2025 12:44:41 GMT

I had not added in both cores. I delete the build folder and I tried it now in both cores and no change. Same errors came out.

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Tue, 21 Jan 2025 12:52:22 GMT

Thanks, did you try to add CONFIG_NRFX_GPPI to both cores? I forgot to specify it

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Mon, 20 Jan 2025 16:23:20 GMT

Deleting the build folder only change the order the errors were logged.

c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/soc/soc/arm/nordic_nrf/lib..__modules__soc-hwmv1__soc__arm__nordic_nrf.a(soc.c.obj): in function `rtc_pretick_cpunet_init':
C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:460: undefined reference to `nrfx_gppi_channel_alloc'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:466: undefined reference to `nrfx_gppi_event_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:467: undefined reference to `nrfx_gppi_task_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:468: undefined reference to `nrfx_gppi_event_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:469: undefined reference to `nrfx_gppi_task_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:470: undefined reference to `nrfx_gppi_channels_enable'
collect2.exe: error: ld returned 1 exit status

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Mon, 20 Jan 2025 07:13:24 GMT

Hi and thanks for the feedback.

Can you try to delete your build folder and try again? I will meanwhile check internally

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Fri, 17 Jan 2025 15:01:56 GMT

I had tried this before and it did not work. I tried it again to copy the error messages.

oc-hwmv1__soc__arm__nordic_nrf.a(soc.c.obj): in function `rtc_pretick_cpuapp_init':
C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:408: undefined reference to `nrfx_gppi_channel_alloc'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:418: undefined reference to `nrfx_gppi_task_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:419: undefined reference to `nrfx_gppi_event_endpoint_setup'
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: C:/ncs/v2.9.0/modules/soc-hwmv1/soc/arm/nordic_nrf/nrf53/soc.c:420: undefined reference to `nrfx_gppi_channels_enable'

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Fri, 17 Jan 2025 08:20:35 GMT

Good morning

Could you try to add CONFIG_NRFX_GPPI to your overlay?

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Thu, 16 Jan 2025 14:19:12 GMT

Yes, I'm using VScode for now and on the build configuration I set the no sysbuild option.

My plans is to test the modification I did to make the code to compile with the SDK 2.8.0. As soon as, I 'm sure the firmware is working I will do the modification to use sysbuild and the hardware model 2 device tree.

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Thu, 16 Jan 2025 12:36:56 GMT

Thanks for the clarification, just to be sure. When you are building you are build with --no-sysbuild? Or if you use VScode the no sysbuild button? When I checked the files they should all be there with the functions

Regards

Runar

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

Leiser — Mon, 13 Jan 2025 15:16:03 GMT

I'm using the HW model 1 and I'm not using sysbuild.

Regards,

Leiser

RE: SDK 2.9.0 undefined reference to `nrfx_gppi_channel_alloc'

runsiv — Mon, 13 Jan 2025 12:47:20 GMT

Just to start with. Which hardware model are you using? As you might know we changed from HW model 1 to HW model 2 with NCS 2.7. With the new HW model board names changed
Please see this part of the release note

The previous method to define a board (hardware model) is deprecated and being replaced by a new method (hardware model v2).
The previous method to define multi-image builds (parent-child images) is deprecated and being replaced by Sysbuild (System build).

All samples and applications in the SDK have been migrated. Consult respective documentation as additional or changed parameters might be needed to build them successfully. Applications that are outside of the SDK and use custom-defined boards should not be affected by these changes. However, modifications might still be required as per the migration procedure described in Migration guide for nRF Connect SDK v2.7.0. nRF Connect for VS Code users migrating to the latest version of the SDK might be affected.

All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

The deprecated methods are scheduled for removal after the next release. We recommend transitioning to the alternatives as soon as possible. Consult migration guides for Migrating to the current hardware model and Migrating from multi-image builds to sysbuild. Exercise caution when migrating production environments to the latest SDK.

"
Regards

Runar