I got the reply from the expert:
Indeed new builds from MSFT (especially Insider preview ones) sometimes induded change in the ACPI table. With non backward compatibility with previous ones. Since SW3497 package contains ACPI table related to a dedicated build (created at that time), it may not be valid for further MSFT builds.
The best approach is to follow instructions of AN11767, extracting ACPI table from the Raspberry Pi target (running the aimed winIoT build), then to add the PN71xx support before regenerating and install it. Here is the detailled procedure:
- copy asl.exe (ARM version can be downloaded from here) to the target memory, for instance using remote access to RPI via file browser.
- open a PowerShell remote session with the target
- extract ACPI table, using command ./asl.exe /tab=dsdt /resdecode from where asl.exe file has been copied, this generates DSDT.ASL file
- edit the DSDT.ASL file to add the PN71xx support, inserting the dedicated lines in the list of Devices declaration (see here).
- generate modified ACPI table, using command ./asl.ex DSDT.ASL, this will create new DSDT.AML file
- rename DSDT.AML file into acpitabl.dat and copy it to c:\Windows\System32
- reboot, the PN71xx Device should appear in the device manager (can be seen through the Device webportal, in Devices, under category "ACPI ARM-based PC"/"Microsoft ACPI-Compliant System",referenced as "ACPI\PN71X0\..." (until driver has been installed , the device should be in StatusCode 25175040 and ProblemCode 28)
For reference, find here a zip file related to the Windows Insider build 14376, containing the DSDT.ASL file modified with PN71xx support as well as related compiled acpitabl.dat.
Then proceed with driver installation using inf file provided as part of the SW3497 package.
