Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


ufx01000.sys failure on start, IOCTL fails

matt_sykesmatt_sykes Member - All Emails Posts: 290
Starting the OTG device in windows 10 IoT enterprise I get this wpp trace:

00000017 ufx01000 4 1124 0 17 01\27\2017-10:04:43:795 CAD device is not available. CADContext:0xFFFFAD876FABFE00, UfxDevice:0x0000527893D49958[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000018 ufx01000 4 1124 0 18 01\27\2017-10:04:43:795 Failed to notify power source update to CAD[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000019 ufx01000 4 1124 0 19 01\27\2017-10:04:43:796 CAD device is not available. CADContext:0xFFFFAD876FABFE00, UfxDevice:0x0000527893D49958[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000020 ufx01000 4 1124 0 20 01\27\2017-10:04:43:796 Failed to notify power source update to CAD[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000021 ufx01000 4 264 0 21 01\27\2017-10:04:48:670 Failed to send 0x32C004 synchronously to IoTarget:0x0000527892116608[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000022 ufx01000 4 264 0 22 01\27\2017-10:04:48:670 Failed to send synchronous ACPI evaluation method request[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000023 ufx01000 4 264 0 23 01\27\2017-10:04:48:671 Failed to open settings reg key [0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000024 ufx01000 4 264 0 24 01\27\2017-10:04:48:672 Failed to send 0x32C004 synchronously to IoTarget:0x0000527892116608[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000025 ufx01000 4 264 0 25 01\27\2017-10:04:48:672 Failed to send synchronous ACPI evaluation method request[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000026 ufx01000 4 264 0 26 01\27\2017-10:04:48:672 Failed to invoke endpoint ACPI. [0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000027 ufx01000 4 260 2 27 01\27\2017-10:04:48:713 Failed to send 0x32C004 synchronously to IoTarget:0x0000527892116608[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000028 ufx01000 4 260 2 28 01\27\2017-10:04:48:713 Failed to send synchronous ACPI evaluation method request[0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND)]
00000029 ufx01000 4 260 2 29 01\27\2017-10:04:48:716 CAD device is not available. CADContext:0xFFFFAD876F699C20, UfxDevice:0x0000527893A8EF38[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000030 ufx01000 4 260 2 30 01\27\2017-10:04:48:716 Failed to notify power source update to CAD[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000031 ufx01000 4 244 3 31 01\27\2017-10:04:53:717 CAD device is not available. CADContext:0xFFFFAD876F699C20, UfxDevice:0x0000527893A8EF38[0xc0000184(STATUS_INVALID_DEVICE_STATE)]
00000032 ufx01000 4 244 3 32 01\27\2017-10:04:53:717 Failed to notify power source update to CAD[0xc0000184(STATUS_INVALID_DEVICE_STATE)]



The ufxsynopsys.sys driver does however report, in device manager, two events, DeviceConfigured and DeviceStarted.

My driver sucessfully gets a pointer to \Device\UfxCx0 (the device name ufx01000 passed when it created its device) however the call to IOCTL_INTERNAL_USBFN_ACTIVATE_USB_BUS failes with 0xc0000010

This is, so far as I can glean, the very first call a client driver of the ufx service must make.



Regarding the hardware, the ID pin is floating, ie, not grounded, so it is in OTG mode and when connected to another PC host will stay floating (only OTG to OTG wil negotiate the bus and force one end to ground the ID pin).


So all in all it looks as if the Ufx drivers arent funtional.

We saw the same thing with the SPI device, it too isnt functional, according to our contacts this is because the technology is new, it was pulled into Enterprise from the Core (ARM based windows IoT) OS and just hasnt been fully implemented yet.

So, quesiton to Microsoft, is this also the case with OTG?


Thanks for any clarification on this.

Comments

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA