This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

大家都是怎么格式化emmc芯片的?能在ADB SHELL 中操作吗?uboot 就实现了GPT分区和烧录功能

Other Parts Discussed in Thread: DM3730

大家都是怎能格式化emmc芯片的,我用DM3730芯片。用的是2.3.4代码 ,kernel是2。6.37  。系统外部sd启动是可以的,我加入了emmc芯片,我在uboot下分区,在uboot下把EXT4文件系统拷贝到其中的分区,我是参考这个链接做的emmc操作    59.124.231.13/.../Android_gingerbread_eMMC_booting

我看有人是在ANDROID系统下格式化EMMC,在系统下格式化emmc的命令都不识别,请问那要怎么操作亚。linux的命令在android下都不识别。格式化、修复emmc的命令在ADB SHELL中都不支持

59.124.231.13/.../Android_gingerbread_eMMC_booting   这个链接是在 UBOOT下分区emmc,和实现烧录,但是别的命令如擦除命令都没实现。在host机做各个IMG文件,然后再mkfs.ext4   格式化IMG文件,在UBOOT下烧录到emmc的各个分区。

制作system。img文件是这样的  :

$cd <YOUR_PATH>/images
/* creating 250MB, it can be configure as per need */
$dd if=/dev/zero of=./system.img bs=1M count=250
$mkfs.ext4 system.img
$mkdir mnt-point
$sudo mount -t ext4 -o loop system.img mnt-point/
$cp -rfp <ANDROID_SOURCE>/out/target/product/omap3evm/system/* mnt-point/
$sudo umount mnt-point


这样操作做的system.img 文件,有250M,系统不识别,当bs=1M count=30  时,可以识别,但这太小不能用

bd2/journal.c JBD: no valid journal superblock found
[    7.316619] JBD: unrecognised superblock format ID
[    7.327758] JBD: Journal too short (blocks 0-0).
[    7.332611] JBD: recovery failed
[    7.335998] EXT4-fs (mmcblk1p6): error loading journal

我 后来用./make_ext4fs -s -l 512M -a system system_new.img system   命令产生system.img文件,但是用DUMPE2FS命令查看,说是没有超级块。我把 -s选项去掉了,有超级块,烧录后,系统mount时出现新的错误

EXT4-fs error (device mmcblk1p6): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 27955 in gd
Aborting journal on device mmcblk1p6-8.
EXT4-fs (mmcblk1p6): Remounting filesystem read-only
EXT4-fs error (device mmcblk1p6) in ext4_reserve_inode_write:5641: Journal has aborted
EXT4-fs error (device mmcblk1p6) in ext4_evict_inode:215: Journal has aborted

  • 在ADB SHELL 中可以执行fdisk 命令,我执行后   ,我开始在下分区EFI    GPT, 但是在系统中MOUNT有问题,请问我用sd启动进入到系统中了,怎么用FDISK分区emmc芯片亚

    我要划分为这样的分区 大家有链接,给我也好

    static struct partition partitions[] = {
        { "-", 128 },
        { "xloader", 128 },
        { "bootloader", 512 },
        /* "misc" partition is required for recovery */
        { "misc", 128 },
        { "-", 384 },
        { "recovery", 8*1024 },
        { "boot", 8*1024 },
        { "system", 256*1024 },
        { "cache", 32*1024 },
        { "userdata", 32*1024},
        { "media", 0 },
        { 0, 0 },
    };
    



     fdisk -l /dev/block/mmcblk1

    Disk /dev/block/mmcblk1: 7847 MB, 7847542784 bytes
    256 heads, 63 sectors/track, 950 cylinders
    Units = cylinders of 16128 * 512 = 8257536 bytes

                  Device Boot      Start         End      Blocks  Id System
    /dev/block/mmcblk1p1               1      266306  2147483647+ ee EFI GPT
    Partition 1 has different physical/logical beginnings (non-Linux?):
         phys=(1023, 255, 63) logical=(0, 0, 2)
    Partition 1 has different physical/logical endings:
         phys=(1023, 255, 63) logical=(266305, 4