SDK v2.5.99-dev1 has many compile errors

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Thu, 11 Apr 2024 07:41:25 GMT

Hi,

[quote user="Gene Roylance"]I would also like to point out one additional issue that I found on my M2 Mac. When I used the Toolchain Manager v1.3.1 (initiated from the nRF Connect for Desktop v4.4.1 application) to try and re-install the v2.6.0 SDK and toolchains, it was downloading the ncs-toolchain-x86_64-macos-580e4ef81c.tar.gz file instead of the ncs-toolchain-aarch64-macos-580e4ef81c.tar.gz file that the nRF Connect extension of Visual Studio Code downloaded (I switched to the VS code installation after the Toolchain Manager failed). The Toolchain Manager v1.3.1 toolchains installation hung (did not complete), which tipped me off to this difference.[/quote]

That does actually make sense. I did not catch that from the support report!..

I will report this to the extension team and check in with them if this is a known behavior or if it should be patched. I know that our plans are to move from the Toolchain manager in nRF Connect SDK and to mainly maintain and support the extension in VSCode, so there might come a time where the toolchain manager gets deprecated (not verified). Unfortunately this creates some artifacts such as the ones you've faced..

Anyways, happy to hear that you were able to resolve the SDK setup and that 2.6.0 now works similarly as it does for your colleagues and also that you were able to resolve the initial build error by changing the CPP configuration

Let me know if everything here has been answered and if so please feel free to raise new questions here on Devzone in the future

Kind regards,
andreas

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Wed, 10 Apr 2024 21:25:39 GMT

Andreas,

Sorry for the delay, but I believe that I have found the solution to the problem that I have been experiencing. First, let me answer you last two questions:

1) Does the JLink version make a different? Answer: No, downgrading to 7.88j made no difference.

2) Does the Toolschain path in the Config setting need to be something other than a null string? Answer Not apparently, I changed the setting to what Steve had ("${nrf-connect.toolchain:2.6.0}") and it made no difference.

So, this is how I fixed my problem. Steve and I were comparing our $HOME/.zprofile files and I noticed that I had some unique lines (as compared to his .zprofie file):

# SDK v2.6.0
export PATH="$PATH:/opt/nordic/ncs/toolchains/580e4ef81c/bin"
# SDK v2.5.0
#export PATH="$PATH:/opt/nordic/ncs/toolchains/20d68df7e5/bin"
# SDK v2.4.1
#export PATH="$PATH:/opt/nordic/ncs/toolchains/4ef6631da0/bin"# nrfutil tools
export PATH="$PATH:/Users/puzl/Library/Python/3.9/bin"

First, I commented out the SDK v2.6.0 toolschains path addition, but that made no difference. Next, I commented out the nrfutil tools PATH command, and again no difference. However, I was a bit curious about the nrfutil tools. I noticed that it had some python applications AND some python libraries included in this tool. I also noticed that the version of this utility was quite old (nrfutil version 5.2.0) whereas the latest version was 7.7.0.

I am not sure where this old version of nrfutil came from, but I did recall that I was trying several versions of the nrfutil tool trying to program a nRF52940 USB dongle device last November. I finally resorted to using the windows version of the tool to complete the dongle programming, but I left the nrfutil tool on my Mac machine (and in my path). I would guess that this tool was conflicting with the v2.6.0 SDK or toolchains.

I would like to point out that I had to remove the v2.6.0 SDK and toolchains and then re-install them after I had removed the nrfutil tool (bin and lib) files from my machine to totally fix the problem.

I would also like to point out one additional issue that I found on my M2 Mac. When I used the Toolchain Manager v1.3.1 (initiated from the nRF Connect for Desktop v4.4.1 application) to try and re-install the v2.6.0 SDK and toolchains, it was downloading the ncs-toolchain-x86_64-macos-580e4ef81c.tar.gz file instead of the ncs-toolchain-aarch64-macos-580e4ef81c.tar.gz file that the nRF Connect extension of Visual Studio Code downloaded (I switched to the VS code installation after the Toolchain Manager failed). The Toolchain Manager v1.3.1 toolchains installation hung (did not complete), which tipped me off to this difference.

One last thing, I was also able to find the answer to the original question that prompted this ticket. I was able to get the v2.5.99-dev1 SDK to build on an existing project by changing this line in the prj.conf file:

-CONFIG_STD_CPP14=y
+CONFIG_STD_CPP17=y

Best Regards,

Gene

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Tue, 09 Apr 2024 08:12:09 GMT

Hi Steve and Gene,

I've not tested if 7.96e is working or not, but I know for sure that a M2 Mac with NCS installed through VS Code extension (toolchain first then the SDK v2.6.0) using JLink 7.88j compiles the template sample without issues.

The reason for your fault is the second item in my previous comment, i.e that the toolchain path is not set, which is caused either due to a faulty installation or that the toolchain/SDK is not installed in a location where the extension/setup expects the two items to be located

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

SteveKranz — Mon, 08 Apr 2024 15:33:20 GMT

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Mon, 08 Apr 2024 12:20:34 GMT

Hi,

Thank you for the comparison Steve

A couple of thoughts:

Steve's using J Link 7.94c, while Gene uses 7.94e. Could you downgrade and check if this resolves the build error?
1. Edit: I see I'm using 7.94e as well, so I don't think thats the issue after all.
I see that Steves path is set while Gene's path is not set under config for toolchain. Could indicate that there's an issue the installation procedure for M2 rather than specifically Genes computer. I assume that both of you have followed the same installation procedure?

[quote user="Gene Roylance"]v2.6.0, then for some reason, find that it had changed to v2.5.2 when I build. [/quote]

