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

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

JONATHAN LL — Mon, 08 Jun 2026 08:37:44 GMT

Adding:

[quote user="liujy"]Are you also unable to pass the test? [/quote]

Yes, for BV-01-I and BV-02-I.

Regards,
Jonathan

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

JONATHAN LL — Mon, 08 Jun 2026 08:31:20 GMT

Hi Liu,

[quote user="liujy"]Do I have to wait until the exemption is approved to skip this test?[/quote]

Yes. We need to wait until waiver is approved to waive BV-03-I.

Are you still facing issues with BV-01-I and BV-02-I ?

Are you using the latest version of the nRF54L15 DK, version 1.0.0 or some older version?

I am asking internally that someone from the team can provide a compiled sample, will update when I have something for you here.

Regards,
Jonathan

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

Nathan — Sat, 06 Jun 2026 06:08:41 GMT

Hi Jonathan，

Thank you for your verification and reply.

CONFIG_BT_MESH_RELAY_RETRANSMIT_COUNT = 1 this options and enter the chamer for testing，Amanda has already mentioned it. I have tried everything but the test still failed.

CONFIG_BT_MESH_NETWORK_TRANSMIT_COUNT this option and change the value to 2 i will test.

Are you also unable to pass the test?

If you have passed the test, could you provide the firmware for me to test and confirm the hardware environment?

Do I have to wait until the exemption is approved to skip this test?

Thanks.

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

JONATHAN LL — Fri, 05 Jun 2026 21:07:17 GMT

Here is the update from our team doing tests:

We have compiled the customer’s provided zip file as is and I can confirm that BV-01-I and BV-02-I pass on my desk:

The BV-03-I also goes past the point of failure shown in the customer’s case and fails at test step number 15 (Mesh Mesh Test specification).

The step number 15 is a known issue with this test case, and these steps will be removed in future via Erratum https://bluetooth.atlassian.net/browse/ES-29264 . The waiver request has been created for this test case: https://bluetooth.atlassian.net/browse/ES-29394 . Once the waiver is approved, Customer can use this waiver request, until last 4 steps have been removed from PTS software. Mentioning this waiver for their qualification documentation will enable them to skip passing BV-03-I test.

For customer’s reference I have attached the logs on my side:
devzone.nordicsemi.com/.../IOPT_5F00_MESH_5F00_NODE_5F00_BV_5F00_xx_5F00_I_5F00_tests_5F00_2026_5F00_06_5F00_05_5F00_17_5F00_35_5F00_20.zip

Some tips to get things passing on customer’s side:

It looks like they have a heavy BLE or WiFi interference which causes problems PTS testing. Use of RF chamber to keep both - IUT and PTS DKs inside is strongly advised.
Secondly, they can try adding these options to prj.conf “CONFIG_BT_MESH_RELAY_RETRANSMIT_COUNT=1 or 2" and “CONFIG_BT_MESH_NETWORK_TRANSMIT_COUNT=1or 2"

Regards,
Jonathan

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

JONATHAN LL — Fri, 05 Jun 2026 10:57:13 GMT

Thanks Liu, we will have a look and update with feedback and next steps here.

Regards,
Jonathan

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

Nathan — Fri, 05 Jun 2026 08:17:16 GMT

Hi Jonathan，

Thank you for your reply and support.

The dongle uses 54L15 DK, and the software will automatically program it to the DK using this tool

The test was also conducted using 54l15 DK

This is the project file for test run, light_ctrl (ncs demo)

devzone.nordicsemi.com/.../light_5F00_ctrl_5F00_324.zip

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

JONATHAN LL — Thu, 04 Jun 2026 22:05:07 GMT

Update:
Can we get the .zip of the build folder, need to look at the compiled firmware, the board name being used and “prj.conf” and “.config” files for compilation.

We typically see that Test 1 and 2 passes easily. Test 3 can present more of a challenge when packets are lost - we call this as “unstable test” however, the main test steps can be complete after 3-4 retries inside the chamber. Though Test 3 will not fully pass due to another problem that appears after this (for which we have created ticket to SIG here https://bluetooth.atlassian.net/browse/ES-29264 ).

Regards,
Jonathan

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

JONATHAN LL — Thu, 04 Jun 2026 12:44:40 GMT

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

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

Nathan — Fri, 29 May 2026 04:17:48 GMT

Hi Amanda：

The test in the chamber also failed.

This is new log devzone.nordicsemi.com/.../Report_5F00_MESH_5F00_2026_5F00_05_5F00_29_5F00_09_5F00_47_5F00_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.

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

Nathan — Fri, 29 May 2026 01:30:00 GMT

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.

devzone.nordicsemi.com/.../1106_2E00_.config.zip

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

Amanda Hsieh — Thu, 28 May 2026 17:01:37 GMT

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?

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

Nathan — Thu, 28 May 2026 02:56:49 GMT

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

devzone.nordicsemi.com/.../Report_5F00_MESH_5F00_2026_5F00_05_5F00_28_5F00_10_5F00_21_5F00_54.zip

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

Amanda Hsieh — Wed, 27 May 2026 13:10:03 GMT

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.

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

Nathan — Mon, 25 May 2026 07:00:39 GMT

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？

devzone.nordicsemi.com/.../Report_5F00_MESH_5F00_2026_5F00_05_5F00_23_5F00_17_5F00_27_5F00_26.zip

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

Amanda Hsieh — Fri, 22 May 2026 13:54:51 GMT

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)

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

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

Nathan — Wed, 20 May 2026 02:00:35 GMT

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

devzone.nordicsemi.com/.../1234.Report_5F00_MESH_5F00_2026_5F00_05_5F00_13_5F00_16_5F00_04_5F00_20.xml

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

Amanda Hsieh — Tue, 19 May 2026 13:59:56 GMT

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.

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

Nathan — Mon, 18 May 2026 08:27:18 GMT

The profiles file for testing at the Bluetooth certification authority was downloaded from the official website.

If I need to pass this mesh testing and certification, what firmware should I use (if available, could you provide it)?

And what do we need to do?

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

Nathan — Fri, 15 May 2026 07:22:11 GMT

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：

devzone.nordicsemi.com/.../Report_5F00_MESH_5F00_2026_5F00_05_5F00_13_5F00_16_5F00_04_5F00_20.xml

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

Amanda Hsieh — Wed, 13 May 2026 14:29:38 GMT

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.