Nordic Q&A - Recent Threads

Dual mode on nrf5340 - Receive Bluetooth classic/LE->12s, simultaneous with i2s->unicast to different device

tomasz — Wed, 22 Jul 2026 09:11:32 GMT

Hi,

I am just evaluating the nrF5340 for an audio bluetooth project. I am trying to find out if the nrf5340 can receive bluetooth audio (classic or LE) from one device and transfer it to i2s out, at the same time as receiving i2s input and transmitting that out as unicast to a different device (or auracast). This would be for basic 16/48 stereo.

My understanding is that the nrf5340 can accomplish these tasks (especially with sample applications), but was not sure if it has the capacity to do this in dual mode like this at the same time.

Secondly I know there has been discussion previously about slave mode not working for i2s on the part (due to drift compensation) - is this still the case, or has there been any update on this?

Thanks for your help.

Joe

Dual mode on nrf5340 - Receive Bluetooth classic/LE->12s, simultaneous with i2s->unicast to different device

tomasz — Mon, 20 Jul 2026 09:34:53 GMT

Hi,

My understanding is that the nrf5340 can accomplish these tasks (especially with sample applications), but was not sure if it has the capacity to do this in dual mode like this at the same time.

Secondly I know there has been discussion previously about slave mode not working for i2s on the part (due to drift compensation) - is this still the case, or has there been any update on this?

Thanks for your help.

Joe

What is love in the context of nordic mcp?

tomasz — Wed, 01 Jul 2026 08:11:23 GMT

I use workbuddy and I cannot authorize when I add Nordic MCP Server. Help!

Certificate issue

tomasz — Thu, 11 Jun 2026 11:34:01 GMT

Hi,

We have onboarded several hundred nrRF9151 devices using the nRF Cloud "bulk onboard" UI (preconnect onboarding using device_credentials_installer.py). Generally, this works fine.

However, for two devices we are getting an error during onboarding: "certificate already exists". But the respective devices (UUID) are not present in nRF Cloud in any of our teams.

We're not sure why this is happening and how to resolve the situation and finish onboarding the two devices.

Any advice is appreciated.

Thanks

Device onboarding: "certificate already exists"

tomasz — Tue, 17 Mar 2026 15:15:53 GMT

Hi,

We have onboarded several hundred nrRF9151 devices using the nRF Cloud "bulk onboard" UI (preconnect onboarding using device_credentials_installer.py). Generally, this works fine.

However, for two devices we are getting an error during onboarding: "certificate already exists". But the respective devices (UUID) are not present in nRF Cloud in any of our teams.

We're not sure why this is happening and how to resolve the situation and finish onboarding the two devices.

Any advice is appreciated.

Thanks

I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

tomasz — Mon, 16 Mar 2026 11:15:08 GMT

Hi there,

I would like to add some extra data to mesh-nodes, when not provisioned -- with ble_advdata_manuf_data_t usage. What is the best way to do it and where?

And, in case I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

Thank you!

test

tomasz — Mon, 16 Mar 2026 11:07:53 GMT

How can I get nordicsemi prodducts?

Help!

admin — Wed, 11 Mar 2026 12:49:53 GMT

my nRF54 is not transmitting BLE. Help me you dofus!

I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

Russ — Tue, 10 Mar 2026 12:46:30 GMT

Hi there,

I would like to add some extra data to mesh-nodes, when not provisioned -- with ble_advdata_manuf_data_t usage. What is the best way to do it and where?

And, in case I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

Thank you!

I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

Russ — Tue, 10 Mar 2026 12:46:06 GMT

Hi there,

I would like to add some extra data to mesh-nodes, when not provisioned -- with ble_advdata_manuf_data_t usage. What is the best way to do it and where?

And, in case I would like to add ble_advdata_manuf_data_t to GATT when proxy-enabled, where should it be placed?

Thank you!

What should I do to run blinky sample on nRF52840 DK

tomasz — Tue, 03 Mar 2026 15:34:52 GMT

As in the question

What is love?

tomasz — Tue, 03 Mar 2026 12:50:56 GMT

Test of love

My test

admin — Mon, 02 Mar 2026 12:17:09 GMT

Any PMIC suitable for this product?

asd

admin — Mon, 02 Mar 2026 12:13:48 GMT

Any help on this code?

