Bureaucrats, dave_user, Administrators
743
edits
Changes
→Introduction
The MVM comes with all the development tools and source code, pre-configured, and requires only a minimal setup by the end user. Two versions are available:
*''basic'': this version
**is distributed as a TBD[https://en.wikipedia.org/wiki/Open_Virtualization_Format OFV Package] for Virtual Box**requires minimal configurations**requires several GB of data to be downloaded from DAVE Embedded Systems' servers**is intended for developers who don't need the full control of the virtual machine creation process*''advanced''**this version is distributed as TBDgit repository**requires the execution of the provisioning process to be created**requires few tens of kB of data to be downloaded from DAVE Embedded Systems' servers**is intended for developers who need the full control of the provisioning process.
===Contents and provided services===
This chapter briefly describes the contents and the services related to the software developing, provided by MVM. Depending on the target operating system (Yocto Linux distribution, Android etc.), contents organization may differ slightly from one MVM to another. Following sections describe these differences for all of the supported target operating systems. In general, MVMs are built upon Debian-based Linux distributions such as Ubuntu.
*username: <code>dvdk</code>
*password: <code>dvdk</code>
<code>dvdk</code> can run commands with root privileges via <code>sudo</code>.
====Yocto-based Linux distribution====
The typical development/deployment process basically consists of two stages:
*editing/building/debugging code: during this stage the target is connected via Ethernet LAN to host machine and is configured to **retrieve binary images (i.e. Linux kernel) via TFTP protocol**mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].*deployment: the goal of this stage is to configure the target for normal operation, that is out of the development environment. A target root file system - optimized in terms of memory footprint - is used. This root file system is stored on target's non-volatile memory.
To implement this workflow, MVM provides
*TFTP server TBD*NFS server TBD*cross-tool chain**by default, cross-tool chain is installed in <code>/home/dvdk/<targetname>/sdk/latest</code>. <targetname> is the name of the actual hardware platform (i.e. <code>lynx</code>, <code>axelulite</code> etc.).*target-specific sources
** U-Boot bootloader
** Linux kernel
** Yocto recipes*target's development root file system*Yocto build system including <code>BitBakebitbake</code> and SDK*[[Debugging_with_Eclipse_(MVM)|Eclipse/ADT integrated development environment]].
== Installation and configuration ==
