11-30-2019, 12:06 AM
(This post was last modified: 11-30-2019, 12:08 AM by Arwen.
Edit Reason: Removed in-correct indenting and redundant line
)
When I ordered my Pinebook Pro, I considered recovery too. So I made a separate order for the eMMC USB adapter.
That way, using another computer, I can wipe the eMMC image. Re-install the eMMC in the Pinebook Pro. Then, on boot, the RK3399 will automatically attempt to boot the SPI, fail because it's empty, attempt to boot the eMMC, fail again because it's empty. Last, boot the SD card.
All that said, it may be possible to un-bind the device for the eMMC and re-bind it. In essence, when you flipped the switch, the SoC thought there was no eMMC on the board, so it moved on to the SD card. If you did not flip the switch back fast enough, the OS on the SD card won't detect the eMMC either. So no device driver and no way to write a new image to the eMMC. Catch-22 as they say.
I have rough instructions on how to un-bind and re-bind a device. But, that was for my SD card on an x64 miniature PC. Similar concept.
You could try this;
You can verify that this is the correct driver and path using something like this;
I take no responsibilty for this procedure. It's un-tested as I have not opened my Pinebook Pro yet. (Nor do I have my second eMMC for my ROCKPro64 to test the concept there.)
Note: The "fe310000.dwmmc" device is likely the SDIO used for WiFi.
That way, using another computer, I can wipe the eMMC image. Re-install the eMMC in the Pinebook Pro. Then, on boot, the RK3399 will automatically attempt to boot the SPI, fail because it's empty, attempt to boot the eMMC, fail again because it's empty. Last, boot the SD card.
All that said, it may be possible to un-bind the device for the eMMC and re-bind it. In essence, when you flipped the switch, the SoC thought there was no eMMC on the board, so it moved on to the SD card. If you did not flip the switch back fast enough, the OS on the SD card won't detect the eMMC either. So no device driver and no way to write a new image to the eMMC. Catch-22 as they say.
I have rough instructions on how to un-bind and re-bind a device. But, that was for my SD card on an x64 miniature PC. Similar concept.
You could try this;
Code:
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bindCode:
root@Debian-Desktop:~# readlink /sys/block/mmcblk1
../devices/platform/fe330000.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1
root@Debian-Desktop:~# ls /sys/bus/platform/drivers/sdhci-arasan/
bind fe330000.sdhci uevent unbind
root@Debian-Desktop:~# readlink /sys/block/mmcblk0
../devices/platform/fe320000.dwmmc/mmc_host/mmc0/mmc0:59b4/block/mmcblk0
root@Debian-Desktop:~# ls /sys/bus/platform/drivers/dwmmc_rockchip/
bind fe310000.dwmmc fe320000.dwmmc uevent unbindNote: The "fe310000.dwmmc" device is likely the SDIO used for WiFi.
--
Arwen Evenstar
Princess of Rivendale
Arwen Evenstar
Princess of Rivendale