locked
The future of Windows 10 IoT Core RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've got a project idea where Windows 10 IoT could be the perfect operating system. I've got the idea years ago, but now the time has come where everything seems to fit into the puzzle. My application is designed to run as a single remote controlled application on a small device.

    As far as I understand, Windows 10 IoT Core will currently run on Rasperry Pi 2 and MinnowBoard MAX only. Right?

    Unfortunately none of these two supported devices meet my requirements. The critical aspects in my application are:

    1. Free RAM for the application should be at least 1 GB (the more the better)
    2. Internal memory must be relatively fast for writing (removable SD cards are too slow/internal eMMC seems to be ok)
    3. Support for a broader range of USB WiFi dongles (incl. Netgear N300)

    While the currently supported devices don't fulfill my requirements regarding RAM and/or eMMC there are devices on the market that perfectly meet my requirements. As an example I did some tests for proof of concept of my app on a Atom Z3735F based Minix Neo Z64 with 2 GB RAM and Windows 10 Home.

    As a conclusion from what I've seen while testing the app under Windows 10 Home on the Minix Neo Z64 and checking out the general possibilities with Windows 10 IoT on my Rasperry Pi 2, I could realize the project, if it could be installed on adequate hardware like the Minix Neo Z64 or similar devices in its class.

    Now the questions:

    1. Can I expect in the NEAR future a broader support of other modern boards and devices, inclusive support for Intel Atom processor family? 
    2. Can I expect in the NEAR future the same level of driver support for USB devices and WiFi dongles that is provided for other Windows 10 editions?

    The only viable option to practically realize my project for NOW would be a self-compiled Linux based solution. However, a Windows based development AND runtime environment would definitely be my preferred solution. Most of the parts of the application are already developed and written in C#. Yet another reason to take the Windows 10 IoT Core route, if there is one.

    Let me know your suggestions and thoughts about what you know or think about the future of Windows 10 IoT Core.

    Peter



    • Edited by Peter Gloor Sunday, August 30, 2015 8:20 PM
    Sunday, August 30, 2015 8:19 PM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote

    Hi Peter

    Windows 10 IoT Core is the smallest member of the Windows 10 product family. Every OS based on the Windows 10 kernel supports a unified driver model call "Universal Windows Driver Platform".

    The following presentation should give you a good overview: https://channel9.msdn.com/Events/WinHEC/2015/IOT201

    The above presentation has also some slides that talk about how OEMs can create their own OS images.

    Once the OEM has ported their drivers to this new platform, they will work on every version of Windows 10 - including Windows 10 IoT Core.

    The Minnowboard MAX board is based on a Atom (see http://ark.intel.com/products/codename/55844/Bay-Trail#@Embedded) CPU. That means that there is (some) support for Atom based CPU available.

    The following post might be interesting as well: https://social.msdn.microsoft.com/Forums/en-US/0757fea1-fa12-4ad3-897d-cfb28c76c3ad/roadmap-for-windows-iot?forum=WindowsIoT

    To your questions:
    I would expect to see broader silicon and board support in the future. For x86 based systems, it all boils down to the question when the required drivers (Universal windows driver) are available.
    Whether this happens in the "NEAR future" is something I cannot answer. Only Microsoft and/or the OEM can answer that question.

    For the time being, you could still start your project using Windows 10 Home and migrate to a Windows 10 IoT Core based device at a later time.

    MVP Windows Embedded

    • Marked as answer by Peter Gloor Tuesday, September 1, 2015 7:19 AM
    Monday, August 31, 2015 8:42 PM