Bureaucrats, dave_user, Administrators
8,221
edits
Changes
no edit summary
The process is relatively straightforward: it consists of writing the WIC file of interest generated by Yocto onto the SD card.
The following instruction explains how to use ''balenaEtcher'' on a Windows host. The procedure is similar when working with a Linux host.
* download the desired binary image to flash (<code>*.wic</code> or <code>*.wic.bz2</code>) from the [https://mirror.dave.eu/desk-mx-l/ mirror binary server] selecting the proper [[DESK-MXxx{{{kit-code}}}-L | DESK-MXxx{{{kit-code}}}-L]] release**among the binaries made available in the [[mirror:desk-mp1{{{kit-lrepo}}}/| mirror]] there are several <code>*.wic.bz2</code> files for the available releases. In particular, there is the <code>dave-image-devel-desk-mxXXXX{{{kit}}}.wic.bz2</code> (for {{{nome-som}}}) file. This image is the one used to program the microSD card delivered along with the evaluation kit.
* connect the microSD card to the PC Host
* open balenaEtcher tool
=== SD card structure ===
The created SD card has the following structure:
* raw sectors for the bootloader storage: tipically typically this is a an 8MB raw part where storing that stores the bootloader binaries (like <code>imxXXX_flashi{{{kit}}}_flash.bin</code>) for the bootrom startup
* <code>FAT32</code> first partition: this will be mapped to the <code>/dev/mmcblkXp1</code> device in Linux
** usually this partition contains the Linux kernel binary and the device tree blob
** the splash screen image is stored in this partition too for a splash image showing during U-Boot startup
* <code>ext4</code> second partition: this will be mapped to the <code>/dev/mmcblkXp2</code> device in Linux
** this partition contains the Linux ''root file system''
Even if the overall binary artifacts have been created by the Yocto build, it is highly discouraged to manually create the SD card starting from them.
The Yocto build take takes care about of the overall binary consistance consistency (like kernel modules and so on) avoiding to mistmatch mismatching different versionversions.
Moreover, the SD card is intended to be used during the development process and not for the production phase (where other deployment specifications and details have to be taken into account).