Andy Nichols is currently a software engineer at The Qt Company in Olso, Norway. He has worked with Qt for the last 8 years. Andy was a Qt support engineer at Nokia for 3 years who focused on customers using Qt for embedded Linux. He later took a role as a software engineer at Nokia with the Qt graphics team where he worked on the Qt Platform Abstraction (QPA) in Qt 5 as well as the QtWayland module. Since joining The Qt Company he has been focused on Wayland, Multimedia, and the Embedded Linux and iOS ports. Andy's current focus is on Qt Enterprise Embedded.
Creating embedded devices comes with many challenges, but with Qt Enterprise Embedded we aim to make the software side much more manageable. With Qt Enterprise Embedded The Qt Companyprovides both a stable software stack as well as the tools needed to develop software for your target embedded device. From prototyping to productisation Qt Enterprise Embedded will make your embedded project easier and thus help you get to market quicker.
Prototyping your embedded device is the first thing you will generally want to do and that is easy to do with Qt Enterprise Embedded. I'll demonstrate how easy it is to prototype an embedded device idea using a pre-built image from one of the supported reference devices (Freescale iMX6, Beaglebone, Raspberry Pi). For the reference devices it is as easy as flashing our provided image to an SD card and powering on the device. From there it is possible from the Qt Creator IDE to build your Qt Application and remotely run, debug, and profile your application on your device. If you do not have one of the supported reference devices it is possible to prototype your device in a simulated environment via the Boot to Qt Emulator.
Once you have prototyped your device and are ready to start moving your software onto your production hardware we give you a few options. If you have some hardware that already supports running the Android OS (version 4.2 or higher) is is possible with Qt Enterprise Embedded to leverage that existing environment to run the Boot to Qt software stack. This way you already have an environment that is able to take advantage of the existing hardware via the Android Linux kernel and drivers, but you have full control over what the device boots to via the Boot to Qt software stack.
It is also possible for you generate a completely customised embedded Linux stack that fits your needs but that is also compatible with the Boot to Qt software stack. I'll show how this is possible using the Boot to Qt build scripts. These builds scripts use the industry standard tools from the Yocto Project, and easily generate kits that can be used in Qt Creator as easily as any reference images used for prototyping.