This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Actinius Icarus nrF9160 issues with hex file

Hi,

I have a board Actinius Icarus nrf9160 and I'm trying to program with external hex file through nrfConnect sdk and Actinius programmer.

Loading prebuilt example works.

1) I followed step by step the hello_world example. Open nrfConnect sdk project ....

secure or non secure gives anyway the same result.

then I select the project and go to Build Solution.

If I upload now the hex file that I find under /.../hello_world/build_nrf9160dk_nrf9160ns/zephyr/zephyr.hex through Actinius programmer, flashing works fine but the file doesn't work.

Same thing if I download the sample file from Actinius and build the solution through nrf Connect.

Thanks for any support you can provide.

Parents
  • 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.


    secure or non secure gives anyway the same result.

     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

Reply
  • 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.


    secure or non secure gives anyway the same result.

     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

Children
No Data
Related