Now the environment is setup, I can build a sample (blinky) successfully.
west build -b circuitdojo_feather_nrf9160/nrf9160/ns -p -d build\circuitdojo_feather_nrf9160
...snip...
-- Configuring done
-- Generating done
-- Build files have been written to: C:/flarehalo/nfed/samples/blinky/build/circuitdojo_feather_nrf9160/blinky/tfm
[10/233] Performing build step for 'tfm'
[136/140] Linking C executable bin\tfm_s.axf
Memory region Used Size Region Size %age Used
FLASH: 31580 B 32256 B 97.90%
RAM: 10404 B 32 KB 31.75%
[140/140] Linking C static library secure_fw\libtfm_s_veneers.a
[12/233] Performing install step for 'tfm'
-- Install configuration: "MinSizeRel"
----- Installing platform NS -----
[233/233] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 19708 B 448 KB 4.30%
RAM: 4968 B 211608 B 2.35%
IDT_LIST: 0 GB 32 KB 0.00%
Generating files from C:/flarehalo/nfed/samples/blinky/build/circuitdojo_feather_nrf9160/blinky/zephyr/zephyr.elf for board: circuitdojo_feather_nrf9160
image.py: sign the payload
image.py: sign the payload
[11/20] Performing build step for 'mcuboot'
[6/223] Generating include/generated/zephyr/version.h
-- Zephyr version: 4.0.99 (C:/flarehalo/zephyr), build: v4.0.99-ncs1-1
[223/223] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 48756 B 48 KB 99.19%
RAM: 24776 B 32 KB 75.61%
IDT_LIST: 0 GB 32 KB 0.00%
Generating files from C:/flarehalo/nfed/samples/blinky/build/circuitdojo_feather_nrf9160/mcuboot/zephyr/zephyr.elf for board: circuitdojo_feather_nrf9160
[20/20] Generating ../merged.hex
Run $ Zephyr Tools: Setup Newtmgr to set the port (COM7) and baud (1000000)
Now I can’t flash it to the device: (its in DFU mode with constant blue led)
$ Zephyr Tools: Load via Bootloader
newtmgr -c vscode-zephyr-tools image upload c:\flarehalo\nfed\samples\blinky\build\circuitdojo_feather_nrf9160\blinky.bin -r 3 -t 0.25
Error: open c:\flarehalo\nfed\samples\blinky\build\circuitdojo_feather_nrf9160\blinky.bin: The system cannot find the file specified.
upload - Upload image to a device
Usage:
newtmgr image upload <image-file> -c <conn_profile> [flags]
Examples:
newtmgr -c olimex image upload bin/slinky_zero/apps/slinky.img
Flags:
-h, --help help for upload
-n, --image int In a multi-image system, which image should be uploaded
-e, --noerase Don't send specific image erase command to start with
-u, --upgrade Only allow the upload if the new image's version is greater than that of the currently running image
Global Flags:
-c, --conn string connection profile to use
--connextra string Additional key-value pair to append to the connstring
--connstring string Connection key-value pairs to use instead of using the profile's connstring
--conntype string Connection type to use instead of using the profile's type
-i, --hci int HCI index for the controller on Linux machine
-l, --loglevel string log level to use (default "info")
--name string name of target BLE device; overrides profile setting
--ompres string Use this CoAP resource instead of /omgr (default "/omgr")
-t, --timeout float timeout in seconds (partial seconds allowed) (default 10)
-r, --tries int total number of tries in case of timeout (default 1)
--write-rsp Send BLE acked write requests instead of unacked write commands
Should the blinky sample work out of the box with the zephyr tools? I don’t think blinky.bin that correct file to flash? (it doesnt exist anyway)
I can manually flash the blinky.signed.bin file, but isnt that what the tool should do?
newtmgr.exe -c vscode-zephyr-tools image upload blinky.signed.bin -r 3 -t 0.25
51.39 KiB / 51.39 KiB [=================================================================================================================] 100.00% 16.53 KiB/s 3s
Done
newtmgr.exe -c vscode-zephyr-tools reset
Done
Am I missing something?