This could happen due to the path not beeing set by the installer or if you've opened something in the workspace thats from 2.5.2. It's annoying, but I find it a good practice to always open a clean workspace when changing toolchains/SDKs to avoid this.

In addition, you may find it useful to reload the window when changing to ensure that the toolchains has been set

Nonetheless, based on your latest replies I think it's either of the two alternatives above. If you could check item 1 (and item 2 if you have additional M2 Macs available) and I'll see if I can reproduce it from my end when I get a hold of someone with a Mac 2. None of my colleagues with M1 has been able to reproduce the faulty build

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

SteveKranz — Fri, 05 Apr 2024 16:38:44 GMT

Hi Andreas,

If it helps I'd like to offer my support_information.txt for comparison with Gene's. Note: With v2.6.0 SDK/ToolChain I can import the Nordic template sample and successfully build/flash, and run, on the nRF52840DK. Support Info below for my MacBookPro (M1) development machine.

devzone.nordicsemi.com/.../2671.support_5F00_information.txt

Thanks, Steve K. PuzL Labs, LLC

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Fri, 05 Apr 2024 14:25:24 GMT

Andreas,

Thanks for getting back to me. I have been deleting the build directory regularly in my experiments. However, whatever I seem to try is still failing. I have had an issue with setting the active SDK to be v2.6.0, then for some reason, find that it had changed to v2.5.2 when I build. So, I tried this experiment.

1. I completely deleted the Matter Template directory that I added as a Copy of Sample code (in case the SDK was set to v2.5.2 when I copied it).

2. I made sure that the toolchain and the SDK was set to v2.6.0 when I added the Matter Template application as a Copy from Sample code.

3. I made sure that the toolchain and the SDK was still at v2.6.0 after the copy completed.

4. I added the build configuration using the defaults for my nRF52840 DK board.

5. I built this configuration, but it resulted in the same Factory Data generate failure.

I generated the support information and uploaded the text file with this information.

Thanks for your help,

Gene

devzone.nordicsemi.com/.../support_5F00_information.txt

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Fri, 05 Apr 2024 13:03:48 GMT

Hi Gene

Apologies for the long response time due to the Easter Holidays period. Thank you for the description. Lets try to close some doors and narrow down what may cause this as it works on my end. What I suspect is that it could be caused by either of these items

Do you have anything in the VS Code workspace? Sometimes the Toolchain and SDK version that is actually used are inherited from projects in the workspace rather than the applications you've loaded into the extension as seen in the image below (which I've forced to showcase this)
When you perform the new build, do you remove the previous build folder?
Could you open the command palette in VS Code and generate support information for the build that faults and upload it here?
Is the template sample something that you copied from elsewhere or is it the pristine sample (unmodified sample) from the unmodified SDK v2.6.0?

I find it hard to narrow it down anything further than this when its not reproducable from my end unfortunately, but hopefully this might allow us to see something!

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Fri, 29 Mar 2024 21:30:23 GMT

Greetings all,

I have a couple of updates. First of all, I was able to restore my deleted toolchain and SDK file by doing the following (restore the directory from the download file):

1. cd /opt/nordic/ncs/toolchains
2. cp ../downloads/ncs-toolchain-aarch64-macos-580e4ef81c.tar.gz .
3. gunzip ncs-toolchain-aarch64-macos-580e4ef81c.tar.gz
4. mkdir 580e4ef81c
5. cd 580e4ef81c
6. tar -xvf ../ncs-toolchain-aarch64-macos-580e4ef81c.tar

I then opened up the "nRF Connect for Desktop v4.4.1" and then opened the Toolchain Manager v1.3.1 and then under the "nRF Connect SDK v2.6.0", I selected the optional action of "Remove".

After I correctly uninstalled the v2.6.0 toolchain and SDK, I tried to re-install the SDK in Visual Studio Code app using this process:

a. click the NRF CONNECT extension tab
b. ran WELCOME -> Manage toolchains -> Install Toolchain -> nRF Connect Toolchain v2.6.0
c. selected WELCOME -> Manage toolchains -> Set Active Toolchain -> nRF Connect SDF Toolchain v2.6.0
d. ran WELCOME -> Manage SDKs -> Install SDK -> v2.6.0
e. selected WELCOME -> Manage SDKs -> Set Active SDK -> nRF Connect SDK v2.6.0

I also tried the following updates:

1. Downloaded and installed nRF Command Line Tools version 10.24.0
2. Ran the "West update" link in the build notification box

However, even with all these steps, building the Matter Template sample still fails at the Factory Data generate operation as before.

On the other hand, I was able to create a new application -- copying from the OpenThread CLI sample and it builds, flashes, and runs on the DK board as expected.

Best Regards,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Fri, 29 Mar 2024 14:18:39 GMT

Andreas,

I was looking over my last reply and realized that I neglected to report an important result. I did try the configuration that you suggested on March 21st before I tried the experiments on my Linux computer and trying to re-install v2.6.0 on my Mac. The configuration that you suggested did not make any difference in the build. I still had the Factory Data generation failure that I reported on March 20th.

Best Regards,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Thu, 28 Mar 2024 02:58:32 GMT

Andreas,

I went through the Release Notes and the Migration Guide but saw nothing that would explain the Factory Data generation error that I have been seeing. So, I tried updating a Linux version of the VSCode and nRF Connect system to v2.6.0 and that was able to build the Matter Template sample without any errors.

