Zephyr Project recently had a major update after v3.6.0 called Hardware Model v2 (HWMv2), see parent issue for details. This update reorganized where boards are located in the Zephyr repo. As a result, the MCUXpresso extension for VS Code can no longer find the NXP boards in the Zephyr repo, as shown in this screenshot:
This impacts v1.6.47 and earlier of the MCUXpresso extension. NXP is updating the VS Code extension to resolve this. In the meantime, one workaround is to use the latest Zephyr release v3.6.0. This release was just before the HWMv2 update, and it still uses the v1 model, and is compatible with the MCUXpresso extension.
When importing the Zephyr repo, you can specify the revision, like this screenshot:
Using Zephyr v3.6.0 or earlier then enables the extension to import for any NXP boards supported in that revision:
Zephyr Project recently had a major update after v3.6.0 called Hardware Model v2 (HWMv2), see parent issue for details. This update reorganized where boards are located in the Zephyr repo. As a result, the MCUXpresso extension for VS Code can no longer find the NXP boards in the Zephyr repo, as shown in this screenshot:
This impacts v1.6.47 and earlier of the MCUXpresso extension. NXP is updating the VS Code extension to resolve this. In the meantime, one workaround is to use the latest Zephyr release v3.6.0. This release was just before the HWMv2 update, and it still uses the v1 model, and is compatible with the MCUXpresso extension.
When importing the Zephyr repo, you can specify the revision, like this screenshot:
Using Zephyr v3.6.0 or earlier then enables the extension to import for any NXP boards supported in that revision: