Changes

|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|X1.Y0.Z0|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|Month YearFeb 2022|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|TBD|-|-|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|[TBD_link X.Y.Z]|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|Month Year|style="border-left:solid 2px #73B2C7; borderFirst DESK-right:solid 2px #73B2C7;borderMX8M-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|TBDL release

=== Program boot images into NOR flash eMMC ===

====u-Boot==== Update to the latest u-boot Boot image version allows usage of u-boot environment variables available. <pre class="workstation-terminal">=> run loadUsing FEC deviceTFTP from server 192.168.0.13; our IP address is 192.168.0.89Filename 'sdvx/u-boot/sdvx-1.0.0_mx6dl_sfczg_spi_u-boot.imx'.Load address: 0x12000000Loading: ################################################################# ################################################################# ## 1.4 MiB/sdoneBytes transferred = 671788 (a402c hex)=> run spi_updateSF: Detected S25FL256S with page size 64 KiB, total 32 MiB=></pre> ====kernel image and device tree==== We assume that the following environment variables are present in u-boot:

loadkmmc_update=tftpboot ${loadaddr} ${serverip}:${bootfile}loadfdt=tftpboot ${fdtaddr} ${serverip}:${fdtfile}spi_updatek=sf erase 200000 800000mmc dev; sf write ${loadaddr} 200000 setexpr blocks ${filesize}spi_updatefdt=sf erase 180000 80000/ 0x200; sf write ${fdtaddr} 180000 setexpr blocks ${filesizeblocks}spi_loadk=sf read ${loadaddr} 200000 800000spi_loadfdt=sf read ${fdtaddr} 180000 80000spi_nand=sf probe+ 1; run spi_loadk spi_loadfdt nandargs addcons addmisc; if run configid_fixupfdt; then bootm mmc write ${loadaddr} - 2 ${fdtaddrblocks}; fi

* Update the <code>bootfile</code> and Load Boot binary form a <code>fdtfiletftp</code> environment variables to fit the filename as found inside the TFTP server.* Program kernel and device tree on NOR flash with the following U-Boot command <pre class="board-terminal">sf probe; run loadk spi_updatek loadfdt spi_updatefdt</pre> E.g.:

u-boot=> sf probe; run loadk spi_updatek loadfdt spi_updatefdtSF: Detected S25FL256S with page size 64 KiB, total 32 MiBloadUsing FEC ethernet@30be0000 deviceTFTP from server 192.168.0.13; our IP address is 192.168.0.9890Filename 'sdvxdesk-mx8m/linux/sdvx-1.0flash.0_lite_uImagebin'.Load address: 0x120000000x40480000

######## 1.5 8 MiB/s

Bytes transferred = 671788 8355840 (a402c 7f8000 hex)u-boot=> run mmc_updatemmc dev 2

mmc2(part 0) is current device (eMMC) MMC write: dev # 2, block # 2, count 1313 ... 1313 blocks written: OKu-boot=> run mmc_update

Load u-boot Boot binary form an <code>SD</code> card:

=> fatload mmc 01:1 ${loadaddr} sdvx-1.0.1_mx6dlaxel_u-bootflash.imxbinreading sdvx-fatload mmc 1:1${loadaddr} flash.0.1_mx6dlaxel_u-boot.imxbin671788 8355840 bytes read in 50 373 ms (1221.8 4 MiB/s)u-boot=> mmc dev 2

mmc2(part 0) is current device (eMMC)u-boot=> run mmc_updateswitch to partitions #0, OKmmc2(part 0) is current device (eMMC) MMC write: dev # 2, block # 2, count 1313 ... 1313 blocks written: OK

We assume that the The following environment variables are present has to be set (or at least checked) in u-boot; depending on the formatted eMMC partition (<code>FAT32</code> or <code>ext4</code>), the vars has to be properly modified:

setenv mmc_loadk='fatload mmc ${mmcdev}:1 ${loadaddr} ${bootfile}'setenv mmc_loadfdt='fatload mmc ${mmcdev}:1 ${fdtaddrfdt_addr} ${fdtfilefdt_file}'setenv mmc_loadsplash='fatload mmc ${mmcdev}:1 ${loadaddr} ${splashfile}; cp.b ${loadaddr} ${splashimage} ${filesize}'</pre> mmcboot=run mmcargs addcons addmisc; if run === ext4 ====<pre>setenv mmc_loadk; then if run 'ext4load mmc ${mmcdev}:1 ${loadaddr} ${bootfile}'setenv mmc_loadfdt'ext4load mmc ${mmcdev}:1 ${fdt_addr} ${fdt_file}'setenv mmc_loadsplash 'ext4load mmc ${mmcdev}:1 ${loadaddr} ${splashfile}; then if run configid_fixupfdt; then bootm cp.b ${loadaddr} - ${fdtaddrsplashimage}; fi; fi; fi${filesize}'

