nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

Toastus — Tue, 08 Sep 2026 18:58:43 GMT

I realize this post is aging, but I want to make a comment here for those who happen to experience a similar problem. What stands out are the warnings from the application build which strongly hint at a fundamental build configuration problem and the app.config, which confirms those problems were indeed applied to the build. I've been building on the nRF54L15 and the only times I've seen these sorts of warnings were when an important node was set to status disabled instead of okay in the device tree.

Here's a warning that caught my attention, for example.

warning: BT_CTLR_TX_PWR_DYNAMIC_CONTROL (defined at subsys/bluetooth\controller/Kconfig:496) was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_HCI_VS (=n),
HAS_BT_CTLR (=n), BT_HCI (=n), BT (=n).

The initial part of the warning, that BT_CTLR_TX_PWR_DYNAMIC_CONTROL is set to 'n' might not alarm you, but its causes given at the bottom of the warning should:

HAS_BT_CTLR(=n) means CONFIG_HAS_BT_CTLR is set to NO in your app.config. This indicates your device has no bluetooth controller! That anything was happening at all in bluetooth is nothing short of a miracle, because bluetooth libraries will not get included typically.

Similarly BT_HCI(=n) means there is no bluetooth host controller interface and BT(=n) tells the build not to support bluetooth.

Was the bluetooth node in your zephyr.dts output set to status=<disabled>? It's not uncommon for some of these nodes to default to disabled unless enabled by an overlay file.

I'm surprised you saw any bluetooth output at all from this build. Are you sure you weren't picking up another system that was further away? It is clearly turned off in the pristine build output you provided.

The whole point of this comment is simple: if you get warnings on a build, it's best to read the entire text to find out why the warning was generated, not just what was the main setting affected. This will help weed out some bad stuff quickly and save you some time in the long run.

I hope this helps someone.

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

ByteSpectrum — Tue, 02 Sep 2025 05:08:59 GMT

Hi Hieu,

No They are not different. Actually, those are from same build.

I am sure it will be very difficult for you to give reason behind this behavior.

As I am not able to reproduce, let's close this thread as of now. I will contact if issue reproduce again in future.

Thanks,

Tarun

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

Hieu — Mon, 01 Sep 2025 19:08:47 GMT

Hi Tarun,

Could you please compare the .bin files from the OTA payload and the merged.hex file you flash directly with the programmer? Are there any chances they are different?

Regards,

Hieu

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

ByteSpectrum — Fri, 29 Aug 2025 10:46:04 GMT

Hi Hieu,

I have found a puzzling issue.

When I updated only the application using an Over-the-Air (OTA) update, the problem persists each and every time. However, when I erased whole flash and flashed both the bootloader and the application together using a programmer, the issue disappeared. Now I am not able to reproduce it.

Any ideas why this might be happening?

Thanks,

Tarun

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

Hieu — Fri, 29 Aug 2025 10:25:24 GMT

Hi Tarun,

I checked the files. So MCUboot doesn't get any BT power config applied, which is expected, because it doesn't have a BT stack. However, that also means that there shouldn't be any strange reason it could affect the TX Power of the main application, whose configurations are properly in place.

Do you use dynamic TX Power control? If not, please try to disable CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL.

If you use dynamic TX Power control, then please try to set it in code.

Hieu

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

ByteSpectrum — Thu, 28 Aug 2025 04:33:38 GMT

Hi Hieu,

Please find attached.

Thanks,

Tarun

devzone.nordicsemi.com/.../pristine_5F00_build_5F00_log.txt devzone.nordicsemi.com/.../app_2E00_config devzone.nordicsemi.com/.../3034_2E00_mcuboot_2E00_config

RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot

Hieu — Wed, 27 Aug 2025 21:22:27 GMT

Hi ByteSpectrum,

Could you please share the following from the build with MCUboot?

The application compiled Kconfig file, located at <build directory>/<application name>/zephyr/.config
The MCUboot compiled Kconfig file, located at <build directory>/mcuboot/zephyr/.config
Full pristine build log

Hieu