I decided to go back to my Mac system and remove the Toolchain and SDK and try to install it again. Unfortunately, I removed the toolchain directory with a terminal command instead of using the Uninstall or Toolchain Manager Remove function. I cannot manage to get the v2.6.0 toolchain to install using commands in either the Toolchain Manager or the Visual Studio Code's NRF CONNECT extension. Is there a way to force the re-installation of the v2.6.0 toolchain tools?

Thanks,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Fri, 22 Mar 2024 08:23:36 GMT

Hi Steve,

Thank you for the update and letting me know that you were able to compile the sample in NCS v2.6.0.

Please let me know if you have any other questions related to this topic when Gene gets back and feel free to open any new cases with questions regarding migration of your firmware from 2.5.2 to 2.6.0.

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

SteveKranz — Thu, 21 Mar 2024 14:50:09 GMT

Hi Andreas,

I am replying to you on behalf of Gene R. as he is away for a few days. I did an experiment with my MacBook (M1) migrated to the Nordic v.2.6.0 toolchain/SDK and I was able to successfully import the Nordic template sample and successfully build it. I wanted to give you that feedback.

When Gene gets back we'll take a fresh look at his machine setup and then start migrating our PuzL Labs Matter app (similar to the older v2.5.2 template app). We'll glance at the following links along the way:

Nordic v2.6.0 Release Notes:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases_and_maturity/releases/release-notes-2.6.0.html

Nordic v2.6.0 Migration Quide:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases_and_maturity/migration/migration_guide_2.6.html

Thanks much,

Steve K, PuzL Labs, LLC

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Thu, 21 Mar 2024 09:07:32 GMT

Hi kammutierspule,

Could you please create a new case and raise your question there with more details.

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Thu, 21 Mar 2024 09:06:57 GMT

Hi Gene,

[quote user="Gene Roylance"]2. Add Build Configuration
    Board = nrf52840dk_nrf52840
    Configuration = prj.conf
    Add Devicetree overlays: boards/nrf52840dk_nrf52840.overlay[/quote]

In step 2: You don't need to specify the configuration and the device tree overlay. If you use "System default", then the build system will use the prj.conf that exists in the source folder. Next it will look at the board you've selected, and if it is a board file that is supported in the SDK out of the box, it will use the default board files located in https://github.com/nrfconnect/sdk-zephyr/tree/main/boards/arm/, for instance the nRF52840DK.

After it has found this board, it will use this to configure the board and next look for any overlay files within your project. The build system will always use <your_board>.overlay if it exists. In this case it does exist within boards/nrf52840dk.nrf52840.overlay, so it will automatically be included.

This is explained in greater detail under the Configuration and building pages in our documentation as well as in our academy pages, more specifically in the first 3 lessons in https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

When you at a later point in time might get to adding a custom board to your projects, we also have documentation for this. Lesson 3 in the intermediate course also shows how to do this: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/

The following configuration resulted in a successful build with no warnings on my end (Windows 10, NCS 2.6.0, Toolchain v2.6.0):

Let me know if you are successful with building the Matter template sample with a similar build configuration as showed in the image above

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

kammutierspule — Wed, 20 Mar 2024 22:08:47 GMT

I have a similar issue:

[22:08:04] nRF Command Line Tools 10.24.0 are up to date
[22:08:09] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.6.0 ===========
📦 Using the nRF Connect SDK v2.6.0 at /home/kammutierspule/ncs/v2.6.0
🕒 dtc is outdated. Found 1.5.0, but 1.5.1-1 is required by the SDK.

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Wed, 20 Mar 2024 21:00:39 GMT

Hello again,

I was able to perform the following experiment with the v2.6.0 SDK:

1. WELCOME -> Create a new application -> Copy a sample -> Matter Template

2. Add Build Configuration
    Board = nrf52840dk_nrf52840
    Configuration = prj.conf
    Add Devicetree overlays: boards/nrf52840dk_nrf52840.overlay

3. Build Configuration

I seem to get the same failure as last time:

-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0-rc1/zephyr), build: v3.5.99-ncs1-rc1
[173/173] Linking C executable zephyr/zephyr.elf
Memory region         Used Size Region Size %age Used
           FLASH:       26618 B        28 KB     92.84%
             RAM:         18 KB       256 KB      7.03%
        IDT_LIST:          0 GB        32 KB      0.00%
[11/732] Generating new Factory Data...
FAILED: zephyr/factory_data.json /Users/puzl/nrf/template_1/build/zephyr/factory_data.json
cd /Users/puzl/nrf/template_1/build/modules/connectedhomeip && /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py --sn 11223344556677889900 --date 2022-01-01 --vendor_id 65521 --product_id 32768 --vendor_name Nordic\ Semiconductor\ ASA --product_name not-specified --hw_ver 0 --hw_ver_str prerelease --dac_cert /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-DAC-FFF1-8000-Cert.der --dac_key /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-DAC-FFF1-8000-Key.der --pai_cert /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-PAI-FFF1-noPID-Cert.der --spake2_it 1000 --spake2_salt U1BBS0UyUCBLZXkgU2FsdA== --discriminator 0xF00 --passcode 20202021 --include_passcode --overwrite --product_finish other --generate_onboarding --enable_key 00112233445566778899AABBCCDDEEFF -o /Users/puzl/nrf/template_1/build/zephyr/factory_data.json -s /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/nrfconnect_factory_data.schema
[INFO] Generating SPAKE2+ Verifier...
Traceback (most recent call last):
File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 577, in <module>
    main()
File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 573, in main
    generator.generate_json()
File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 277, in generate_json
    spake_2_verifier = self._generate_spake2_verifier()
File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 380, in _generate_spake2_verifier
    return generate_verifier(self._args.passcode, self._args.spake2_salt, self._args.spake2_it)