Then, u-boot uses the previous previously listed commands for reading the binary images and starting the linux Linux bootstrap from the ''MMC part 2'' (which is reserved for the root-file system storage). The following u-boot environment variables are present for this purposes:

setenv mmcboot 'run mmcargs addcons addmisc; if run mmc_loadk; then if run mmc_loadfdt; then if run configid_fixupfdt; then bootm ${loadaddr} - ${fdtaddr}; fi; fi; fi'setenv mmcargs='setenv bootargs root=${mmcroot}'setenv mmcroot='/dev/mmcblk2p2 rootwait rw'saveenv

=> setenv bootfile sdvx-1.0.1_lite_uImageImage=> setenv fdtfile sdvx-1.0.1_lite_imx6dlfdt_file imx8mp-sdv03mito8mplus-cb002acb1001.dtb

=== Program root file system into NAND flash eMMC === * Boot the system via SD or NFS as described in the e [[(<KIT>)#Quick_start_guide|Quick start guide]]* By default, the NAND is already partitioned to allow booting from NAND-only (see next section) and, thus, some partitions are reserved for u-boot and kernel images. Here we won't modify this default configuration. The [[Memory Tecnology Device (MTD)|MTD]] partitions can be dumped with <code>/proc/mtd</code> (the partition's name should be self-explanatory)<pre class="workstation-terminal">root@sdvx-lite:~# cat /proc/mtddev: size erasesize namemtd0: 00800000 00020000 "nand-uboot"mtd1: 00100000 00020000 "nand-env1"mtd2: 00100000 00020000 "nand-env2"mtd3: 00100000 00020000 "nand-fdt"mtd4: 00100000 00020000 "nand-spare"mtd5: 00800000 00020000 "nand-kernel"mtd6: 00600000 00020000 "nand-splash"mtd7: 3e600000 00020000 "nand-ubi"root@sdvx-lite:~# </pre> {{ImportantMessage|text=Please note that MTD partition index may change depending of flash device availability, flash device size, u-boot environment variables or kernel device driver load order. Always take care of looking inside <code>/proc/mtd</code> to match your specific layout}}  * Format and initialize ''nand-ubi'' partition, which in our case is <code>mtd7</code>, using [[Memory Tecnology Device (MTD)#UBI|UBI]] with: <pre>ubiformat /dev/mtd7ubiattach -m 7ubimkvol /dev/ubi0 -N rootfs -m</pre> E.g. <pre class="workstation-terminal">root@sdvx-lite:~# ubiformat /dev/mtd7ubiformat: mtd7 (nand), size 1048576000 bytes (1000.0 MiB), 8000 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 byteslibscan: scanning eraseblock 7999 -- 100 % completeubiformat: 8000 eraseblocks have valid erase counter, mean value is 1ubiformat: formatting eraseblock 7999 -- 100 % completeroot@sdvx-lite:~# ubiattach -m 7[ 1714.823600] UBI: attaching mtd7 to ubi0[ 1726.415587] UBI: scanning is finished[ 1726.483765] UBI: attached mtd7 (name "nand-ubi", size 1000 MiB) to ubi0[ 1726.491062] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes[ 1726.498301] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048[ 1726.505030] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096[ 1726.512430] UBI: good PEBs: 8000, bad PEBs: 0, corrupted PEBs: 0[ 1726.518861] UBI: user volume: 0, internal volumes: 1, max. volumes count: 128[ 1726.526025] UBI: max/mean erase counter: 3/2, WL threshold: 4096, image sequence number: 623070258[ 1726.535433] UBI: available PEBs: 7836, total reserved PEBs: 164, PEBs reserved for bad PEB handling: 160[ 1726.545260] UBI: background thread "ubi_bgt0d" started, PID 714UBI device number 0, total 8000 LEBs (1015808000 bytes, 968.8 MiB), available 7836 LEBs (994983936 bytes, 948.9 MiB), LEB size 126976 bytes (124.0 KiB)root@sdvx-lite:~# ubimkvol /dev/ubi0 -N rootfs -mSet volume size to 994983936Volume ID 0, size 7836 LEBs (994983936 bytes, 948.9 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1</pre> * Now mount the UBI volume using [[Memory Tecnology Device (MTD)#UBIFS|UBIFS]] in a temporary directory <pre>mkdir -p /mnt/nandmount -t ubifs ubi0_0 /mnt/nand</pre> E.g.: <pre class="workstation-terminal">root@sdvx-lite:~# mkdir -p /mnt/nandroot@sdvx-lite:~# mount -t ubifs ubi0_0 /mnt/nand[ 1810.301461] UBIFS: default file-system created[ 1810.308952] UBIFS: background thread "ubifs_bgt0_0" started, PID 717[ 1810.452274] UBIFS: mounted UBI device 0, volume 0, name "rootfs"[ 1810.459421] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes[ 1810.469398] UBIFS: FS size: 992698368 bytes (946 MiB, 7818 LEBs), journal size 33521664 bytes (31 MiB, 264 LEBs)[ 1810.480976] UBIFS: reserved for root: 4952683 bytes (4836 KiB)[ 1810.487210] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 99D0F3C6-5955-4B30-9E2D-72202281BD30, small LPT model</pre> * you can now extract the root file system into that directory <pre>tar xvjf sdvx-1.0.1_image-devel-sdvx-lite.tar.bz2 -C /mnt/nand</pre> * finally, you need to cleanly umount and detach the MTD partition

<pre>umount /mnt/nand/ubidetach -m 7</pre> E.g. <pre class="workstation-terminal">root@sdvx-lite:~# umount /mnt/nand/[ 2446.743091] UBIFS: un-mount UBI device 0, volume 0[ 2446.749670] UBIFS: background thread "ubifs_bgt0_0" stopsroot@sdvx-lite:~# ubidetach -m 7[ 2450.738153] UBI: detaching mtd7 from ubi0[ 2450.759527] UBI: mtd7 is detached from ubi0</pre> You can now safely reboot or turn off the system. In U-Boot environment check the following variable, which must contain the same MTD partition number used above <pre>nand_args=setenv bootargs root=ubi0:rootfs rootfstype=ubifs rw ubi.mtd=7</pre> === Program root file system into eMMC flash === * Boot boot the system via SD or NFS as described in the e [[(<KIT>)#Quick_start_guideDESK-MX8M-L/General/Booting_from_NFS|Quick start guideBooting from NFS]]

==== FAT32 partition Partitioning ====

{ echo ${boot_start},${boot_size},0c'''83''',-; echo ${rfs_start},${rfs_size},83,-; } | sfdisk --force ${node}

mkfs.vfat ext4 -F 32 -n boot ${node}${part}1-Lboot

SD total size: 3776KB[ 1341.905014] mmcblk2: p1 p2..Checking that no-one is using this disk right now ... OK

root@sdvx-lite:/mnt/emmc# cp /tftpboot/sdvx/linuxdesk-mx-l/sdvx-1.0.1*dtb .root@sdvx-lite:/mnt/emmc# cp /tftpboot/sdvxdesk-mx-l/linux/sdvx-1.0.1*uImage Image .root@sdvx-lite:/mnt/emmc# cp /tftpboot/sdvx/linuxdesk-mx-l/splash_image.bmp .

root@sdvxdesk-litemx8mp:~# mount /dev/mmcblk2p2 /mnt/emmc[ 1810 27.899327437492] EXT4-fs (mmcblk2p2): mounting ext3 file system using the ext4 subsystem[ 27.455201] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)root@sdvxdesk-litemx8mp:~# cd /mnt/emmc/root@sdvxdesk-litemx8mp:/mnt/emmc#

tar xvjf sdvxdave-1.0.1_imageimage-devel-sdvxdesk-litemx8mp.tar.bz2

root@sdvxdesk-litemx8mp:/mnt/emmc# cdroot@sdvxdesk-litemx8mp:~# umount /mnt/emmcroot@sdvxdesk-litemx8mp:~# reboot

u-boot=> setenv bootcmd run mmcboot=> saveenv</pre> ==== ext4 partition ====For using an <b>ext4</b> partition also for boot files, it is possibile to change the formatting script:  { echo ${boot_start},${boot_size},'''83''',-; echo ${rfs_start},${rfs_size},83,-; } | sfdisk --force ${node} and formatting the first partition using ''mkfs.ext4''  mkfs.ext4 -F ${node}${part}1 -Lboot then, the u-boot <code>environment</code> has to be properly configured: <pre class="workstation-terminal">=> setenv mmc_loadk 'ext4load mmc ${mmcdev}:1 ${loadaddr} ${bootfile}'=> setenv mmc_loadfdt 'ext4load mmc ${mmcdev}:1 ${fdtaddr} ${fdtfile}'=> setenv mmc_loadsplash 'ext4load mmc ${mmcdev}:1 ${loadaddr} ${splashfile}; cp.b ${loadaddr} ${splashimage} ${filesize}'=> saveenv

[[Category:ORCA]] [[Category:MITO 8M Mini]]