No, it won't be able to run Raspberry Pi's OS.
Remember if these are unsigned drivers, windows security kernel will prevent the installation. Only signed drivers are typically installed without problems. If installing unsigned drivers (you can have this problem with Beaglebone boards on Windows 10 also), there are three ways to do the install (command line admin level cntrl/shift/enter, bcdedit /set testsigning on, install drivers, /set testsigning off etc.)
see https://www.maketecheasier.com/install-unsigned-drivers-windows10/ for all three ways to install unsigned drivers.
Maybe it was off-topic for this area, however I solved, first upgrading to BIOS 15 then following this post: (https://forum.up-community.org/discussion/717/installation-of-win10-64-step-1-drivers-fails). The key is to remove spaces of the folder name.
@beaker The source code isn't currently published on a public git repository, but it can be obtained in a number of ways:
On a board with the kernel installed, run the following command:sudo apt-get source linux-hwe
(You might need to uncomment the relevant deb-src entry in /etc/apt/... and run sudo apt update first)
sudo apt-get source linux-hwe
sudo apt update first
Or download the source package directly from the PPA here:https://launchpad.net/~aaeonaeu/+archive/ubuntu/upboard/+sourcefiles/linux-hwe-edge/5.0.0-1.2~upboard4/linux-hwe-edge_5.0.0-1.2~upboard4.tar.gz
Yes that is correct, the BIOS is the same for all boards, but on Celeron and i3 variants Intel AMT is not supported.
We will update the information accordingly and also check how we can make it more clear in our BIOS.
please refer this link https://docs.microsoft.com/zh-tw/windows-hardware/drivers/partnerapps/wi-fi-direct ,
SoftAP is not supported in windows except windows7, you can download and refer WiFiDirectLegacyAPDemo source code in the link.
Up IoT Core driver has supported WiFi Direct APIs, it's no problem to support hotspot.
You appear to be accessing the wrong I2C controller for some reason. That error message shows "808622C1:04" but the correct I2C controller connected to pins 2-3 is "808622C1:01"
In addition to the information requested by DCleri above, can you also post the output of the following 2 commands:
cat /sys/bus/acpi/devices/808622C1:01/status # should be 15, if BIOS settings are ok
ls /sys/devices/pci0000:00/808622C1:01/ # this will give you the correct Linux I2C bus number to use, if the path exists
Please use the following command when scanning the I2C bus on an UP board:sudo i2cdetect -r -y 5 # Replace 5 with the correct Linux I2C bus number if different - see previous command above
sudo i2cdetect -r -y 5 # Replace 5 with the correct Linux I2C bus number if different - see previous command above
What kind of antenna did you connect?
You should use an active antenna.
I would suggest to go with an UP Squared with AI Core which you can use for the detection.
You also have plenty of digital I/O to use.
This is the board: https://up-board.org/upsquared/specifications/
This is the AI accelerator: https://up-board.org/ai-edge/ai-core/
And you can buy from the UP-shop:https://up-shop.org/home/270-up-squared.htmlhttps://up-shop.org/featured/204-up-ai-core.html
Soon the AI Core X will also be available, which embeds the new generation Myriad X VPU.
Yes that version is fine to update with latest BIOS.