Using shell_module sample program with nRF54H20 PDK

[DBT]

I recently got an nRF54H20 PDK board and went through the Getting started with the nRF54H20 DK guide

That seemed to go well and the Hello World example at the end seemed to work.

I updated nRF Connect for Desktop (v5.0.2)

I updated Toolchain Manager (v1.5.1)

I installed nRF Connect SDK v2.7.0

Now I'm trying to use the nRF54H20 PDK board with some standard sample programs

Within Toolchain Manager I clicked on "Open VS Code" for v2.7.0 then click on the nRF Connect extension within VS Code.  It shows the toolchain and workspace as v2.7.0

I click on "Create a new application", "Copy a sample", search on "shell" and click on "Shell Sample" and choose a directory "c:\wm3.1\shell_module_270D"

In the pop up I choose "Open" and click on the nRF Connect extension

The toolchain and workspace now show v2.6.0

I change both back to v2.7.0

I click "add build configuration" under shell_module_270D

I change the board and optimization settings, then click "Build Configuration"

The build process aborts with this information in the terminal:

CMake Error at C:/nordic/ncs/v2.7.0/zephyr/cmake/modules/boards.cmake:244 (message):
Invalid BOARD; see above.
Call Stack (most recent call first):
C:/nordic/ncs/v2.7.0/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
C:/nordic/ncs/v2.7.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/nordic/ncs/v2.7.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:4 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\nordic\ncs\toolchains\ce3b5ff664\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/nordic/ncs/toolchains/ce3b5ff664/opt/bin/python.exe '-Bc:\wm3.1\shell_module_270D\build' -GNinja -DBOARD=nrf54h20dk_nrf54h20_cpuapp -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DBOARD_ROOT=c:/wm3.1/shell_module_270d '-Sc:\wm3.1\shell_module_270D'

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

Please let me know if you have some advice for getting past this.

[Kazi Afroza Sultana]

Hello Douglas,

I have built with the following configuration:

Yes the baudrate is as same as 115200.

You may try to change the COM port for your serial terminal?

[DBT]

Thanks Kazi.

I have been able to build/flash the example and have it work on the console.

The issue now is that the results are inconsistent, and I haven't been able to build for debug successfully (Optimize for debugging (-Og) never works).

As described above, I can edit the build configuration, have it work, then if I change something (board target, optimization level, base configuration file, extra Kconfig fragmet, etc.) it might break (so it stops working).  Then if I revert back to the settings I had before (that were working before) it still doesn't work.  It seems almost random whether the build will work or not.  When I say a build works it means that it builds and flashes successfully and I see the shell console on the terminal.

Do you see the same thing?

[DBT]

I'm closing this ticket and continuing it as a private ticket