Not updated with Build(ACTIONS/Build)

RE: Not updated with Build(ACTIONS/Build)

KatoTakayuki — Tue, 24 Feb 2026 00:23:39 GMT

This issue appears to have been derived from another issue (Case ID: 357348).

"Build" still does not create merged.hex, but there are no problems when debugging.
This issue will be closed for now.

Thank you for your response.

Best regards,

Kato.

RE: Not updated with Build(ACTIONS/Build)

Samruddhi Jadhav — Fri, 20 Feb 2026 08:40:31 GMT

Hi,

1) Firstly, its supposed to work with normal build not just with pristine build. Are you using the "Generate and Build" option? Sysbuild has to be enabled. Make sure you are selecting the right application or sample in VS Code because which one you select can also affect the build and merge file.

2) Since zephyr.hex is an output file of the Zephyr Project RTOS, you can find it in : build/<your_application_name>/zephyr directory.

3) The programmer app can use both .hex (including zephyr.hex or merged.hex) and .zip files. It then flashes application firmware.

If you want more information on how to program the output build files, take a look at the following documentation: Programming an application

Best Regards,

Samruddhi

RE: Not updated with Build(ACTIONS/Build)

KatoTakayuki — Thu, 19 Feb 2026 00:58:40 GMT

Thanks your constant support.

I may have made a basic mistake. Let me confirm the following.

merged.hex(./build/merged.hex) is only created in "Pristine Build".
Does "Build" create up to zephyr.elf/zephyr.hex (./build/1nce9151/zephyr/zephyr.*)?
("Build" does not create merged.hex)
Is zephyr.hex the file to be written with "Programmer" (nRF Connect for Desktop)?
(I was writing merged.hex)

In this case, the current behavior is correct.

Best Regards.

Kato.

RE: Not updated with Build(ACTIONS/Build)

Samruddhi Jadhav — Wed, 18 Feb 2026 13:20:59 GMT

Hi,

Your board target seems fine. Normally, if you have made any changes to the board target or proj.conf, you would use pristine build to rebuild from scratch which ensures there are no errors or cached files. If the merged.hex is created by using "pristine build" but not "build", this may be caused by a fault during the build configuration. There are a couple of things, I would recommend you to check:

Do you see any option or box in the configuration to generate a hex file which has to be enabled?
What is the output log showing with just "build"? Are there any warnings or errors here? It would be great if you could share the output log.
Have you also checked your build directory for the hex file?
Is sysbuild enabled?
Have you configured your application such that it includes a bootloader or security peripheral manager?

I would also recommend you to check this Output build files documentation to see if you are getting any other output files which are also listed in this. The type of file can help to understand more about the configuration.

Are you using any of our samples?

Best Regards,

Samruddhi

RE: Not updated with Build(ACTIONS/Build)

KatoTakayuki — Wed, 18 Feb 2026 00:43:03 GMT

Thanks,

My board settings are as follows:

The following operation failed: (The hex file is not updated.)

This is successful. (The hex file is updated.)

There is no error message in either case.

Best regards,
Kato.

RE: Not updated with Build(ACTIONS/Build)

Samruddhi Jadhav — Tue, 17 Feb 2026 09:27:36 GMT

Hi,

What is the board target which you are setting for your custom board? Is it in the format: <custom_board_name>/nrf9151/ns? Ensure that you are using /ns because this gives the merged image.

You should be able to see the merged file in : <build_dir>/zephyr/merged.hex.

You can take a look at our Merging files with mergehex documentation for merghex commands and how to merge three HEX files.

Let me know if you have any further questions.

Best Regards,

Samruddhi