Part Number:AM3352
Tool/software: Linux
I have custom AM3352 based board, and I have SPI flash and eMMC only (NO SD Card). How to format eMMC and create partition from target board Linux (not from HOST)?
U-boot is booting from SPI flash.
I transfer linux image from tftp and Linux is up and running.
I wanted to format my eMMC which is 2Gbytes, when I use fidsk it crashes.
Linux 4.14.40-g4796173fc5 #3 PREEMPT Mon Sep 24 21:29:38 PDT 2018 armv7l GNU/Linux
root@ am335x:/# fdisk -ul
Disk /dev/mmcblk0: 1832 MB, 1920991232 bytes, 3751936 sectors
58624 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/mmcblk0 doesn't contain a valid partition table
Disk /dev/mmcblk0boot1: 1 MB, 1048576 bytes, 2048 sectors
32 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/mmcblk0boot0: 1 MB, 1048576 bytes, 2048 sectors
32 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/mmcblk0boot0 doesn't contain a valid partition table
root@ am335x:/# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 1832 MB, 1920991232 bytes, 3751936 sectors
58624 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/mmcblk0 doesn't contain a valid partition table
root@am335x:/# fdisk /dev/mmcblk0
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 58624.
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)
Segmentation fault
and here is my boot log
cat boot.log | grep -i mmc
[ 2.833704] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
[ 2.833715] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[ 2.833734] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@48060000[0]'
[ 2.833744] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@48060000[0]'
[ 2.833751] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[ 2.833760] omap_hsmmc 48060000.mmc: lookup for GPIO cd failed
[ 2.833770] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
[ 2.833776] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[ 2.833784] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
[ 2.833792] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
[ 2.833799] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[ 2.833805] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
[ 2.994982] mmc0: new high speed MMC card at address 0001