I am testing the “Sample KMDF Function Driver for OSR USB-FX2” with a board that uses FX2LP and USB interface. I changed the GUID in osrusbfx2.inx and in public.h. But the Device Manager could detect the driver file (.sys and .inf) when I do “Update Driver Software”.
it says “Windows could not find driver software for your device”
What could be the course of this?
Thanks.
Does your hardware ID match? Find your device in device manager, right click, choose properties, details tab and select the hardware ids. Does any value in that list match what your inf specifies?
Sent from Outlook Mailhttp: for Windows 10
From: xxxxx@gmail.com
Sent: Wednesday, June 24, 2015 1:04 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] device drivrer not regonized by device manager
I am testing the “Sample KMDF Function Driver for OSR USB-FX2” with a board that uses FX2LP and USB interface. I changed the GUID in osrusbfx2.inx and in public.h. But the Device Manager could detect the driver file (.sys and .inf) when I do “Update Driver Software”.
it says “Windows could not find driver software for your device”
What could be the course of this?
Thanks.
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</http:>
Hi Doron,
The Hardware ID shows: “USB\VID_04B4&PID_1003&REV_0000”
And in the .inf file, it shows:
; For Win2K
[Microsoft]
%USB\VID_04b4&PID_1003.DeviceDesc%=osrusbfx2.Dev, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
Look in %windir%\inf\setupapi.dev.log (near the end) to see what hardware IDs were attempted to match on and why your INF was not chosen
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, June 24, 2015 1:41 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] device drivrer not regonized by device manager
Hi Doron,
The Hardware ID shows: “USB\VID_04B4&PID_1003&REV_0000”
And in the .inf file, it shows:
; For Win2K
[Microsoft]
%USB\VID_04b4&PID_1003.DeviceDesc%=osrusbfx2.Dev, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
xxxxx@gmail.com wrote:
Hi Doron,
The Hardware ID shows: “USB\VID_04B4&PID_1003&REV_0000”
And in the .inf file, it shows:
; For Win2K
[Microsoft]
%USB\VID_04b4&PID_1003.DeviceDesc%=osrusbfx2.Dev, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
OK, but you’ll never use that section. What about the
[Microsoft.NT$ARCH$] section?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Tim,
I change the [Manufacturer] from Microsoft,NTx86 to Device,NT,NTx86,NTamd64 and now the device manager is able to detect the driver software but I got another error.
“The driver installation file for this device is missing a necessary entry. This may be because the INF was written for Windows95 or later.”
xxxxx@gmail.com wrote:
I change the [Manufacturer] from Microsoft,NTx86 to Device,NT,NTx86,NTamd64 and now the device manager is able to detect the driver software but I got another error.
“The driver installation file for this device is missing a necessary entry. This may be because the INF was written for Windows95 or later.”
Post your entire INF. There are way too many dependencies in an INF for
us to make a diagnosis.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Tim, below is the inf file, the computer I am using is 64bit with Intel(R) Core i7 CPU, Win 7
[Version]
Signature=“$WINDOWS NT$”
Class=USB
ClassGuid={36FC9E60-C465-11CF-8056-444553540000}
Provider=%MSFT%
DriverVer=06/24/2015,16.46.33.708
CatalogFile=KmdfSamples.cat
[SourceDisksFiles]
OSRUSBFX2.sys = 1
; ================= Class section =====================
[ClassInstall32]
Addreg=SampleClassReg
[SampleClassReg]
HKR,0,%ClassName%
HKR,Icon,-5
; ================= Device section =====================
[Manufacturer]
%MfgName%=Microsoft,NT,NTx86,NTamd64
; For Win2K
[Microsoft.NT]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[Microsoft.NTx86]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[Microsoft.NTamd64]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[osrusbfx2.Dev.NT]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NT.HW]
AddReg=osrusbfx2.AddReg.Guid
[Switch.Dev.NT.Services]
AddService = , %SPSVCINST_ASSOCSERVICE%,
[osrusbfx2.Dev.NT.Services]
AddService = osrusbfx2, %SPSVCINST_ASSOCSERVICE%, osrusbfx2.AddService
[osrusbfx2.NTx86]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NTx86.HW]
AddReg=osrusbfx2.AddReg.Guid
[osrusbfx2.NTx86.Services]
Addservice = osrusbfx2,2,osrusbfx2.AddService
[osrusbfx2.NTamd64]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NTamd64.HW]
AddReg=osrusbfx2.AddReg.Guid
[osrusbfx2.NTamd64.Services]
Addservice = osrusbfx2,2,osrusbfx2.AddService
[osrusbfx2.AddReg]
; Deprecating - do not use in new apps to identify a osrusbfx2 driver
HKR,DevLoader,*ntkern
HKR,NTMPDriver,osrusbfx2.sys
; You may optionally include a check for DriverBase in your application to check for a osrusbfx2 driver
HKR,DriverBase,osrusbfx2.sys
HKR,“Parameters”,“MaximumTransferSize”,0x10001,4096
HKR,“Parameters”,“DebugLevel”,0x10001,2
HKR,FriendlyName,%osrusbfx2_Description%
[osrusbfx2.AddService]
DisplayName = %osrusbfx2.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\osrusbfx2.sys
AddReg = osrusbfx2.AddReg
LoadOrderGroup = Base
[osrusbfx2.Files.Ext]
osrusbfx2.sys
[osrusbfx2.AddReg.Guid]
HKR,DriverGUID,%osrusbfx2.GUID%
;HKR,DriverPowerPolicySetup,%ENABLE_DRIVER_POWER_POLICY%
[SourceDisksNames]
1=%Disk_Description%,
[SourceDisksFiles]
osrusbfx2.sys = 1
[DestinationDirs]
DefaultDestDir = 12
;-------------- WDF Coinstaller installation
[DestinationDirs]
CoInstaller_CopyFiles = 11
[osrusbfx2.Dev.NT.CoInstallers]
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles
[CoInstaller_CopyFiles]
WdfCoInstaller01011.dll
[SourceDisksFiles]
WdfCoInstaller01011.dll=1 ; make sure the number matches with SourceDisksNames
[CoInstaller_AddReg]
HKR,CoInstallers32,0x00010000, “WdfCoInstaller01011.dll,WdfCoInstaller”
[osrusbfx2.Dev.NT.Wdf]
KmdfService = osrusbfx2, osrusbfx2_wdfsect
[osrusbfx2_wdfsect]
KmdfLibraryVersion = 1.11
;---------------------------------------------------------------;
[Strings]
MSFT=“Microsoft”
MfgName=“OSR”
Disk_Description=“OSRUSBFX2 Installation Disk”
USB\VID_04b4&PID_1003.DeviceDesc=“WDF Sample Driver for OSR USB-FX2 Learning Kit”
osrusbfx2.SvcDesc=“WDF Sample Driver for OSR USB-FX2 Learning Kit”
ClassName = “Sample Device”
Switch.DeviceDesc = “OsrUsbFX2 RawPdo For Switch”
SPSVCINST_ASSOCSERVICE= 0x00000002
VID_04B4&PID_1003.DeviceDesc=“Commtech USB to Serial Device”
osrusbfx2.GUID=“{AE18AA60-7F6A-11d4-97DD-00010229B959}”
xxxxx@gmail.com wrote:
Hi Tim, below is the inf file, the computer I am using is 64bit with Intel(R) Core i7 CPU, Win 7
[Version]
Signature=“$WINDOWS NT$”
Class=USB
ClassGuid={36FC9E60-C465-11CF-8056-444553540000}
Provider=%MSFT%
DriverVer=06/24/2015,16.46.33.708
CatalogFile=KmdfSamples.cat
You will want to provide your own CAT file at some point.
; ================= Device section =====================
[Manufacturer]
%MfgName%=Microsoft,NT,NTx86,NTamd64; For Win2K
[Microsoft.NT]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo[Microsoft.NTx86]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo[Microsoft.NTamd64]
%VID_04B4&PID_1003.DeviceDesc%=CyUsb3, USB\VID_04b4&PID_1003
%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
You do not have any sections based on the name [CyUsb3]. That’s why it
failed. The sections in this file are called “osrusbfx2”. The name you
provide in those lines becomes the base for the main action sections.
It will look for [CyUsb3.NT] or [CyUsb3.NT.x86] or [CyUsb3.NTamd64],
plus [CyUsb3.Dev.NT] etc, plus [CyUsb3.NT.Services], etc.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I really appreciate your assistance. I made some change in the inf file and the error was there is gone.
But now I got a new error: "Windows found driver software for your device but encountered an error while attempting to install it. "
And it says: “Driver is not intended for this platform”
Below is the inf file after change:
;/*++
;
;Copyright (c) Microsoft Corporation. All rights reserved.
;
; THIS CODE AND INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY
; KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
; IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR
; PURPOSE.
;
;Module Name:
;
; OSRUSBFX2.INF
;
;Abstract:
; Installation inf for OSR USB-FX2 Learning Kit
;
;–*/
[Version]
Signature=“$WINDOWS NT$”
Class=USB
ClassGuid={36FC9E60-C465-11CF-8056-444553540000}
Provider=%MSFT%
DriverVer=06/26/2015,15.18.28.401
CatalogFile=KmdfSamples.cat
[SourceDisksNames]
1=%OSRUSBFX2_Install%,
[SourceDisksFiles]
OSRUSBFX2.sys = 1
; ================= Class section =====================
[ClassInstall32]
Addreg=SampleClassReg
[SampleClassReg]
HKR,0,%ClassName%
HKR,Icon,-5
[DestinationDirs]
OSRUSBFX2.Files.Ext = 10,System32\Drivers
[ControlFlags]
ExcludeFromSelect = *
; ================= Device section =====================
[Manufacturer]
%MfgName%=Microsoft,NT,NTx86,NTamd64
; For Win2K
[Microsoft.NT]
%VID_04B4&PID_1003.DeviceDesc%=osrusbfx2, USB\VID_04b4&PID_1003
;%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[Microsoft.NTx86]
%VID_04B4&PID_1003.DeviceDesc%=osrusbfx2, USB\VID_04b4&PID_1003
;%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[Microsoft.NTamd64]
%VID_04B4&PID_1003.DeviceDesc%=osrusbfx2, USB\VID_04b4&PID_1003
;%Switch.DeviceDesc%=Switch.Dev, {AE18AA60-7F6A-11d4-97DD-00010229B959}\OsrUsbFxRawPdo
[osrusbfx2.NT]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NT.HW]
AddReg=osrusbfx2.AddReg.Guid
[Switch.Dev.NT.Services]
AddService = , %SPSVCINST_ASSOCSERVICE%,
[osrusbfx2.NT.Services]
AddService = osrusbfx2, %SPSVCINST_ASSOCSERVICE%, osrusbfx2.AddService
[osrusbfx2.NTx86]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NTx86.HW]
AddReg=osrusbfx2.AddReg.Guid
[osrusbfx2.NTx86.Services]
Addservice = osrusbfx2,2,osrusbfx2.AddService
[osrusbfx2.NTamd64]
CopyFiles=osrusbfx2.Files.Ext
AddReg=osrusbfx2.AddReg
[osrusbfx2.NTamd64.HW]
AddReg=osrusbfx2.AddReg.Guid
[osrusbfx2.NTamd64.Services]
Addservice = osrusbfx2,2,osrusbfx2.AddService
[osrusbfx2.AddReg]
; Deprecating - do not use in new apps to identify a osrusbfx2 driver
HKR,DevLoader,*ntkern
HKR,NTMPDriver,osrusbfx2.sys
; You may optionally include a check for DriverBase in your application to check for a osrusbfx2 driver
HKR,DriverBase,osrusbfx2.sys
HKR,“Parameters”,“MaximumTransferSize”,0x10001,4096
HKR,“Parameters”,“DebugLevel”,0x10001,2
HKR,FriendlyName,%osrusbfx2_Description%
[osrusbfx2.AddService]
DisplayName = %osrusbfx2.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\osrusbfx2.sys
AddReg = osrusbfx2.AddReg
LoadOrderGroup = Base
[osrusbfx2.Files.Ext]
osrusbfx2.sys
[osrusbfx2.AddReg.Guid]
HKR,DriverGUID,%osrusbfx2.GUID%
;HKR,DriverPowerPolicySetup,%ENABLE_DRIVER_POWER_POLICY%
[SourceDisksNames]
1=%Disk_Description%,
[SourceDisksFiles]
osrusbfx2.sys = 1
[DestinationDirs]
DefaultDestDir = 12
;-------------- WDF Coinstaller installation
[DestinationDirs]
CoInstaller_CopyFiles = 11
[OSRUSBFX2.NTamd64.CoInstallers]
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles
[CYUSB3.NTx86.CoInstallers]
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles
[CoInstaller_CopyFiles]
WdfCoInstaller01011.dll
[SourceDisksFiles]
WdfCoInstaller01011.dll=1 ; make sure the number matches with SourceDisksNames
[CoInstaller_AddReg]
HKR,CoInstallers32,0x00010000, “WdfCoInstaller01011.dll,WdfCoInstaller”
[OSRUSBFX2.NTamd64.Wdf]
KmdfService = OSRUSBFX2, OSRUSBFX2_wdfsect
[OSRUSBFX2.NTx86.Wdf]
KmdfService = OSRUSBFX2, OSRUSBFX2_wdfsect
[osrusbfx2_wdfsect]
KmdfLibraryVersion = 1.11
;---------------------------------------------------------------;
[Strings]
MSFT=“Microsoft”
MfgName=“OSR”
Disk_Description=“OSRUSBFX2 Installation Disk”
OSRUSBFX2_Install = “Commtech USB Driver Installation Disk”
USB\VID_04b4&PID_1003.DeviceDesc=“WDF Sample Driver for OSR USB-FX2 Learning Kit”
osrusbfx2.SvcDesc=“WDF Sample Driver for OSR USB-FX2 Learning Kit”
ClassName = “Sample Device”
Switch.DeviceDesc = “OsrUsbFX2 RawPdo For Switch”
SPSVCINST_ASSOCSERVICE= 0x00000002
VID_04B4&PID_1003.DeviceDesc=“Commtech USB to Serial Device”
osrusbfx2.GUID=“{AE18AA60-7F6A-11d4-97DD-00010229B959}”
There is an explicit path dependence on how we achieve the ?inter-connectedness? between the various elements of our strategy to gain momentum.
On Jun 26, 2015, at 1:29 PM, xxxxx@gmail.com wrote:
I really appreciate your assistance. I made some change in the inf file and the error was there is gone.
But now I got a new error: "Windows found driver software for your device but encountered an error while attempting to install it. "
And it says: "Driver is not intended for this platform”
That seems fairly obvious, doesn’t it? You have to build a 32-bit driver for 32-bit systems, and a 64-bit driver for 64-bit systems. My guess is that you didn’t do that. You have to decide whether you want to have one single driver package for both systems, or separate driver packages. If you want one single driver package, then you will need to have both drivers in the package, and that means you have to use separate directories. If you want separate driver packages, then you need to remove the “NTx86” section from one of them, and remove the “NTamd64” section from the other.
—
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.