Adding Custom Board Support

[Jamal_nRF]

Hi there,

Under lesson 3 of devAcademy

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/

There is an "important" mention stating this

"

The lesson covers how to define boards in the nRF Connect SDK up to version 2.6.1. It’s important to note that starting from version 2.7.0, the nRF Connect SDK uses a new hardware model (Hardware Model V2), which is not covered in this lesson.

"

Where / When would support be available for adding custom board support when using the latest nRF Connect SDK version 2.7.x

Thank you

[nordicator_prim3]

Here is the documentation for how to migrate to the new hardware model.

[Jamal_nRF]

the link seems broken

"

We couldn’t find the page you were looking for.

"

[Jamal_nRF]

Thanks Runar,

For a workspace type of application, the source code resides under an application folder --as created automatically by VS Code using this guidelines

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/create_application.html#creating_application_in_the_nrf_connect_for_vs_code_extension

For my project, the application folder is committed to source control (github)

Ideally I would like to have the boards folder located under the application folder.

For creating my new custom board based off the nRF9151dk, I am following guidelines from exercise number 2 as suggested

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/topic/exercise-2-5/

What would be the recommended folder structure to use in this case instead of

C:/my_boards

Thanks,

Jamal

[runsiv]

Hi please see
https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/bd_work_with_boards.html

Its fine to create a folder inside your application and store the boards there. Then you just need to add the folder. 
You can also add the folder inside the settings in the extention

Regards

Runar

[Jamal_nRF]

Hi Runar,

1-

Thanks for the confirmation for locating the boards folder under the application folder--so it does automatically go under source control.

2-

For adding the new custom board, I had to update the BOARD_ROOT variable.

Adding it to the application CMakeLists.txt file as indicated by the devAcademy course

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/topic/exercise-2-5/

3. Point the build system to the custom board root directory.

Option 1: Inside the application CMake file, CMakeLists.txt.

did not work! --several build errors!

FYI,

As a starting point, I am using the Serial LTE Modem application from the nRF Connect SDK.

Located under

\\external\nrf\applications\serial_lte_modem

which has a sysbuild folder.

So I had to add a new CMakeLists.txt file under the sysbuild folder with the content copy/paste below.

message(">>> Sysbuild Board Name >>> ${BOARD}")

message(">>> Sysbuild Source Directory >>> ${CMAKE_CURRENT_SOURCE_DIR}")

# Set BOARD_ROOT for sysbuild to find custom boards

if(NOT ${BOARD} STREQUAL "nrf9151dk/nrf9151/ns")

  message(">>> Sysbuild: Adding board root for custom board")

  # BOARD_ROOT should point to directory that CONTAINS the 'boards' subdirectory

  list (APPEND BOARD_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/..)

endif()

# Load the sysbuild package - this is required for build_info and other commands

find_package(Sysbuild REQUIRED HINTS $ENV{ZEPHYR_BASE})

project(sysbuild LANGUAGES)

Queston:

Please confirm this is a viable solution,

or whether the VS Code solution is better

>>> nrf-coinnect-extension >>> Nrf-connect: Board Roots >>> Add item

Best regards,

[Jamal_nRF]

Appreciate a response on my last comment. I has been a month...

Thank you

[runsiv]

Sorry for the delay. 
Both options are fine, If this is only on one computer I would recommend using the add item in VScode. 
As I might create building project with different custom boards I have created a custom board folder inside the folder where I store customer projects. So For any project I would be able to find it there and it require the least amount of modification on my side. 

Regards

Runar