nRF7002DK board target nrf7002dk_nrf5340_cpuapp_ns is not working for v2.7.0-rc3

[Abhishek]

Hello,

I wanted to evaluate the nRF53 platform with nrf connect SDK so I got new nRF7002DK board. I have following versions of all tools installed.

- nRF connect SDK :- v2.7.0-rc3

- Toolchain version :- v2.6.0

- Board :- nRF7002DK

When I tried to do the build configuration I am getting following error.

-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
CMake Warning at D:/ncs/v2.7.0-rc3/zephyr/cmake/modules/boards.cmake:110 (message):
  Deprecated BOARD=nrf7002dk_nrf5340_cpuapp_ns specified, board automatically
  changed to: nrf7002dk/nrf5340/cpuapp_ns.
Call Stack (most recent call first):
  D:/ncs/v2.7.0-rc3/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
  D:/ncs/v2.7.0-rc3/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  D:/ncs/v2.7.0-rc3/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)


CMake Error at D:/ncs/v2.7.0-rc3/zephyr/cmake/modules/boards.cmake:320 (message):
  Board qualifiers `/nrf5340/cpuapp_ns` for board `nrf7002dk` not found.
  Please specify a valid board target.

  Valid board targets for nrf7002dk are:

  nrf7002dk/nrf5340/cpuapp

  nrf7002dk/nrf5340/cpuapp/ns

  nrf7002dk/nrf5340/cpuapp/nrf7001

  nrf7002dk/nrf5340/cpuapp/nrf7001/ns

  nrf7002dk/nrf5340/cpunet

  nrf7002dk/nrf5340/cpunet/nrf7001

Call Stack (most recent call first):
  D:/ncs/v2.7.0-rc3/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
  D:/ncs/v2.7.0-rc3/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  D:/ncs/v2.7.0-rc3/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)

It works with board target nrf7002dk_nrf5340_cpuapp. Can someone help me solve this issue as i want to work with trusted unit so want to select _ns version of board.

Thanks

[runsiv]

Hi

I would recommend using the same toolchain as SDK version. As NCS 2.7 is out I would suggest using it instead of 2.7-rc3 and using the correct toolchain. 

Which sample are you trying? You would need to add TF-M, which you can do by adding CONFIG_BUILD_WITH_TFM in your prj.conf. I would also suggest having a look at Running applications with Trusted Firmware-M. 

Additionally, there is TF-M secure peripheral partition sample which demonstrates the configuration of peripherals as secure peripherals, and the usage of the secure peripherals in the secure partition

Regards

Runar

[Abhishek]

Hi,

Thanks for replay. I was trying blinky sample earlier to keep things simple.
As per your suggestion, now I have 2.7 for both SDK and tool chain.Now trying to build TF-M secure peripheral partition for nRF7002dk board (you can see the snapshot of configuration below) which results in same result as mentioned in description earlier.

As far as my analysis goes this is problem in some cmake file regarding board resolution as it tried to resolve it to ``nrf5340/cpuapp_ns`` but in SDK now we have files in ``nrf5340/cpuapp/ns``.

[runsiv]

Something here is a bit strange. Your build target should be nrf7002dk/nrf5340/cpuapp/ns due to the new naming scheme 

I would guess you have not changed toolchain/version. So I would verify that you have the correct version selected of both and then delete the build configuration and try again

Regards

Runar

[Abhishek]

Seems possible that the boards are not shown correctly as you mentioned. However I had only one toolchain version installed and I see only these borads and not with /../../
Following is an image which where you can see active versions of toolchain and sdk.

[runsiv]

Did you close the build configuration window between switching SDK version? You will need to do it after switching. 

I see know that the T-FM secure sample needed more configuration that what I initially believed 

Regards

Runar

[Abhishek]

I deleted everything including vscode restarted my machine and did fresh setup only for 2.7.0.

There is no improvement. Build configuration window still shows same board types as mentioned in comment above.

Regards,