File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/spake2p/spake2p.py", line 51, in generate_verifier
    return w0.to_bytes(NIST256p.baselen, byteorder='big') + L.to_bytes('uncompressed')
AttributeError: 'Point' object has no attribute 'to_bytes'

Any further thoughts?

Thanks,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Tue, 12 Mar 2024 07:49:10 GMT

Good morning from Norway,

Do you see the same error with a pristine sample from the SDK, as well as your custom firmware based on the Matter template? How about other non-matter samples?

What build configuration have you selected, i.e did you use west build with any other parameters added? If you've used the nRF Connect extension to build, could you post a screen shot of the build configuration?

The error you're getting seems to be connected to the SPAKE2+ verifier specifically.

  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/spake2p/spake2p.py", line 51, in generate_verifier
    return w0.to_bytes(NIST256p.baselen, byteorder='big') + L.to_bytes('uncompressed')
AttributeError: 'Point' object has no attribute 'to_bytes'

If you're using a SPAKE2+ from your 2.5 based custom project using Matter v1.1 into the NCS v2.6.0 using Matter v1.2, could you verify if anything has changed w.r.t formatting or other things?

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Tue, 12 Mar 2024 00:57:29 GMT

[10/774] Generating new Factory Data...
FAILED: zephyr/factory_data.json /Users/puzl/nrf/PuzLLabs_Thread/build/zephyr/factory_data.json
cd /Users/puzl/nrf/PuzLLabs_Thread/build/modules/connectedhomeip && /opt/nordic/ncs/toolchains/da6f6379ec/opt/python@3.9/bin/python3.9 /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py --sn 11223344556677889900 --date 2022-01-01 --vendor_id 65521 --product_id 32768 --vendor_name PuzL\ Labs --product_name PuzL\ Detect --hw_ver 0 --hw_ver_str prerelease --dac_cert /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-DAC-FFF1-8000-Cert.der --dac_key /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-DAC-FFF1-8000-Key.der --pai_cert /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/credentials/development/attestation/Matter-Development-PAI-FFF1-noPID-Cert.der --spake2_it 1000 --spake2_salt U1BBS0UyUCBLZXkgU2FsdA== --discriminator 0xF00 --passcode 20202021 --include_passcode --overwrite --product_finish other --generate_onboarding --enable_key 00112233445566778899AABBCCDDEEFF -o /Users/puzl/nrf/PuzLLabs_Thread/build/zephyr/factory_data.json -s /opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/nrfconnect_factory_data.schema
[INFO] Generating SPAKE2+ Verifier...
Traceback (most recent call last):
  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 577, in <module>
    main()
  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 573, in main
    generator.generate_json()
  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 277, in generate_json
    spake_2_verifier = self._generate_spake2_verifier()
  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/nrfconnect/generate_nrfconnect_chip_factory_data.py", line 380, in _generate_spake2_verifier
    return generate_verifier(self._args.passcode, self._args.spake2_salt, self._args.spake2_it)
  File "/opt/nordic/ncs/v2.6.0-rc1/modules/lib/matter/scripts/tools/spake2p/spake2p.py", line 51, in generate_verifier
    return w0.to_bytes(NIST256p.baselen, byteorder='big') + L.to_bytes('uncompressed')
