Changes

Jump to: navigation, search
no edit summary
{{InfoBoxTop}}
{{AppliesToAxelLite}}
{{AppliesToAXEL Lite TN}}
{{AppliesToSMARX TN}}
{{AppliesToAXELULite}}
{{AppliesToAXEL ULite TN}}
{{InfoBoxBottom}}
[[Category:MISC-AN-TN]]
[[Category:MISC-TN]]
 
==History==
{| class="wikitable" border="1"
|-
|1.0.0
|December 2017January 2018
|First release
|}
 
==Introduction==
One of the most appreciated characteristics of the Axel family is the scalability in terms of performances and feature set. This technical note illustrates a real-world example in which this scalability was heavily exploited by DAVE Embedded Systems to produce an entire family of products originated from a common hardware project. Furthermore, all the variants share a unified software development environment.
All of this allowed our customer to reduce dramatically the time-to-market and to limit the software development/maintenance costs.
==The hardware platform==
==The unified software development environment==
From the a software development standpoint, the common factor across all the product variants is the main user application. To simplify the management of all the variants, we provided the customer with one virtual machine implemented as a [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine (MVM)]].
This virtual machine, in turn, is based on the MVMs delivered along with the following development kits:
*[[Axel_Embedded_Linux_Kit_(XELK)|Axel Embedded Linux Kit (XELK)]].
We managed to set up in one MVM all the tools required to handle the board support packages (BSP) for all the models and to develop the main application–which application—which is based on the well-known [https://www.qt.io/ Qt 5.9.2 libraries]–in —in just '''one''' MVM. In combination with the [[ConfigID_and_UniqueID|ConfigID]] feature, this allows the development team to maintain '''just one application that can run on all the platform variants''', as it can detect at runtime which variant it is running on.
8,186
edits

Navigation menu