Nordic Q&A - Recent Threads

RE: Which pin can be used for GPIO P0 on SPIM30 of nRF54L15?

zlittell — Wed, 09 Sep 2026 20:45:47 GMT

Not to dig up an old thread, but just to confirm. I am putting SPIM30 on port0 as intended I can use any pins as long as the clock pin is on a clock capable output? The documentation is much more exact about some of the other ports listing the SPIM instances in the peripheral column of the pin table.

For example: P0.01 CSn, P0.02 COPI, P0.00 CIPO, P0.04 SCLK would be a valid configuration?

Which pin can be used for GPIO P0 on SPIM30 of nRF54L15?

Kenta — Thu, 11 Dec 2025 04:53:58 GMT

Hello,
I am looking at pages 871 and 872 of the datasheet for the QFN48 package, but I’m not sure I understand correctly.
Could you please tell me which GPIO P0 pins can be used for SPIM30 on the nRF54L15?

Best regards.

Kenta.

Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

Arthur C — Wed, 09 Sep 2026 06:34:39 GMT

Hello, since thisisant.com is no more, the process to get whitelisted for the ant-nrfconnect/sdk-ant github repository through the ANT Adopter process does not work. I have tried both using the Visual Studio nrf Connect SDK and using the command line to add +ant to my SDK version manifest and `west update` with the same results.

I'm a hobbyist trying to do some data translation to expose to a Garmin GPS using an nrf52840 SoC.

My github account is dyniper

Thanks for helping with this.

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

Arthur C — Wed, 09 Sep 2026 20:11:02 GMT

Thank you so much!

RE: VS Code SDK install failure

RFLABS — Wed, 09 Sep 2026 19:52:34 GMT

I do see this message:

[bookmarks] Loaded 0 bookmarks

[kit] Successfully loaded 0 kits from C:\Users\david\AppData\Local\CMakeTools\cmake-tools-kits.json

[variant] Loaded new set of variants

[extension] CMake not found during configure-on-open. Waiting for nRF Connect to finish setup...

[extension] CMake not found after 4 retries

[main] Configuring project: firealarm

VS Code SDK install failure

RFLABS — Fri, 21 Aug 2026 15:34:17 GMT

Have tried several times to install the SDK into VS code without success. This is one of the errors I am getting:

