Item Preview
Windows-10-IoT-Core-v1607-Device-info.jpg
2,053
Views
10
Favorites
DOWNLOAD OPTIONS
Uploaded by
TedezaRize
on
SIMILAR ITEMS (based on metadata)
В данной статье мы постараемся ответить на часто задаваемые вопросы по отличиям настольных версий Windows 10 и так называемых «Embedded»-версий Windows 10 (т.е. версий для производителей устройств строго определенного функционала), которые получили приставку «IoT», от «Internet of Things». Пусть вас не смущает аббревиатура, эта ОС применима абсолютно во всех устройствах, которые не являются универсальными ПК (об этом — ниже).
Если в прошлых редакциях эти отличия были очевидны – явно отличающиеся названия, компонентная структура, использование специальных инструментов для сборки, то для Windows 10 Microsoft в стремлении к унификации версий, сделал более схожими названия, технические возможности, инструменты, политику поддержки и продвижения.
Все это привело к массе вопросов от пользователей (и даже сотрудников Microsoft из других подразделений!) относительно отличий Embedded и не-Embedded версий, способов их лицензирования, активации, обновления и т.п.
В связи с этим, мы решили сделать небольшой FAQ c ТОП5 вопросов по встраиваемым версиям Windows 10. Надеемся, эта информация будет полезна аудитории разработчиков и поможет сделать правильный выбор версии ОС в зависимости от проекта.
Вопрос: Чем отличаются версии Windows 10 Enterprise от Windows 10 IoT Enterprise?
Ответ: Рассмотрим три аспекта отличий: технический, лицензионный и ценовой.
Технически (если рассматривать дистрибутив LTSС), эти версии идентичны. Однако, для IoT-версии можно получить особый ключ (ePKEA), не требующий активации для начала работы (см. вопрос «Нужна ли активация для Windows 10 IoT?»). Ключ для «настольной» Windows 10 Enterprise потребует активации на каждом устройстве.
Лицензионные же отличия достаточно существенны:
Во-первых, лицензия Windows 10 Enterprise доступна только для конечного пользователя (организации) и является
именной
лицензией для
внутреннего
использования. Ее перепродажа другому лицу невозможна. В то время как лицензия Windows 10 IoT Enterprise
не именная
, поставляется через
Embedded-дистрибуторов
сборщикам и производителям устройств, которые могут
перепродавать
эту лицензию неограниченному числу клиентов вместе с устройством, на которое она установлена (так называемая OEM-лицензия);
Во-вторых, лицензия Windows 10 Enterprise может быть установлена на
любое
компьютерное устройство, тогда как Windows 10 IoT Enterprise – только на устройство
специализированного
применения. Здесь имеется в виду не форм-фактор устройства, а его назначение. Это может быть обычный ПК, но применяемый для какой-то узкой функции, например — касса или видеосервер. Ограничение сугубо лицензионное, технически система установится везде, где поддерживается Windows 10.
В качестве наиболее распространенных устройств на основе этих ОС можно привести: POS-системы, инфо- и платежные киоски, системы видеонаблюдения, СКУД, медицинские устройства, системы промышленной автоматизации, тонкие клиенты, устройства самообслуживания, цифровые вывески и меню, постаматы и т.п., все перечислить невозможно, т.к. новые типы устройств появляются постоянно (например, в связи с COVID — «умные» санитайзеры и тепловизоры);
В-третьих, в Windows 10 IoT Enterprise существуют 3 варианта лицензирования (3 разных SKU), в зависимости от мощности (модели) процессора, чего нет в настольной Windows 10 Enterprise, где одна редакция и одна цена. Эта уникальная схема ценообразования позволяет экономить до 70% от цены настольного аналога, если ваше устройство работает на CPU типа Atom и до 50% на CPU типа Core i3/i5!;
В-четвертых, Windows 10 IoT Enterprise поставляется производителям в полной версии, а настольная Windows 10 Enterprise – только в версии «
обновление
» и, соответственно, потребует наличие установленной предыдущей версии.
Последний немаловажный фактор — поддержка. Все IoT-версии с дистрибутивом LTSC гарантированно поддерживаются Microsoft в течение 10 лет и столько же времени доступны для покупки.
Ценовые отличия: В силу оптимизации под узкоспециализированные ПК, все лицензии IoT
существенно дешевле
чем настольные версии и экономически оправданы во всех случаях, где устройство не является универсальным ПК. Причем оплату за лицензии производитель осуществляет только когда получает заказ на устройства от своего клиента, поскольку дистрибутив (и право установки внутри организации) ему предоставляется бесплатно.
Вопрос: Что такое дистрибутив LTSС и чем он отличается от обычного дистрибутива Windows 10.
Ответ: LTSС – это Long Term Servicing Channel – особый вариант политики управления обновлениями, в котором не поставляются автоматически функциональные (версионные) обновления операционной системы. Предназначен он для «mission critical» устройств, где такое «самообновление» может повлечь за собой незапланированный останов устройства. Критичные исправления и обновления безопасности будут по-прежнему доставляться регулярно в соответствии с установленной для устройств политикой, т.е. устройство остается защищенным. Как уже упоминалось, поддержка и поставка обновлений безопасности осуществляется в течение 10 лет, в отличие от «настольных» вариантов, где каждый релиз поддерживается полтора года, после чего приходится переходить на новую версию.
Для LTSC существует отдельный дистрибутив Windows 10 IoT Enterprise, в котором отсутствуют: Store UX, Cortana, Edge и приложения, обслуживаемые через Store (News, Sports, Finance и т.п.).
Как правило, под Windows 10 IoT Enterprise понимают именно Windows 10 Enterprise LTSС. Именно этот дистрибутив чаще всего используется производителями специализированных устройств.
Вопрос: Как приобрести Windows 10 Enterprise LTSC?
Купить Windows 10 Enterprise LTSC возможно двумя путями:
- Конечному пользователю (организации) – у реселлера Microsoft по программам корпоративного лицензирования. Доступно только обновление;
- Производителю или интегратору – у дистрибутора Windows Embedded. Доступна полная версия, по более выгодной цене. В этом случае продукт называется «Windows 10 IoT Enterprise».
Вопрос: Требуется ли активация для Windows 10 IoT?
Ответ: В отличие от Windows 10 Enterprise, ключ для Windows 10 IoT Enterprise LTSC (называется ePKEA) вводится на производстве и
не требует активации
пользователем и подключения к Интернет для начала работы. В дальнейшем, в случае подключении к сети Интернет, система активируется самостоятельно и «бесшумно» без каких-либо видимых уведомлений и изменений в работе устройства. Если подключения не произойдет – устройство будет продолжать работать весь срок службы, не требуя активации.
Вопрос: Какие версии Windows 10 IoT существуют?
Ответ: Существуют несколько продуктов с приставкой «IoT»:
- Windows 10 IoT Enterprise (LTSC или SAC) — описанная выше полноценная Windows Enterprise для применения в широком спектре встраиваемых устройств (в трех вариантах лицензирования в зависимости от модели процессора – Entry, Value, High End);
- Windows 10 IoT Core — бесплатная легкая ОС для простых компактных устройств, с поддержкой ARM-архитектуры (не совместима с классическими Windows-приложениями и устройствами, не имеет собственной графической оболочки);
- Windows Server IoT 2019 — серверная операционная система для решений специализированного назначения, сходная по правилам лицензирования с Windows 10 IoT Enterprise и технически аналогичная стандартному Windows Server 2019, но гораздо более экономичная;
- Microsoft SQL Server IoT — сервер баз данных, лицензионно ограниченный для применения в Embedded/IoT-системах и значительно более выгодный с точки зрения стоимости лицензии чем его стандартный аналог;
Для работы с продуктами Windows 10 IoT не требуются специальные средства разработки, как это было с Windows Embedded, но для использования в полной мере всех возможностей «встраивания» и для настройки образа под определенные требования имеется бесплатный инструмент Windows Imaging and Configuration Designer (ICD), о котором мы подробно писали ранее. ICD включен в Windows ADK, который можно загрузить здесь.
Доступны также инструменты для упрощения настройки образа Windows 10 IoT Enterprise от сторонних производителей, такие как ZereOS Embedded Configuration Manager
Канал на YouTube, посвященный Windows Embedded/IoT: www.youtube.com/user/QuartaTechnologies1/videos
Мы готовы ответить и на другие ваши вопросы. Обращайтесь, пишите комментарии!
UPD: В феврале 2021 года, Windows 10 Enterprise (а вместе с ней и ее аналог — Windows 10 IoT Enterprise) получила долгожданный сертификат ФСТЭК, что расширяет сферу применения этой ОС.
Сертификат номер 4369 подтверждает, что операционная система Windows 10 IoT Enterprise LTSC 2019 (1809) соответствует требованиям доверия 6 уровня, требованиям безопасности информации к операционным системам и профилю защиты операционных систем типа А шестого класса защиты. Срок действия сертификата: до 10.02.2026.
Получить дополнительные консультации, заказать разработку и приобрести встраиваемые ОС Microsoft вы можете у авторизованного дистрибутора в России и странах СНГ «Кварта Технологии», www.quarta-embedded.ru
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Sign up
Appearance settings
- About
- Embedded / IoT
- Embedded / IoT Operating Systems
- IoT / Embedded
- Windows 11 IoT Enterprise 2024 LTSC
- Windows IoT on ARM
- Windows 10 IoT Enterprise 2021 LTSC
- Windows Embedded 8.1 Industry Pro
- Windows Embedded 8 Industry Pro
- Windows Embedded 8 Standard
- Windows Embedded Standard 7
- POSReady 7
- POS Ready 2009
- Windows Embedded Standard 2009
- XP Embedded
- Compact
- Windows 10 IoT Core Pro
- Compact7
- CE6
- For Embedded Systems
- Windows Embedded 8 Pro
- Windows 7 For Embedded Systems
- XP Professional
- Embedded / IoT Server
- Windows Server 2022
- SQL Server 2022
- Windows Server 2012
- SQL Server 2012
- Storage Server 2012
- Azure Sphere
- IoT / Embedded
- Basics & Availablility
- CLA
- Licensing
- Product Key Request
- Value Based Pricing
- Embedded / IoT Operating Systems
- Services
- Technical Partner zereOS
- Technical Support
- License Consulting
- Technical Trainings
- Image Development
- ESU Specialists
- News
- Events
- References
- Tools
- Embedded Toolkit
- Embedded Configuration Manager
- Footprint Technology (zOFT)
- Device Manager (zDM)
- Smart Activation (zSA)
- Onscreen Keyboard (zOSK)
- Contact
- English
- Deutsch
- Français
- Italiano
- Español
- Nederlands
- Magyar
- Čeština
- Polski
- Svenska
Windows 10 IoT Core Pro
The new Windows 10 IoT Core is a minimized version of Windows 10 that runs on the following devices: The Raspberry Pi 2 and 3, the DragonBoard 410c and the MinnowBoard MAX. Microsoft already had a minimized version of Windows 8.1 running on small footprint devices such as the Intel Galileo board. Now they have released the final version based on Windows 10 called Windows 10 IoT Core. Microsoft released this version of Windows 10 at the same time as the Windows 10 IoT Enterprise system.
Windows 10 IoT Core is a great operating system for small footprint devices or as an endpoint for the cloud. There are many great features included in this version. Some of them are described here.
Operation Modes
Windows 10 IoT Core is designed for only one Graphical User Interface Application (GUI) but it is possible to run as many applications as you want in the background (background workers). You can use a Windows 10 IoT Core running device in two different modes: headed and headless.
The headless mode means that you do not have to connect a display because you can connect to the device remotely. You can use the headless mode if you do not need a Graphical User Interface.
UWP
All applications that should run on Windows 10 IoT Core must be Universal Windows Apps. These are applications are based on the new Universal Windows Platform (UWP). The Universal Windows Platform is a new platform from Microsoft for Windows 10 devices. This means that, if you write an application once based on the UWP, you can use it on any Windows 10 running device – it doesn’t matter if it is Windows 10 Enterprise, Windows 10 Mobile, Windows 10 IoT Core, Xbox or HoloLens.
Porting
To port existing applications to the Universal Windows Platform, Microsoft designed some tools to analyze the source code of the existing Windows applications. If you use these tools, they will tell you what part of the source code you have to change to build an Universal Windows App.
Architectures
One of the most interesting things is, that this operating system runs on two different architectures. For example: The Windows 10 IoT Core version on the Raspberry Pi 2 and 3 is ARM-based and the Windows 10 IoT Core version on the MinnowBoard MAX runs on x86-based architecture. There is a 32-bit and a 64-bit version available. If you use the x86-based version, it is possible to use the drivers from the classic Windows 10 devices. For the ARM version it is required to compile the drivers.
Remote Connection via PowerShell
After the installation it is possible to connect to your Windows 10 IoT Core device remotely by using the PowerShell. You just need to start the PowerShell as an administrator and type in two commands. The first to start the Windows Remote Management Service and the second to connect to the device remotely.
Via this connection it is possible to configure a few things like the name of the device or the password, which is recommended because all devices have the same password after the first boot. You can also retrieve a process list and setup a startup application.
Remote Connection via Remote Client
It is also possible to connect to a Windows 10 IoT Core running device remotely with the Windows IoT Remote Client. You can download this application from the Windows Store. The Remote Client shows you a list of all Windows 10 IoT Core running devices in your network and you can select a specific device you want to connect remotely. After the connection is established, you will see the devices screen content and can use your mouse and keyboard to control the device. This allows to run the device headless and still be able to control and configure it easily.
Windows IoT Core Dashboard & Device Portal
The IoT Core Dashboard allows you to see a list of all Windows 10 IoT Core running devices connected to your network. You can click on a specific device and select “Open in Device Portal”. There is a great web interface for your Windows 10 IoT Core device which lets you configure many things much easier than with the PowerShell remote connection.
Start Page
It is possible to do important standard configurations like changing the name of the device or the password of the administrator account here. You can also change the time zone or configure the display resolution and the display orientation here. Many things listed here are also displayed in the default application on the device itself.
App Manager
In this section you can configure your applications. You can change the default GUI application and you can do the installation of all applications by just browsing for the AppX files to install them on the device. You can also uninstall applications which you do not need on the device anymore.
Performance
This point gives you a great overview about the utilization of your device. It shows you the graph of the CPU and the RAM memory. You can also see how much memory is installed and in use. There is also the graph of the GPU utilization visible if your device supports it and you can take a look on the I/O of the device.
Device Manager
There is also a simplified Device Manager as on a normal Windows 10 running device. You can update drivers in there and export a list of all devices into a file.
Windows Update
Windows 10 IoT Core devices search automatically for new updates.
This configuration page lists you all available Windows Updates and will show you some information during an installation progress.
If the device has scheduled an update installation, you can also start the process immediately here.
Microsoft is continuously improving the web interface on Windows 10 IoT Core to allow you to setup the device more easily. The most recent version could already include more than shown here!
Installation / Image Deployment
Prepare to install
Installation
To start the installation, please run the IoT Core Dashboard and select “Install”. Then you just have to select your device type and the microSD card and hit the “Install” button. After doing this, a file called “Flash.ffu” will be downloaded automatically. This .ffu-file is similar to a .wim file but includes the content of a full disk with the Core system on it. The difference between a .wim-file and a .ffu-file is that a .ffu-file also includes complete disk partitions and not just files.
Now the tool will flash the image on your microSD card. After this has completed, you can hook up your board and start it.
The first boot will take about two minutes. Then you will see the Windows 10 IoT Core default application instead of a classic desktop shell.
This default application shows you some details about the device like the name, the IP address or how it is connected to the network. You can configure things like the language, bluetooth or network settings.
Please click here for a very detailed guide that shows you how to create a basic image, add an app to your image, add a file and a registry setting to an image, add networking and other provisioning package settings to an image, add a driver to an image, build a retail image, creating your own board support package, update your apps.
Comparison: Windows IoT Core vs Windows IoT Core Pro
Lets take a closer look on the two different versions of Windows 10 IoT Core. There two different versions available: The normal “Windows 10 IoT Core” version and the “Windows 10 IoT Core Pro” version. Technically they are nearly the same but in general the Pro version has some advantages which are very important for the embedded channel.
Windows 10 IoT Core
vs.
Windows 10 IoT Core Pro
Windows 10 IoT Core is for makers (hobbyists). That means commercial projects must be registered. They have to sign an agreement for Microsoft. This agreement contains licensing terms which are similar to our ATs and they get very limited liability from Microsoft.
LIABILITY
Windows 10 IoT Core Pro is covered through the Customer License Agreement (CLA).
In the normal version, you have to install all updates and the devices can update themselves at any time in the field. This is a big problem because if an application doesn’t work with the new update all devices are not functional anymore and it is not allowed to deactivate the updates.
WINDOWS UPDATE
In the Pro version the Current Branch for Business is available. That means that you have control over the updates. You can defer them for at least 4 months and test the updates before you update all your devices. There is also the possibility to deactivate them completely.
For the normal version you get no COAs and you have to sign an agreement for the commercial usage for Microsoft.
LICENSE STICKER
For the Pro version you can pay a small fee to receive a Tracking label.
Page load link
Go to Top
When it comes to choosing an OS for your embedded system, performance matters.
There are many variations of Windows IoT products. With similar-sounding names, it’s easy to think they are closely related.
However, some have fundamental differences in the way they function.
For instance, how does Windows 10 IoT Enterprise ARM64 on i.MX93 stack up against Linux in benchmarks?
This analysis puts Windows IoT Enterprise to the test against Linux on the same i.MX93 hardware to compare performance.
The results reveal when Windows IoT makes sense and where Linux still shines.
What is Windows 10 IoT Enterprise for ARM64?
Windows 10 IoT Enterprise is the replacement for Windows Embedded Compact 2013 or Windows CE, which became end of life in October 2023.
It was released in 2015 alongside Windows 10 IoT Core as a more complete version and remains the sole remaining Windows embedded solution with support from Microsoft, after Windows 10 IoT Core became end-of-line in Nov 2020.
The latest LTSC (Long Term Support Contract) release of Windows 10 IoT Enterprise has a stated support time of 2032!
How does Windows 10 IoT Enterprise ARM64 differ from other versions of Windows 10?
Windows 10 IoT Core is an ARM-based version of Windows 10 that is more akin to Windows Embedded Compact or Windows CE.
However, Windows 10 IoT Enterprise ARM64 – built for ARM64 embedded systems, such as the NXP iMX8 and iMX9x series of embedded processors – is the full Windows 10 experience.
Running Windows 10 IoT Enterprise ARM64 is equivalent to running Windows on a desktop or laptop; all development / management tools used on a normal Windows setup can also be used for ARM64 on the i.MX93 or iMX8 systems.
This analysis focuses on the i.MX93 device. This is a low-cost, low-power yet high performance dual-core ARM CPU in the NXP portfolio.
The System-on-Chip device offers a rich set of peripherals targeting automotive, industrial, and consumer IoT market segments, and can run in a fanless environment without the need for active cooling, unlike most x86 CPUs.
Using this fully-featured OS distribution can massively speed up the development time for your applications, as it can all be done from your normal Windows’ development machine.
Since 1996, when Microsoft released their first embedded solution (Windows Embedded CE 1.0), Microsoft has had a multitude of options for an embedded Windows solution, with Windows IoT Enterprise being the latest, and by far the most feature-rich.
What is the i.MX93?
The i.MX93 is the latest in a long line of NXP i.MX chips. It features 2 Cortex A55 and 1 Cortex M33 processors, a dedicated 2D graphics chip and 2 1GB Ethernets.
NXP i.MX93 System Structure
The BSP (Board Support Package, meaning the structure of the firmware file) for the Windows IoT Enterprise for ARM64 system is split into two parts:
- the ARM64 specific firmware
- and the generic Windows binary and drivers
The ARM64 firmware is compiled into a FIT image format comprised of a U-Boot SPL, U-Boot image, UEFI FIT image and any trusted/secure firmware blobs.
The boot structure is shown below:
For custom hardware, the modifications start in U-Boot. This is performed in the same way that you would customise U-Boot for a Linux solution, with DTS and configuration file changes.
U-Boot is mainly used to transition the bootloader over to UEFI, where most of the hardware drivers are stored, so it will be a very familiar workflow for Linux BSP engineers.
The UEFI used is a modified version of Project MU, a project from Microsoft to make UEFI development more collaborative and maintainable. NXP has added some silicon-specific code, and then configuration files for all of their supported hardware.
Customising the UEFI code
To customise the UEFI code, you will need to edit ACPI tables for each of the hardware components (UART, Ethernet, USB, etc.) as well as some configuration files. The UEFI is what boots into Windows 10 IoT Enterprise.
Since all board-specific customisation is done in the ARM64 bootloader, a combination of U-Boot and UEFI, any Windows development you do for your application can be transferred from the i.MX93 EVK straight to your custom hardware, with only the operating system and bootloader needing to be ported by device builders (something we here at ByteSnap have expertise in).
For more information on customising the UEFI code with Azure IoT Edge, please refer to the user guide at https://aka.ms/nxpiot.
Windows drivers
The Windows drivers are built using Visual Studio Code 2019 with the Windows development kit extensions. The drivers are then combined with the latest Windows 10 IoT Enterprise LTSC binary.
There is no board-specific configuration that needs to go along with this, apart from any Windows device drivers you may need to add for additional hardware support.
Windows 10 IoT Enterprise ARM64 on the i.MX93 — Compatibility
CPP Executables
To test how easy it is to write applications for Windows 10 IoT Enterprise ARM64 on the i.MX93, I loaded up Visual Studios 2019 and compiled one of the template applications for x86 on my Windows machine.
I downloaded the latest Visual Studio redistribution packages for x86 and installed them onto the i.MX93 running Windows 10 IoT Enterprise ARM64.
After this, I was able to run the x86 template application complied on my Windows machine on my ARM64 i.MX93 target, no other configuration was needed.
This is because x86 applications are run though the WOW64 x86 emulator, which allows 32-bit applications to be run painlessly on 64-bit systems.
Running x86 apps takes a slight performance hit, as the emulation layer has to covert the 32-bit code into 64-bit. Therefore, for the best performance, it would be ideal to compile your application for ARM64.
Bear in mind that many applications don’t need this extra performance; for developments where applications can’t be recompiled due to legacy issues, this step wouldn’t be required.
|
Windows 10 Enterprise |
Windows 10 IoT Enterprise |
Windows 11 IoT Enterprise |
|
|---|---|---|---|
|
X86 |
X |
X |
X |
|
ARM64 |
X |
X |
|
|
X64 |
X |
One of the main benefits of using Windows 10 IoT Enterprise ARM64 for i.MX93 is the standard Windows experience.
You get all the benefits of Microsoft’s updates and security, which means you can manage your embedded system in the same way you manage the rest of your Windows 10 systems on your network.
Screen shots of the default experience when you boot up, with web browsing via Edge and multi-window capabilities
Obviously, this is not the main use case for an embedded system, so Windows 10 IoT Enterprise ARM64 has many features to help make your embedded system more specialised.
Kiosk mode will open one (or show a start menu with a range of options) application, and block access to all other functions.
By default, this mode will also turn on several security features. There is also a dedicated embedded mode, used for making sure background apps can be automatically restarted, and giving deeper lower-level access to the hardware such as GPIO, SPI and I2C.
«Soft Real-Time» feature
Windows 10 IoT Enterprise for ARM64 also has a `soft real-time` feature for applications where getting the timing of processes consistent and reliable is essential – for example, motors on a robotic arm.
Branding is also important for any embedded product, and Windows 10 IoT allows you to remove the Windows branding, and enable custom boot / login pages and notifications.
Benchmark Test
To test performance, I compiled the standard Dhrystone benchmark test in C, which has historically been used as a measure of integer processing performance.
I compiled for Windows 10 IoT Enterprise for both ARM64 and x86, as well as Linux ARM64, to compare how performance changes over these environments on the same hardware.
Both the Windows ARM64 and x86 were compiled using Visual Studios 2019, using the standard Visual Studios C compiler and had identical source code. The Linux version had small changes to the source code to account for the different system calls, but no logic was changed. It was compiled using GCC with optimisation level 3.
The results: as they have all been compiled on different compilers, with the Linux one not even having identical source code, take these scores as an indicative guideline as to the difference in performance.
No surprise then that the native Linux version performs the best, with Windows 10 IoT Enterprise ARM64 coming in second.
For a comparison, the development laptop using an 11th gen Intel i5 hitting 4.2Ghz clock speed scored a 48,134.
Summary
Overall, Windows 10 IoT Enterprise for ARM64 on i.MX93 seems a great way to get your applications into the embedded space. We are getting closer and closer to a time where you can have a seamless Windows experience on a low power embedded device.
If you have an application already running on a Windows system, or want the benefit of having your product run in a Windows environment, Windows 10 IoT Enterprise ARM64 for i.MX93 is the perfect option.
However, if you are already in the Linux space, or need maximise the performance of your device, then a Yocto-based Linux BSP still seems like the way to go.
Get expert engineering support for your IoT product development
At ByteSnap, our engineers have the hands-on experience to help determine
if Windows IoT is the right choice for your embedded system project.
Book a discovery call to discuss your needs, and how we can support your team to get products to market faster.
Harrison Wood Embedded Software Engineer
Harrison Wood is an accomplished Embedded Software Engineer at ByteSnap, bringing a strong foundation in mathematics and physics to his work. He holds a Masters degree in Maths and Physics from the University of Warwick, where he honed his analytical skills and problem-solving abilities.
Since joining ByteSnap, Harrison has worked on a diverse range of projects, showcasing his versatility and expertise in embedded systems development. His portfolio includes work on medical devices, light controllers, and smart heating systems.
With a focus on embedded Linux and Windows systems, Harrison has developed a deep understanding of Yocto-based Linux BSPs and has successfully undertaken Windows-to-Linux porting projects. He has also developed QNX-based systems.
(Fun fact: Harrison was part of the University Ultimate Frisbee Club, reaching the nationals for both the indoor and outdoor competitions!)