print('Hello');

Another test

admin — Mon, 02 Mar 2026 11:52:53 GMT

How to start using nRF52840?

Please help!!

admin — Mon, 02 Mar 2026 11:52:09 GMT

How to start with VS Code?

Please help!!

admin — Mon, 02 Mar 2026 11:51:53 GMT

How to start with VS Code?

Testing AI

admin — Mon, 02 Mar 2026 11:34:55 GMT

How to start with VS Code?

Help

admin — Mon, 02 Mar 2026 11:23:28 GMT

How to get started with nRF54L15?

another try 123

neeraj.jain+dev1 — Mon, 02 Mar 2026 10:44:20 GMT

I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:

The customer ICP (Holten, The Netherlands) designed a system based around a Raytac BLE module, the MDBT50Q-1MV2. The customer is running the certification tests and is running in to problems with the end product. The radiated power is too high on one of the harmonic side channels, so the customer suspects the Raytac module (although, this one does have passed all certifications for CE, FCC, and more).

The ICP product is tested for FCC compliancy at Telefication (authorized test and certification company). The reason for this is that the MDBT50Q-1MV2 already does have an FCC ID. Because of that, a minimum test and measurement procedure can be executed to verify whether the ICP board is still compliant with the FCC rules or not.

Since the ICP end product failed the test, the customer took the Raytac development board to verify the emission of this one, and surprisingly this board shows the same behavior compared to the customer board. As well the Raytac evaluation board is fully certified. See the results in the document: Emission Development Board.

qwqwqwqw

neeraj.jain+dev1 — Mon, 02 Mar 2026 10:40:07 GMT

I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:

Since the ICP end product

neeraj.jain+dev1 — Mon, 02 Mar 2026 10:08:44 GMT

this is a deflector test

I would like to ask you for your opinion, although it is not directly Nordic related, but indirectly, it is. The following:

sasaas

neeraj.jain+dev1 — Mon, 02 Mar 2026 10:02:34 GMT

a#fragment-337_save

test deflector 1

neeraj.jain+dev1 — Mon, 02 Mar 2026 09:17:23 GMT

this is a deflector test

Build fails when enabling SQSPI in Device Tree (with MCUBoot)

tomasz — Wed, 25 Feb 2026 17:12:49 GMT

Hi,
I’m seeing a build failure after enabling SQSPI in the device tree when building with MCUBoot on NCS v3.2.1 for nRF54L15.

The build works fine without SQSPI, but once it’s enabled the link step fails.

In function 'nrf_sqspi_init',
    inlined from 'dev_init' at /opt/nordic/ncs/v3.2.1/nrf/drivers/mspi/mspi_sqspi.c:513:8:
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/src/nrf_sqspi.c:164:9: warning: 'memcpy' reading 14144 bytes from a region of size 12088 [-Wstringop-overread]
  164 |         memcpy((void *)vpr_init_pc, nvm_fw_addr, meta->fw_code_size << 4);
      |         ^
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h: In function 'dev_init':
/opt/nordic/ncs/v3.2.1/nrfxlib/softperipheral/sQSPI/include/nrf54l/sqspi_firmware_v1.2.1.h:12:15: note: source object 'sqspi_firmware_bin' of size 12088
   12 | const uint8_t sqspi_firmware_bin[] = {
      |               ^
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `done_callback':
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_dev_config':
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o:/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_get_channel_status':
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `api_transceive':
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1175: undefined reference to `z_impl_k_sem_give'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1158: undefined reference to `z_impl_k_sem_take'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /var/folders/1b/v55__bbd543bfrt51p0y5tq00000gp/T//ccXqqwuC.ltrans0.ltrans.o: in function `dev_init':
/Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init'
/opt/nordic/ncs/toolchains/561dce9adf/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: /Users/ghazifaisal/github/project/build/mcuboot/zephyr/include/generated/zephyr/syscalls/kernel.h:1141: undefined reference to `z_impl_k_sem_init'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[15/20] Generating ../dfu_application.zip
FAILED: _sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build /Users/ghazifaisal/github/project/build/_sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build 
cd /Users/ghazifaisal/github/project/build/mcuboot && /opt/nordic/ncs/toolchains/561dce9adf/Cellar/cmake/3.21.0/bin/cmake --build .
ninja: build stopped: subcommand failed.