nRF Connect for VS Code failed to import bsim (tools/bsim)

[Thoste]

Hi,

I'm getting the following error over and over again from the nrf connect plugin in VSCode:

[west]: FATAL ERROR: failed manifest import in bsim (tools/bsim):
[west]: Failed importing "west.yml" from revision "384a091445c57b44ac8cbd18ebd245b47c71db94"
[west]: Hint: bsim must be cloned and its manifest-rev ref must point to a commit with the import data
[west]: To fix, run "west update"

This started happening after switching to a newer version of the nrf connect sdk (v2.9.2).
I'm still able to build my projects, however the continues error throwing slows down vscode and de building process it seems.
Furthermore, the applications tab of the nrf connect plugin seems to be very buggy.
I almost always have to delete the entire build folder and add the build configuration, I think this is also correlated to the errors I'm getting.

I tried several vs code version and nrf connect plugin versions. Im now on v2025.5.152 of the nrf connect for vs code.
And the following vs code version:

[dejans]

Hi,

How did you fetch BabbleSim?

[west]: FATAL ERROR: failed manifest import in bsim (tools/bsim):
[west]: Failed importing "west.yml" from revision "384a091445c57b44ac8cbd18ebd245b47c71db94"
[west]: Hint: bsim must be cloned and its manifest-rev ref must point to a commit with the import data
[west]: To fix, run "west update"

Which action from your side caused this error?

Best regards,
Dejan

[Thoste]

Hi,

I am not actively using bsim, but ncs/zehpyr is using it I guess. It started after installing a new toolchain v2.9.2 of ncs through the manage toolchains option in the nrf connect plugin of vs code.

Now every time I interact with the nrf connect plugin it spams this error for like 8-10 times. So if i click on a build configuration the error is thrown in the output window for 8-10 times. Then if i start a build, again the error is thrown for couple of times. The build does complete like normal, however when it finishes the output window again pops-up and shows the error is thrown again for x times. 

The error suggests that to fix it you run "west update", but this doesnt fix the issue. West update works and doesnt give any error. But then if I interact with the nrf connect plugin then the output window starts throwing errors again.  

[dejans]

Hi,

Can you share the output of the "west update" command?

Best regards,
Dejan

[Thoste]

There is nothing interesting to see in the west update. Just that everything updated just fine. However, VSCode stopped spamming the error, so it seems solved now. No clue what has changed.

=== updating nrf (nrf):
HEAD is now at 8f350bab46 Merge tag 'v2.9.2' into main
=== updating zephyr (zephyr):
HEAD is now at be33fea3178 Merge tag 'v3.7.99-ncs2-2' into main
=== updating codestyle (app/utils/codestyle):
HEAD is now at 1964c8b Merge branch 'feature/update-clang-format' into 'master'
=== updating docs (app/utils/docs):
HEAD is now at 0396374 Merge branch 'hotfix/latest' into 'develop'
=== updating mcuboot (bootloader/mcuboot):
HEAD is now at 12e5ee10 [nrf noup] boot: bootutil: Allow configuring number of KMU keys
=== updating mbedtls (modules/crypto/mbedtls):
HEAD is now at 98603a8c9 [nrf noup]: Allow for using legacy when MBEDTLS_FORCE_LEGACY_MD/CIPHER
=== updating nrfxlib (nrfxlib):
HEAD is now at 1143aee1 softdevice_controller: rev 8c085997976be1de80e5fdf6b458ff37d96de558
=== updating trusted-firmware-m (modules/tee/tf-m/trusted-firmware-m):
HEAD is now at e200da60e [nrf noup] Remove version mismatch CMake warning
=== updating nanopb (modules/lib/nanopb):
HEAD is now at 4474bd3 Do not include system paths when finding generator script
=== updating cmsis (modules/hal/cmsis):
HEAD is now at 4b96cbb doc: Update documentations for CMSIS 5.9.0
=== updating hal_nordic (modules/hal/nordic):
HEAD is now at bc671cb nrfx: mdk: Update to version 8.68.2
=== updating hal_st (modules/hal/st):
HEAD is now at b2f548f sensor/stmemsc: Align stmemsc i/f to v2.6
=== updating hostap (modules/lib/hostap):
HEAD is now at 442853103 [noup] wpa_supplicant: Fix unused variable warning
=== updating libmetal (modules/hal/libmetal):
HEAD is now at a6851ba lib: update libmetal to release v2024.05.0
=== updating open-amp (modules/lib/open-amp):
HEAD is now at b735edb lib: remoteproc: replace strncpy with internal strlcpy
=== updating segger (modules/debug/segger):
HEAD is now at b011c45 segger: config: Add CCM option for linker sections
=== updating tinycrypt (modules/crypto/tinycrypt):
HEAD is now at 1012a3e Fix warnings reported by UBSAN
=== updating zcbor (modules/lib/zcbor):
HEAD is now at 47f34dd Update version to 0.9.0

[dejans]

Hi,

Thoste said:

VSCode stopped spamming the error

Thank you for the update.

Best regards,
Dejan