WIN10 / Unable to run Dio sample

Hi All,
I'm currently working on a prototype based on an Up Board with Windows 10. I need to use some GPIO to drive peripheral devices and sensors.
After installing all the WIN10_64 drivers, I tried to run the Dio sample provided with SDK but without success. I receive a popup saying "It Cannot Open Library!".
Then, I tried to invoke AaeonIo.dll from a very simple C# app. A call to aaeonioOpen returns a zero handle.
A few unknown devices are visible in the Device manager but I see somewhere on the forum that it's not an issue to access GPIO.
Is this a driver issue ? Or a setting I missed somewhere ?
Thanks for your help.
Johann
I'm currently working on a prototype based on an Up Board with Windows 10. I need to use some GPIO to drive peripheral devices and sensors.
After installing all the WIN10_64 drivers, I tried to run the Dio sample provided with SDK but without success. I receive a popup saying "It Cannot Open Library!".
Then, I tried to invoke AaeonIo.dll from a very simple C# app. A call to aaeonioOpen returns a zero handle.
A few unknown devices are visible in the Device manager but I see somewhere on the forum that it's not an issue to access GPIO.
Is this a driver issue ? Or a setting I missed somewhere ?
Thanks for your help.
Johann
Comments
Same result from a C# app invoking AaeonIo.dll.
Does anyone successfully use gpio from a windows app?
As I'm experimented with Raspberry, I played with our up board this week end and installed ubilinux. Without success, the gpio does not seem accessible (tested with RPi.GPIO, MRAA and through /sys/class/gpio).
I did not see any option in the bios to enable or set the gpio.
Could this be a hardware issue ? Do you have any tip/tool to check gpio availability, either on Windows or ubilinux ?
I have to quickly validate this device for the next step of our project, thank you for your help.
Johann
+5V, +3.3V and GND pins are where they are supposed to be.
1. Select "Mode" to "Output"
2. Select "Value" to "Low"
3. Press "Set" button. (A little bit slow...please wait a moment)
4. The value LED should change, and your pin 3 voltage out will become 0
The status change is visible in Hi-Safe (and in sample apps) but nothing happens at the pin level.
I just did the test, whatever the mode (input/output) and value (high, low) set in Hi-Safe, the pin is always at 3.3V.
The same applies to all accessible dio in Hi-Safe.
So I wonder on Windows, if you tried to run the GUI app as Administrator, does it behave any different? At least that is what I would try next...
This is not the best topic for this, but under ubilinux, I get the following results:
- an invalid argument error when I try to "echo 2 > export" in /sys/class/gpio
- a channel already in use when I try to set a gpio with Python
I never encountered this kind of issue with RPi, could this be a sign of a defective device ?
Most of my discussion on this is in the thread: https://up-community.org/forum/general-discussion/876-mraa-and-the-up-board and I believe there was another thread talking about Ubuntu 16.04...
but again with Ubuntu, the echo fails unless you are running as Super user.
sudo echo did not work.
But sudo sh
then under the sh command the echo commands worked.
But again this is Ubuntu... your millage may differ on ubilinux.
If you can't have a success to control GPIO under Windows nor Linux, this should not be a software setting problem.
We assume this could be a single issue on the board itself, and we would be happy to provide RMA.
Please go to your “order details & history “in the UP shop, and our staff will guide you from there.