NRF9160 Development Board cannot properly flash the Icarus board with Tag connect.

[ashay]

   After successful compilation of code the west flash command shows this output after using Tag connect to debug the icarus board with the nrf9160 development board. Normally the flashed successfully message should also show the following: - 

Please help me find a solution as its been 3 weeks since I am trying to resolve this problem. The output in the PuTTy terminal is weird and this proves that the flashing action didn't took place correctly. I have deinstalled and reinstalled nrf connect multiple times, also updated and installed the nrf command line tools and also made sure that 

nrfjprog.dll and its exe is in C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin location. I hope to get a response with a working solution as soon as possible. Thank you

[ashay]

Hi Jonathan, 

Before we start the MCU boot mode the Asset Tracker(Factory Firmware Bundle) should be uploaded then a blue light comes in. Only then MCU Boot mode can be succesfully used to write hex files. I wrote the app_signed.hex file but no output at the PuTTy Client also later the blue color fails to show. Can you please tell me which mode should i select on the dk board while using MCU BOOT? should it be nrf52 or nrf91?

Best Regards,

Ashay

[JONATHAN LL]

Can you use west or the programmer(if MCUboot works) to flash the AT_client example on to the Icarus. 

The SW5 is to select what chip to program so it is to the debug input and not debug output, so it does not matter, you can do as they propose in previous link on how to use the DK as a programmer and switch SW5 to nrf52, so that you dont accidently program the DK.

ashay said:

Can you please tell me which mode should i select on the dk board while using MCU BOOT? should it be nrf52 or nrf91?

You dont need to use the DK if you want to use the MCUBoot, then uart/usb is ok.



Regards,
Jonathan