Failed to register SDK installation: west failed with code -4058 (cmd 'west zephyr-export) (cwd 'd:\ncs\v3.3.0'):

The SDK will not be detected by VSCode before the CMake Package Registry is corrected for the Zephyr package: d:\ncs\v3.3.0

[11:17:50] Unable to find the toolchain at path: C:/ncs/toolchains/dcbdc366a1/opt/zephyr-sdk/gnu/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe

I also tried reinstalling without success. Do I need to stall more than "nRF Connect for VS Code Extension Pack v2025.4.4" before installing the SDK?

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

sr-ant-wireless — Wed, 09 Sep 2026 19:45:51 GMT

Hi there, we're in a transition period for sdk-ant repository access, sorry for the inconvenience.

I will manually add your account for now.

blog contributor

tuxap — Wed, 09 Sep 2026 16:49:44 GMT

Hello,

I have been a Nordic DevZone member for several years, but I have never published a blog post.

I would now like to contribute a technical article about an open-source project we are developing called nRFClaw:

github.com/.../nrfclaw

https://nrfclaw.cloud/

nRFClaw explores AI-assisted programming of deeply embedded Nordic devices. Natural-language instructions are transformed into compact, deterministic programs that execute on the nRF52832, allowing the device to remain extremely power efficient and operate autonomously for long periods from a battery.

Our reference hardware is NINASENSE, an ultra-low-power nRF52832 platform with Bluetooth Low Energy, LoRa, motion/vibration sensing, and interfaces for external sensors.

I believe the project could be interesting to the Nordic developer community, and I would like to write a technical DevZone article tentatively titled:

“Natural-Language Programming on an nRF52832: AI at Development Time, Microamps at Runtime”

However, when I log into DevZone, I do not see an option to create or submit a blog post.

Do community members still have the ability to contribute articles to the Nordic DevZone Blog? If so, does my account need to be granted contributor/blog publishing permission, or is there a submission/review process I should follow?

We are also preparing NINASENSE for submission to the Nordic Community Hub through Crowd Supply.

Thank you,
André Heringer
NearMeter Technologies LLC

Configuring Post-Production Cryptographic Key Provisioning via nRF Cloud and Memfault

Uri Rotshtein — Wed, 09 Sep 2026 16:10:15 GMT

I need an architectural guide and recommended workflow for setting up post-production (in-field) cryptographic key provisioning on Nordic nRF devices (nRF9160 and nRF9151) upon their initial network connection.

While I plan to use nRF Cloud and Memfault for device management and telemetry, our core application data must route through a separate, custom MQTT broker utilizing the public key generated during the provisioning process.

Please address the following requirements:

Provisioning Workflow: How to trigger and execute over-the-air (OTA) cryptographic key provisioning or certificate injection once the device establishes its initial network connection.
Integration Strategy: How to leverage nRF Cloud for this provisioning flow while maintaining a completely separate custom MQTT broker for standard application traffic using the newly provisioned keypair.
Notifications & Key Retrieval: How to receive a notification when the provisioning process completes and how to programmatically access the generated public key for use with the custom MQTT broker.
Security & SDK Configs: Essential security considerations and specific nRF Connect SDK configurations required to handle keys securely during late-binding field provisioning.

RE: MPSL Assert 3,39

grantrudd — Wed, 09 Sep 2026 15:21:41 GMT

devzone.nordicsemi.com/.../timeslot_5F00_usage.c

Hi Edvin,

I attached a simplified version of our timeslot code that highlights how we are making requests.

When the radio is needed, `_request` is called by our protocol code. This sets the `RADIO_ACCESS_REQUESTED_BIT` bit in an atomic field and makes an earliest request. As long as `RADIO_ACCESS_REQUESTED_BIT` is set, we'll extend the timeslot in our TIMER0 callback.

If we're blocked or cancelled or the extension request fails, we will request a new timeslot using the appropriate request mechanism.

If we want to dig deeper into our source code, I'd like to turn this into a private thread.

As far as patterns go, the only thing we know about is that this started happening after enabling ANT+. It just seems to happen randomly during normal usage.

Somewhat related, we build production code with asserts enabled to catch critical system failures that can be recovered via reset. This means that any MPSL asserts will also trigger a reset. Are the MPSL asserts generally a debugging tool or do they represent critical, unrecoverable timeslot issues that require a CPU reset or can they be suppressed for production?

Thanks,

Grant

MPSL Assert 3,39

grantrudd — Tue, 01 Sep 2026 15:23:27 GMT

Hello,

We are seeing an intermittent MPSL assert with the code 3, 39. Can you tell us what this code points to?

Thanks,

Grant

nRF54L15 CSTONES: where are PHASESHIFT and the FAE/frequency-offset corrections applied in the tone processing chain?

John Jacobson — Wed, 02 Sep 2026 00:03:35 GMT

I'm working with Channel Sounding on the nRF54L15 and trying to understand the CSTONES tone-processing block at the register level so I can post-process the results correctly and, for a custom localization experiment, drive the block directly from the application core via TASKS_CSTONESSTART.

From the Product Specification (RADIO chapter) I understand the chain as: NUMSAMPLES input IQ samples at the 2 MHz sample rate → optional DOWNSAMPLE → IQRAWMEAN ("Mean of IQ values") → MAGPHASEMEAN ("Mean magnitude and phase of the signal before it is converted to PCT16") → PCT16 ("Mean magnitude and mean phase converted to IQ"). I have three questions about where the corrections sit in that chain:

CSTONES.PHASESHIFT (0x1018, "Parameter used in TPM, provided by software"). Is this phase shift applied to the incoming IQ samples before averaging, so that IQRAWMEAN already reflects it, or is it applied to the mean value after averaging, so that only MAGPHASEMEAN/PCT16 reflect it? What unit and sign convention does it use (e.g., 16-bit fraction of 2π)? What value does the SoftDevice Controller normally program here, and is it derived from the previous step's PCT or from calibration?
CSTONES.FAEPEER / CSTONES.FREQOFFSET / CSTONES.FFOEST. When the peer's frequency actuation error and the FFO estimate are known, is the resulting phase-rotation compensation performed sample-by-sample on the IQ stream during the T_PM window (a derotation before the mean), or as a single rotation of the averaged value? Same question for the T_PM_CENTER_DELTA correction from Core Vol 6 Part A §6.3.
Reflector with Inline PCT Transfer enabled. When the reflector adjusts the phase of its transmitted CS tone so that the reported Q sample is zero, which part of the radio applies that adjustment: is the measured phase written into the tone generation path (a phase/DTC setting in the frequency synthesizer), or is a phase rotation applied to a digital baseband value before the transmit path? Is that adjustment visible or configurable from the application core, or entirely inside the SoftDevice Controller? The SDC changelog mentions additional "TX Phase settling time" in T_IP2 when IPT is used; a pointer to what that settling covers would help me set the interlude correctly.

If any of this is documented in a version of the Product Specification or an SDC document I've missed, a link is fine. Thanks.

RE: nRF54L15 CSTONES: where are PHASESHIFT and the FAE/frequency-offset corrections applied in the tone processing chain?

John Jacobson — Wed, 09 Sep 2026 14:57:37 GMT

Thank you Elfving,

That section appears to be the spec's reference receiver for the sounding-sequence path. What I'm after is the nRF54L15's mode-2 tone path: is FREQOFFSET applied to the IQ samples before IQRAWMEAN is formed, or to the mean afterward? If R&D can confirm either way, that should answer it. Thanks for the back and forth on this!

Does single-cell location nrfcloud API work in India for Jio network?

anupamvarghese — Tue, 08 Sep 2026 14:05:38 GMT

Hi,

We are unable to get the correct location (even approximate) using the nrfCloud API for Location based on Single-Cell.
For the given
"mcc", "mnc", "tac" and "eci" combination, it seems to always return some location in Mumbai for a SIM being testing in Bangalore.

Could you please confirm Jio's NB-IoT tower network in India is mapped on your cloud?

Thanks.

- Anupam

RE: Does single-cell location nrfcloud API work in India for Jio network?

anupamvarghese — Wed, 09 Sep 2026 14:38:56 GMT

You were right Nishant, our eci was truncated to uint16 while testing, hence the error. Using the correct uint32 value gives us the correct approx location. Thanks a ton!

RE: nRF54LM20A-PAAA Reference circuit - bulk capacitor

Ressa — Wed, 09 Sep 2026 14:26:14 GMT

Hi,

The bulk capacitor you are mentioning is the biggest cap on VDD and its main tasks is to prevent voltage drop during high current activities. So depending on the quality of ground plane/ traces / maximum current consumption in your application, cap value can be changed. If you are using 3.3 V supply and having a good quality supply source (low internal resistance) and the connection between supply source and VDD pins are solid (like having dedicated power plane undeath SoC), so I personally think the value can be changed (reduced). But it is not something that has been validated by Nordic, so you need to verify/validate it on your prototype over several samples.

Br,
Ressa

nRF54LM20A-PAAA Reference circuit - bulk capacitor

HW72 — Wed, 09 Sep 2026 09:49:32 GMT

Hello,

According to the reference circuit (https://docs.nordicsemi.com/r/bundle/ps_nrf54lm20a/page/chapters/ref_circuitry.html-concept_refcircuit_config_1), a bulk capacitor C4 with a value of 10 µF / 6.3 V in a 0402 package is used. If a 3.3 V MCU supply voltage is used, the effective capacitance is approximately 4 µF in the 0402 package.

Is this expected to be the minimum effective capacitance, or is a lower capacitance acceptable?

I am asking because I need to save space on the PCB, so I would like to know whether this minimum capacitance is actually acceptable.

Thank you.

10 µF

Capacitor, X6S, 6.3 V, ±20%

0402

RE: nRF52840: QSPI pin configuration confirmation

Nissanth — Wed, 09 Sep 2026 14:22:34 GMT

Hi Kaushik,

Your pin selection is fine. None of the six pins you listed is restricted to "low frequency I/O only" in the pin assignment table, so all pins you mentioned can be used for standard SPI or QSPI.

Regards,

Nissanth Karunanithy

nRF52840: QSPI pin configuration confirmation

Kaushik Thumar — Wed, 09 Sep 2026 06:43:23 GMT

Hi Team,

We are planning to use the following nRF52840 GPIOs for our current SPI interface, with the intention of migrating to QSPI in the future:

CSn: P0.08
CLK: P0.16
IO0 / MOSI: P0.15
IO1 / MISO: P1.08
IO2 / WPn: P0.04
IO3 / RESETn: P0.05

Could you please confirm if there are any restrictions when using these specific pins for standard SPI and subsequently QSPI?

Additionally, since the Nordic reference design recommends different default pins for QSPI, will using our custom pin assignment cause any side effects—such as limitations on maximum clock speed, potential RF/OTA degradation, or anything else?

Thanks and regards,

Kaushik Thumar

RE: nRF93M1 DK offline firmware update

Hakon — Wed, 09 Sep 2026 14:21:21 GMT

It seems that at the moment it is not possible to do serial DFU on the nrf93m1. But in the near future (couple days or weeks) it will be possible to do this from Quick Start. I will come back with more information soon.

nRF93M1 DK offline firmware update

Shinjo Park — Wed, 09 Sep 2026 11:02:06 GMT

Hi, I just started evaluating the nRF93M1 DK (LABA version) and have questions about the firmware version.The AT+CGMR gives "mfw_nrf93m1_1.4.1", which seems to be a bit older than the latest one. According to the AT command manual there should be 1.5.x version.

Yes, I know that [mention:1e83a7aa0e3a42f08db388fba8a82535:46448885d0e64133bbfbf0cd7b0fd6f7] exists, but the solution suggested there uses online OTA update. How can I perform an offline update without plugging in a SIM card?

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

Arthur C — Wed, 09 Sep 2026 14:18:36 GMT

This looks like this link is for commercial license only, which my project definitely isn't. Do you think I should fill that out anyway?

nRF5 SDK 17.1.0: Numeric Comparison pairing dialog on phone fails to dismiss after peripheral rejects pairing

David Duan — Wed, 09 Sep 2026 07:08:14 GMT

Hi DevZone,

My customer is using nRF5 SDK v17.1.0 with LESC Numeric Comparison pairing. They have encountered an issue during the pairing process: when the central (phone) initiates pairing, the

peripheral correctly displays the passkey. However, if the pairing request is rejected on the peripheral side, the pairing dialog box on the central side does not disappear. According to the

customer, BLE chips from other vendors do not exhibit this behavior.

I replicated and tested this issue using a standard nRF5 SDK v17.1.0 example on an nRF52832 DK.

The results confirmed that when the peripheral rejects the pairing, the pairing dialog box on the phone remains visible. Interestingly, when I ran the same test using NCS 3.4, the pairing dialog dismissed normally as expected.

After further investigation, I noticed that in NCS, if the peripheral rejects the pairing, it explicitly sends an SMP Pairing Failed packet. However, in the nRF5 SDK, even though the corresponding code logic triggers key_type = BLE_GAP_AUTH_KEY_TYPE_NONE, the device does not actually send the SMP Pairing Failed (Reason: 0x04 - Confirm Value Failed) command.

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:83ab9a02-c795-45df-a189-decc8b750235:type=text&text=static%20ret_code_t%20num_comp_reply%28uint16_t%20conn_handle%2C%20bool%20accept%29%0D%0A%7B%0D%0A%20%20%20%20uint8_t%20%20%20%20key_type%3B%0D%0A%20%20%20%20ret_code_t%20err_code%3B%0D%0A%0D%0A%20%20%20%20if%20%28accept%29%0D%0A%20%20%20%20%7B%0D%0A%20%20%20%20%20%20%20%20NRF_LOG_INFO%28%22Numeric%20match%20confirmed.%20Conn%20handle%3A%20%25d%22%2C%20conn_handle%29%3B%0D%0A%20%20%20%20%20%20%20%20key_type%20%3D%20BLE_GAP_AUTH_KEY_TYPE_PASSKEY%3B%0D%0A%20%20%20%20%7D%0D%0A%20%20%20%20else%0D%0A%20%20%20%20%7B%0D%0A%20%20%20%20%20%20%20%20NRF_LOG_INFO%28%22Numeric%20match%20rejected.%20Conn%20handle%3A%20%25d%22%2C%20conn_handle%29%3B%0D%0A%20%20%20%20%20%20%20%20key_type%20%3D%20BLE_GAP_AUTH_KEY_TYPE_NONE%3B%0D%0A%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20Must%20be%20set%20before%20the%20reply%3A%20replying%20with%20BLE_GAP_AUTH_KEY_TYPE_NONE%20makes%20the%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20SoftDevice%20send%20an%20SMP%20Pairing%20Failed%20PDU%20%28Numeric%20Comparison%20Failed%29%20and%20raise%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20BLE_GAP_EVT_AUTH_STATUS%2C%20which%20in%20turn%20produces%20PM_EVT_CONN_SEC_FAILED.%0D%0A%20%20%20%20%20%20%20%20m_num_comp_rejected_locally%20%3D%20true%3B%0D%0A%20%20%20%20%7D%0D%0A%0D%0A%20%20%20%20err_code%20%3D%20sd_ble_gap_auth_key_reply%28conn_handle%2C%20key_type%2C%20NULL%29%3B%0D%0A%0D%0A%20%20%20%20%2F%2F%20Do%20NOT%20use%20APP_ERROR_CHECK%28%29%20here%3A%20a%20failure%20must%20stay%20visible%20instead%20of%0D%0A%20%20%20%20%2F%2F%20resetting%20the%20chip%2C%20because%20on%20an%20error%20nothing%20is%20transmitted%20and%20the%20SMP%0D%0A%20%20%20%20%2F%2F%20request%20is%20still%20pending.%0D%0A%20%20%20%20if%20%28err_code%20%3D%3D%20NRF_SUCCESS%29%0D%0A%20%20%20%20%7B%0D%0A%20%20%20%20%20%20%20%20NRF_LOG_INFO%28%22sd_ble_gap_auth_key_reply%28key_type%3D%25d%29%20OK%22%2C%20key_type%29%3B%0D%0A%20%20%20%20%7D%0D%0A%20%20%20%20else%0D%0A%20%20%20%20%7B%0D%0A%20%20%20%20%20%20%20%20m_num_comp_rejected_locally%20%3D%20false%3B%0D%0A%20%20%20%20%20%20%20%20NRF_LOG_ERROR%28%22sd_ble_gap_auth_key_reply%28key_type%3D%25d%29%20failed%3A%200x%25x%20%28%25s%29%22%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20key_type%2C%20err_code%2C%20nrf_log_push%28%28char%20%2A%29nrf_strerror_get%28err_code%29%29%29%3B%0D%0A%20%20%20%20%20%20%20%20NRF_LOG_ERROR%28%22Nothing%20was%20sent%20on%20air%3B%20the%20SMP%20request%20is%20still%20pending.%22%29%3B%0D%0A%20%20%20%20%20%20%20%20printf%28%22%5Cr%5Cnauth_key_reply%20failed%3A%200x%25lx%5Cr%5Cn%22%2C%20%28unsigned%20long%29err_code%29%3B%0D%0A%20%20%20%20%7D%0D%0A%0D%0A%20%20%20%20return%20err_code%3B%0D%0A%7D]

NCS 3.4 Test Result: When the peripheral rejects the pairing request, the pairing dialog box on the phone disappears normally.

[View:/cfs-file/__key/communityserver-discussions-components-files/4/NCS_5F00_SDK_5F00_V1.mp4:320:240]nRF5 SDK 17.10 Test Result: When the peripheral rejects the pairing request, the pairing dialog box on the phone fails to disappear.

[View:/cfs-file/__key/communityserver-discussions-components-files/4/NRF5_5F00_SDK_5F00_V1.mp4:320:240]

The test project for NRF5 SDK(nrf5sdk 17.10,SEGGER Embedded Studio for ARM v5.68)

[View:/cfs-file/__key/communityserver-discussions-components-files/4/ble_5F00_app_5F00_uart_5F00_tst.7z:320:240]

The test project on NCS3.4.0

[View:/cfs-file/__key/communityserver-discussions-components-files/4/peripheral_5F00_lesc.7z:320:240]

Question:
I would like to confirm whether the nRF5 SDK SoftDevice itself inherently does not support sending this SMP Pairing Failed command in this scenario?

RE: nRF5 SDK 17.1.0: Numeric Comparison pairing dialog on phone fails to dismiss after peripheral rejects pairing

tesc — Wed, 09 Sep 2026 13:42:17 GMT

Hi,

[quote user=""]Question:
I would like to confirm whether the nRF5 SDK SoftDevice itself inherently does not support sending this SMP Pairing Failed command in this scenario?[/quote]

The SoftDevice should send the SMP Pairing failed command. The code that you shared looks correct. Setting key_type = BLE_GAP_AUTH_KEY_TYPE_NONE and sending that value in sd_ble_gap_auth_key_reply() should lead to the SoftDevice sending SMP Pairing failed, as per the Bonding: Numeric Comparison Message Sequence Chart.

I see from the logs that the error code returned by the SoftDevice from the call to sd_ble_gap_auth_key_reply() is NRF_SUCCESS, so if there is no SMP Pairing failed command sent then this looks like an issue with the SoftDevice. However I do not find any similar prior reports, and nRF5 SDK is several years old at this point. Are you able to confirm there is indeed no SMP Pairing failed command sent, by using a sniffer (such as for instance the nRF Sniffer)?

Regards,
Terje

RE: 在vscode中，中国源下载sdk失败，具体报错代码如下

1230 — Wed, 09 Sep 2026 13:28:49 GMT

我当然知道这个方法并且已经通过国际源下载了，但是那速度巨慢。我发布这个求助帖子是想让官方给我一个中国源不行的原因并解决，而不是让我去换个方法。

Nordic Q&A - Recent Threads

RE: Which pin can be used for GPIO P0 on SPIM30 of nRF54L15?

Which pin can be used for GPIO P0 on SPIM30 of nRF54L15?

Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

RE: VS Code SDK install failure

VS Code SDK install failure

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

blog contributor

Configuring Post-Production Cryptographic Key Provisioning via nRF Cloud and Memfault

RE: MPSL Assert 3,39

MPSL Assert 3,39

nRF54L15 CSTONES: where are PHASESHIFT and the FAE/frequency-offset corrections applied in the tone processing chain?

RE: nRF54L15 CSTONES: where are PHASESHIFT and the FAE/frequency-offset corrections applied in the tone processing chain?

Does single-cell location nrfcloud API work in India for Jio network?

RE: Does single-cell location nrfcloud API work in India for Jio network?

RE: nRF54LM20A-PAAA Reference circuit - bulk capacitor

nRF54LM20A-PAAA Reference circuit - bulk capacitor

RE: nRF52840: QSPI pin configuration confirmation

nRF52840: QSPI pin configuration confirmation

RE: nRF93M1 DK offline firmware update

nRF93M1 DK offline firmware update

RE: Cannot get whitelisted for ant-nrfconnect/sdk-ant github repository

nRF5 SDK 17.1.0: Numeric Comparison pairing dialog on phone fails to dismiss after peripheral rejects pairing

RE: nRF5 SDK 17.1.0: Numeric Comparison pairing dialog on phone fails to dismiss after peripheral rejects pairing

RE: 在vscode中，中国源 下载sdk失败，具体报错代码如下

RE: 在vscode中，中国源下载sdk失败，具体报错代码如下