nrfutil pkg generate with bootloader only generates unexpected and invalid package

RE: nrfutil pkg generate with bootloader only generates unexpected and invalid package

Amanda Hsieh — Wed, 23 Oct 2019 09:21:15 GMT

Hi,

It looks like a typo in the document.

Yes, you are right. What they mean is that you can either pass a *.bin or a *.hex file (in intelHex format). However, the nrfutil expects it to be .hex which is the output in all of our SDK examples.

-Amanda H.

RE: nrfutil pkg generate with bootloader only generates unexpected and invalid package

andreasd — Tue, 22 Oct 2019 15:27:20 GMT

Hi Amanda, thanks for the reply. What does the documentation mean by "hexadecimal format"? I'm pretty sure nrfutil works with what I think are Intel HEX files, as long as they have the file extension .hex.

RE: nrfutil pkg generate with bootloader only generates unexpected and invalid package

Amanda Hsieh — Fri, 18 Oct 2019 12:21:32 GMT

Hi,

According to the Creating a firmware package with nrfutil page:

You can add the following firmware images in binary or hexadecimal format to the zip file:

--application image: an image of an application
--bootloader image: an image of a bootloader
--softdevice image: an image of a SoftDevice

However, Intel HEX is not recognized or supported by nrfutil.

I would report to the development team. Thanks for the feedback.

-Amanda H.

RE: nrfutil pkg generate with bootloader only generates unexpected and invalid package

andreasd — Fri, 18 Oct 2019 08:12:06 GMT

Found the culprit: The problem is the file ending .ihex (which was used by the Toolchain/Makefile I was using to generate the project).

nrfutill doesn't seem to recognize this as a valid hex file and does strange things with it. Renaming the file to Bootloader.hex yields the expected result.

Still, would you consider this a bug in nrfutil that should be fixed?