54l15-NCS3.2.4-NLC(mesh)-PST-Certification

[Nathan]

Hi Nordic team:

If my product has mesh functionality and needs to pass NLC certification and needs to be tested with a PST tool at a testing agency.

Do I need to flash a dedicated firmware (Bluetooth tester) for this?

Can the mesh demo of NCS pass Bluetooth certification?

github.com/.../tester

The testing agency said that the mesh functionality needs to be tested. If I want to pass the certification, do I have to combine the Bluetooth tester demo with the mesh demo to create a dedicated firmware for certification? Now that I have flashed the mesh demo firmware, it fails the PST tool test (the log keeps showing connection timeout).

Can the NLC mesh routine of NCS be directly certified, or just demonstrate its function? If I need to test the mesh function and also pass PST, what should I do?

I am not very familiar with certification, and I hope to receive clear answers to the above questions。

Thanks.

[Amanda Hsieh]

Hi Iiu, 

Nordic's Bluetooth Mesh stack in nRF Connect SDK is pre-qualified by Bluetooth SIG, covering Bluetooth Mesh Protocol v1.1, Mesh Model v1.1, Mesh DFU, BLOB Transfer, and NLC Profiles. According to the listing at Bluetooth SIG (requires a user account to view), Q380588 covers all NCS 3.2.x releases. 

You can inherit Nordic's qualification rather than re-testing everything from scratch, provided you do not modify the qualified stack. The Bluetooth LE qualification process is largely declarative. You can reference Nordic's Design Number (DN) in your own product listing. See the Bluetooth Qualification.

The NLC mesh samples (e.g., Lightness Controller, Sensor Server/Client, Dimming Control) are provided as functional application samples. They are built on top of the qualified stack. See the Bluetooth Mesh Samples and Bluetooth Networked Lighting Control profiles.

Regards,
Amanda H.

[Nathan]

Hi Amanda，

Thank you for your reply.So for Bluetooth authentication,we only need to inherit Nordic's authentication.

We just need to run a demo to prove whether the product has used an authenticated demo. However, we are currently facing some issues.

When testing The NLC mesh samples and attempting to use the PST tool for authentication pre-testing.

All three demos log display connection timeout issues. How can we resolve this?

Thanks.

NCSversion：3.2.4 54L15 DK
PTSversion：8.13.0 Build 4
Source：github.com/.../light_ctrl

log：

Report_MESH_2026_05_13_16_04_20.xml

[Amanda Hsieh]

You should use your own application to pass the certification and PTS tests, and your PTS ICS must match your implemented features. If there are errors while executing the tests, please tell us what errors you get.

[Nathan]

Hi Amanda，

Does the Nordic team have a demo of mesh functionality that has passed PST testing and certification for our reference?

The current issue we are facing is that the firmware cannot connect to PST (connection keeps timing out). Below is the log

1234.Report_MESH_2026_05_13_16_04_20.xml

[Amanda Hsieh]

From the team:

#1
IOPT/MESH/NODE/BV-03-I : Failure is because of the wrong setting of the PTS Tool.

Explanation:

Set TSPX_maximum_network_cache_size to 64 (i.e. same as CONFIG_BT_MESH_MSG_CACHE_SIZE for NLC samples)

#2

IOPT/MESH/NODE/BV-01-I
IOPT/MESH/NODE/BV-02-I
We see that these two PTS tests are passing

[Nathan]

Hi Amanda：

Thank you very much for your reply.

The default value of CONFIG_BT_MESH_MSG_CACHE_SIZE in the sample is 64.

I ran the test again,BV-03-I still failed.

Could you please take a look at the log？

Report_MESH_2026_05_23_17_27_26.zip

[Amanda Hsieh]

As you can see from the logs, the test runs, provisioning works, but it fails in the middle. The failures are because of the packet losses when the dongle fails to receive a packet. I observed a similar failure on the desk. It is recommended to run these tests inside the chamber, alternatively - when running without the chamber, you can try adding the following KCONFIG to your project.conf and recompile CONFIG_BT_MESH_RELAY_RETRANSMIT_COUNT=1. Let me know what the result is. With this, the first two tests will pass, the third test “03” will show a pop-up towards the end of the test, which should not be there. We have filed a report to fix this issue in the IOPT test specification on the SIG side (https://bluetooth.atlassian.net/browse/ES-29264). Once Bluetooth SIG agrees with this test fix, they will add a waiver for this test.

[Nathan]

Hi Amanda，

Thank you very much for your reply.

The log still shows failure after adding CONFIG_BT_MESH_RELAY_RETRANSMIT_COUNT=1.

May I ask if you can pass the test?

Here is the latest log

Report_MESH_2026_05_28_10_21_54.zip

[Amanda Hsieh]

Have you tried running tests in the RF chamber?

For BV-03:

- No Relay packet received. Packet already processed. (count 30)

This shows that the packet was lost. This PTS test case is a bit sensitive to packet losses and should must be performed in the chamber.

For BV-02 and BV-01:
You can see that the same problem happens for BV-02 and BV-01, but in this case, Device Composition Get fails (provisioning succeeds, but communication seems to fail).

Which PTS dongle are you using?
Could you share the .config file under build/app_name/zephyr?

[Nathan]

Hi Amanda：

Thanks for your reply.

Do we have to conduct the test in chamber by BV-03?

Below is the .config file, please check.

Thank you.

1106..config.zip

[Nathan]

Hi Amanda：

The test in the chamber  also failed.

This is new log Report_MESH_2026_05_29_09_47_57.zip

I am using the light_ctrl routine within NCS 3.2.4.

Could you please provide me with the firmware you have tested for reference？

The PST dongle used is 54L15 DK board,is it related to this？

Thank you.

[JONATHAN LL]

Hi Liu, 

I have taken over for Amanda as she is away. 

I am working on getting you an update here as soon as possible. 

Regards,
Jonathan