SDK 3.0.0 custom board definition

RE: SDK 3.0.0 custom board definition

Tiit — Mon, 04 Aug 2025 08:39:50 GMT

Hi Simonr,

That seems to have fixed the issue now. Thank you so much for this. I can now take this and start modifying it to match my actual board.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Tue, 29 Jul 2025 08:43:57 GMT

Hi Tiit

Can you check if adding the -DSB_CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y and -DCONFIG_CHIP_SPI_NOR=y to the build command helps? Our suspicion is that we enable some options based on the DK and not SoC in the Matter projects (see this). That is because we don't know what customers are going to do with the SoC, so it seemed to be a good idea to set this to the DK and not the SoC selection.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Wed, 23 Jul 2025 12:29:12 GMT

Hi Simon,

It's good that you could at least confirm that the issue exists. I tried the in-tree build and that seems to have the same issue for me. I hope the devs will have time to look at this next week. I'm working on multiple projects with this SOC and so far at least one has already reverted back to nRF52840 as their schedule did not allow for a delay as long as this.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Tue, 22 Jul 2025 10:35:18 GMT

An initial question from one of our developers, to narrow down where the issue here lies. Are you also able to see this if you add the custom boards and build it from the directory in-tree of the window covering sample?

Note that this is not a proposed fix, but will allow the devs to narrow down what's wrong. I can try it myself as well, but due to the staff shortage at the moment I won't have time this week I think.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Simonr — Tue, 22 Jul 2025 08:08:54 GMT

I can confirm I've reproduced this now, and I see what you mean. I don't see a reason why all of a sudden absolutely nothing happens. I've now reported it to the developers to see if they have a good reason as to why this happens. I'm sorry it took so long to get to this point.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Fri, 18 Jul 2025 09:50:43 GMT

Hi,

I will try to describe step by step what I did and I will also attach the whole result here so you can try that.

1. I create a new project in VSCode using the nRF Connect tab. There I select copy sample and copy the sample Matter Window Cover from SDK 3.0.1.

2. I make copies of the files nrf54l15dk_nrf54l15_cpuapp.conf and nrf54l15dk_nrf54l15_cpuapp.overlay and rename them for the new blindy_v4 board (blindy_v4_nrf54l15_cpuapp.conf and blindy_v4_nrf54l15_cpuapp.overlay). I add CONFIG_ZMS=y to my new blindy_v4_nrf54l15_cpuapp.conf.

3. I make renamed copies the same way in the sysbuild/mcuboot/boards folder

4. I make a copy of the pm_static_nrf54l15dk_nrf54l15_cpuapp.yml file and name the copy pm_static_blindy_v4_nrf54l15_cpuapp.yml

5. I close VSCode and open it again (so the new boards become available in the IDE)

6. I add new configuration, select SDK and toolchain 3.0.1, board target blindy_v4/nrf54l15/cpuapp

7. Build and flash the code the the DK

8. Cry in desperation as nothing happens. No leds blink, nothing is printed to RTT or the serial ports. Debugging still fails in this project as well for some reason.

devzone.nordicsemi.com/.../window_5F00_covering_5F00_1.zip

I have attached a project with everything I did here.

Looking forward to your feedback on this.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Thu, 17 Jul 2025 12:49:23 GMT

Sorry about the misunderstandings here, and I'm trying to recreate it on my end now with the blindy_v4 files you've shared, but it seems like you have a lot of discrepancies from the DK file in the config files at least. I'm trying to build it for the nRF54L15_cpuapp_ns target for the window_covering sample project, but need some more pointers on how to recreate this runtime error. Also, how does this runtime error look on your end?

If I can recreate it or get some information on how it fails in runtime I can ping the correct developers to try getting somewhere with this, as your description indeed sounds like an issue building Matter projects for custom targets.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Tue, 15 Jul 2025 11:11:37 GMT

That is exactly what I'm saying. Can you please try the project or board files that have been linked to this ticket multiple times already. This exact same conversation has been had in this thread more than once already. Following that guide is useless for Matter samples as they have very complex requirements for the board and that guide shows how to get a blinky sample running. Blinky samples work with thees board files. Almost all samples work but Matter does not. Please just try the files linked here and see for yourself.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Tue, 15 Jul 2025 11:01:52 GMT

