Error when making a driver for Windows IoT core using WDK
I am trying to make a driver to connect a device to a RPi running Windows IoT as specified in this link, using the Windows Driver Kit.
EDIT:
-The iot_adk_addonkit is placed on the D partition due to a lack of space on C.
-With setenv arm the environment for the driver was set to ARM.
When I do the following command in the cmd:
inf2cab D:\_Kobe\driver\driver\oem71.inf
I first get:
Authoring Drivers.oem71.wm.xml
Processing Drivers.oem71.wm.xml
which is ok, but then i get:
the system cannot find the file specified
ThreadId11364 ERROR: (0,0):
ERROR: 0x80070002
ERROR: PkgGen
ERROR: EXCEPTION: ExecuteCommands::Run: Failed to find makecat.exe. Make sure path environment variable is set right
ERROR: STACKTRACE: bij Microsoft.Composition.ToolBox.ExecuteCommands.Run(String toolPath, String args, Boolean loadUserProfile, UInt32 retryCount, Logger logger)
ERROR: bij Microsoft.Composition.Packaging.PkgManifest.CreateCatalog(String catPath, IEnumerable`1 filesToSign, String packageName, Keyform keyform, PackageType packageType)
ERROR: bij Microsoft.Composition.Packaging.PkgManifest.GenerateAndSignCatalog(Boolean signCatalog)
ERROR: bij Microsoft.Composition.Packaging.PkgManifest.SerializeMum(String outputFolder)
ERROR: bij Microsoft.Composition.Packaging.PkgManifest.SaveManifest(String outputFolder)
ERROR: bij Microsoft.Composition.Packaging.CbsPackage.SavePackage(String outputFolder, Boolean compressManifests)
ERROR: bij Microsoft.Composition.Packaging.CbsPackage.SavePackage(String outputFolder)
(PkgToolBox) : error : ExecuteCommands::Run: Failed to find makecat.exe. Make sure path environment variable is set right
Error : Failed to create package. See D:\_Kobe\driver\driver\Drivers.oem71.wm.log
In the log file I read the following:
Creating Drivers.oem70.wm.xml Package with version 10.0.1.0 for
Microsoft (C) PkgGen 10.0.10011.16384
HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\oem70.inf_x86_af229e1a5336e4b5\Configurations\Minidriver32_61_Install.NT\Properties\{a45c254e-df1c-4efd-8020-67d146a850e0}\000E
D:(A;CI;KA;;;SY)
NT AUTHORITY\SYSTEM,FullControl
HKEY_LOCAL_MACHINE\SYSTEM\Setup\ResolveFilePaths
D:(A;OICI;KR;;;RC)(A;OICI;KA;;;SY)(A;OICI;KA;;;BA)
NT AUTHORITY\BEPERKT,ReadKey
NT AUTHORITY\SYSTEM,FullControl
INGEBOUWD\Administrators,FullControl
ThreadId6472 INFO
Loading Package:C:\Users\Michel\AppData\Local\Temp\syslzvvj.dbd\update.mum\.Drivers.oem70~31bf3856ad364e35~x86~~10.0.1.0.mum
ThreadId6472 INFO Loading manifest file C:\Users\Michel\AppData\Local\Temp\syslzvvj.dbd\update.mum\.Drivers.oem70~31bf3856ad364e35~x86~~10.0.1.0.mum
ThreadId6472 INFO
Done loading Package:C:\Users\Michel\AppData\Local\Temp\syslzvvj.dbd\update.mum\.Drivers.oem70~31bf3856ad364e35~x86~~10.0.1.0.mum
ThreadId6472 INFO Adding file of type CsiManifest with detination path and source path C:\Users\Michel\AppData\Local\Temp\cpufor3p.ube\manifests\.Drivers.oem70.man
ThreadId6472 INFO Converting C:\Users\Michel\AppData\Local\Temp\cpufor3p.ube\manifests\.Drivers.oem70.man to CMI manifest
ThreadId6472 INFO Saving CMI Manifest File to : C:\Users\Michel\AppData\Local\Temp\ts1zo1md.thw
ThreadId6472 INFO Adding file of type Manifest with detination path and source path C:\Users\Michel\AppData\Local\Temp\ts1zo1md.thw\x86_.drivers.oem70_31bf3856ad364e35_10.0.1.0_none_6e00b92b9c937322.manifest
ThreadId6472 INFO Loading manifest file C:\Users\Michel\AppData\Local\Temp\q24qwfnq.hul\x86_.drivers.oem70-deployment_31bf3856ad364e35_10.0.1.0_none_d8eada46b31a0442.manifest
Found Driver = C:\Users\Michel\AppData\Local\Temp\cpufor3p.ube\drivers\oem70.inf
ThreadId6472 INFO Adding file of type CsiManifest with detination path and source path C:\Users\Michel\AppData\Local\Temp\cpufor3p.ube\manifests\dual_oem70.inf.man
ThreadId6472 INFO Converting C:\Users\Michel\AppData\Local\Temp\cpufor3p.ube\manifests\dual_oem70.inf.man to CMI manifest
ThreadId6472 INFO Copying 'D:\_Kobe\driver\driver\oem70.inf' to 'C:\Users\Michel\AppData\Local\Temp\4yykdphz.aof\x86_dual_oem70.inf_31bf3856ad364e35_10.0.1.0_none_97edf2b190a48552\oem70.inf'.
ThreadId6472 INFO Saving CMI Manifest File to : C:\Users\Michel\AppData\Local\Temp\4yykdphz.aof
ThreadId6472 INFO Adding file of type Manifest with detination path and source path C:\Users\Michel\AppData\Local\Temp\4yykdphz.aof\x86_dual_oem70.inf_31bf3856ad364e35_10.0.1.0_none_97edf2b190a48552.manifest
ThreadId6472 INFO
Saving CAB D:\Build\x86\pkgs\.Drivers.oem70.cab for package .Drivers.oem70
ThreadId6472 INFO
Saving package .Drivers.oem70 to C:\Users\Michel\AppData\Local\Temp\t0zrnkcl.wnw
ThreadId6472 INFO
Validating Package '.Drivers.oem70'
ThreadId6472 INFO Serialized C:\Users\Michel\AppData\Local\Temp\t0zrnkcl.wnw\x86_-drivers-oem70-deployment-deployment_31bf3856ad364e35_10.0.1.0_none_485b13d3c5ee921e.manifest to disk
ThreadId6472 INFO Running makecat.exe /v "C:\Users\Michel\AppData\Local\Temp\jq3yfkv5.3y1\.Drivers.oem70~31bf3856ad364e35~x86~~10.0.1.0"
--Stack Trace--
bij Microsoft.Composition.ToolBox.ExecuteCommands.Run(String toolPath, String args, Boolean loadUserProfile, UInt32 retryCount, Logger logger)
bij Microsoft.Composition.Packaging.PkgManifest.CreateCatalog(String catPath, IEnumerable`1 filesToSign, String packageName, Keyform keyform, PackageType packageType)
bij Microsoft.Composition.Packaging.PkgManifest.GenerateAndSignCatalog(Boolean signCatalog)
bij Microsoft.Composition.Packaging.PkgManifest.SerializeMum(String outputFolder)
bij Microsoft.Composition.Packaging.PkgManifest.SaveManifest(String outputFolder)
bij Microsoft.Composition.Packaging.CbsPackage.SavePackage(String outputFolder, Boolean compressManifests)
bij Microsoft.Composition.Packaging.CbsPackage.SavePackage(String outputFolder)
bij Microsoft.Composition.Packaging.CbsPackage.SaveCab(String cabPath, CompressionType compressionType)
bij Microsoft.CompPlat.PkgBldr.CabGen.Assembly.ConvertEntries(XElement parent, Dictionary`2 plugins, Config enviorn, XElement component)
bij Microsoft.CompPlat.PkgBldr.Program.BuildPackage(Config config, MacroResolver commandLineMacros)
bij Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
--End Stack Trace--
Package creation failed with error -1
I have already corrected some paths used in the WDK and those look OK to me now.
Makecat.exe is also in the folder it is supposed to be, so I don't understand that one either.
EDIT:
-I now tried moving the iot_adk_addonkit to the C disk, this didn't make a difference.
-I also tried including this folder in the Path of the cmd so i wouldn't have to work in that specific folder. This didn't work either.
If someone could help me see what I'm doing wrong... Thanks already!
Solution
I use IoTCoreShell-arm.cmd in iot-adk-addonkit. C and D disks both work for me. You can also use IoTCoreShell.cmd and select ARM Architecture. The following is how I run the command, you can have a try to see if it works.
More information: "Lab 1e: Add a driver to an image"
- UEFI Application: UEFI NTFS driver is not loading properly
- Pc does not accept any input after setting up controller
- Error when installing Microsoft Sql Server 2019, cannot find the microsoft OLE DB Driver
- USB2.0 control endpoint stall upon set_configuration request
- Writing character device driver, ioctl() vs normal read/write?
- wdk ddk compiler problems with std::string and std::wstring
- Windows WDI Driver Sample Problem - MiniportInitializeEx operation failed
- Installing a driver via pnputil
- TIUSB3410 Linux Driver
- What is the difference between SESSION_DRIVER=file and SESSION_DRIVER=redis in env laravel?
- Why could DDK successfully compile an invalid source file?
- Could not load dynamic library 'libcublasLt.so.11'; dlerror: libcublasLt.so.11: cannot open shared object file: No such file or directory
- descriptor concept in NIC
- Microsoft SSIS - Issues switching from attunity driver to new Microsoft Oracle Connector v1.3
- How to identify device at i2c address?
- Why is my STM32F407 not being recognized by the computer (Windows 10)?
- Cannot load `swrast` and `iris` drivers in Fedora 35
- Number of outstanding clients of a service/driver IO file on Windows
- How is stack frame managed within a thread in Cuda?
- Unable to interact with my Flutter app to find elements location on Appium inspector 2023.12.2 with Appium 2.4.1
- Access denied while using ObRegisterCallbacks from Windows Driver Kit
- How to make a Git custom merge driver automatically stage resolved files?
- What is the difference between FIQ and IRQ interrupt system?
- Why am I getting an error before configuring a device in Visual Studio 2015?
- Kernel Mode Driver, Empty (KMDF) No Linker under Configuration Properties
- Driver compilation successful but no .sys file generated
- Zephyr build error when trying to switch board target
- Windows Driver : Install legacy hardware with command line tool
- Running JavaFX app inside Docker container: failed to load driver: iris
- MSBuild detect if signed driver is same as previous built non-signed driver (prevent re-signing via caching)