Answered by:
NXP OM5577 NFC board driver broken on 10586

Question
-
Hi there,
I'm trying to use the NXP OM5577 NFC demo board for RaspberryPi.
Board is supposed to be tested as per https://ms-iot.github.io/content/en-US/win10/SupportedInterfaces.htm#NFCI had it recognized by the provided driver with the RTM build but it fails to load the driver on 10586.
This is what I get by installing the driver as documented:
ID : ACPI\PN7120\2&DABA3FF&0
StatusCode : 25175040
ProblemCode : 28Anyone knows how to get it working?
Thank you.
Edoardo.
Thursday, December 3, 2015 9:59 PM
Answers
-
Hi Edoardo, there was a regression in the OS that prevents devcon.exe from installing the driver on 10586. We're working to fix it in a future release, in the meantime though below is a modified INF that will work-around the problem. Just copy+paste it using Notepad to replace your existing NXPPN7120.INF file and follow all the instructions as normal:
;/*++ ; ; Copyright (c) Microsoft Corporation. All rights reserved. ; ; Module Name: ; NXPPN7120.inf ; ; Abstract: ; INF file for installing NXP's NCI based NFC controller ; ;--*/ [Version] Signature="$Windows NT$" Class=Proximity ClassGuid={5630831C-06C9-4856-B327-F5D32586E060} Provider=%ManufacturerName% DriverVer=06/21/2006,10.0.10572.1000 [Manufacturer] %ManufacturerName%=Standard,NTarm [Standard.NTarm] %DeviceName%=MyDevice_Install, ACPI\PN7120 [SourceDisksNames] 1=%DiskName% [SourceDisksFiles] ; =================== UMDF Device ================================== [DefaultInstall] [MyDevice_Install.NT] [MyDevice_Install.NT.hw] [MyDevice_Install.NT.Services] AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall [MyDevice_Install.NT.CoInstallers] AddReg=CoInstallers_AddReg [MyDevice_Install.NT.Wdf] UmdfService=NxpNfcPn7120ClientDriver,NxpNfcPn7120ClientDriver_Install UmdfServiceOrder=NxpNfcPn7120ClientDriver UmdfDirectHardwareAccess=AllowDirectHardwareAccess UmdfFileObjectPolicy=AllowNullAndUnknownFileObjects UmdfImpersonationLevel=Impersonation [NxpNfcPn7120ClientDriver_Install] UmdfLibraryVersion=2.0.0 ServiceBinary=%12%\UMDF\MSNfcI2C547.dll UmdfExtensions=NfcCx0102 [WUDFRD_ServiceInstall] DisplayName=%WudfRdDisplayName% ServiceType=1 StartType=3 ErrorControl=1 ServiceBinary=%12%\WUDFRd.sys [CoInstallers_AddReg] HKR,,CoInstallers32,0x00010000,"WUDFCoinstaller.dll" [DestinationDirs] [ControlFlags] ExcludeFromSelect=* ; =================== Generic ================================== [Strings] ManufacturerName="NXP Semiconductors" DiskName="NxpNfcPn7120ClientDriver Installation Disk" WudfRdDisplayName="Windows Driver Foundation - User-mode Driver Framework Reflector" DeviceName="NxpNfcPn7120ClientDriver Device"
- Edited by Alex McKelvey Wednesday, January 6, 2016 10:56 PM
- Proposed as answer by Alex McKelvey Wednesday, January 6, 2016 10:56 PM
- Marked as answer by IoTGirlMicrosoft employee Wednesday, January 6, 2016 11:37 PM
Wednesday, January 6, 2016 10:55 PM
All replies
-
Try with the newly released (not the earlier leaked version) 10586 RTM.
https://ms-iot.github.io/content/en-US/Downloads.htm
riclh
Friday, December 4, 2015 1:19 AM -
Hi there.
I have the same problem.
Original Image from NXP works with 10240.
But i need WinIot 10586 to get my TP-Link WN725N running.
I Installed the mentioned 10586 RTM.
7120 Device not running.
Anyone got it running ?
mfg
Smithsonian 1974
Thursday, December 17, 2015 2:14 PM -
Hi Edoardo, there was a regression in the OS that prevents devcon.exe from installing the driver on 10586. We're working to fix it in a future release, in the meantime though below is a modified INF that will work-around the problem. Just copy+paste it using Notepad to replace your existing NXPPN7120.INF file and follow all the instructions as normal:
;/*++ ; ; Copyright (c) Microsoft Corporation. All rights reserved. ; ; Module Name: ; NXPPN7120.inf ; ; Abstract: ; INF file for installing NXP's NCI based NFC controller ; ;--*/ [Version] Signature="$Windows NT$" Class=Proximity ClassGuid={5630831C-06C9-4856-B327-F5D32586E060} Provider=%ManufacturerName% DriverVer=06/21/2006,10.0.10572.1000 [Manufacturer] %ManufacturerName%=Standard,NTarm [Standard.NTarm] %DeviceName%=MyDevice_Install, ACPI\PN7120 [SourceDisksNames] 1=%DiskName% [SourceDisksFiles] ; =================== UMDF Device ================================== [DefaultInstall] [MyDevice_Install.NT] [MyDevice_Install.NT.hw] [MyDevice_Install.NT.Services] AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall [MyDevice_Install.NT.CoInstallers] AddReg=CoInstallers_AddReg [MyDevice_Install.NT.Wdf] UmdfService=NxpNfcPn7120ClientDriver,NxpNfcPn7120ClientDriver_Install UmdfServiceOrder=NxpNfcPn7120ClientDriver UmdfDirectHardwareAccess=AllowDirectHardwareAccess UmdfFileObjectPolicy=AllowNullAndUnknownFileObjects UmdfImpersonationLevel=Impersonation [NxpNfcPn7120ClientDriver_Install] UmdfLibraryVersion=2.0.0 ServiceBinary=%12%\UMDF\MSNfcI2C547.dll UmdfExtensions=NfcCx0102 [WUDFRD_ServiceInstall] DisplayName=%WudfRdDisplayName% ServiceType=1 StartType=3 ErrorControl=1 ServiceBinary=%12%\WUDFRd.sys [CoInstallers_AddReg] HKR,,CoInstallers32,0x00010000,"WUDFCoinstaller.dll" [DestinationDirs] [ControlFlags] ExcludeFromSelect=* ; =================== Generic ================================== [Strings] ManufacturerName="NXP Semiconductors" DiskName="NxpNfcPn7120ClientDriver Installation Disk" WudfRdDisplayName="Windows Driver Foundation - User-mode Driver Framework Reflector" DeviceName="NxpNfcPn7120ClientDriver Device"
- Edited by Alex McKelvey Wednesday, January 6, 2016 10:56 PM
- Proposed as answer by Alex McKelvey Wednesday, January 6, 2016 10:56 PM
- Marked as answer by IoTGirlMicrosoft employee Wednesday, January 6, 2016 11:37 PM
Wednesday, January 6, 2016 10:55 PM -
Great Job.
Now its working.
Thanx for help
Greets
Frank Schmidt
Monday, January 18, 2016 3:37 PM -
This Solution also helped me out, an my Raspberry Pi 2, So thanks,
but a bit of warning on the Raspberry Pi 3 with build 10.0.14279.1000
installing the driver causes an inaccessible boot device !!
Hence I needed to do an re-Flash of the MicroSD.
Meanwhile back on RPi2, I did not test new build on RPi2
Greetings Marc
Tuesday, March 15, 2016 10:52 PM -
RPi2 with build 10.0.14279.1000 gives error
StatusCode : 25175040
ProblemCode : 28Anyone got a fix for build 10.0.14279.1000?
Tuesday, April 5, 2016 8:13 AM -
Yes, I had the revised inf in this post working on 10586 but doing the same actions on 14393 results in a failure to find the proximity device.
The official NXP OM5577 drivers and instructions are still not functional and I was hoping this fix would still work.
I bought this device because it is specifically listed on the compatibility list:
https://developer.microsoft.com/en-us/windows/iot/docs/hardwarecompatlist#NFCIs there any progress on getting this proximity device actually working on Windows 10 IoT Core?
- Edited by Steven Hook Thursday, September 29, 2016 3:58 PM
Thursday, September 29, 2016 3:57 PM -
Yes, I had the revised inf in this post working on 10586 but doing the same actions on 14393 results in a failure to find the proximity device.
The official NXP OM5577 drivers and instructions are still not functional and I was hoping this fix would still work.
I bought this device because it is specifically listed on the compatibility list:
https://developer.microsoft.com/en-us/windows/iot/docs/hardwarecompatlist#NFCIs there any progress on getting this proximity device actually working on Windows 10 IoT Core?
We also purchased the OM5577 based on the hardware compatibility list for the Raspberry Pi 3 and require this to be actually supported. Projects are paused until resolved.Friday, October 28, 2016 5:27 AM