Please check out the Defining custom board documentation page for a starting point in defining your own boards. Are you saying that duplicating the DK board file and making a copy somewhere else in the SDK won't work on your end?

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Mon, 14 Jul 2025 08:04:42 GMT

Hi Simon,

I'm not sure you understand my problem. I want to build the Matter Window cover sample for a custom board. How do I do that? Please describe step by step how I can do that. I can build the sample for the DK already.

My whole problem is I have nothing to start from with this. I want to create a starting point - a board definition that is exactly like the DK. I can't just start modifying the DK files inside the SDK (well I could technically but that would be the ugliest way imaginable to approach this). I need a custom board inside the project folder that builds and runs the sample on the DK hardware. Then I will start doing exactly what you said - step by step modifications to get to my real board. But right now I have nothing to start from.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Mon, 14 Jul 2025 07:34:04 GMT

So "adding all the overlays you think are necessary" and the parts of the DK board file you think are necessary is the wrong way to go about this I think. Rather begin with the working DK sample project and remove one and one of the things you don't need, rebuilding the project inbetween so you're able to see at which point the application starts failing so we know what the cause is exactly.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Fri, 11 Jul 2025 08:40:28 GMT

Hi Simon,

I am trying to run the unchanged Matter Window Cover sample on the 54L15 DK, It runs nicely if built for the DK board files in the SDK, I copied the SDK board files into a custom board folder, renamed them and added all the overlays I think are necessary but the custom board fails to run. I'm still doing all that on the DK hardware so the issue can not be in hardware. The details of the failures are in this thread. I think the blindy_4.zip here is the board folder that should be a clean copy of the DK board files. If you just try to compile the Matter Window Cover sample for that board and run that on the 54L15 DK it should fail with a runtime exception. I can not run the debugger in that project for some reason so I don't know exactly where it fails.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Fri, 11 Jul 2025 07:01:40 GMT

Okay, that makes more sense. Could we, just to make sure, do a HW review of your custom board to make sure the HW is in fact a true copy of the DK? If you upload the HW files (schematics and gerber files). When you say that it fails to run, do you have any details on what fails. Do you see it advertising on whatever you're trying to connect it to and it fails during connection or doesn't it appear to be working at all?

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Thu, 10 Jul 2025 12:00:55 GMT

Hi Simon,

Thank you for taking over this issue.

I'm afraid you didn't understand the issue completely correct. The issue is that the Matter Window Cover sample works if built for the 54L15 DK but fails if built for a direct copy of the DK board files as a custom board. Thanks to your support I now have a version where it all builds for the custom board but it still fails to run and for some reason I can not debug the sample project to see where it crashes. My last state is a fresh copy of the DK board files with just the board name changed. This works with most other samples in the 3.0.1 SDK. But it still fails with the Matter sample. I just need a starting point that works with the Matter sample. Then I would do exactly what you say - I would start changing the board item by item to get to my own custom board. I have done the same process with older SDK-s for the 52840 and even in this new SDK I did another board with 52840 which works just fine. The issue is I have no custom board to start from with the 54L15 SOC.

Tiit

RE: SDK 3.0.0 custom board definition

Simonr — Thu, 10 Jul 2025 11:54:34 GMT

Hi Tiit

I'm taking over this ticket while Edvin and Andreas is away, and had a chance to chat with them before they left. If I've gotten the gist of this issue correctly, it is that your custom board, which is a fully fledged copy doesn't work using your board files, but it does work if you just copy the DK's board files, correct? Excuse me if I'm mistaken here, but this is a long ticket and a lot to read and possibly misunderstand.

If this is the case, then there must be some vital differences between the DKs board file and the ones you have made that are necessary for the board to run correctly. My suggestion would be to, starting with the working version of the sample that Edvin provided last week, remove one and one of the things you don't need from the board file there until you find what causes the application to break.

Best regards,

Simon

RE: SDK 3.0.0 custom board definition

Tiit — Mon, 07 Jul 2025 12:28:16 GMT

Hi,

Ok so we got that working but this still doesn't fix my original issue. I'm not sure how creating a new ticket with the exact same problem will help anything. The original issue still stands - the Matter samples do not work on a custom board that is a copy of the DK. For the Matter samples the 54 DK is also supported out of the box and everything works if compiled for the DK. Compiling the same thing for the copy with a different name and it fails to do anything.

