RE: Guidance on how to modify pin assignments

kcl — Fri, 22 Mar 2024 04:12:28 GMT

Thank you so much for your assistance. I just realized that the nRF7002EK use SPIM instead of QSPI. I have successfully built and executed the wifi_shell example on my custom board.

RE: Guidance on how to modify pin assignments

Sigurd Hellesvik — Thu, 21 Mar 2024 14:18:37 GMT

The shield redefine arduino_spi, so this node needs to exist for your board.

RE: Guidance on how to modify pin assignments

kcl — Thu, 21 Mar 2024 09:54:08 GMT

Thank you for the prompt response. I have made the necessary changes to the pin assignment based on the nRF Connect SDK course. However, I am facing difficulties when attempting to build the example wifi_shell project using my custom board. The hardware connection on my nRF7002 is identical to that of the nRF7002 EK, and the nRF52840 QSPI connection follows the recommendations in the datasheet as follow.

P0.19 <---> QSPI-CLK
P0.21 <---> QSPI0
P0.22 <---> QSPI1
P0.18/nRESET <---> QSPI-CS
P0.23 <---> QSPI3
P1.00 <---> QSPI2

Despite I am not using "arduino_spi", the error indicating that "arduino_spi" is missing in the devicetree file. I would like to know how I can assign the nRF7002 to use QSPI instead of "arduino_spi". Any guidance on this matter would be greatly appreciated.

The error code I am receiving is:

Building shell_custom
C:\WINDOWS\system32\cmd.exe /d /s /c "west build --build-dir d:/ncs/shell_custom/build d:/ncs/shell_custom --pristine --board tracker_nrf52840 --no-sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DCONFIG_CORTEX_M_DEBUG_MONITOR_HOOK=y -DCONFIG_SEGGER_DEBUGMON=y -DBOARD_ROOT=d:/ncs/my_board;d:/ncs/shell_custom -DSHIELD=nrf7002ek"

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: D:/ncs/shell_custom
-- CMake version: 3.20.5
-- Found Python3: D:/ncs/toolchains/c57af46cb7/opt/bin/python.exe (found suitable version "3.8.2", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: D:/ncs/v2.5.1/zephyr/.cache
-- Zephyr version: 3.4.99 (D:/ncs/v2.5.1/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: tracker_nrf52840
-- Shield(s): nrf7002ek
-- Found host-tools: zephyr 0.16.1 (D:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (D:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found Dtc: D:/ncs/toolchains/c57af46cb7/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: D:/ncs/my_board/boards/arm/tracker_nrf52840/tracker_nrf52840.dts
-- Found devicetree overlay: D:/ncs/v2.5.1/nrf/boards/shields/nrf7002ek/nrf7002ek.overlay
devicetree error: D:/ncs/v2.5.1/nrf/boards/shields/nrf7002ek/nrf7002ek.overlay:8 (column 1): parse error: undefined node label 'arduino_spi'
CMake Error at D:/ncs/v2.5.1/zephyr/cmake/modules/dts.cmake:279 (message):
gen_defines.py failed with return code: 1
Call Stack (most recent call first):
D:/ncs/v2.5.1/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
D:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
D:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:9 (find_package)

-- In: D:/ncs/shell_custom/build/zephyr, command: D:/ncs/toolchains/c57af46cb7/opt/bin/python.exe;D:/ncs/v2.5.1/zephyr/scripts/dts/gen_defines.py;--dts;D:/ncs/shell_custom/build/zephyr/zephyr.dts.pre;--dtc-flags;'';--bindings-dirs;D:/ncs/v2.5.1/nrf/dts/bindings;D:/ncs/v2.5.1/zephyr/dts/bindings;--header-out;D:/ncs/shell_custom/build/zephyr/include/generated/devicetree_generated.h.new;--dts-out;D:/ncs/shell_custom/build/zephyr/zephyr.dts.new;--edt-pickle-out;D:/ncs/shell_custom/build/zephyr/edt.pickle;--vendor-prefixes;D:/ncs/v2.5.1/nrf/dts/bindings/vendor-prefixes.txt;--vendor-prefixes;D:/ncs/v2.5.1/zephyr/dts/bindings/vendor-prefixes.txt
-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'D:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' -DWEST_PYTHON=D:/ncs/toolchains/c57af46cb7/opt/bin/python.exe '-Bd:\ncs\shell_custom\build' -GNinja -DBOARD=tracker_nrf52840 -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DCONFIG_CORTEX_M_DEBUG_MONITOR_HOOK=y -DCONFIG_SEGGER_DEBUGMON=y '-DBOARD_ROOT=d:/ncs/my_board;d:/ncs/shell_custom' -DSHIELD=nrf7002ek '-Sd:\ncs\shell_custom'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

here is the custom board devicetree files.

devzone.nordicsemi.com/.../tracker_5F00_nrf52840.zip

RE: Guidance on how to modify pin assignments

Sigurd Hellesvik — Wed, 20 Mar 2024 14:55:08 GMT

Hi,

You change pins by creating a custom board and configuring the DeviceTree for the custom board.

To learn about how this works, see the following courses:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate

Regards,
Sigurd Hellesvik