nRF Stop scanning coded phy beacon

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Mon, 05 Oct 2026 09:34:11 GMT

Okay Thanks for your quick reply Einar Thorsrud .

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Mon, 05 Oct 2026 09:31:38 GMT

Hi Saurabh,

That is expected. For the app core, the image hash is verified via SMP (typically by nRF Connect or Device Manager), and the update is only initiated if needed. For the network core, the running image is not visible and no such pre-check is done.

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Mon, 05 Oct 2026 06:39:12 GMT

Hello Einar Thorsrud , i added functionality to update DFU for both application + network core OTA,
Have following question,
when i perform OTA for application core (only application core) if is already with updated it will not start DFU process,
but when i did for both network + application OTA using bluetooth (same way as application core) after one time update with both files, if i perform again is again starting DFU process one time (i don't know for which one, but may be for network core), is this process is as expected or i am missing anything.

Thanks,
Saurabh.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Tue, 29 Sep 2026 07:53:09 GMT

Hi,

If you originally did not include support for updating the network core (for instance by not including the network core bootloader b0n, there is no way to update it via DFU. You will have to program it via SWD

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Tue, 29 Sep 2026 06:43:54 GMT

Hello Einar Thorsrud , how can i perform both core OTA in a code that currently supports only application core OTA,
Is it possible to do so, if yes then how to achieve that, or i need to flash manually in each device ?

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Mon, 28 Sep 2026 09:08:38 GMT

Hi,

I see. That is interesting. DFU on the nRF5340 can be done in several ways, both simultaniously updateing app and net core or only updating app (or net) core. So this depends on how you have set up and perform the DFU. Based on your test results, it could look like you are not updating the net core. Regardign the DFU, I recommend you look at DFU for the nRF5340 SoC (which is part of our DevAcademy NCS intemediate corese).

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Sat, 26 Sep 2026 04:53:31 GMT

Hello Einar Thorsrud , in one of the device i flash (erase and flash) using sysbuild and nrf5340dk/nrf5340/cpuapp and is working fine,
But on another 2 devices i did OTA for the same firmware but still getting an issue,
My question is when i perform OTA is it did for both app as well as net core or only for app core ?
If it is only for app core then i need to manually flash for all the devices or is there any way to perform ota for net core.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Thu, 24 Sep 2026 11:40:16 GMT

I see.

Can you share the generated .config for both the app core and net core image? Also, if you are able to share a minimal project that reproduce thi sissue that coult be usefull so that I can have a closer look.

If not, can you share your scan callback so that I can have a look? Could there be an issue there which prevents you from properly receiving the callbacks (perhaps it blocks, or some other error means they are not properly processed making it seem like they do not occur)?

Also, share details (prefrably code) on what you use the 1M phy for at the same time as scanning on coded PHY, it is not clear to me and may be relevant.

Can you confirm again that there is no active connection? If there is, and I see you ahve configured default event length of 4s, that would take time away from scanning.

I am not able to link to this issue, but your Kconfig snippets show a few potentially interesting things. Particularily for the application CONFIG_BT_BUF_EVT_RX_COUNT is set on the net core, but try increasing this on the app core as well (it is a long shot, though).

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Thu, 24 Sep 2026 07:40:37 GMT

Hello Einar Thorsrud , Thanks for your quick response,
I am using the updated ncs version 3.3.0 and getting this issue i already enable the log on netcore side as well,
my current buffer size for CONFIG_BT_BUF_EVT_RX_COUNT is 32 and CONFIG_BT_BUF_EVT_DISCARDABLE_COUNT is 3, and i am building and flashing on both core app + net.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Thu, 24 Sep 2026 07:36:01 GMT

Hi,

I see. Are you now testing on 3.0.0 again, or did you stay on a higher version? If stil on 3.0.0, you need to migrate as there is the mentioned known issue that can cause this precise behaviour. Also, when you test a higher version, make sure you program the net core in addition to the app core, as that is where this known issue resides. I focus on this issue stil as it matches the behaviour you are describing. Can you double-check that you are building with a new SDK version and that you program both cores with the update when you test?

If you consistently reproduce on a higher version then there is something else and we need to look elsewhere. A couple of things in that case:

Regarding that you did not get any logs, have you enabled logging on the network core as well now and are checking those? That would be sensible to do at this point.
As you see other activity stil working when this issue occured(?) on the 1M Phy, that means that the net core is stil running, so my comment about net core monitor earlier does not seem relevant.
If this is another issue, it could potentially be a buffer issue on the host (application core) side. So it is worth increasing CONFIG_BT_BUF_EVT_RX_COUNT and CONFIG_BT_BUF_EVT_DISCARDABLE_COUNT to see if that helps. This might be a long shot, though, but it is something we have seen in the past.

Regarding SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC I do not see that it should be relevant for this issue, but at the same time I cannot rule out anything before the issue is understood.

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Thu, 24 Sep 2026 05:05:31 GMT

Hello Einar Thorsrud I already added this buffer related configurations, but currently not enable the configuration of

SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC, let me know if this make any difference,
Talking about logs i am not getting any warning or error logs when it stop detection of coded phy meanwhile is receiving data for 1M Phy.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Wed, 23 Sep 2026 13:45:29 GMT

Hi,

I came across another report of a similar issue, where the problem was too small buffer sizes on the network core. It could be worth increasing those on your end as well unless you have allready figured this out.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Mon, 21 Sep 2026 13:54:50 GMT

Hi,

I see. I understand that you do not get any logging from teh snippet above, as that is from when you process advertising reports (which I undertands stop comming for some reason). But do you have logging so that you would log other errors? If so, it could be interesting to see the log. I also look forward to seein gthe resuls of your test with the network core monitor.

Also, can you confirm that you continje to test on 3.3.x now and that both the network core and application core has been programmed with that firmware? That way we do not risk the known issue meantionned before to also play a part when testing.

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Fri, 18 Sep 2026 13:09:02 GMT

Thanks for your quick reply,
I will try to answer your all the questions,

Q. How long does it typically take before advertising reports stop?
-> It took almost 5-6 hours, and coded phy data stop coming in scanning call back,

Q. Are there any factors you have seen that affect it?
-> As i mentioned earlier that we are restart bluetooth scanning every 5 minutes and our scanning options is same ".options = CONFIG_BT_LE_SCAN_OPT" but still not receiving any data.

Q. Do you have logging in both the application core and network core? Can you share the logs?
-> Currently we are building with board target nrf5340dk/nrf5340/cpuapp and we don't have any network core log, but in application core we added the logs when bluetooth data received with

info->primary_phy as below

case BT_GAP_LE_PHY_CODED:

case BT_GAP_LE_PHY_CODED_S2:

case BT_GAP_LE_PHY_CODED_S8:

LOG_WRN("Received Coded Phy tag:%d", info->primary_phy);

but not getting this log as well

Q. What else happens when advertising reports stop? Could it be a problem with the network core? It could be interesting to see if eanbling the network core monitor makes a difference.
-> Let me enable this configuration for more details,

one more thing i want to share that we are scanning for bluetooth beacon and we are not connecting with that just scanning data, even they are advertising we not able to receive it on this callback.

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Fri, 18 Sep 2026 13:00:11 GMT

Hi,

The issue I was refering to was fixed SDK 3.1.0, and the fix is part of 3.3.0. If you see this with 3.3.0 as well, it points to potentially another issue.

Some quesions in order to understand more:

How long does it typically take before advertising reports stop?
Are there any factors you have seen that affect it?
Do you have logging in both the application core and network core? Can you share the logs?
What else happens when advertising reports stop? Could it be a problem with the network core? It could be interesting to see if eanbling the network core monitor makes a difference.

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Fri, 18 Sep 2026 12:34:31 GMT

Below is the ipc_prj,conf

CONFIG_HEAP_MEM_POOL_SIZE=8192
CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

CONFIG_MBOX=y
CONFIG_IPC_SERVICE=y

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_CTLR_ASSERT_HANDLER=y
CONFIG_BT_EXT_ADV=y

# Ensure BLE ECC key generation works
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
CONFIG_BT_CTLR_LE_PING=y
CONFIG_ENTROPY_GENERATOR=y
CONFIG_ENTROPY_BT_HCI=y


#CONFIG_BT_MAX_CONN=16

# Enable and adjust the below value as necessary
CONFIG_BT_BUF_EVT_RX_COUNT=32
CONFIG_BT_BUF_EVT_RX_SIZE=255
CONFIG_BT_BUF_ACL_RX_SIZE=255
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_BUF_CMD_TX_SIZE=255

CONFIG_BT_CTLR_SDC_MAX_CONN_EVENT_LEN_DEFAULT=4000000

CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_BUF_ACL_RX_SIZE=502
CONFIG_BT_BUF_ACL_TX_SIZE=502

CONFIG_BT_MAX_CONN=2

CONFIG_ASSERT=y

CONFIG_IPC_RADIO_BT=y
CONFIG_IPC_RADIO_BT_HCI_IPC=y

#Added to fix BLE crash in coex enable cases.
CONFIG_NRF_RPC=n
CONFIG_NRF_RPC_CBOR=n

Below is the mcuboot.conf

# Enable logging for MCUboot
CONFIG_LOG=y

# Turn on a LED so we can see when Serial Recovery mode is active
CONFIG_MCUBOOT_INDICATION_LED=n

# Step 1.2 - Enable QSPI driver for MCUboot
CONFIG_NORDIC_QSPI_NOR=y

# Step 4.1 - Increase number of sectors
# This is 512 for the nRF54L15 but can be smaller for other chips
CONFIG_BOOT_MAX_IMG_SECTORS=512

CONFIG_PM=n

CONFIG_MAIN_STACK_SIZE=10240

CONFIG_BOOT_SWAP_SAVE_ENCTLV=n
CONFIG_BOOT_ENCRYPT_IMAGE=n

CONFIG_BOOT_UPGRADE_ONLY=n
CONFIG_BOOT_BOOTSTRAP=n

### mbedTLS has its own heap
# CONFIG_HEAP_MEM_POOL_SIZE is not set

### We never want Zephyr's copy of tinycrypt.  If tinycrypt is needed,
### MCUboot has its own copy in tree.

CONFIG_FLASH=y
CONFIG_FPROTECT=y

### Various Zephyr boards enable features that we don't want.
# CONFIG_BT is not set
# CONFIG_I2C is not set

CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y # former CONFIG_MODE_MINIMAL
### Ensure Zephyr logging changes don't use more resources
CONFIG_LOG_DEFAULT_LEVEL=0
### Use info log level by default
CONFIG_MCUBOOT_LOG_LEVEL_INF=y
### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y
CONFIG_CBPRINTF_NANO=y
CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=0
### Use the minimal C library to reduce flash usage
CONFIG_MINIMAL_LIBC=y

#core should be on a clean state when TF-M starts
CONFIG_MCUBOOT_CLEANUP_ARM_CORE=n

and below is the prj.conf

CONFIG_GPIO=y

# Enable mcumgr DFU in application
CONFIG_MCUMGR=y

# Enable MCUMGR management for both OS and Images
CONFIG_MCUMGR_GRP_OS=y
CONFIG_MCUMGR_GRP_IMG=y

# Configure MCUMGR transport to UART
# CONFIG_MCUMGR_TRANSPORT_UART=y
CONFIG_MCUMGR_TRANSPORT_BT=y

# Dependencies
# Configure dependencies for CONFIG_MCUMGR  
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_CRC=y

# Configure dependencies for CONFIG_MCUMGR_GRP_IMG  
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y

# Configure dependencies for CONFIG_IMG_MANAGER  
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

# Configure dependencies for CONFIG_MCUMGR_TRANSPORT_UART 
CONFIG_BASE64=y

# Step 1.1 - Enable QSPI driver for Application
CONFIG_NORDIC_QSPI_NOR=y
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

# CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME_DYNAMIC=y
CONFIG_BT_SETTINGS=y
CONFIG_BT_DEVICE_NAME_MAX=48
# Step 2.2 - Enable FOTA over Bluetooth LE
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

CONFIG_LOG=y

CONFIG_SPI=y

# CONFIG_MAIN_STACK_SIZE=4096

CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y
CONFIG_FPU=y
CONFIG_CBPRINTF_FP_SUPPORT=y

CONFIG_FILE_SYSTEM_MKFS=y
CONFIG_FILE_SYSTEM=y
CONFIG_FILE_SYSTEM_LITTLEFS=y

CONFIG_BT_CENTRAL=y
CONFIG_BT_SCAN=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_GATT_DM=y
CONFIG_FS_LITTLEFS_NUM_FILES=10
CONFIG_FS_LITTLEFS_NUM_DIRS=1
CONFIG_FS_LITTLEFS_FMP_DEV=y

CONFIG_FLASH_JESD216_API=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_PM_PARTITION_REGION_LITTLEFS_EXTERNAL=y
CONFIG_PM_PARTITION_SIZE_LITTLEFS=0x70c000

# CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_DK_LIBRARY=y

CONFIG_BT_DEVICE_APPEARANCE=832
CONFIG_BT_MAX_CONN=1
CONFIG_BT_MAX_PAIRED=1

CONFIG_BT_SMP=y
CONFIG_BT_EXT_ADV=y

# Enable nRFx TWIS (I2C Slave)
CONFIG_I2C=y
CONFIG_I2C_TARGET=y
# NCS 3.2.0 (nrfx 4.0) migration: per-instance CONFIG_NRFX_TWIS3 was consolidated into the
# single CONFIG_NRFX_TWIS option; the concrete instance (TWIS3 / i2c3) is still selected via
# the "nordic,nrf-twis" devicetree node (see boards/nrf5340dk_nrf5340_cpuapp.overlay).
CONFIG_NRFX_TWIS=y
CONFIG_I2C_NRFX=y

CONFIG_NVS=y
CONFIG_SETTINGS_NVS=y
# CONFIG_BT_BUF_ACL_TX_COUNT=10
# CONFIG_BT_BUF_ACL_RX_COUNT=10
# CONFIG_BT_L2CAP_TX_BUF_COUNT=10
CONFIG_BT_L2CAP_TX_MTU=247

# ----------------------
# Antenna Board selection
# ----------------------
# Gateway Antenna B10
CONFIG_ANT_B10=y
# Node Antenna B11
CONFIG_ANT_B11=n

# Set to y for gateway hardware version 3.1
CONFIG_GATEWAY_HW_V2=n
CONFIG_BT_DEVICE_NAME="Gateway"

# ----------------------
# General Configurations
# ----------------------
CONFIG_ASSERT=y
CONFIG_HW_STACK_PROTECTION=y # Hardware stack protection to detect overflows earlier
CONFIG_NEWLIB_LIBC=y # To make visible math.h


# ----------------------
# Debug Logger configuration
# ----------------------

# Enable this when tracking using python script.
# CONFIG_LOG_OVERRIDE_LEVEL=1

CONFIG_LOG=y                     # Enable Zephyr logging subsystem
CONFIG_SERIAL=y                  # Enable serial driver
CONFIG_CONSOLE=y                 # Enable console output

# Enable this for UART logging, Disable the RTT
CONFIG_UART_CONSOLE=y            # Disable UART console (we are using ACM)
# CONFIG_STDOUT_CONSOLE=n          # Send the printf to console

# CONFIG_FPU=y                     # Enable floating point unit
# CONFIG_CBPRINTF_FP_SUPPORT=y     # Enable floating-point support for logging

CONFIG_LOG_BUFFER_SIZE=8196
# CONFIG_LOG_MODE_MINIMAL=y      # Disable Full log mode with timestamps and module inf
CONFIG_LOG_MODE_DEFERRED=y       # Logs are processed in seperate thread from ring buffer.
CONFIG_LOG_DEFAULT_LEVEL=2

#
# ------- Configuration For High Speed Logging --------->
#

# JLinkExe -if SWD -device nrf5340 -speed 8000 -autoconnect 1 --> Terminal 1
# JLinkRTTClient --> Terminal 2

# Use SEGGER RTT as backend
# CONFIG_USE_SEGGER_RTT=y
# CONFIG_LOG_BACKEND_RTT=y

# High Speed Configurations
# CONFIG_LOG_BACKEND_RTT_MODE_DROP=y
# CONFIG_LOG_BACKEND_RTT_MODE_BLOCK=n
# CONFIG_LOG_BACKEND_RTT_MODE_OVERWRITE=n

# Target -> host buffer
# CONFIG_SEGGER_RTT_BUFFER_SIZE_DOWN=8192
# Host -> target buffer
# CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=8192

# Max log message size, Valid for Drop Mode
# CONFIG_LOG_BACKEND_RTT_MESSAGE_SIZE=256

# Logger up-buffer
# CONFIG_LOG_BACKEND_RTT_BUFFER=1
# CONFIG_LOG_BACKEND_RTT_BUFFER_SIZE=8192

# Retry settings, Valid for Block Mode
# CONFIG_LOG_BACKEND_RTT_RETRY_CNT=10
# CONFIG_LOG_BACKEND_RTT_RETRY_DELAY_MS=10
# Message formatting buffer
# CONFIG_LOG_BACKEND_RTT_OUTPUT_BUFFER_SIZE=512


# -------------------------------
# Ant-b1x configuration
# ------------------------------
CONFIG_UART_INTERRUPT_DRIVEN=y
# NCS 3.2.0 (nrfx 4.0) migration: per-instance CONFIG_NRFX_UARTE1 was consolidated into the
# single CONFIG_NRFX_UARTE option; the concrete instance (UARTE1) is still selected via the
# uart1 devicetree node status = "okay" (see boards/*.overlay).
CONFIG_NRFX_UARTE=y
# CONFIG_TFM_LOG_LEVEL_SILENCE=y # CRITICAL : Disable TFM logs on UART1, Don't enable this.

# ---- UART DMA configurations ------------
CONFIG_UART_ASYNC_API=y # Enable for DMA
CONFIG_UART_1_ASYNC=y # Enable DMA support for UART1
CONFIG_UART_1_INTERRUPT_DRIVEN=n # Disable interrupt to use DMA
CONFIG_RING_BUFFER=y

CONFIG_HEAP_MEM_POOL_SIZE=35840

# -------------------------------
# STACK size configurations
# -------------------------------
CONFIG_MAIN_STACK_SIZE=8196
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

CONFIG_MCUMGR_MGMT_NOTIFICATION_HOOKS=y
CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS=y
CONFIG_MCUMGR_GRP_IMG_UPLOAD_CHECK_HOOK=y

CONFIG_WATCHDOG=y
CONFIG_STREAM_FLASH=y
CONFIG_STREAM_FLASH_ERASE=y
CONFIG_DFU_TARGET=y
CONFIG_DFU_TARGET_STREAM=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_DFU_TARGET_MODEM_DELTA=n
CONFIG_MPU_ALLOW_FLASH_WRITE=y

# -------------------------------
# ANT-B10 firmware update (SMP/mcumgr serial client, module/smp_dfu.c)
# -------------------------------
# No new Kconfig options required: this feature relays/uploads the ANT-B10 image using a
# self-contained base64/CRC16/CBOR implementation (does not use CONFIG_ZCBOR / CONFIG_BASE64,
# which stay enabled above only for the existing BT MCUmgr DFU and Nordic self-update paths).
# It reuses the already-enabled CONFIG_FILE_SYSTEM_LITTLEFS (image staging) and the existing
# UART1/ANT-B10 driver config above (CONFIG_NRFX_UARTE, CONFIG_UART_ASYNC_API, etc.).
#
# Standalone ANT-B10 DFU POC (module/antb10_dfu_poc.c, embedded-buffer test): disabled by
# default. To enable, uncomment the line below and rebuild:
#CONFIG_ANTB10_DFU_POC=y

And using ncs version 3.3.0 and tool chain version 3.3.0 but still facing the same issue.

RE: nRF Stop scanning coded phy beacon

saurabh_embrill — Fri, 18 Sep 2026 12:21:29 GMT

Hello Einar Thorsrud ,
Thanks for your reply,
is this issue fixed in nrf connect sdk 3.3.0 ?

RE: nRF Stop scanning coded phy beacon

Einar Thorsrud — Thu, 17 Sep 2026 14:43:19 GMT

Hi,

There is a known issue in the SoftDevice Controller where sometimes stopped generating advertising reprots when doing extended scanning (like scanning coded PHY). This is fixed in nRF Connect SDK 3.1.0, so i recommend updateing to that or later.