AttributeError: 'Point' object has no attribute 'to_bytes'
[12/774] cd /Users/puzl/nrf/PuzLLabs_Thread/build/modules/openthread/build && /opt/nordic/ncs/toolchains/da6f6379ec/Cellar/cmake/3.21.0/bin/cmake -DLIST="OPENTHREAD_CONFIG_RADIO_LINK_IEEE_802_15_4_ENABLE=1;OPENTHREAD_CONFIG_TMF_ANYCAST_LOCATOR_ENABLE=0;OPENTHREAD_CONFIG_ASSERT_ENABLE=1;OPENTHREAD_CONFIG_BACKBONE_ROUTER_ENABLE=0;OPENTHREAD_CONFIG_BACKBONE_ROUTER_DUA_NDPROXYING_ENABLE=0;OPENTHREAD_CONFIG_BACKBONE_ROUTER_MULTICAST_ROUTING_ENABLE=0;OPENTHREAD_CONFIG_BLE_TCAT_ENABLE=0;OPENTHREAD_CONFIG_BORDER_AGENT_ENABLE=0;OPENTHREAD_CONFIG_BORDER_ROUTER_ENABLE=0;OPENTHREAD_CONFIG_BORDER_ROUTING_ENABLE=0;OPENTHREAD_CONFIG_BORDER_ROUTING_DHCP6_PD_ENABLE=0;OPENTHREAD_CONFIG_IP6_BR_COUNTERS_ENABLE=0;OPENTHREAD_CONFIG_CHANNEL_MANAGER_ENABLE=0;OPENTHREAD_CONFIG_CHANNEL_MONITOR_ENABLE=0;OPENTHREAD_CONFIG_COAP_API_ENABLE=1;OPENTHREAD_CONFIG_COAP_BLOCKWISE_TRANSFER_ENABLE=0;OPENTHREAD_CONFIG_COAP_OBSERVE_API_ENABLE=0;OPENTHREAD_CONFIG_COAP_SECURE_API_ENABLE=0;OPENTHREAD_CONFIG_COMMISSIONER_ENABLE=0;OPENTHREAD_CONFIG_MAC_CSL_AUTO_SYNC_ENABLE=1;OPENTHREAD_CONFIG_MAC_CSL_DEBUG_ENABLE=0;OPENTHREAD_CONFIG_MAC_CSL_RECEIVER_ENABLE=1;OPENTHREAD_CONFIG_MAC_CSL_RECEIVER_LOCAL_TIME_SYNC=0;OPENTHREAD_CONFIG_DATASET_UPDATER_ENABLE=0;OPENTHREAD_CONFIG_MLE_DEVICE_PROPERTY_LEADER_WEIGHT_ENABLE=0;OPENTHREAD_CONFIG_DHCP6_CLIENT_ENABLE=0;OPENTHREAD_CONFIG_DHCP6_SERVER_ENABLE=0;OPENTHREAD_CONFIG_DIAG_ENABLE=0;OPENTHREAD_CONFIG_DNS_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_DNS_CLIENT_OVER_TCP_ENABLE=0;OPENTHREAD_CONFIG_DNS_DSO_ENABLE=0;OPENTHREAD_CONFIG_DNS_UPSTREAM_QUERY_ENABLE=0;OPENTHREAD_CONFIG_DNSSD_SERVER_ENABLE=0;OPENTHREAD_CONFIG_DUA_ENABLE=1;OPENTHREAD_CONFIG_ECDSA_ENABLE=1;OPENTHREAD_CONFIG_HEAP_EXTERNAL_ENABLE=1;OPENTHREAD_POSIX_CONFIG_FIREWALL_ENABLE=0;OPENTHREAD_CONFIG_HISTORY_TRACKER_ENABLE=0;OPENTHREAD_CONFIG_IP6_FRAGMENTATION_ENABLE=1;OPENTHREAD_CONFIG_JAM_DETECTION_ENABLE=0;OPENTHREAD_CONFIG_JOINER_ENABLE=0;OPENTHREAD_CONFIG_MLE_LINK_METRICS_INITIATOR_ENABLE=0;OPENTHREAD_CONFIG_LINK_METRICS_MANAGER_ENABLE=0;OPENTHREAD_CONFIG_MLE_LINK_METRICS_SUBJECT_ENABLE=0;OPENTHREAD_CONFIG_LINK_RAW_ENABLE=0;OPENTHREAD_CONFIG_LOG_LEVEL_DYNAMIC_ENABLE=0;OPENTHREAD_CONFIG_MAC_FILTER_ENABLE=0;OPENTHREAD_CONFIG_MESH_DIAG_ENABLE=0;OPENTHREAD_CONFIG_MESSAGE_USE_HEAP_ENABLE=0;OPENTHREAD_CONFIG_MLE_LONG_ROUTES_ENABLE=0;OPENTHREAD_CONFIG_MLR_ENABLE=1;OPENTHREAD_CONFIG_MULTIPAN_RCP_ENABLE=0;OPENTHREAD_CONFIG_MULTIPLE_INSTANCE_ENABLE=0;OPENTHREAD_CONFIG_NAT64_BORDER_ROUTING_ENABLE=0;OPENTHREAD_CONFIG_NAT64_TRANSLATOR_ENABLE=0;OPENTHREAD_CONFIG_NEIGHBOR_DISCOVERY_AGENT_ENABLE=0;OPENTHREAD_CONFIG_NETDATA_PUBLISHER_ENABLE=0;OPENTHREAD_CONFIG_TMF_NETDIAG_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_OPERATIONAL_DATASET_AUTO_INIT=1;OPENTHREAD_CONFIG_OTNS_ENABLE=0;OPENTHREAD_CONFIG_PING_SENDER_ENABLE=1;OPENTHREAD_CONFIG_PLATFORM_BOOTLOADER_MODE_ENABLE=0;OPENTHREAD_CONFIG_PLATFORM_KEY_REFERENCES_ENABLE=1;OPENTHREAD_CONFIG_PLATFORM_NETIF_ENABLE=0;OPENTHREAD_CONFIG_PLATFORM_POWER_CALIBRATION_ENABLE=0;OPENTHREAD_CONFIG_PLATFORM_UDP_ENABLE=0;OPENTHREAD_CONFIG_REFERENCE_DEVICE_ENABLE=0;OPENTHREAD_CONFIG_TMF_NETDATA_SERVICE_ENABLE=0;OPENTHREAD_SETTINGS_RAM=0;OPENTHREAD_CONFIG_IP6_SLAAC_ENABLE=1;OPENTHREAD_CONFIG_SNTP_CLIENT_ENABLE=0;OPENTHREAD_CONFIG_SRP_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_SRP_SERVER_ENABLE=0;OPENTHREAD_CONFIG_TCP_ENABLE=0;OPENTHREAD_CONFIG_TIME_SYNC_ENABLE=0;OPENTHREAD_CONFIG_RADIO_LINK_TREL_ENABLE=0;OPENTHREAD_CONFIG_MAC_OUTGOING_BEACON_PAYLOAD_ENABLE=0;OPENTHREAD_CONFIG_TX_QUEUE_STATISTICS_ENABLE=0;OPENTHREAD_CONFIG_UDP_FORWARD_ENABLE=0;OPENTHREAD_CONFIG_UPTIME_ENABLE=0;OPENTHREAD_CONFIG_THREAD_VERSION=OT_THREAD_VERSION_1_3;OPENTHREAD_CONFIG_DEVICE_POWER_SUPPLY=OT_POWER_SUPPLY_EXTERNAL;OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS=0;OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS_MANAGEMENT=0;PACKAGE_NAME="OPENTHREAD";OPENTHREAD_CONFIG_NCP_HDLC_ENABLE=1;KERNEL;__ZEPHYR__=1;_FORTIFY_SOURCE=1;_ANSI_SOURCE;__LINUX_ERRNO_EXTENSIONS__;USE_PARTITION_MANAGER=1;__PROGRAM_START;NRF52840_XXAA;ZCBOR_ASSERTS;MBEDTLS_CONFIG_FILE="nrf-config.h";MBEDTLS_PSA_CRYPTO_CONFIG_FILE="nrf-psa-crypto-want-config.h";MBEDTLS_PSA_CRYPTO_USER_CONFIG_FILE="nrf-psa-crypto-config.h";NRF_802154_SERIALIZATION_HOST=0;NRF_802154_USE_RAW_API=1;NRF_802154_PENDING_SHORT_ADDRESSES=16;NRF_802154_PENDING_EXTENDED_ADDRESSES=16;NRF_802154_RX_BUFFERS=16;NRF_802154_TX_STARTED_NOTIFY_ENABLED=1;NRF_802154_ACK_TIMEOUT_ENABLED=1;NRF_802154_CCA_CORR_LIMIT_DEFAULT=2;NRF_802154_CCA_CORR_THRESHOLD_DEFAULT=45;NRF_802154_CCA_ED_THRESHOLD_DEFAULT=45;NRF_802154_SECURITY_KEY_STORAGE_SIZE=3;NRF_802154_CCA_MODE_DEFAULT=NRF_RADIO_CCA_MODE_ED;NRF_802154_ENCRYPTION_ENABLED=1;NRF_802154_SECURITY_WRITER_ENABLED=1;NRF_802154_IE_WRITER_ENABLED=1;NRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0;NRF_802154_CARRIER_FUNCTIONS_ENABLED=0;NRF_802154_ENERGY_DETECTED_VERSION=1;NRF_802154_PLATFORM_ASSERT_INCLUDE="nrf_802154_assert_zephyr.h";NRF_802154_ECB_PRIORITY=-1;NRF_802154_SWI_PRIORITY=1" -P /opt/nordic/ncs/v2.6.0-rc1/modules/lib/openthread/etc/cmake/print.cmake
OPENTHREAD_CONFIG_RADIO_LINK_IEEE_802_15_4_ENABLE=1
OPENTHREAD_CONFIG_TMF_ANYCAST_LOCATOR_ENABLE=0
OPENTHREAD_CONFIG_ASSERT_ENABLE=1
OPENTHREAD_CONFIG_BACKBONE_ROUTER_ENABLE=0
OPENTHREAD_CONFIG_BACKBONE_ROUTER_DUA_NDPROXYING_ENABLE=0
OPENTHREAD_CONFIG_BACKBONE_ROUTER_MULTICAST_ROUTING_ENABLE=0
OPENTHREAD_CONFIG_BLE_TCAT_ENABLE=0
OPENTHREAD_CONFIG_BORDER_AGENT_ENABLE=0
OPENTHREAD_CONFIG_BORDER_ROUTER_ENABLE=0
OPENTHREAD_CONFIG_BORDER_ROUTING_ENABLE=0
OPENTHREAD_CONFIG_BORDER_ROUTING_DHCP6_PD_ENABLE=0
OPENTHREAD_CONFIG_IP6_BR_COUNTERS_ENABLE=0
OPENTHREAD_CONFIG_CHANNEL_MANAGER_ENABLE=0
OPENTHREAD_CONFIG_CHANNEL_MONITOR_ENABLE=0
OPENTHREAD_CONFIG_COAP_API_ENABLE=1
OPENTHREAD_CONFIG_COAP_BLOCKWISE_TRANSFER_ENABLE=0
OPENTHREAD_CONFIG_COAP_OBSERVE_API_ENABLE=0
OPENTHREAD_CONFIG_COAP_SECURE_API_ENABLE=0
OPENTHREAD_CONFIG_COMMISSIONER_ENABLE=0
OPENTHREAD_CONFIG_MAC_CSL_AUTO_SYNC_ENABLE=1
OPENTHREAD_CONFIG_MAC_CSL_DEBUG_ENABLE=0
OPENTHREAD_CONFIG_MAC_CSL_RECEIVER_ENABLE=1
OPENTHREAD_CONFIG_MAC_CSL_RECEIVER_LOCAL_TIME_SYNC=0
OPENTHREAD_CONFIG_DATASET_UPDATER_ENABLE=0
OPENTHREAD_CONFIG_MLE_DEVICE_PROPERTY_LEADER_WEIGHT_ENABLE=0
OPENTHREAD_CONFIG_DHCP6_CLIENT_ENABLE=0
OPENTHREAD_CONFIG_DHCP6_SERVER_ENABLE=0
OPENTHREAD_CONFIG_DIAG_ENABLE=0
OPENTHREAD_CONFIG_DNS_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_DNS_CLIENT_OVER_TCP_ENABLE=0
OPENTHREAD_CONFIG_DNS_DSO_ENABLE=0
OPENTHREAD_CONFIG_DNS_UPSTREAM_QUERY_ENABLE=0
OPENTHREAD_CONFIG_DNSSD_SERVER_ENABLE=0
OPENTHREAD_CONFIG_DUA_ENABLE=1
OPENTHREAD_CONFIG_ECDSA_ENABLE=1
OPENTHREAD_CONFIG_HEAP_EXTERNAL_ENABLE=1
OPENTHREAD_POSIX_CONFIG_FIREWALL_ENABLE=0
OPENTHREAD_CONFIG_HISTORY_TRACKER_ENABLE=0
OPENTHREAD_CONFIG_IP6_FRAGMENTATION_ENABLE=1
OPENTHREAD_CONFIG_JAM_DETECTION_ENABLE=0
OPENTHREAD_CONFIG_JOINER_ENABLE=0
OPENTHREAD_CONFIG_MLE_LINK_METRICS_INITIATOR_ENABLE=0
OPENTHREAD_CONFIG_LINK_METRICS_MANAGER_ENABLE=0
OPENTHREAD_CONFIG_MLE_LINK_METRICS_SUBJECT_ENABLE=0
OPENTHREAD_CONFIG_LINK_RAW_ENABLE=0
OPENTHREAD_CONFIG_LOG_LEVEL_DYNAMIC_ENABLE=0
OPENTHREAD_CONFIG_MAC_FILTER_ENABLE=0
OPENTHREAD_CONFIG_MESH_DIAG_ENABLE=0
OPENTHREAD_CONFIG_MESSAGE_USE_HEAP_ENABLE=0
OPENTHREAD_CONFIG_MLE_LONG_ROUTES_ENABLE=0
OPENTHREAD_CONFIG_MLR_ENABLE=1
OPENTHREAD_CONFIG_MULTIPAN_RCP_ENABLE=0
OPENTHREAD_CONFIG_MULTIPLE_INSTANCE_ENABLE=0
OPENTHREAD_CONFIG_NAT64_BORDER_ROUTING_ENABLE=0
OPENTHREAD_CONFIG_NAT64_TRANSLATOR_ENABLE=0
OPENTHREAD_CONFIG_NEIGHBOR_DISCOVERY_AGENT_ENABLE=0
OPENTHREAD_CONFIG_NETDATA_PUBLISHER_ENABLE=0
OPENTHREAD_CONFIG_TMF_NETDIAG_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_OPERATIONAL_DATASET_AUTO_INIT=1
OPENTHREAD_CONFIG_OTNS_ENABLE=0
OPENTHREAD_CONFIG_PING_SENDER_ENABLE=1
OPENTHREAD_CONFIG_PLATFORM_BOOTLOADER_MODE_ENABLE=0
OPENTHREAD_CONFIG_PLATFORM_KEY_REFERENCES_ENABLE=1
OPENTHREAD_CONFIG_PLATFORM_NETIF_ENABLE=0
OPENTHREAD_CONFIG_PLATFORM_POWER_CALIBRATION_ENABLE=0
OPENTHREAD_CONFIG_PLATFORM_UDP_ENABLE=0
OPENTHREAD_CONFIG_REFERENCE_DEVICE_ENABLE=0
OPENTHREAD_CONFIG_TMF_NETDATA_SERVICE_ENABLE=0
OPENTHREAD_SETTINGS_RAM=0
OPENTHREAD_CONFIG_IP6_SLAAC_ENABLE=1
OPENTHREAD_CONFIG_SNTP_CLIENT_ENABLE=0
OPENTHREAD_CONFIG_SRP_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_SRP_SERVER_ENABLE=0
OPENTHREAD_CONFIG_TCP_ENABLE=0
OPENTHREAD_CONFIG_TIME_SYNC_ENABLE=0
OPENTHREAD_CONFIG_RADIO_LINK_TREL_ENABLE=0
OPENTHREAD_CONFIG_MAC_OUTGOING_BEACON_PAYLOAD_ENABLE=0
OPENTHREAD_CONFIG_TX_QUEUE_STATISTICS_ENABLE=0
OPENTHREAD_CONFIG_UDP_FORWARD_ENABLE=0
OPENTHREAD_CONFIG_UPTIME_ENABLE=0
OPENTHREAD_CONFIG_THREAD_VERSION=OT_THREAD_VERSION_1_3
OPENTHREAD_CONFIG_DEVICE_POWER_SUPPLY=OT_POWER_SUPPLY_EXTERNAL
OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS=0
OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS_MANAGEMENT=0
PACKAGE_NAME=OPENTHREAD
OPENTHREAD_CONFIG_NCP_HDLC_ENABLE=1
KERNEL
__ZEPHYR__=1
_FORTIFY_SOURCE=1
_ANSI_SOURCE
__LINUX_ERRNO_EXTENSIONS__
USE_PARTITION_MANAGER=1
__PROGRAM_START
NRF52840_XXAA
ZCBOR_ASSERTS
MBEDTLS_CONFIG_FILE=nrf-config.h
MBEDTLS_PSA_CRYPTO_CONFIG_FILE=nrf-psa-crypto-want-config.h
MBEDTLS_PSA_CRYPTO_USER_CONFIG_FILE=nrf-psa-crypto-config.h
NRF_802154_SERIALIZATION_HOST=0
NRF_802154_USE_RAW_API=1
NRF_802154_PENDING_SHORT_ADDRESSES=16
NRF_802154_PENDING_EXTENDED_ADDRESSES=16
NRF_802154_RX_BUFFERS=16
NRF_802154_TX_STARTED_NOTIFY_ENABLED=1
NRF_802154_ACK_TIMEOUT_ENABLED=1
NRF_802154_CCA_CORR_LIMIT_DEFAULT=2
NRF_802154_CCA_CORR_THRESHOLD_DEFAULT=45
NRF_802154_CCA_ED_THRESHOLD_DEFAULT=45
NRF_802154_SECURITY_KEY_STORAGE_SIZE=3
NRF_802154_CCA_MODE_DEFAULT=NRF_RADIO_CCA_MODE_ED
NRF_802154_ENCRYPTION_ENABLED=1
NRF_802154_SECURITY_WRITER_ENABLED=1
NRF_802154_IE_WRITER_ENABLED=1
NRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0
NRF_802154_CARRIER_FUNCTIONS_ENABLED=0
NRF_802154_ENERGY_DETECTED_VERSION=1
NRF_802154_PLATFORM_ASSERT_INCLUDE=nrf_802154_assert_zephyr.h
NRF_802154_ECB_PRIORITY=-1
NRF_802154_SWI_PRIORITY=1
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/da6f6379ec/bin/cmake --build /Users/puzl/nrf/PuzLLabs_Thread/build

 *  The terminal process terminated with exit code: 1.
 *  Terminal will be reused by tasks, press any key to close it.

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Tue, 12 Mar 2024 00:53:57 GMT

