DART-6UL eMMC: Difference between revisions
(Created page with "{{PageHeader|DART-6UL - eMMC}} {{DocImage|category1=DART-6UL|category2=Yocto}} __toc__ {{note| NOTE:<br>Make sure you booted from sdcard with imx6ul-var-dart-sd_emmc.dtb selec...") |
No edit summary |
||
Line 6: | Line 6: | ||
$ dmesg | grep mmcblk | $ dmesg | grep mmcblk | ||
</pre> | </pre> | ||
* Output example | * Output example: | ||
<pre> | |||
mmcblk1: mmc1:0001 MMC04G 3.52 GiB | |||
mmcblk1boot0: mmc1:0001 MMC04G partition 1 16.0 MiB | |||
mmcblk1boot1: mmc1:0001 MMC04G partition 2 16.0 MiB | |||
mmcblk1rpmb: mmc1:0001 MMC04G partition 3 128 KiB | |||
mmcblk1: unknown partition table | |||
mmcblk1boot1: unknown partition table | |||
mmcblk1boot0: unknown partition table | |||
</pre> | |||
Select the eMMC device number. Number will change if SD card is in. | Select the eMMC device number. Number will change if SD card is in. | ||
* Create partition | * Create partition |
Revision as of 07:11, 28 December 2015
Make sure you booted from sdcard with imx6ul-var-dart-sd_emmc.dtb selected
nand-recovery supports flashing of eMMC without the requirement of the process below. Just run android-emmc.sh on the command line.
- Check that the device is up.
$ dmesg | grep mmcblk
- Output example:
mmcblk1: mmc1:0001 MMC04G 3.52 GiB mmcblk1boot0: mmc1:0001 MMC04G partition 1 16.0 MiB mmcblk1boot1: mmc1:0001 MMC04G partition 2 16.0 MiB mmcblk1rpmb: mmc1:0001 MMC04G partition 3 128 KiB mmcblk1: unknown partition table mmcblk1boot1: unknown partition table mmcblk1boot0: unknown partition table
Select the eMMC device number. Number will change if SD card is in.
- Create partition
$fdisk /dev/mmcblk1 enter n p 1 <enter> <enter> w
Example of a partition root@varsomimx6:~# fdisk /dev/mmcblk1 Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that the previous content won't be recoverable.
The number of cylinders for this disk is set to 954240.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): n Command action
e extended p primary partition (1-4)
p Partition number (1-4): 1 First cylinder (1-954240, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-954240, default 954240): Using default value 954240
Command (m for help): p
Disk /dev/mmcblk1: 31.2 GB, 31268536320 bytes 4 heads, 16 sectors/track, 954240 cylinders Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk1p1 1 954240 30535672 83 Linux
Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table
mmcblk1: p1
- Format and mount
$ mkfs.ext3 /dev/mmcblk1p1 $ reboot