Custom board for nRF54L15

[garrettb]

Hi

Are there any examples of a custom board for nRF54L15?

I have a project built/running on the nRF54L15 DK.

I now want to create a custom board for the nRF54L15.

I tried to do this from with nRF Connect, but of course my existing project won’t build, and I went down a long path of trying to solve this.

I thought a better approach might be to start with the DK, since the application runs successfully on it, and modify it…

So, I tried to copy some of the board files form here:

C:\ncs\v2.9.2\zephyr\boards\nordic\nrf54l15dk

To a local folder, rename them, edit the board names inside etc., and just see if I could get a starting build configuration that way. The idea was that if I copy/rename/edit the correct files, and I don’t change anything else, then the application should build.

However, that didn’t work either.

Perhaps I didn’t copy/edit enough of the files, or there are some subtle implications when the board name is changed – perhaps the build system doesn’t automatically include other files etc.

I have gone through the example in the Nordic Dev Academy, looking at Nordic videos, read the literature, talked with certain AI bots, and pulled my (remaining) hair out.

Any real help / pointer son this would be greatly appreciated.

For now, I am using SDK 2.9.2, because I am not sure of the stability of 3.x.x

Regards

Garrett

[SwRa]

Hi Garrett,

C:\ncs\v2.9.2\zephyr\boards\nordic\nrf54l15dk

To a local folder, rename them, edit the board names inside etc., and just see if I could get a starting build configuration that way. The idea was that if I copy/rename/edit the correct files, and I don’t change anything else, then the application should build.

The recommended process is to copy the board files from the nRF54L15 DK (located in `zephyr/boards/nordic/nrf54l15dk`) to your own directory, rename the folder and files, and update all internal references to match your new board name. The steps are similar to a explained in the DevAcademy course: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/topic/exercise-2-5/ Please make sure that you are not missing out on any steps here. See also: https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/develop/application/index.html#custom_board_devicetree_and_soc_definitions 

Also, there are known issues that you need to consider when using nRF54L15. If you are using nRF Connect SDK v2.8.0 or later, there is a known issue where custom boards for nRF54L15 rev. Engineering B may include incorrect Kconfig options for the Engineering A version. You must manually update these in your custom board's Kconfig file:
- Replace `SOC_NRF54L15_ENGA_CPUAPP` with `SOC_NRF54L15_CPUAPP` (present in known issues for v2.8.0)
- Replace `SOC_NRF54L15_ENGA_CPUFLPR` with `SOC_NRF54L15_CPUFLPR`(present in known issues for v2.8.0)
- Remove `CONFIG_SOC_NRF_FORCE_CONSTLAT` if present

It is specifically mentioned: "In the Kconfig file for your custom board (named Kconfig.<custom_board_name>, where <custom_board_name> is the name of your board), manually remove the CONFIG_SOC_NRF_FORCE_CONSTLAT Kconfig option. Then, manually regenerate the board."

See here:https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-9-2 

There are a few other tickets that you could also refer which I have pointed below.

If your custom board does not use the same external flash as the DK (e.g., MX25R64), you must update the device tree to remove or modify the flash node. For internal flash, you may need to add "zephyr,flash-controller = &rram_controller;" in your "/chosen" node in the .dts file. Refer:  Porting MCUBoot Application From nRF54L15DK to nRF54L15 Custom Board  

If you are using MCUBoot or FOTA, ensure that you provide the correct overlays and configuration files for your custom board. Refer:  Adding FOTA Support to custom board  

Hope this helps.

Best Regards,

Swathy