Andreas,

Thanks for the suggestions. I tried the following on my Mac OS system. I went into /opt/nordic/ncs/ and moved my existing v2.6.0-rc1 directory to Saved.v2.6.0-rc1 (to save my work). I then started up the Toolchain manager and installed the v2.6.0-rc1 tool chain. This installed the /opt/nordic/ncs/toolchains files AND the ~/nrf/v2.6.0-rc1 SDF. I then opened up VSCode and set the active toolchain and SDK to point to these versions of v2.6.0-rc1. I got the following error on my first build:

Cannot file file: /opt/nordic/v2.6.0-rc1/nrf/samples/matter/common/src/led_widget.h

I had several other iterations of similar errors. I fixed these by running these shell commands:

cd /opt/nordic/v2.6.0-rc1/nrf/samples/matter/common/src
ln -s app/fabric_table_delegate.h .
ln -s board/led_* .
ln -s bt_nus/bt_nus_service.* .
ln -s dfu/ota/ota_util.* .
ln -s pwm/pwm_device.* .
ln -s persistent_storage/persistent_storage_* .

This allowed me to get past the compile errors. However the build now fails during the "Generating new Factory Data..." step. I will attach the error message below.

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Mon, 11 Mar 2024 11:40:42 GMT

Hi Gene,

