Replies: 2 comments 2 replies
-
Can you reattach as plain text, or just dump in a comment here? I'll ping our devices folks and see what they say. |
Beta Was this translation helpful? Give feedback.
-
Actually Windows.Devices.GPIO/I2C/SPI has been working on Desktop for quite a while, that's what we use in the Windows on Raspberry Pi project.
The issue is it requires a table from system firmware, specifically a definition of RHProxy device in ACPI table, describing all the GPIO pins and I2C/SPI/UART controllers on the device. And this kind of description does not work very well on something like USB GPIO dongle or something. https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/enable-usermode-access |
Beta Was this translation helpful? Give feedback.
-
Will ProjectReunion help me use GPIO, I2C, SPI "low level" devices on Windows 10 that were available on Windows IoT?
The ability that would like to have is to add GPIO, I2C, SPI devices on a standard Windows 10 laptop/PC. Think about being able to take button input (via events) or add a sensor to be used with an app.
The folks at maintaining
System.Devices.Gpio
(.NET IoT) pointed me towards buying a FT4222 dev board (UMFT4222EV is what I got), and was able to get it to work on a .NET 5 sample app and encouraged by that. I currently develop UWP apps but hit some roadblocks unable to referenceIot.Device.Bindings
and getting it to work.Will ProjectReunion allow my UWP get this capability with .NET 5/6, maintain the same look/feel AND be able to distribute via the Store?
Attached chat log with .NET IoT folks: Chat.docx
Beta Was this translation helpful? Give feedback.
All reactions