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

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

Priyanka — Tue, 11 Mar 2025 13:29:35 GMT

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

-Priyanka

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

droberson — Fri, 07 Mar 2025 18:11:16 GMT

Glad I am not the only one. Hopefully Nordic fixes this.

Thanks for sharing!

Derek

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

bringert — Fri, 07 Mar 2025 11:11:18 GMT

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)

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

droberson — Tue, 28 Jan 2025 21:58:08 GMT

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:

Close the project
Close VS Code
Reopen VS Code
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