It looks like you're validating the toolchain corresponding to nRF Connect SDK v2.5.1 with SDK v2.6.0 selected. Could you verify how it looks in the VS Code extension on your end? On my end it looks like this. I've installed and/or set the SDK version first, then Toolchain version.

The installation should update every requirement when installing, but it looks like it has skipped this in your case (unless installing Toolchain for v2.6.0).

An issue that typically happening on Windows (not sure how it is for MacOs) is that VSCode inherits the SDK and toolchain versions from a project that is in your workspace, so the first thing I would like you to do is to open VSCode and nRF Connect for VS Code extension without any NCS projects in the workspace and then try to set the SDK version and Toolchain version as in the image below. Remove the installation you have present to make sure that you don't have any artifacts from there and select "Install SDK" before selecting toolchain.

Alternatively you can install the SDK version through the Toolchain manager found in nRF Connect for Desktop.

If you open the SDK through the toolchain manager, it should set both SDK and Toolchain version in the extension to match the instance you opened in the toolchain manager.

Let me know if this resolves the issue

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Mon, 11 Mar 2024 01:11:45 GMT

Andreas,

Thank you for the information. I did notice that there was an option to install the v2.6.0-rc1 that showed up in my Visual Studio Code application. I tried it out and it successfully installed. However, at the end of the installation, I got these warnings:

