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,

 This is the 244 line of boards.cmake file (message(FATAL_ERROR "Invalid BOARD; see above.")). 

The application you are trying to build is your custom application?  The board definition files might not be correctly set up or located in the right directory. 

can you share the application folder so I can reproduce here?

[Nguyen Hoan Hoang]

Actually this is generalized error in the latest SDK.  The 2.7 cannot compile for the H20, any example.  Only the previous RC1 works.  There is definitely as bug in the 2.7

[DBT]

Wondering if I'm able to re-open this ticket...K. HELMUT LORD (Field Application Engineer) has been helping me on the side.

He tells me that I actually have an nRF54H20-DK board rather than PDK

He also prompted me to switch to the pre-release version of the VScode extension, which got me a little further, but I'm still having problems. 

After switching to the pre-release version of the VScode extension, I was able to build the project in VScode.
Flashing from VScode appears to work, but I don't see anything on the consoles after flashing.
(The nRF54H20-DK board allocates 2 COM ports. I have both open with settings 115200 baud 8N1 but neither show anything after flashing or pushing the reset button)
I tried looking at what's programmed using the Programmer app. It shows these failures when reading the memory:

I tried "Erase All" in the Programmer app and got these errors

Remember that I ran this board through the Getting started with the nRF54H20 DK stuff

It included things like this that I'm not sure I understand yet (but the hello world sample worked at the time)

Programming the BICR

Programming the SDFW and SCFW

Transitioning the nRF54H20 SoC to RoT

Programming the sample (which I think programs multiple cores)

Did that make it so that the sample shell program won't run on this board?

Or did something about flashing from VScode mess up something from the "getting started" exercise?

I also tried the following (in the "getting started" exercise:

nrfutil device recover --core Application (seemed to work)

nrfutil device recover --core Network (seemed to work)

Reflashed using VScode - but still nothing on the consoles 

Any ideas of what is needed?

[Kazi Afroza Sultana]

Hello,

We have tried your sample on nRF54H20 DK (PCA10175 v0.8.0), and it worked fine here. We also got output accordingly on the terminal.

You can check if both west and toolchains are same version of 2.7.0

Thanks.

BR

Kazi

[DBT]

Well, I had a second nRF54H20 DK (PCA10175 v0.8.0) board that was unopened.  I tried flashing it via VSCode which appeared to work (no warnings/errors) but still saw no console.  I'm using console settings of 115200 baud 8N1.  Is that what you are using?

Could you also share the steps that you take once you open VScode when using the shell_module sample?  

Do you "Create a new application" or "Open an existing application"?

When you add a build configuration, what settings do you use?

[DBT]

Never mind.  I think the issue is that I needed to choose something in Edit Build Configuration for "Add Configuration File".  I chose "prj.conf" and built/flashed, and now I see the console.

[DBT]

Within a few minutes of writing that last response I realized there's still something wrong.  If I make a change to the build configuration (like changing the board target from nrf54h20dk/nrf54h20/cpurad to nrf54h20dk/nrf54h20/cpuapp, changing the optimization level, add/remove a base configuration file, add/remove an extra Kconfig fragmet, etc.), click on "Build Configuration" then "Flash", the console may or may not come up.  If the console was working and then I make a change and it stops working, if I revert the changes it may or may not start working again.

I tried figuring out if there is a pattern but it seems random.  Do you get the same results?