I bought a m2u and am having a hard time to get things up and running. I have tried all images and the only image that boot up from a sd card is the old debian lite version: https://drive.google.com/file/d/0B_YnvHgh2rwjS0NXakYtS3VQQk0/view
After booting I do not see a device called: /dev/mmcblk1 Also fdisk -l only shows the sd card.
Now my question is: Is my eMMC chip defect or am I doing something wrong?
You should try flashing anything after the date 11/29. Also if your not using and LCD make sure to get the image without LCD in the title. I hope this helps.
Perhaps I mentioned it not clearly, but all the other images won’t boot. I have just retried the last Debian version (again) : https://docs.google.com/uc?id=0B_YnvHgh2rwjR0p6WVUwbU5JcVk&export=download and this image start with a BPI logi and then it’s getting a kernell panic and reboots after about 10 seconds. I will try to capture the error over the UART perhaps this explains something.
Any other ideas?
No I don’t have much to help you with but if /dev/mmcblk1 isn’t listed I’d contact Bpi right away anyways.
HI: Please update BPI-M2Ultra firmware. And try it
Just updated with with the bpi-tool. cat /proc/version is now saying: Linux version 3.10.65-BPI-M2U-Kernel (root@62ace36efaf0) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #5 SMP Tue Nov 29 03:11:02 UTC 2016
Still no eMMC device /dev/mmcblk1 is found on my board.
Can anybody check the output of “mmc info” and “mmc list” in U-boot? You’ll have to hit a key while booting. My output is:
IoT# mmc info Device: SUNXI SD/MMC Manufacturer ID: 27 OEM: 5048 Name: SD4GB Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 3.7 GiB Bus Width: 4-bit IoT# mmc list SUNXI SD/MMC: 0
I do not understand the output of mmc list… mmc rescan gives: IoT# mmc rescan [mmc]: 50 MHz… [mmc]: sample: 53 - 188(ps) [mmc]: 100 MHz… [mmc]: sample: 26 - 192(ps) [mmc]: 200 MHz… [mmc]: sample: 13 - 192(ps) [mmc]: media type 0x0 [mmc]: Wrong media type 0x0 [mmc]: Try SD card 0 [mmc]: mmc 0 cmd 8 timeout, err 100 [mmc]: smc 0 err, cmd 8, RTO [mmc]: mmc 0 close bus gating and reset [mmc]: mmc 0 mmc cmd 8 err 0x00000100 [mmc]: mmc send if cond failed [mmc]: mmc 0 cmd 55 timeout, err 100 [mmc]: smc 0 err, cmd 55, RTO [mmc]: mmc 0 close bus gating and reset [mmc]: mmc 0 mmc cmd 55 err 0x00000100 [mmc]: send app cmd failed [mmc]: Try MMC card 0 [mmc]: mmc 0 cmd 1 timeout, err 100 [mmc]: smc 0 err, cmd 1, RTO [mmc]: mmc 0 close bus gating and reset [mmc]: mmc 0 mmc cmd 1 err 0x00000100 [mmc]: read op condition failed [mmc]: mmc send op cond failed Card did not respond to voltage select! [mmc]: SD/MMC 0 init error!!! [mmc]: erase_grp_size : 0x1WrBlk*0x200=0x200 Byte [mmc]: secure_feature : 0x0 [mmc]: secure_removal_type : 0x0
Is there anything else I can try?
Hi Frank,
Thanks for your reply. I see your eMMC chip is also not showing. I have read your tests and saw you do have the /dev/mmcblk1 in your system, so probably the two commands do not show the EMMC chip of the board. Hope BPI can help me as they say it’s a software problem…
/dev/mmcblk1 is the eMMC, you can format it and mount as usual.
*If you boot from SD card
[ 2.234987] mmcblk1: mmc1:0001 8WPD3R 7.28 GiB [ 2.235202] mmcblk1boot0: mmc1:0001 8WPD3R partition 1 4.00 MiB [ 2.235384] mmcblk1boot1: mmc1:0001 8WPD3R partition 2 4.00 MiB [ 2.236883] mmcblk1: unknown partition table [ 2.239489] mmcblk1boot1: unknown partition table [ 2.240999] mmcblk1boot0: unknown partition table
I was also able to boot from eMMC with some tricks:
Filesystem Size Used Avail Use% Mounted on /dev/root 7.0G 2.8G 3.9G 42% / devtmpfs 879M 0 879M 0% /dev tmpfs 1007M 140K 1007M 1% /dev/shm tmpfs 1007M 18M 990M 2% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1007M 0 1007M 0% /sys/fs/cgroup tmpfs 202M 36K 202M 1% /run/user/1000 /dev/mmcblk0p1 120M 6.6M 114M 6% /media/ubuntu/emmcboot
See: [ 2.045284] mmcblk0: mmc1:0001 8WPD3R 7.28 GiB [ 2.045459] mmcblk0boot0: mmc1:0001 8WPD3R partition 1 4.00 MiB [ 2.045627] mmcblk0boot1: mmc1:0001 8WPD3R partition 2 4.00 MiB [ 2.047173] mmcblk0: p1 p2 [ 2.050882] mmcblk0boot1: unknown partition table [ 2.052439] mmcblk0boot0: unknown partition table
But the /dev/mmcblk1 is missing…
You can check if BOOT0 detected the eMMC. Print the output of BOOT0.
putty.log (9.1 KB) Here is a complete capture of the bootup. Hopefully it helps understanding and solving the problem.
Regards, Arnoud
Hello Arnoud,
my boot.log looks like yours. But when i use fdisk i get this.
root@bpi-iot-ros-ai:~# fdisk -l
Disk /dev/mmcblk0: 14.7 GiB, 15811477504 bytes, 30881792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0002583b
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 204800 729087 524288 256M c W95 FAT32 (LBA)
/dev/mmcblk0p2 729088 30881791 30152704 14.4G 83 Linux
Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I think that your eMMC is dead 
Any ideas how to restore mmcblk1 if somebody accidently deleted it? 
I was hopping to get rid of Android from it…well that didn’t work. What worst lsblk returns :
mmcblk0 179:0 0 29G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /media/pi/BPI-BOOT
└─mmcblk0p2 179:2 0 7G 0 part /
cat /proc/partitions returns:
major minor #blocks name
179 0 30388224 mmcblk0
179 1 262144 mmcblk0p1
179 2 7269376 mmcblk0p2
Any idea how to fix that?Isse is hight , esspecially that I receive kernel panic error during reboot or shutdown and there are another errors regarding partitions…
Hi. I don’t know if you delete it, but maybe you could try to boot from a SD and see if mmcblk1 shows up.
I’ve notice that using this image on M64 works: 2017-08-13-ubuntu-16.04-lxde-desktop-beta-aarch64-bpi-m64-sd-emmc.img
But if I use another image, the mmcblk1 seems missing, for example this one: 2018-04-17-ubuntu-16.04-mate-desktop-demo3-k4.4.89-vdpau-3-mic-docker-bpi-r18-avs-aarch64-sd-emmc.img
Regards! Gustavo.