I’ve just installed Windows 10 IOT edition on a Raspberry Pi 2 – and I have my suspicions that this isn’t necessarily the same operating system that I am running on my laptop.
Let’s have a bit of context
The challenge to IT – and indeed to us developers – is that users are no longer experiencing our applications or operating systems on the boring beige box like they used to. People are just as likely to use their phone or a tablet as a laptop or a desktop to run that shiny new app. This is something we need to consider when designing the user experience for our products – be they operating systems or applications.
So Microsoft has been working towards unifying their operating systems – which is why you can now get windows 10 running on mobile phones such as the Lumia 550 or Lumia 950 and even the Surface product range. I believe that Microsoft are talking here about the main kernel for their OS, rather than the whole OS. A window manager for desktop PC’s would be very different from a window manager for Mobile phones or tablet based systems. Except that I don’t believe they have gotten around to their IOT offerings yet.
Microsoft’s process for interacting with Raspberry Pis, and turning them into IOT devices is simple enough. Instructions and write ups for the Raspberry Pi can be found here but Windows 10 IOT also supports Minnowboard MAX and the Qualcomm DragonBoard 410c – but with DragonBoards costing roughly £60, and minnowboards going for roughly £100 , the obvious choice is a raspberry pi costing £30. I happen to have a spare raspberry pi hanging around, so I thought I’d give it a go. I set up the pi using the IoT Dashboard Tool.
After my machine had booted, I clicked around on the web based dashboard, looking at my wondrous new machine that was connected to the TV in the other room.
Clicking on some of the options I found a debug page, which listed 2 errors – which I thought was strange considering that the device was doing nothing.
Being the inquisitive sort I clicked on the first error, which confusingly is at the bottom of the list :
|1/21/2016, 10:50:46 PM||Critical unknown a0795c9de6cdb1f43e165a29b7f6d42caeb2b||SYSTEM||Archive|
Clicking on the Name took me to a detailed screen showing more information about the error :
The friendly name for that error : WindowsPhone8ExecManService
I’m not a gambling man, but I reckon that all Microsoft have done here is compile their windows 8 phone OS for the ARM chip on the Raspberry Pi, and replaced the front end string resources with “Windows 10”. For those interested, the Chip in the Raspberry Pi is a quad-core ARM Cortex A7 – the same processor running on the Microsoft Lumia 550 – which while based on the SnapDragon 210 SOC, has ARM Coretx A7 Processors.
Was able to find something for the WindowsPhone8ExecManService error on stackoverflow :
The value EM_WATCHDOG_TIMEOUT likely indicates that you have blocked the UI thread with a long running piece of code or a wait of some description.
Mark Radbourne [MSFT]