Flashing an application using the Actinius I/O Serial Programmer

[Neso]

Hi. I'm trying to flash the Cell Fund Lesson 4, Exercise 1 app – Reading buttons and controlling LEDs over MQTT, to an Icarus IoT Board v2 using the Actinius I/O Serial Programmer via usb.

I'm using SDK v2.8.0 and have flashed this successfully to the Thingy91.

I tried clean builds, and also tried including the following to prj.conf for the Icarus IoT Board v2 build with board target actinius_icarus/nrf9160/ns

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_BUILD_OUTPUT_BIN=y

App builds fine, but I can't find the app_update.bin file. (or zephyr.signed.bin) and trying to flash any other *.bin file from the <path>MQTT_broker\IcarusBuild\MQTT_broker\zephyr folder gives an "Upload failed Firmware is not a valid device image." message.

What am I doing wrong?

[dejans]

Hi,

Do you see the same behavior when using any older NCS version?
You could try the same exercise for NCS v2.4.0-v2.6.2 and for NCS v2.2.0-v2.3.0.

How are Thingy91 and Icarus IoT board related in your case regarding existence of update files?

Best regards,
Dejan

[Neso]

Haven't tried older versions. What do you mean by update files?
I see that my nrf9160 and icarus builds are missing the mcuboot folder completely. Trying to figure that out at the moment.

[Neso]

Test

[Neso]

No.. I'm able to build and flash successfully to the Thingy91, but building for the Icarus IoT V2 does not generate an app_update.bin (or zephyr.signed.bin) file, so I'm unable to flash it.

With SB_CONFIG_BOOTLOADER_MCUBOOT=y in prj.conf, nothing changed. Still no bin file.

When I included a sysbuild.conf file with SB_CONFIG_BOOTLOADER_MCUBOOT=y like you said, the build fails.
 
Files included. See Build_Fail.txt for build log. Wasn't able to include it here. 

Icarus_Fund_L1E2.zip

[dejans]

Hi,

Your Build_fail.txt file appears to be empty. Can you check this and re-upload?

Best regards,
Dejan

[Neso]

I get errors when trying to paste it into this section. 

Build_Fail.zip

[dejans]

Hi,

I can see in your log that conflicting file names have been discovered by the build system.

CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/extensions.cmake:2842 (message):
  Conflicting file names discovered.  Cannot use both
  actinius_icarus_nrf9160.conf and actinius_icarus.conf.  Please choose one
  naming style, actinius_icarus_nrf9160.conf is recommended.

You could try to resolve this naming issue.

Best regards,
Dejan

[Neso]

Holy.. Not sure how I got this conflict, but I deleted and installed board files again. It worked.

[Neso]

My colleague got the same duplicate file error on Mac. Is it something wrong in the nRF connect install?

[dejans]

Hi,

Neso said:

Not sure how I got this conflict, but I deleted and installed board files again. It worked.

That is great to hear.

Neso said:

My colleague got the same duplicate file error on Mac.

Did it work for your colleague as well after re-installing board files?
Which operating system do you use?

Neso said:

Is it something wrong in the nRF connect install?

There should not be anything wrong. How did you install your NCS v2.8.0?

Best regards,
Dejan