Hi,

I used the Jlink to program the feather using the 6 pin Tag connect header and used nrfjprog in cmd line to program the board using the following command:

C:\Users\Chris>nrfjprog --program "C:\Users\Chris\OneDrive\Copper\copperCubeNRF9160\app\build\zephyr\merged.hex" --chiperase -f NRF91 --snr 50120338 --verify

I get the following results:
Parsing image file. Verifying programming. Verified OK.

I found this to not work and now when I try to program the board I get an error 3 in VSCode. Jlink can still attach to the CPU. Any thoughts on how to resolve this?

I can put the device into programming mode by holding the mode button and the blue led lights up consistently.

Any insight would be helpful, thanks!

    You should only need

    nrfjprog --program <hex name> --chiperase

    What programmer are you using. There are only certain ones that support the nRF91.

    cchoi22915 I get the following results:
    Parsing image file. Verifying programming. Verified OK.

    This appears to be the right output.

    cchoi22915 I can put the device into programming mode by holding the mode button and the blue led lights up consistently.

    This is only for loading over USB using newtmgr.

    Are you programming the nRF9160 Feather or another board?

          jaredwolff

          I am using a Jlink Base using Commander V7.66b. I have successfully programmed the feather using this method, but it appears the UART bootloader is gone?

          This is only for loading over USB using newtmgr.

          Yes I am trying to use newtmgr to program the feather after I have programmed the board using a tag connect, and now I cannot use newtmgr.

          I am programming the feather along with another board. I am talking about the feather in this case.

              cchoi22915

              # Enable Zephyr application to be booted by MCUboot
CONFIG_BOOTLOADER_MCUBOOT=y

              Gotta make sure that the bootloader is turned on using the above ☝️ Place it in your prj.conf or within a circuitdojo_feather_nrf9160_ns.conf if you have one.

                Terms and Conditions | Privacy Policy