Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→Downloadable binary images
| Device tree || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-divelk.dtb|am335x-divelk.dtb]] || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-sbcd.dtb|am335x-sbcd.dtb]]
|}
=== DIVELK microSD Layout ===
The microSD card provided with DIVELK is partitioned as shown in the following image:
[[File:DIVELK-uSD-partitioning.png|thumb|center|300px|microSD card partitioning]]
Most of storage space is occupied by two partitions:
*a <code>FAT32</code> partition (<code>mmcblk0p1</code>) containing:
**U-Boot <code>bootscript</code>
**Linux kernel and DTB binary images
**DIVELK virtual machine image in OFV format ([[Managed_Virtual_Machine_(MVM)|MVM]] basic version)
**7-zip Windows executable file
*an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target.
<code>bootscript</code> and root file system are used to boot the target as described in [[#Target_setup_and_first_boot|this section]].
It is worth remembering that the microSD card is bootable, because U-Boot image files ('''MLO''' and '''u-boot.img''') and kernel image ('''uImage''') are present into first FAT32 partition: filename '''MUST''' be the one written before.
However, even if U-Boot is run from the microSD card, '''the environment is retrieved from NOR flash'''.
====How to create a bootable microSD card====
For creating a bootable microSD card, simply follows the following steps:
* create two partition: first partition FAT32 and a second partition ext3
* mark as "bootable" the first partition (using for example <code>gparted</code> on VM)
* copy MLO, u-boot.img and boot.scr on FAT32 partition
** copy kernel and dtb on the same partition
** all files can be retrieved from [Diva_Embedded_Linux_Kit_(DIVELK)#Downloadable_binary_images here]
* extract rfs on ext3 partition
=== DIVELK Updates ===
