The serial pins on the Raspberry PI now have a driver in Windows 10 IoT Core on RPI2!
Read the rest of entry »
Publ2shed on Codeplex and GitHub. More details later:Win10 IoT Core Universal Windows App runs on a Raspberry PI 2 (& desktop) that reads some sensors (on an Arduino board) saves to and from Azure Mobile Service
Development environment and tools for Windows Embedded CE 6.0, Windows Embedded Compact 7 and 2013.
In a previous blog I covered the use of the FTDI D2XX driver on a Windows 10 IoT Core Raspberry PI 2. An issue arose with respect to Startup Tasks. Microsoft have looked into the issue.
There are currently 2 reserved GPIO pins on the RPI2 that ordinarily are SOC (I call native) serial. A future Tx and Rx but not at the moment. Serial is achieved on the RPI2 with Win 10 IoT Core via a USB-Serial device connected to a Host USB port on the RPI2. There are though limitations in that the widely used FTDI chipset is not supported by Microsoft, although we have a solution. An alternative is over Bluetooth but there is an issue there.
In a previous blog I covered the use of the FTDI D2XX driver on a Windows 10 IoT Core Raspberry PI 2. This covered a missing plank from the Win10RPI2 armour that was much called for. It facilitates the use of USB-Serial devices based upon the FTDI chipset of which there are many. Jark took an idea I had to use the FTDI ARM Windows RT D2XX driver for the RT Surface 1 & 2 and created a comprehensive Universal Windows App that used the driver. His GitHub project contains complete instructions to install the driver on a RPI2. This project is though an App. What about a using it in a Startup Task on a headless RPI2? A blocking issue has arisen.
A new version of Windows 10 IoT is available on Windows Dev Center. Version 5.x of SysInfo is now available on GitHub that addresses the OS changes in the web portal. This version has two versions of the commands in the JSON file. One for the new OS and one for the RTM version. Version 5.0 Adds [Rename Device] and [Set Admin Password]. There are also some coding corrections for the generic [api] command.
Version 4.x of SysInfo is now available on GitHub. T)his version has much improved JSON processing and includes additional commands Startapp, StopApp, Shutdown and Reboot. A customisable JSON file is used to list the app commands and their relative URLs.Update Version 4.5 has “Uninstall Package” command.
I am using Visual Studio 2015 to create my Windows Universal
Application and when I build and deploy it, I can’t find it listed on device or
it is listed but with a GUID instead of the human readable name that I carefully
gave it. How can I fix this?
How can I see this problem?
The picture below shows the web access to a Raspberry Pi running
Windows 10 IoT Core. The highlighted item is the app that we will fix by giving
it a human readable name.
In Visual Studio, the Build output window shows:
1>Deployment complete (13982ms). Full package name:
How can I fix this problem?
You can edit the Package Manifest file, Package.appxmanifest, to change the
Building on my previous articles (Windows 10 IoT Core: Starting a Package on Raspberry Pi and Windows 10 IoT Core: Getting the MAC Address from Raspberry Pi) the following shows how to stop a running package.
We start with the function StopApp(), which can be called either of the following ways:
private async void StopApp(string appName, bool Force)
String FullName = await GetPackageFullName(appName);
byte toEncodeAsBytes = System.Text.ASCIIEncoding.ASCII.GetBytes(FullName);
string appName64 = System.Convert.ToBase64String(toEncodeAsBytes);
String URL = "http://localhost:8080/api/taskmanager/stop?" + (Force ? "?forcestop=true&" : "") + "package=" + appName64;
StreamReader SR = await PostJsonStreamData(URL);
To stop the package ...