I tried to install Tow Boot on SPI memory, but as I said, Tow Boot on SPI does not detect the encrypted SDcard. Then I replaced the encrypted SDcard with the Tow Boot SDcard containing, rebooted and overwritten the SPI memory.įinally, I replaced the Tow Boot SDcard with the encrypted SDcard, and when I restarted, everything was working normally. # dd if= of=/dev/mmcblk2 bs=1M oflag=direct conv=fsync # dd if= of=/dev/mmcblk2 bs=1M oflag=direct,sync status=progress # /dev/mmcblk2 is internal emmc memory. Perhaps due to the abnormal boot, I was unable to use dd with the options given in the documentation.
Then, I plugged the USB key into the faulty computer, and I started it with the encrypted SDcard to arrive at the emergency shell.
U boot splash archive#
Choose the pinebookPro version.Īssume the latest version is $ wget # download archive On another computer, download the latest version of Tow Boot at. However, when Tow Boot is installed on the SPI, I have exactly the same problem as with U-Boot: the system does not detect the encrypted partition on the SD card, it does not detect the SD card at all (no /dev/mmcblk1), booting is impossible and I get into an emergency shell. I installed Tow Boot on the emmc which solved the problem.
U boot splash pro#
However, it is necessary to check on U-Boot is installed on the emmc or SD card, before overwriting the SPIFlash memory, otherwise the Pinebook pro will not restart.įor this I can, “short pin 6 of the SPI flash to GND and boot” and see if the pinebook pro reboots. It is therefore possible to deactivate SPIFlash by overwriting the memory (software deactivation) Run rkdeveloptool rd to reboot your Pinebook Pro.If successful, output should read Reset Device OK. Test the installation: rkdeveloptool td.If successful, the output should read: Write LBA from file (100%). Flash the new SPI binary: rkdeveloptool wl 0 zero.bin.If successful, the output should read Downloading bootloader succeeded. Flash the flash helper db file: rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin.Create the binary file dd if=/dev/zero of=zero.bin bs=1M count=16.To do that, you follow the same steps above to enter maskrom mode and then write a binary file that consists of all zeros. In case, you wrote something bad to your SPI, it’s helpful to wipe away that data with zeros. I can disable the SPIFlash to try to start U-Boot on the emmc or on the SD card (hardware deactivation).This version of U-Boot is unsuitable for SPIFlash.manjaro-arm-installer presumably installed U-Boot on SPIFlash when installing Manjaro on the emmc.This is expected to change, as there are people working on issue. At present, April 19th, 2020, there is no good bootloader image to flash into the SPI flash device. The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware. This will render the SoC bootrom unable to read from the SPI flash and have it fall back to reading the bootloader from other boot media like the eMMC or Micro SD card. ARM/ARM64 computers do not have a standardized BIOS, yet.Įven if you need to recover from a defective bootloader written to the SPI flash, you can simply short pin 6 of the SPI flash to GND and boot. So the SoC moves on to the next potential boot device, the eMMC. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. I deduce that U-Boot is loaded from the SPIFlash memory, and not from the emmc. I also wish to know if these commands would make all the data on mmcblk2 inaccessible, or if this operation would just replace u-boot without touching the rest. I wish confirmation that the indications contained in uboot-pinebookpro.install are correct. I wish confirmation that the problem came from u-boot. # dd if=/boot/b of=/dev/mmcblkX seek=16384 conv=notrunc,fsync # dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc,fsync You can do that by running these two commands: I found the uboot-pinebookpro page on manjaro’s gitlab, and in the uboot-pinebookpro.install file it says: New version of U-Boot firmware can be flashed to your microSD card (mmcblk1) I asked for help on, and wdt replied that u-boot was at fault and that it had to be replaced. On the emergency shell, it is possible to boot a dysfunctional operating system on a USB key, without wifi and without kernel modules.
0 kommentar(er)