I tried debugging that again hoping to see where it gets stuck but debugging fails there for some reason. I can debug the COAP sample just fine. But if I try the same thing for Matter I get this:

Unable to start debugging. GDB exited unexpectedly with exit code 254 (0xFE). Failed to open listener port (Default: 2331)

I'm not sure how to proceed from here.

Tiit

RE: SDK 3.0.0 custom board definition

Edvin — Fri, 04 Jul 2025 12:39:48 GMT

Seems like it is just bad luck. The coap_server sample doesn't work out of the box with the nRF54L15DK either. Same issue. You can tell from the sample's description that it is not listed as a supported/tested board:
https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/openthread/coap_server/README.html

However, copying a few files from one of the samples where the nRF54L15 DK is supported, the CLI sample:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/openthread/cli/README.html

mainly, the nrf54l15dk_nrf54l15_cpuapp.conf and nrf54l15dk_nrf54l15_cpuapp.overlay, over to coap_server/boards, then it works on the DK.

Similarly, copying these files again, and naming them blindy_v4_nrf54l15_cpuapp.conf and blindy_v4_nrf54l15_cpuapp.overlay, and building again, then the sample runs using your board files.

I will be out of office from after today, for a few weeks. Andreas, who handlet this ticket previously, will also. So if you have any more questions on the topic, I suggest you create a new topic, but hopefully, this will get you going with your custom board files.

Attached is the modified sample (with the added .conf and .overlay files), that should build and run using your board files, blindy_v4 (tested in NCS v3.0.1)

If you run into other issues, it may be a good idea to check if it runs correctly on the nRF54L15 DK using the DK's board files.

devzone.nordicsemi.com/.../1325.coap_5F00_server.zip

Best regards,

Edvin

RE: SDK 3.0.0 custom board definition

Tiit — Tue, 01 Jul 2025 11:02:24 GMT

Hi,

I had another go at making an identical board to the DK again. Attached here is the result. Like I suspected there is absolutely no difference - still fails exactly the same with Thread. I'm not sure how I can communicate my issue more clearly. The issue only happens when Thread is used. It does not seem to be a Matter sample specific thing. I use the exact same process of copying the DK board files and modifying for my own board for the 52840 and there are no issues with that. I have no idea how to proceed from here.

Tiit

devzone.nordicsemi.com/.../blindy_5F00_v4.zip

RE: SDK 3.0.0 custom board definition

Edvin — Mon, 30 Jun 2025 13:55:33 GMT

To the left is the folder boards\blindy_v3 that I sent you, and to the right is the boards\blindy_v3 that you sent in the wc.zip file:

All the blue files have changes:

Since these were not here iin the first place, but they are present in the nRF54L15 DK's board files, it makes me believe that you have not copied these files directly. At least not from SDK v3.0.1. If these were not copied, I don't have the exact overview what other parts were not copied when you initially created your board files.

Best regards,

Edvin

RE: SDK 3.0.0 custom board definition

Tiit — Mon, 30 Jun 2025 08:08:41 GMT

Hi Edvin,

I'm sorry but I don't understand the changes you made to the board files to be honest. I may be mistaken but it seems that you copied some of the content from the files that the board files included from the SDK directly into the board folder. I'm not sure why that would make a difference though. But the change regarding UART seems to be in the file blindy_v3_nrf54l15_cpuapp.overlay (the line "zephyr,shell-uart = &uart20;" in the "chosen" block. And I don't see that in the othe roverlay file for the DK. The board files I used as a base were from the SDK 3.0.1 that I have used throughout this thread. I think there is a newer version of the SDK out now which I suppose I could try this with but I really don't think I made a mistake since other samples seem to work - it only fails in samples that use Thread. Like I reported in the other response to this I tracked the usage fault to some crypto function that seems to fail when creating key material for Thread initialization.

I do not "want" to have my board behave like the DK. I want a custom board with just RTT and the external memory to work with the Matter samples. This is just a stepping stone on my path to that as I have been unable to get a Matter sample to work on anything but the official DK so far. THey all seem to fail in Thread setup.

