The current Windows 10 IoT core (V 10.0.10240, Sept 2015) claims not to have tested the Raspberry Pi 2B on-board UART (physical P1 pins 8=tx, 10=rx) for serial io. Here is the list of officially supported I/O: https://ms-iot.github.io/content/en-US/win10/SupportedInterfaces.htm
Has anybody gotten this on-board UART Serial IO to work with Windows 10 IoT? Tips?
The October insider release has the onboard serial enabled. I have modified the serial example and have had mixed results so far. One issue that it has seems to be that if data is being sent to the pi while the port is being initialized, it throws an exception. Trying to work around it for now.
Related
My Setup:
Windows 10 VM running in VirtualBox on Windows 7 Pro
Raspberry Pi 3 running Windows 10 IoT Core - 10.0.16299.19
The VM can see the RaspberryPi/Wionows IoT
I know this because:
On the VMI I can Install and Debug from Visual Studio 2017 to the Pi.
On the VM the IoT Dashboard detects the PI and allows me to change
settings
On the VM I can access the Pi's Device Portal
On the VM I can use Powershell to log in to the Pi.
What I can't do is use Windows IoT Remote Client. Which I want so I can see changes produced by my code.
When I start the client I get the spinning buffer animation followed by a blank, white screen.
I have tried the following as recommended in web articles:
Reset the Pi resolution to 800x600 - This killed the Pi's ability to
display at all; including on the attached HDMI.
Checked Enable Windows IoT Remote Server in Device Portal. - This is
set to On
Disconnected the HDMI from the Pi - Made no difference.
Typed the following into an Admin level PowerShell:
net start WinRM
Set-Item WSMan:\localhost\Client\TrustedHosts -Value
PiName
This allowed Powershell access but no change to Remote Desktop
What should I try next?
On version 16299,the Windows IoT Remote client does not work for Raspberry Pi. Please reference the know issue of release notes for Windows 10 IoT 16299.Currently you can attach a monitor for local display.
Try starting the NanoRDP server manually (not through the web interface) and see if that helps. That has solved a few issues for me.
I believe the executable is in c:\windows\ and is called nanordpserver.exe. just SSH or Powershell into the device, run nanordpserver.exe and try again.
The lightweight RDP protocol that IoT Core uses is not as robust as the version installed on the full Windows 10 OS.
We have several Sun 100 Blades in our Software lab that are currently running Solaris 8. Since the lifetime of Solaris 8 is running out in November, we are moving to Solaris 10. These are SPARC stations. Here is the problem.
These systems are old and only contain a CD R/W and not a DVD R/W. You can download Solaris 10 SPARC ISO for DVD. I've searched the net on how to divide the DVD into CD's with no luck. Plus, you can no longer get Solaris 10 on CD's. We've discussed purchasing DVD drives and replacing the CD drives, but the time to get them on dock does not meet our schedule.
I've found how to load/mount an ISO file onto a Solaris OS but when I reboot (from both reboot command and init 6) the mount goes away. I've also found how to use one system to do a new install with the ISO. But, I've been given permission to experiment with one station only.
Here is the question:
Is there anyway to use the ISO mounted then upgrade the Solaris 8 to 10?
Thanks
Used an x86 Solaris VM running on RHEL and did a network install.
I have recently installed a xamarin android player for developing android application but after the complete installation when i open a xamarin android player it will throw a following error...
****xamarin android player failed to initialize device vboxmanag****
Can anyone help me or tell me what can I do.
I am running Windows 10 Pro and use Oracle VBox v.5.0.4.
if your case same with me : first, you need to uninstall the current version of Oracle VBox then install the new version that already support Windows 10. i use v. 5.1. You can download it here
then, just try to re-launch the emulator.
I found some info by Googling around that may help starting a device in the Android Player. I have Vers 0.6.5 of the player.
Open VirtualBox directly as suggested by Cook Data. You will get the REAL error message which may related to vt-ix....
Make sure that the the bios has enabled the virtual technology aka vt-ix. Just do a reboot and you should find it in he bios setup - maybe under advanced. AMD and INTEL have slightly different names for it.
Reduce the system memory for the device you wish to start to 1024 Mb if it is currently 2048 Mb
I also got a warning about video memory which I increased to 10Mb from 8Mb
My setup runs over Hyper-V which has its own foibles so YMMV and I only started on this stuff today...
For Windows 10 users
(After Bios Virtualization enabled)
Use VirtualBox 5.1.14
https://www.virtualbox.org/wiki/Downloads
After setting up Windows 10 IoT Core on Raspberry Pi 2 and getting all comfortable with it, along comes Visual Studio 2015 with the message: "Please upgrade your remote debugger to match Visual Studio." which apparently means repeating the entire installation (flash from scratch) as described here http://ms-iot.github.io/content/en-US/win10/SetupRPI.htm
Is a "reinstall from scratch" the only way to currently update the Windows 10 IoT Core ? What about something like apt-get update?
With the release of Windows 10 IoT Core build 10586, you can update Windows IoT over the Internet just like we do in Windows.
To update Windows IoT, follow the steps:
Connect your Raspberry Pi 2's Ethernet to the Internet (i.e. with Internet Router or Modem).
Connect your computer/tablet to the same network on which Raspberry Pi 2 is connected.
Open Windows IoT's Web-management portal.
Login to the Web-management portal.
From the left black-panel 'UTILITIES', click 'Windows Update'.
Finally, to update Windows 10 IoT Core, click on 'Check for updates' button and wait for the magic.
Newer to web management portal?
Please refer "Web-Management Portal" section of this ProTip article: https://www.hackster.io/AnuragVasanwala/windows-10-iot-core-setting-startup-app-887ed0
When I make a call to get network interfaces' name using winpcap I get all devices name but I am not getting ppp device(my 3g usb stick).
How can I capture packets coming from this device?
I am working on windows vista.
Unfortunately, as indicated by question 5 in the WinPcap FAQ, that's not supported on Windows Vista or Windows 7.