Can't create new nRF Connect SDK v2.9.0 application and build configuration - Error: HMv2 SOCs must be passed to determine identifier components

Hello,

When I follow the steps to create a new standalone workspace application for SDK and Toolchain 2.9.0, and then add a new build configuration and build the project, I receive the error "HMv2 SOCs must be passed to determine identifier components" and the project does not compile.

Steps I use to create a Workspace application (recommended): https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/create_application.html#creating_application_in_the_nrf_connect_for_vs_code_extension

  • Hardware: nRF9161DK
  • SDK: 2.9.0
  • Toolchain: 2.9.0
  • OS: Windows 11
  • Note: I also have SDK/Toolchain 2.8.0 and 2.6.2 installed under c:\ncs\...

Following the steps in the link above:

For Step 4, I selected the following: Copy a sample -> nRF Connect SDK 2.9.0 -> Filter for nRF9161 Non Secure board -> TLS Ciphersuites sample

For step 5 I used: "c:\ncs_workspace\ciphersuites"

For step 7.d, the location I enter is: "c:\ncs_workspace\ciphersuites"

For step 7.e, I select SDK 2.9.0 (C:\ncs\v2.9.0)

Step 7.f doesn't make sense to me. After selecting Manage SDKs -> Manage West Workspace -> West Update. it asks you to select the SDK again and the only option that makes sense is "nrf Connect SDK v2.9.0 [nrf] C:\ncs\v2.9.0". However, I DO NOT do this step as written. Is this a bug in nRF Connect plugin, or are the instructions wrong? Instead, I click "TERMINAL" at the bottom of VS Code, then the dropdown, and "nRF Connect". This opens a nRF Connect terminal where the icon shows that SDK and Toolchain 2.9.0 is being used for the terminal.

I then enter "west update" into the terminal and wait for the SDK to download (Takes 10-20 minutes for me). The completion of this step is indicated by:

HEAD is now at 47f34dd Update version to 0.9.0
HEAD is now at 47f34dd Update version to 0.9.0
PS C:\ncs_workspace\ciphersuites>

- Now I navigate to the nRF Connect plugin -> "Add build configuration" under the "application" folder in the "APPLICATIONS" section. Here you will observe that the project SDK is still pointing to "C:\ncs\v2.9.0".

You must close the project via File -> Close Folder. Then reopen the application on the nRF Connect plugin via "Open an existing application" and point to "C:\ncs_workspace\ciphersuites\application".

- Now navigate back to nRF Connect plugin -> "Add build configuration" under the "application" folder in the "APPLICATIONS" section. Observe an asterisk "*" on the SDK version and confirm that the SDK is now pointing to the local project as so:

- Now select the "Board target" as "nrf9161dk/nrf9161/ns" as shown in the screenshot above. Leave all other build configurations at their default value.

Make sure "Build after generating configuration" is checked, and click "Build Configuration". Observe the build partially complete with the error "HMv2 SOCs must be passed to determine identifier components" and no build configuration was created.

Now, if I click the blue "Pristine Build" button, the following error is displayed (Unable to build SDK...") :

This thing seems all sorts of broken. Not sure what I am doing wrong, or if I am doing anything wrong.

I have run these steps 3 times now with the same results using SDK 2.9.0. I plan to try with SDK 2.8.0 next.

Can you reproduce this? Any idea what's going on?

Thanks,

Derek

  • Well, I just found a workaround. Don't know why I didn't think to try this sooner. After creating a build configuration and receiving the error "HMv2 SOCs must be passed to determine identifier components", do the following:

    1. Close the project
    2. Close VS Code
    3. Reopen VS Code
    4. Reopen the project with the nRF Connect plugin -> Open an existing application

    Once the project is reopened, you will see that the build configuration is now present. Clicking on it and performing a pristine build works. I just flashed my board and the example ran. Seems like the example is broken (A whole different unrelated low priority issue), but at least the code runs!

    I will leave this ticket open in case Nordic wants to test the bug, log it, and add it to their bugfix list for the next release (If it is a bug, looks like one).

    Note: You may just be able to close the project and reopen it without closing VS Code. Since I didn't test this path, I noted the working steps I took above.

    Derek

  • I'm also getting the "HMv2 SOCs must be passed to determine identifier components" error after creating the build configuration. This is in an workspace application repository. Closing and reopening the editor is enough the clear the error and allow me to build.

    • Hardware: xiao_ble/nrf52840/sense
    • SDK: 2.9.0
    • Toolchain: 2.9.0
    • OS: Mac OS X 15.3.1
    • Editor: Cursor 0.46.8 (VSCode Version: 1.96.2)
  • Glad I am not the only one. Hopefully Nordic fixes this.

    Thanks for sharing!

    Derek

  • Thank you for letting us now. We have noted this and will be looking int it.

    -Priyanka

Related