boot priority - has precedence changed?
#1
How to install and boot ROCK64 from eMMC? - https://forum.pine64.org/showthread.php?tid=4713
    shows
boot priority:
eMMC--> SPI flash-->  SD card

But, with both eMMC and microSD installed, I am seeing my Rock64 boot to microSD. How can this be?

1. Has the priority of the devices changed generally for the Rock64, or is it just my unit?
2. Does one of the devices boot directly, i.e. not use/require the SPI flash?
3. I found the following.
    Flashing and Erasing the SPI - https://github.com/ayufan-rock64/linux-b...ash-spi.md
Traditionally, booting Linux on the ROCK64 required an eMMC or microSD card, however it is now possible to boot without those, assuming the SPI memory has been flashed. The ROCK64 contains an onboard 128Mbit SPI flash memory, which can be flashed with U-Boot in order to provide additional boot options:
    USB2 / USB3 drive
    PXE
    microSD
    eMMC
Boot order:
  1. SPI flash
  2. eMMC (disable with jumper)
  3. microSD
  4. USB drive
  5. PXE
This suggests that SPI must come first.
Can anyone comfirm the functioning of this u-boot?
Could someone point me to a pertinent thread for this u-boot?

4. How may I restore the original SPI flash?
  Reply
#2
You are mixing many "boot" phases.

  1. Bootrom phase booting order is "eMMC, SPI Nor Flash, SDMMC card, USB OTG". See RK3328TRM page 14 and can be "changed" only by killing device (like installing jumper that force GND to eMMCCLK signal).
    Bootrom phase search valid "ID magic" and load/run sequentially DDR.bin,TPL.bin, SPL.bin and U-Boot.bin binaries.
  2. U-Boot phase order is determined by "bootcmd" script that uses "boot_targets" variable with "mmc0 mmc1 usb0 pxe dhcp" (mmc# can be SDCARD or eMMC it depends on dts for u-boot). eMMC can still be killed by jumper.
  3. Kernel phase chooses kernel from extlinux.conf (now on root ext4 /boot/extlinux/extlinux.conf and NOT on efi partition /extlinux/extlinux.conf).

So check, change and save U-Boot variable "boot_targets" to change order for U-Boot phase in your U-Boot variables from chosen from Bootrom phase (eMMC in your case).
Default SPI flash is empty.
I left this community in Aug 2019 due to PINE64 refusal to produce/deliver ROCK64-1G version 3 after more than one year of changing statuses to "planning", "evaluating", "releasing", "availability", "estimated availability" and finally "no schedule" Angry. ROCK64 is dead platform without any advantage. Buy Raspberry PI 4 !
Away
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Bug u-boot (forks) status mcerveny 6 777 9 hours ago
Last Post: ayufan
  doesn't boot, no video cjyar 6 153 09-17-2019, 12:41 PM
Last Post: cjyar
  Unable to boot from SPI stevefan1999 4 740 05-01-2019, 04:47 PM
Last Post: rhens1
  No Boot, Red Green and White flash at 1 sec intervals wesleykonrad 2 278 01-28-2019, 11:54 PM
Last Post: wesleykonrad
  Enable I2C, I2s, SPI in boot-config file? HelgeMK 3 1,551 08-14-2018, 10:59 AM
Last Post: pas059
  New ROCK64 doesn't boot p3ntium 18 1,344 06-03-2018, 06:06 PM
Last Post: Rocklobster
  boot logs shows chinese ip trying to login ssh i69fstop 6 460 06-02-2018, 07:25 PM
Last Post: Z80
  Boot Problems, LEDs lit continuously Facecreator 22 2,737 05-14-2018, 10:24 PM
Last Post: pfeerick
  No boot at all Arkadiusz 4 812 04-18-2018, 08:48 PM
Last Post: pfeerick
  Rock64 does not boot - SPI problem [resolved] csharpy 7 2,193 03-21-2018, 09:34 PM
Last Post: pfeerick

Forum Jump:


Users browsing this thread: 1 Guest(s)