I have compared my board files to the DK and they look identical to me. The ones that you modified are different and I'm not sure how or why they are like that. But the ones that I have posted should be identical to the DK in the important parts (names have to be different obviously).

I now have multiple projects being blocked by this and I'm seriously doubting if I can even use the 54 series chips in production next year. I can easily make projects using the 52840 in the same way and even in SDK 3.0.1 they work beautifully with all the Matter samples. This is something specific to the 54 (or the TrustZone).

Tiit

RE: SDK 3.0.0 custom board definition

Edvin — Fri, 27 Jun 2025 12:35:18 GMT

Hello,

[quote user="Tiit Ratsep"]I see the serial output now so thank you for that. But I still don't understand why this is not working if the same sample built for the DK works. My board files are a direct copy of the DK board files so it should compile to an almost identical binary[/quote]

That is not the case. The changes that I did to your board files was copying parts from the DK board files, and into your board files. Perhaps they were a copy of the board files in an older NCS version. I don't know. But e.g. UART was not enabled, which they are in the board files for the DK.

If you want it to behave like the DK, I suggest you try once more to copy the board files from NCS, and change the name of the files and content to match your own board name's file.

For your Thread/Matter issues. Do the samples build for the DK? If so, I think you need to compare your board files to the DK's again.

Best regards,

Edvin

RE: SDK 3.0.0 custom board definition

Tiit — Fri, 27 Jun 2025 11:23:31 GMT

Hi Edvin,

I tried debugging the project you sent me. It seems to crash in thread setup. Specifically it fails in some crypto library function. In the OpenThread library there is crypto_psa.c. The function from that file called otPlatCryptoImportKey calls psa_import_key. That in turn calls psa_crypto_storage_store and that in turn calls trusted_storage_get_key. Eventually exection ends up in hw_unique_key_derive_key. It starts going through the cracen_key_derivation set of functions ending with cracen_key_derivation_output_bytes. But execution stops upon entering the cracen_key_derivation_output_bytes function with a USAGE FAULT. I'm not sure why this happens but it is very similar to the way the Matter samples fail with this board setup. This again confirms my suspicion that the root cause of all these problems is somehow related to Thread. All the samples I have tried that do not have Matter work with this board definition. The fact that UART also had issues is interesting but I don't think that is really related to the main issue.

Tiit

RE: SDK 3.0.0 custom board definition

Tiit — Fri, 27 Jun 2025 10:03:39 GMT

Hi Edvin,

I see the serial output now so thank you for that. But I still don't understand why this is not working if the same sample built for the DK works. My board files are a direct copy of the DK board files so it should compile to an almost identical binary (just the board name is different). Even this UART change should not have been necessary as far as I understand. This overflow error now is another difference that makes me worried. The coap sample is rather simple (as is the hello world sample) and I do believe we can get those to work. But my end goal is the Matter window cover sample. That is a crazy complex sample that touches almost every part of the SOC system so these small differences will add up and this makes me worried that there will be hidden issues with the more complex sample. I really just want to port my own code that currently runs well on the 52840 to this new SOC. Right now it seems that this will be more difficult than going from a legacy 51822 project to a 52840 and Zephyr. I have done another project porting a 52840 based project to the new SDK3.0.1 and that went rather painlessly. So the issue really is just with the new 54 series SOCs. Maybe you can just make a simple custom board file using the 54L15 that would work with the Matter sample and post that somewhere. Seeing how many people seem to follow this post I'm not alone in having issues with this right now.

Tiit

RE: SDK 3.0.0 custom board definition

Edvin — Tue, 24 Jun 2025 11:40:29 GMT

I see. There were no UART console in your board files. Sorry this took so long, but I needed to dig out why the DRIVER_HAS_SERIAL was not set, and it was the lacking settings in the board files.

Please see the attached project with it's boards folder:

devzone.nordicsemi.com/.../7725.coap_5F00_server.zip

Warning: I do get an assert when running (stack overflow) but I didn't have time to look into the application why this was happening. I tested the same board files with the hello_world sample (NCS\zephyr\samples\hello_world), and that worked as intended. I don't know what other changes that may have been done to the coap_server sample.

Best regards,

Edvin

RE: SDK 3.0.0 custom board definition

Tiit — Thu, 19 Jun 2025 10:13:03 GMT

Hi Edvin,

Yes. There is no UART output.