Actinius Icarus nrF9160 issues with hex file

RE: Actinius Icarus nrF9160 issues with hex file

mike_actinius — Fri, 19 Mar 2021 13:28:52 GMT

Hi Robi,

The screenshots did not come through, but if I understand correctly you tried to upload merged.hex/zephyr.hex via USB (MCUboot) which indeed won't work. The merged.hex should only be used when uploading with a JLink as it contains all of the hex files together (MCUboot, SPM, Application). When uploading with MCUboot, only the application should be uploaded (that's the "app_signed.hex" that is mentioned in the docs).

-- Mike

RE: Actinius Icarus nrF9160 issues with hex file

Robi — Fri, 19 Mar 2021 07:39:29 GMT

Hi Thanks, for the support, but ...

First time I was selecting the wrong board. Quite awkward ...

Now the board is the right one

I'm trying to use the Actinius Programmer to program with Icarus connected directly to the Mac via USB

In hello_world folder

In prj.conf

In CMakeLists.txt

Then I build solution

and I get both merged.hex and zephyr.hex

From Actinius Programmer

And after successful uploading ... nothing happen.

So I went to the link from Mike and added the two files.

and I also tried with and without the two additional lines in CmakeLists.txt

Still the same result. Sorry if I keep wasting your time. I'm probably doing something stupid, but I don't see it (with Arduino was easier ...)

Thanks all

RE: Actinius Icarus nrF9160 issues with hex file

mike_actinius — Thu, 18 Mar 2021 14:34:41 GMT

Hi!

From your screenshots it looks like you have the nRF9160 DK selected as the target for the build instead of the Icarus. Could you confirm that you actually selected the Icarus (actinius_icarus_ns) from the list during your tests? The "3rd party kits" checkbox needs to be checked, otherwise no board other than Nordic's own boards appear in the board lists.

Also, are you uploading via JLink or USB (MCUboot)? If it is the latter, you need to make sure that the partitions in your project are the same as what the MCUboot on the board expects, because partitioning changed after nRF Connect v1.3.x (see https://docs.actinius.com/icarus/building/zephyr). If you are using JLink or you have uploaded MCUboot yourself and you are not using the preinstalled MCUboot you can disregard this!

-- Mike

RE: Actinius Icarus nrF9160 issues with hex file

Heidi — Thu, 18 Mar 2021 12:55:45 GMT

Hi!

When you build using the non-secure board, you need to use the file "merged.hex" (/.../hello_world/build_nrf9160dk_nrf9160ns/zephyr/merged.hex). This is because any application to run on the non-secure board needs have the Secure Partition Manager sample included as a child image, and merged.hex is then the resulting image.

When building for the secure board, "zephyr.hex" is the full application image. I just tested it on my DK and it worked.

[quote user=""]secure or non secure gives anyway the same result.[/quote]

This is strange since "zephyr.hex" is the correct file to use when building for the secure board and when I tested it just now, it worked and printed

*** Booting Zephyr OS build v2.4.99-ncs1  ***
Hello World! nrf9160dk_nrf9160

Could you walk me through the steps you took when building for the secure board and flashing the file to the device?

Best regards,

Heidi