Hi,
The i.MX Windows IoT User’s Guide, Rev. 1.5.1 — 24 May 2024 (IMXWGU.pdf) only talks about installing the Windows 10 SDK, ADK and WDK, but when targeting Windows 11 IoT on the iMX93, shouldn't this all be the Windows 11 SDK, ADK and WDK?
I'm just installing a fresh build PC to build a custom image for the i.MX 93 EVK, and I don't want to mess it up already at the install of VS2019...
An updated version of the i.MX Windows IoT User’s Guide (IMXWGU.pdf) explaining exactly what to install if you are wanting to build a Win11 image would be much appreciated (a reply here is of course also sufficient for now).
Hello,
For this question is better go with Microsoft.
Regards
I'll go ask Microsoft, but I am a bit surprised at your response...
The download links on your site show the BSP supports Windows 10 & 11:
But the Quick Start & User Guide only contain instructions on how to build Windows 10. Now surely, your team must have built Windows 11 to make the claim that the BSP supports Windows 11, right?
My question is super simple; do I need Windows 11 SDK/ADK/WDK to build Windows 11 using your BSP or not? It should not be a difficult question to answer if the team tried it once. And if they did, why didn't they simply update the PDFs with their findings?
Anyway, I'll go and ask Microsoft...
If you already have working BSP binaries, you can use either Windows 10 or Windows 11 ADK + WinPE add-on for the ADK to integrate the drivers into the Windows 11 IoT Enterprise image. I've tested both.
I haven't tried building the i.MX 93 drivers from the BSP source code, but since the pre-built BSP package only has a single set of drivers that is used for both Windows 10 and Windows 11, I believe that the listed prerequisites in the User Guide should work for both.
With the latest Win11 ADK/DDK/SDK you will run into a lot of build and sign errors. The sign errors are due to the signing not using local time (that's an easy fix in the project settings; Inf2Cat use local time). The build errors are due to the, I guess, new requirement for driver installers to not set any registry settings outside of the normal driver registry (galcore for instance has a few registry settings in HKLM\Software which are not allowed). Oh, and a bunch of 5272 compiler warnings that are treated as errors, disabling those for now).
All in all it's definitely not a straightforward "follow the guide" experience. It needs updating, especially the WSL and building in Linux part. If you follow those instructions you are absolutely hitting a brick wall. Try it.
I have tried using the latest VS2022 + WDK + SDK, but was not able to build the drivers in the BSP. I recall seeing some of the same errors you mentioned below. Were you ever able to get it building with the latest Visual Studio, WDK, SDK?
Using the exact versions of Visual Studio, MSVC, ADK, SDK, WDK that are called out in the User Guide, I was able to build the BSP drivers from source.
I haven't tried that on i.MX 93 + Windows 11 yet, but I would guess it'd work based on my comment earlier.
Yes, with all the changes I described above, I can build all drivers without any errors. Of course, galcore will need another component added that will set the correct registry settings outside of the driver registry (so probably galcore will use defaults for now, hopefully those defaults are the right ones...).
I may just have to go back and install exactly the ADK/WDK/SDK versions described in the pdf...
However, the firmware part doesn't build at all. I don't think anyone has ever actually followed the instructions for that, because those instructions are all out of order and/or not working at all.
I've got an EEAP feedback active on the MS partner collaborate portal, so hopefully I will get some help there.
Oh, and I flashed the pre-built binaries to an SD card (as per the quick start guide). Windows 11 boots into UEFI but then the USB keyboard doesn't work (all on the iMX93 EVK that should work AS-IS), so also there I am totally stuck...
Hello,
The answer is no. the windows BSP is made by Microsoft.
regards