02-08-2018, 10:11 AM
Ok, so I tried something else.
I decided to use the emmc jumper method to copy directly onto my emmc module... but I have no serial console (so, it's tricky !!!)
After many tries, I finally see my /dev/mmcblk0 in the fdisk -l.
So, I use the curl command to directly copy the stretch-minimal image onto the /dev/mmcblk0 device. Everything's fine.
Before rebooting, i just typed a fdisk -l to see... and I saw a red warning :
I tried to do a fdisk /dev/mmcblk0 then a "w" but the system replies :
I decided to reboot (properly) onto the emmc. At the reboot, I get many error messages like :
After rebooting (with the jumper interrupt method) I tried again, then I tried with a dd command to flash the image. It gives me a input / output error. Unable to write an image with the dd command...
In fact, it's like something was wrong with this module, maybe some defectuous blocks or something else ?
What do you think about this ?
EDIT : last thing : after the curl command, as I do a fdisk -l I saw :
- the mmcblk1 with its 7 partitions
- the mmcblk0 with its 7 partitions (and the red warning about PMBR)
- Two others devices : mmcblk0boot0 and mmcblk0boot1
Are these Two others devices normal ?
I decided to use the emmc jumper method to copy directly onto my emmc module... but I have no serial console (so, it's tricky !!!)
After many tries, I finally see my /dev/mmcblk0 in the fdisk -l.
So, I use the curl command to directly copy the stretch-minimal image onto the /dev/mmcblk0 device. Everything's fine.
Before rebooting, i just typed a fdisk -l to see... and I saw a red warning :
Code:
PMBR size mismatch (4458495 !=30310399) will be corrected by w(rite)
I tried to do a fdisk /dev/mmcblk0 then a "w" but the system replies :
Code:
fdisk : failed to write disklabel; Argument invalide
Code:
dwmmc_rockchip ff520000.rksdmmc: All phases work, using default phase 0.
dwmmc_rockchip ff520000.rksdmmc: Unexcpected command timeout, state 3.
mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
mmcblk0: error -110 transferring data, sector 267672, nr 8, cmd response 0x900, card status 0x0
mmcblk0: retrying using single block read
retrying because a re-tune was needed
In fact, it's like something was wrong with this module, maybe some defectuous blocks or something else ?
What do you think about this ?
EDIT : last thing : after the curl command, as I do a fdisk -l I saw :
- the mmcblk1 with its 7 partitions
- the mmcblk0 with its 7 partitions (and the red warning about PMBR)
- Two others devices : mmcblk0boot0 and mmcblk0boot1
Are these Two others devices normal ?