[17:53:17] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.5.1 ===========
📦 Using the nRF Connect SDK v2.6.0-rc1 at /shared/ncs/v2.6.0-rc1
🕒 zephyr-sdk is outdated. Found 0.16.1, but 0.16.5 is required by the SDK.
🕒 cmake is outdated. Found 3.20.5, but 3.21.0 is required by the SDK.
🕒 west is outdated. Found 1.1.0, but 1.2.0 is required by the SDK.
🕒 python is outdated. Found 3.8.2, but 3.9.18 is required by the SDK.
🕒 ninja is outdated. Found 1.9.0, but 1.10.2 is required by the SDK.
🕒 dtc is outdated. Found 1.4.7, but 1.5.1-1 is required by the SDK.

I am wondering if these outdated tools are contributing to the failures that I do experience when trying out the v2.6.0-rc1 SDK. I have spent some time searching your website for ways to manually update these tools, since there is not a v2.6.0 version of the Toolchain. I have not been able to find a satisfactory answer.

Would it be possible to provide me with instructions on how to update these tools (perhaps from a command-line tool)?

Thanks so much,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Thu, 07 Mar 2024 10:32:23 GMT

Hi Gene,

Great, let me know if you have any progress in tracking down the differences. There are a quite significant amount of changes in 2.5.0 and 2.6.0 w.r.t Matter, and among them are the adaptation of Matter v1.2 spec.

Since my initial reply we have also tagged v2.6.0-rc1 which should be both more stable and closer to the full release of NCS v2.6.0

Kind regards,
Andreas

RE: SDK v2.5.99-dev1 has many compile errors

Gene Roylance — Tue, 05 Mar 2024 03:28:17 GMT

Andreas,

Thanks for the reply. I will look at the release notes for version 2.5.99-dev1 branch and see there are any indications for the issue I am seeing.

The code that I am building is based on the nrf/samples/matter/template sample code.

Any other thoughts?

Best Regards,
Gene

RE: SDK v2.5.99-dev1 has many compile errors

AHaug — Mon, 26 Feb 2024 14:13:13 GMT

Hi,

I will look into this

However the build error state that the Clusters and structs have changed since you last compiled it. Have you examined the changes from 2.5.99-dev1 and v2.5.0 w.r.t this aspect?

Is your application custom or is it based on a sample found in the SDK? If so, which sample? Do you see the same thing if you try to take a sample from NCS v2.5.0 and compile it in the 2.5.99-dev tag?

Kind regards,
Andreas