VSCode - Zephyr SDK Tools install - challenge

cptel

I have a macbook Air and am stuck at the ‘Initializing Project’ screen. Thoughts on how I can proceed?

any easy way to attach a screenshot here?

jaredwolff

cptel you should be able to drag the file or upload it using the image option. The logs are also selectable/copyable

cptel

managed to get a bit further, but not much. Here’s the log:

note: pip –version (response) and the pip new release error - which is incorrect.
pip 25.2 from /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pip (python 3.13)

********** LOG START *************

Executing task: west init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git –mf west.yml

FATAL ERROR: already initialized in /opt/nordic/ncs/zephyrproject, aborting.
Note:
In your environment, ZEPHYR_BASE is set to:
/opt/nordic/ncs/zephyrproject/zephyr

This forces west to search for a workspace there.
Try unsetting ZEPHYR_BASE and re-running this command.

The terminal process “/bin/zsh ‘-l’, ‘-c’, ‘west init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git –mf west.yml’” terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.
Executing task: west update

=== updating acpica (modules/lib/acpica):
HEAD is now at 8d24867bc Merge pull request #5 from dcpleung/kernel/mm_z_phys_map_unmap_rename
=== updating cmsis (modules/hal/cmsis):
HEAD is now at d1b8b20 Backport CMSIS_6#102 to CMSIS 5.9.0
=== updating cmsis-dsp (modules/lib/cmsis-dsp):
HEAD is now at d80a49b2 do not generate warnings when scalar functions are used with MVE
=== updating cmsis-nn (modules/lib/cmsis-nn):
HEAD is now at e9328d6 manifest: zephyr module file
=== updating cmsis_6 (modules/hal/cmsis_6):
HEAD is now at 6dd50439 cmsis_6: Integrate with zephyr build system
=== updating edtt (tools/edtt):
HEAD is now at b9ca3c7 Fix for for python >= 3.11
=== updating fatfs (modules/fs/fatfs):
HEAD is now at 16245c7 fs: Update driver to version 0.15a
=== updating hal_adi (modules/hal/adi):
HEAD is now at f8f6547 chore(PeriphDrivers): Replace pow() with left shift in UART drivers
=== updating hal_ambiq (modules/hal/ambiq):
HEAD is now at 080be37 hal: cmakelist: add uart hal support for apollo510
=== updating hal_atmel (modules/hal/atmel):
HEAD is now at ca7e4c6 sam3x: spi: missing adc macro
=== updating hal_bouffalolab (modules/hal/bouffalolab):
HEAD is now at 5811738 bflb: add register files for bl60x
=== updating hal_espressif (modules/hal/espressif):
HEAD is now at 19deab4177 esp32c2: rom: use puts from system libc
=== updating hal_ethos_u (modules/hal/ethos_u):
HEAD is now at 50ddffc Cache optimizations
=== updating hal_gigadevice (modules/hal/gigadevice):
HEAD is now at 2994b7d README.md: add pllmf and pack exception for gd32a50x
=== updating hal_infineon (modules/hal/infineon):
HEAD is now at e0a50ce hal: infineon: Update bt_stack-integration for 20829
=== updating hal_intel (modules/hal/intel):
HEAD is now at 0447cd2 Update pm_regs.h
=== updating hal_microchip (modules/hal/microchip):
HEAD is now at 15ca197 hal: microchip: mec5: Fix bugs in EC subsystem debug enable
=== updating hal_nordic (modules/hal/nordic):
HEAD is now at a5a2277 nrfx: drivers: rramc: Declare functions as unused
=== updating hal_nuvoton (modules/hal/nuvoton):
HEAD is now at be1042d hal:nuvoton:m55m1: support emac
=== updating hal_nxp (modules/hal/nxp):
HEAD is now at a961ce3b drivers: usdhc: change the driver to be aarch64 compatible
=== updating hal_openisa (modules/hal/openisa):
HEAD is now at eabd530 fix-double-promotion in fsl_xcvr_trim
=== updating hal_quicklogic (modules/hal/quicklogic):
HEAD is now at bad8944 HAL: eoss3_dev: add missing __cplusplus handling
=== updating hal_renesas (modules/hal/renesas):
HEAD is now at 9d68ee7 portable: rp_crc: add runtime reconfigure for CRC
=== updating hal_rpi_pico (modules/hal/rpi_pico):
HEAD is now at 7b57b24 Merge pull request #8 from ajf58/merge-2.1.0
=== updating hal_silabs (modules/hal/silabs):
HEAD is now at 389726f wiseconnect: Avoid symbols conflicts in PSRAM driver
=== updating hal_st (modules/hal/st):
HEAD is now at 9f81b44 sensor/stmemsc: Align stmemsc i/f to v2.9.1
=== updating hal_stm32 (modules/hal/stm32):
HEAD is now at 6e4716f8 dts: st: update pinctrls related to dcmipp pins
=== updating hal_tdk (modules/hal/tdk):
HEAD is now at 6727477 Merge pull request #8 from tdk-invn-oss/main
=== updating hal_telink (modules/hal/telink):
HEAD is now at 4226c7f drivers: Disable BLE support
=== updating hal_ti (modules/hal/ti):
HEAD is now at 258652a simplelink_lpf3: Add README.md
=== updating hal_wch (modules/hal/wch):
HEAD is now at 1de9d3e Add hal_wch based on the ‘ch32v003fun’ project
=== updating hal_wurthelektronik (modules/hal/wurthelektronik):
HEAD is now at e3e2797 Remove preprocessor warnings for not enabling float
=== updating hal_xtensa (modules/hal/xtensa):
HEAD is now at b38620c zephyr: Add SoC overlay for i.MXRT700 HiFi1 DSP
=== updating hostap (modules/lib/hostap):
HEAD is now at 8412f4b23 [noup] zephyr: remove zephyr wpas monitor socket pair
=== updating liblc3 (modules/lib/liblc3):
HEAD is now at 48bbd3e Rename lc3 python package to lc3py, and bump version to 1.1.2
=== updating libmctp (modules/lib/libmctp):
HEAD is now at b97860e build MCTP zephyr library only when CONFIG_MCTP is enabled
=== updating libmetal (modules/hal/libmetal):
HEAD is now at 14f5195 lib: update libmetal to SHA 9a21915a5f8f
=== updating littlefs (modules/fs/littlefs):
HEAD is now at ed0531d Merge pull request #15 from Jappie3/zephyr
=== updating loramac-node (modules/lib/loramac-node):
HEAD is now at fb00b383 zephyr: configure FragDecoder using Kconfig
=== updating lvgl (modules/lib/gui/lvgl):
HEAD is now at 1ed1ddd88 docs(Alif): add docs for Alif chip vendor (#7622)
=== updating mbedtls (modules/crypto/mbedtls):
HEAD is now at 5f8899343 Merge pull request #70 from tomi-font/bump_to_3.6.3
=== updating mcuboot (bootloader/mcuboot):
HEAD is now at 990b1fcb docs: release-notes: Add additional fixes
=== updating mipi-sys-t (modules/debug/mipi-sys-t):
HEAD is now at 33e5c23 Fix for warning of potential error using = instead of ==
=== updating net-tools (tools/net-tools):
HEAD is now at 986bfeb Replace native_posix with native_sim
=== updating nrf_hw_models (modules/bsim_hw_models/nrf_hw_models):
HEAD is now at d5b95fd grtc hal replacement: Fix bug in nrf_grtc_int_group_enable/disable()
=== updating nrf_wifi (modules/lib/nrf_wifi):
HEAD is now at e0adc31 nrf_wifi : Update Wi-Fi FW blobs and shared header file
=== updating open-amp (modules/lib/open-amp):
HEAD is now at f7f4d08 lib: update open-amp lib to SHA 9a21915a5f8f
=== updating openthread (modules/lib/openthread):
HEAD is now at 3ae741f95 [instance] fix index computation in multi-instances context (#11099)
=== updating percepio (modules/debug/percepio):
HEAD is now at 49e6dc2 Merge branch ‘main’ into zephyr
=== updating picolibc (modules/lib/picolibc):
HEAD is now at 82d62ed1a zephyr: Disable LTO when building the library
=== updating segger (modules/debug/segger):
HEAD is now at cf56b1d readme: Add readme
=== updating tinycrypt (modules/crypto/tinycrypt):
HEAD is now at 1012a3e Fix warnings reported by UBSAN
=== updating trusted-firmware-a (modules/tee/tf-a/trusted-firmware-a):
HEAD is now at 713ffbf96 Merge pull request #4 from ceolin/v2.10.4
=== updating trusted-firmware-m (modules/tee/tf-m/trusted-firmware-m):
HEAD is now at 64738996d Revert “platform: ext: add local copy of CMSIS v6 files”
=== updating uoscore-uedhoc (modules/lib/uoscore-uedhoc):
HEAD is now at 54abc10 Merge pull request #5 from rlubos/upmerge-02-2025
=== updating zcbor (modules/lib/zcbor):
HEAD is now at 9b07780 Update version to 0.9.1

Terminal will be reused by tasks, press any key to close it.
Executing task: “/Users/summer/.zephyrtools/env/bin/python” -m pip install -r zephyr/scripts/requirements.txt

[notice] A new release of pip is available: 25.0.1 -> 25.2
[notice] To update, run: python -m pip install –upgrade pip
ERROR: Could not open requirements file: [Errno 2] No such file or directory: ‘zephyr/scripts/requirements.txt’

The terminal process “/bin/zsh ‘-l’, ‘-c’, ‘”/Users/summer/.zephyrtools/env/bin/python" -m pip install -r zephyr/scripts/requirements.txt’" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.

jaredwolff

cptel that actually shows a lot. Nordic’s tools are redirecting using their SDK vs the one that is getting pulled down with the application. It’s an either or. You can’t have both. I would disable Nordic’s extension, close VSCode, then init into a fresh directory.

Otherwise if you prefer keeping their tools, then follow these instructions: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html Make sure you disable the CD extension.

cptel

jaredwolff Thx!

cptel

Goal: using vs-code, build the “blinky” and program the Feather v1 board.

I downloaded the project from “https://github.com/circuitdojo/nrf9151-feather”
opened the “blinky” sample code in vs-code
In build-config: Board target, i do not see an option for circuitdojo/nrf9151-feather/ns. And same for all available sample apps. However, I am able to see that as an option for the original software I created for 9151dk.

Thoughts on why I am not seeing the circuitdojo/nrf9151-feather/ns board option?

cptel

one more… looking at this page: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html at the bottom, the install and other commands appear to reference: nRF9160_xxAA board.

I see 9160 and 9151 being inter-mixed.

sounds confusing to this newbie 🙂

jaredwolff

cptel I’ll work on that. Thanks for the feedback

jaredwolff

@cptel

Regarding build targets you can use this CMakePresets.json:

{
    "version": 2,
    "cmakeMinimumRequired": {
        "major": 3,
        "minor": 20
    },
    "configurePresets": [
        {
            "name": "build_nrf9151",
            "displayName": "Build for CircuitDojo Feather nRF9151 Non Secure",
            "generator": "Ninja",
            "binaryDir": "${sourceDir}/build_nrf9151",
            "cacheVariables": {
                "NCS_TOOLCHAIN_VERSION": "NONE",
                "BOARD": "circuitdojo_feather_nrf9151/nrf9151/ns"
            }
        },
        {
            "name": "build_nrf9160",
            "displayName": "Build for CircuitDojo Feather nRF9160 Non Secure",
            "generator": "Ninja",
            "binaryDir": "${sourceDir}/build_nrf9160",
            "cacheVariables": {
                "NCS_TOOLCHAIN_VERSION": "NONE",
                "BOARD": "circuitdojo_feather_nrf9160/nrf9160/ns"
            }
        }
    ]
}

This will pre-populate your build options. Place it in the same folder as the sample you’re trying to populate. It’s very important that you clone as suggested in the docs a the board definitions are located in the Circuit Dojo repoistory.

cptel

Thinking out loud - as I am currently stuck at the “Board Target” in the ‘Add Build Config’ step.
Looking into this further, I navigated to …/zephyr/boards/circuitdojo/feather directory and do not see any boards with name: 9151.
That begs the question - is the circuit dojo 9151 board files added to the west update? Assuming this is where the boards are pulled/populated…

jaredwolff

@cptel did you follow the instructions in https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html? You need to pull a custom repository (https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git). That will pull all the dependencies, including board files, for what you need.

I would recommend setting it up in a fresh directory or else you’re going to keep running into trouble.

cptel

jaredwolff yes, i did that this morning as a fresh pull on a brand new path. I’ll try again in case if I missed anything - fairly confident I did per the steps including the path for custom repository.

jaredwolff

Easy way to check is if you have a nrf9160-feather-examples-and-drivers folder in the project root

These should be the options that pop up if done correctly:

cptel

Yay! I can upload images now 🙂

cptel

to install run… the instructions on https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html says: “pyocd pack install nRF9160_xxAA”. Is that accurate or should it be nRF9151_xxAA?

I ran it as per the instruction with ….nRF9160_xxAA and is taking a while to download the descriptors - is that normal?

Currently stuck (appears to be) at:
0001017 I No pack index present, downloading now… [pack_cmd]
Downloading descriptors (062/1653)

jaredwolff

The recommendation is probe-rs now. I’ve removed pyocd from the docs. Since you’re using Nordic’s setup, you’ll have to invoke probe-rs manually. Here’s more info on setting it up: https://probe.rs/docs/getting-started/installation/

cptel

Success!! able to build and flash Blink and the LED blinks as expected.

on to making this thing supercharged!

Sincerely appreciate your support and patience along the way!

jaredwolff

Woohoo! Awesome @cptel