11-20-2019, 01:05 AM
(11-19-2019, 10:49 AM)martinayotte Wrote: If booting SD allows you to see /dev/mmcblk2, but you are unable to do "fdisk /dev/mmcblk2", there is maybe an hardware issue.
What do you see doing "dmesg | grep mmc" ?
Quote:# dmesg |grep mmc
dmesg |grep mmc
[ 2.600060] sunxi-mmc 4020000.mmc: Got CD GPIO
[ 2.625463] sunxi-mmc 4020000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[ 2.626861] sunxi-mmc 4021000.mmc: allocated mmc-pwrseq
[ 2.661362] mmc0: host does not support reading read-only switch, assuming write-enable
[ 2.663300] mmc0: new high speed SDXC card at address 0007
[ 2.664391] mmcblk0: mmc0:0007 SD64G 58.2 GiB
[ 2.665690] mmcblk0: p1
[ 2.856778] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[ 2.875136] mmc1: new high speed SDIO card at address 0001
[ 2.883469] sunxi-mmc 4022000.mmc: initialized, max. request size: 2048 KB, uses new timings mode
[ 3.364311] mmc2: new DDR MMC card at address 0001
[ 3.365596] mmcblk2: mmc2:0001 CJNB4R 58.2 GiB
[ 3.366487] mmcblk2boot0: mmc2:0001 CJNB4R partition 1 4.00 MiB
[ 3.367339] mmcblk2boot1: mmc2:0001 CJNB4R partition 2 4.00 MiB
[ 3.368442] mmcblk2: p1
[ 3.650870] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
[ 4.951199] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[ 76.012041] sunxi-mmc 4022000.mmc: data error, sending stop command
[ 77.008200] sunxi-mmc 4022000.mmc: send stop command failed
The data error stop command were emitted when I tried to access the eMMC device.
(11-19-2019, 03:29 PM)xalius Wrote: Is there maybe one of the two supply voltages for eMMC missing?
How would I check for that? Is a missing supply voltage something that would allow for partial function? It is worth noting that the android eMMC and the aosc images linked on the pine64 wiki boot fine from eMMC. So I have been operating under the assumption this was a software only problem.