Changes

{{ImportantMessage|text=Please note that access to DAVE Embedded Systems' git repositories is granted to development kit's owners only. Please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]] for detailed instructions on how to get access.}}

The components listed in the table above sources can be kept in sync and up to date with DAVE Embedded Systems' repositories.

 {{ImportantMessage|text=Technically speaking, the developer can run a Yocto-based full build process to (re)generate all the pre-built objects includes included in the MVM. However, this process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it is discouraged to use the MVM to perform such build. Using a physical machine is recommended instead. For more details on this, please refer to [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)|this page]].

BELK/BXELK provides one (or more) pre-built root file systemIn general, that can be used during the evaluation/development phase since it provides a relatively rich set of packages for working with the BORA platform. This kit supports several root file system is located hereimages. The typical images are the following: *<code>/home/dvdk/<target_name>/rfs/<kit_name>-image</code>. BELK/BXELK also provides **This is a rich repository containing pre-built applications and libraries. These packages minimal image that can be easily installed on the target by using used as starting point for the production file system.*<code>smart<target_name>-image-networking</code> tool. Please refer to [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)#Using_pre-built_package_archive|this section]] for more details. The following table lists **This is like the minimal image with the pre-built root file systems included in addition of the MVMmost common packages used to implement networking applications.{| class="wikitable" border="1"!Kit version*<brcode>BELK<brtarget_name>BXELK!Image name!Build commands!Path|-|<br>4.0.0<br>2.0.0|<code>bora-image-devel</code>|<pre>dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repodvdk@dvdk-vm:~/belk$ chmod **This is an image that includes a+x repodvdk@dvdk-vm:~/belk$ rich set of packages convenient for the development stage./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-mortydvdk@dvdk-vm:~/belk$ Usually, the memory footprint of this image is significantly greater than the other ones./repo syncdvdk@dvdkMVM includes one (or more) pre-vm:~/belk$ source bora-bsp-init-envbuilt images.shdvdk@dvdk-vmThey are located here:~/belk/build$ bitbake bora-image-devel</pre>|<code>/home/dvdk/bora<target_name>/rfs/belk-4.0.0<kit_name></code>|-|}. Kit specific documentation describes hot to build such images.

The following table lists the development kits that are based on Yocto are also provided along with a rich repository containing pre-built Yocto SDKs included in the MVMapplications and libraries. These SDKs are associated with packages can be easily installed on the target by using the root file system images mentioned above.{| class="wikitable" border="1"!Kit version<br>BELK<br>BXELK!SDK name!Build commands!Path|-|<br>4.0.0<br>2.0.0|<code>bora-image-develsmart</code>|<pre>bitbake bora-image-devel -c populate-sdk</pre>|<code>/home/dvdk/bora/sdk/belk-4tool.0Please refer to the specific documentation of your kit to have more information about the use of this tool.0/sysroots/cortexa9hf-neon-xilinx-linux-gnueabi</code>|-|}