SDK v2.5.99-dev1 has many compile errors

Hello,

I am working on a Mac mini, Apple M2 chipset, macOS Sonoma 14.2.1.   I am using Visual Studio Code Version: 1.86.2 (Universal) Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:42:13.651Z Electron: 27.2.3 ElectronBuildId: 26908389 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0

I have been developing code on the nRF52840 DK for several months using SDK v2.5.0.   I recently downloaded SDK v2.5.99-dev1

After successfully building with SDK v2.5.0, I remove the build directory, change the active SDK to 2.5.99-dev1, create a new Build configuration (the same way I did for v2.5.0 SDK), and then build.   I get many compile errors like this:

../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp: In member function 'CHIP_ERROR chip::app::Clusters::UnitTesting::Structs::TestFabricScoped::DecodableType::Decode(chip::TLV::TLVReader&)':
../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp:20334:37: error: 'class chip::app::Clusters::detail::StructDecodeIterator' has no member named 'Next'
20334 |         auto __element = __iterator.Next();
      |                                     ^~~~
../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp:20335:18: error: 'holds_alternative' is not a member of 'std'
20335 |         if (std::holds_alternative<CHIP_ERROR>(__element))
      |                  ^~~~~~~~~~~~~~~~~

Parents
  • 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

  • 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

  • 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.

    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.
    
    {
      "platform": {
        "os": "darwin",
        "osVersion": "Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000",
        "osKernel": "23.4.0",
        "vscode": "1.81.0",
        "electron": "22.3.18",
        "node": "v16.17.1"
      },
      "system": {
        "date": "2024-04-05T16:26:20.024Z",
        "vscodeRoot": "/private/var/folders/_j/1y61dvds1pbf1k2q2p1rz8g40000gn/T/AppTranslocation/65839C9E-5691-47C6-8000-A4BDDAAA1B23/d/Visual Studio Code.app/Contents/Resources/app",
        "nrfConnectForDesktopInstalled": true,
        "vscodeUptime": "38:24:50",
        "osUptime": "72:33:02",
        "cpu": "Apple M1 Pro"
      },
      "workspace": {
        "name": "GitLab (Workspace)",
        "workspaceFile": "/Users/Kranz/puzl/nrf/GitLab.code-workspace",
        "folders": [
          "/Users/Kranz/puzl/nrf/GitLab",
          "/Users/Kranz/puzl/nrf/template2.5.2",
          "/Users/Kranz/puzl/nrf/template",
          "/Users/Kranz/puzl/nrf/blinky2.6.0"
        ]
      },
      "sdks": [
        {
          "version": "v2.6.0",
          "path": "/opt/nordic/ncs/v2.6.0"
        },
        {
          "version": "v2.5.2",
          "path": "/opt/nordic/ncs/v2.5.2"
        },
        {
          "version": "v2.5.0",
          "path": "/opt/nordic/ncs/v2.5.0"
        }
      ],
      "activeBuild": "/Users/Kranz/puzl/nrf/template/build",
      "apps": [
        {
          "workspace": "/Users/Kranz/puzl/nrf/GitLab",
          "uri": "/Users/Kranz/puzl/nrf/GitLab",
          "buildConfigurations": [
            {
              "id": "/Users/Kranz/puzl/nrf/GitLab/build",
              "name": "build",
              "boardId": "nrf52840dk_nrf52840",
              "type": "Zephyr",
              "isChild": false,
              "isStale": false,
              "taskBindings": {
                "build": [],
                "pristineBuild": [],
                "flash": [],
                "eraseAndFlash": []
              }
            }
          ]
        },
        {
          "workspace": "/Users/Kranz/puzl/nrf/template2.5.2",
          "uri": "/Users/Kranz/puzl/nrf/template2.5.2",
          "buildConfigurations": []
        },
        {
          "workspace": "/Users/Kranz/puzl/nrf/template",
          "uri": "/Users/Kranz/puzl/nrf/template",
          "buildConfigurations": [
            {
              "id": "/Users/Kranz/puzl/nrf/template/build",
              "name": "build",
              "boardId": "nrf52840dk_nrf52840",
              "type": "Zephyr",
              "isChild": false,
              "isStale": false,
              "taskBindings": {
                "build": [],
                "pristineBuild": [],
                "flash": [],
                "eraseAndFlash": []
              }
            }
          ]
        },
        {
          "workspace": "/Users/Kranz/puzl/nrf/blinky2.6.0",
          "uri": "/Users/Kranz/puzl/nrf/blinky2.6.0",
          "buildConfigurations": [
            {
              "id": "/Users/Kranz/puzl/nrf/blinky2.6.0/build",
              "name": "build",
              "boardId": "nrf52840dk_nrf52840",
              "type": "Zephyr",
              "isChild": false,
              "isStale": false,
              "taskBindings": {
                "build": [],
                "pristineBuild": [],
                "flash": [],
                "eraseAndFlash": []
              }
            }
          ]
        }
      ],
      "topdir": "/opt/nordic/ncs/v2.6.0",
      "workspaceState": "freestanding-ready",
      "toolchains": [
        {
          "version": "2.6.0",
          "path": "/opt/nordic/ncs/toolchains/580e4ef81c"
        },
        {
          "version": "2.5.2",
          "path": "/opt/nordic/ncs/toolchains/20d68df7e5"
        },
        {
          "version": "2.5.0",
          "path": "/opt/nordic/ncs/toolchains/20d68df7e5"
        },
        {
          "version": "2.4.1",
          "path": "/opt/nordic/ncs/toolchains/4ef6631da0"
        }
      ],
      "connectedDevices": [
        {
          "serialNumber": "001050258135",
          "boardVersion": "PCA10056",
          "deviceFamily": "NRF52_FAMILY",
          "deviceVersion": "NRF52840_xxAA_REV3",
          "jlinkObFirmwareVersion": "J-Link OB-nRF5340-NordicSemi compiled Oct 30 2023 12:13:06"
        }
      ],
      "deviceProvider": "nrfutil",
      "tools": {
        "/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc": "0.16.5",
        "/Applications/SEGGER/JLink/JLinkExe": "7.94c",
        "/usr/local/bin/nrfjprog": "10.23.0",
        "nrfutil": "Not found",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/cmake": "3.21.0",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/west": "1.2.0",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/python3": "3.9.6",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/ninja": "1.10.2",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/gperf": "3.1",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/dtc": "1.6.1",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/gn": "2154",
        "/opt/nordic/ncs/toolchains/580e4ef81c/bin/git": "2.37.3",
        "gdbPath": "/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb"
      },
      "nrfutil": {
        "nrfutil-device": {
          "version": "2.0.0",
          "binPath": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-connect-2024.3.25-darwin-arm64/platform/nrfutil/bin/nrfutil-device"
        },
        "nrfutil-toolchain-manager": {
          "version": "0.14.1",
          "binPath": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-connect-2024.3.25-darwin-arm64/platform/nrfutil/bin/nrfutil-toolchain-manager"
        }
      },
      "environment": {
        "westEnv": {
          "ELECTRON_RUN_AS_NODE": "1",
          "GIT_EXEC_PATH": "/opt/nordic/ncs/toolchains/580e4ef81c/Cellar/git/2.37.3/libexec/git-core",
          "HOME": "/Users/Kranz",
          "PATH": "/opt/nordic/ncs/toolchains/580e4ef81c/bin:/opt/nordic/ncs/toolchains/580e4ef81c/usr/bin:/opt/nordic/ncs/toolchains/580e4ef81c/usr/local/bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/nanopb/generator-bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/aarch64-zephyr-elf/bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/x86_64-zephyr-elf/bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin:/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/riscv64-zephyr-elf/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/Users/Kranz:/Users/Kranz/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/opt/nordic/ncs/toolchains/20d68df7e5/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/Users/Kranz:/Users/Kranz/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/opt/nordic/ncs/toolchains/20d68df7e5/bin",
          "ZEPHYR_BASE": "/opt/nordic/ncs/v2.6.0/zephyr",
          "ZEPHYR_TOOLCHAIN_VARIANT": "zephyr",
          "ZEPHYR_SDK_INSTALL_DIR": "/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk",
          "USER": "Kranz"
        },
        "inherited": {
          "ELECTRON_RUN_AS_NODE": "1",
          "HOME": "/Users/Kranz",
          "PATH": "/Library/Frameworks/Python.framework/Versions/3.12/bin:/Library/Frameworks/Python.framework/Versions/3.12/bin:/Users/Kranz:/Users/Kranz/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/opt/nordic/ncs/toolchains/20d68df7e5/bin",
          "USER": "Kranz"
        },
        "toolchainPath": "/opt/nordic/ncs/toolchains/580e4ef81c",
        "toolchainBinPath": "/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin",
        "toolchainVersion": "2.6.0"
      },
      "terminal": {
        "defaultProfile": null
      },
      "config": {
        "nordic-semiconductor.nrf-connect": {
          "topdir": "${nrf-connect.sdk:2.6.0}",
          "toolchain": {
            "path": "${nrf-connect.toolchain:2.6.0}"
          },
          "ozonePath": "",
          "applications": [
            "${workspaceFolder}"
          ],
          "applicationOptions": {},
          "kconfig": {
            "interface": "kconfig"
          },
          "west": {
            "env": {
              "$base": "terminal"
            }
          },
          "boardRoots": [],
          "taskBindings": {},
          "buildTerminal": {
            "condensedProgress": true
          },
          "debugging": {
            "flash": true,
            "bindings": {
              "${workspaceFolder}/build": "Launch GitLab/build"
            },
            "justMyCode": true
          },
          "activeAppFollowActiveEditor": true,
          "deviceProvider": "",
          "flash": {
            "softreset": false,
            "erase": false,
            "recover": false
          },
          "enableTelemetry": false,
          "thirdpartyIntegration": {},
          "toolchainManager": {
            "indexURL": null,
            "installDirectory": null
          },
          "nrfutil": {
            "home": null
          },
          "defaultOpenAction": "ask",
          "welcome": {
            "showOnStartup": true
          }
        },
        "nordic-semiconductor.nrf-terminal": {
          "terminalMode": "character"
        }
      },
      "extensions": {
        "internal": {
          "nordic-semiconductor.nrf-connect": {
            "version": "2024.3.25",
            "path": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-connect-2024.3.25-darwin-arm64",
            "isActive": true
          },
          "nordic-semiconductor.nrf-terminal": {
            "version": "2024.3.15",
            "path": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-terminal-2024.3.15",
            "isActive": true
          },
          "nordic-semiconductor.nrf-devicetree": {
            "version": "2024.3.78",
            "path": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-devicetree-2024.3.78",
            "isActive": true
          },
          "nordic-semiconductor.nrf-kconfig": {
            "version": "2024.3.21",
            "path": "/Users/Kranz/.vscode/extensions/nordic-semiconductor.nrf-kconfig-2024.3.21",
            "isActive": true
          }
        },
        "external": {
          "marus25.cortex-debug": null,
          "ms-vscode.cpptools": "1.19.9",
          "ms-vscode.js-debug": "1.81.0",
          "ms-vscode.js-debug-companion": "1.1.2",
          "ms-vscode.vscode-js-profile-table": "1.0.3",
          "eamodio.gitlens": "14.5.2",
          "shd101wyy.markdown-preview-enhanced": "0.8.13",
          "trond-snekvik.gnu-mapfiles": "1.1.0",
          "twxs.cmake": "0.0.17"
        }
      }
    }

    Thanks, Steve K. PuzL Labs, LLC

  • Hi,

    Thank you for the comparison Steve

    A couple of thoughts:

    1. 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.
    2. 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?
    Gene Roylance said:
    v2.6.0, then for some reason, find that it had changed to v2.5.2 when I build. 

    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

  • 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

  • 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

Reply
  • 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

Children
  • Hi,

    Gene Roylance said:
    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.

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

    Gene Roylance said:
    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.

    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

Related