Mainline U-Boot with SPI, NVMe and SATA boot support
#71
(01-05-2021, 01:01 PM)jja2000 Wrote:
(01-05-2021, 10:23 AM)amiraeva Wrote:
(01-05-2021, 05:14 AM)jja2000 Wrote: I'm running into the same problem. How do I remove usb start from the preboot env variable? Booting timeout is on 0 so I don't have the chance to mash any keys.
If I'm not mistaken, even with a timeout of 0 - there is a narrow window to stop the automatic boot process. Just had to mash keys in the UART console right as you turn your SBC on. At least that's how I was able to muck around in the uboot console.
I read that you could use escape in UART yes, I was hoping that I could do it through the videoconsole too. Time to bust out the CP2102 then Tongue

If you do have "usb start" in the preboot env variable, the USB system will be init'ed when U-Boot starts. So then after you see messages about USB starting, you can hit Ctrl-C on the USB keyboard repeatedly until you've cancelled all the attempts to boot from MMC, network and so on, and you should hopefully arrive at the U-Boot prompt, allowing keyboard interaction.
  Reply
#72
(08-02-2020, 09:00 PM)Mentaluproar Wrote:
(07-26-2020, 05:20 PM)belfastraven Wrote:
(07-26-2020, 05:33 AM)sigmaris Wrote: I've made another build based on 2020.07 using this branch, with a couple of additional patches:

Patch from Tian Yuanhao which allows compressed (gzip, etc) kernels to be loaded. No need to gunzip the default arm64 kernels to load them with u-boot anymore.
Patch from Jagan Teki which is supposed to enable USB-3 support on the USB-3.0 type A port. When testing this with the one USB-3 disk drive I have, it didn't seem to work, the disk drive wasn't detected in the USB-3.0 port. I'd be interested to hear if anyone else has success in using USB-3.0 devices in USB-3.0 mode with this. Note the USB Type C port is configured as OTG mode by default in the DTS, and so won't be used as a host port, so only the Type A port should be used for USB-3.0.

Build artifacts for MMC and SPI installation from this branch can be found here.
This works fine for me with USB3--  I  have attached the u-boot logs from booting a SANDISK extreme stick and then a Samsung portable ssd T150.  I was booting from SPI .  I also booted my NVME,  which I removed in order to boot the other devices,  since that is first in the boot order.   When not booting from the USB3,  the kernel recognizes the USB3 devices, just FYI.   Is there anything in particular I could do to help you debug your issue?
Opposite experience for me here.  I did a fresh install of manjaro on a USB flash drive, ran all the updates and then installed from the link above.  Sata boot still works, but this breaks USB boot.  Not even USB2 boots properly now.  Both stick at "Booting using fdtblob at 0x1f0000000"

Was seeing this on the screen something we could have turned on before?  I prefer it to the blindly waiting for the OS to load.

Hi, could you or someone resolve this "Booting using fdtblob at 0x1f0000000" somehow?
I got the same with latest Armbian_21.02.3_Rockpro64_focal_current_5.10.21.img.xz and U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000))
Code:
U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 2 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
Card did not respond to voltage select!

Device 0: unknown device
scanning bus for devices...
Target spinup took 0 ms.
SATA link 1 timeout.
SATA link 2 timeout.
SATA link 3 timeout.
SATA link 4 timeout.
AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode
flags: 64bit ncq stag pm led clo pmp fbss pio slum part ccc apst boh
  Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
            Type: Hard Disk
            Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)

Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
            Type: Hard Disk
            Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)
... is now current device
Scanning scsi 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 9 ms (344.7 KiB/s)
## Executing script at 00500000
Boot script loaded from scsi 0
166 bytes read in 8 ms (19.5 KiB/s)
15335962 bytes read in 254 ms (57.6 MiB/s)
28582400 bytes read in 463 ms (58.9 MiB/s)
75809 bytes read in 19 ms (3.8 MiB/s)
2698 bytes read in 15 ms (174.8 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15335898 Bytes = 14.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
  Reply
#73
(03-14-2021, 03:48 AM)mdesign Wrote: Hi, could you or someone resolve this "Booting using fdtblob at 0x1f0000000" somehow?
I got the same with latest Armbian_21.02.3_Rockpro64_focal_current_5.10.21.img.xz and U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000))
Code:
U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 2 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
Card did not respond to voltage select!

Device 0: unknown device
scanning bus for devices...
Target spinup took 0 ms.
SATA link 1 timeout.
SATA link 2 timeout.
SATA link 3 timeout.
SATA link 4 timeout.
AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode
flags: 64bit ncq stag pm led clo pmp fbss pio slum part ccc apst boh
  Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
            Type: Hard Disk
            Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)

Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
            Type: Hard Disk
            Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)
... is now current device
Scanning scsi 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 9 ms (344.7 KiB/s)
## Executing script at 00500000
Boot script loaded from scsi 0
166 bytes read in 8 ms (19.5 KiB/s)
15335962 bytes read in 254 ms (57.6 MiB/s)
28582400 bytes read in 463 ms (58.9 MiB/s)
75809 bytes read in 19 ms (3.8 MiB/s)
2698 bytes read in 15 ms (174.8 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15335898 Bytes = 14.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000

I think you're encountering the same problem, where U-Boot starting USB before boot will cause booting the kernel to hang.

I noticed that Debian has disabled starting USB in U-Boot preboot (https://bugs.debian.org/cgi-bin/bugrepor...bug=973323), I haven't seen this problem on my RockPro64 board but enough other people have reported issues with USB that I decided to make another release, updating to be based on v2021.01, with starting USB disabled in preboot: https://github.com/sigmaris/u-boot/relea...ckpro64-ci

Try that and see if it fixes the issue (though it will sacrifice the use of USB keyboard in U-Boot).
  Reply
#74
I'm currently experiencing problems booting the latest Armbian release on my rockpro64 from eMMC.
I just hangs like you can see on the photo on the first comment in this forumthread:
https://forum.armbian.com/topic/14724-ro...-v44-does/

Would this u-boot also solve that problem? Currently booting from SDCard but would prefer eMMC of course.
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  PCIe Armbian and Ayufan for nvme ssd LMM 1 330 02-03-2021, 04:38 PM
Last Post: LMM
  Camera sensor support on MIPI lines abhimanyu_gr 0 254 01-22-2021, 09:23 AM
Last Post: abhimanyu_gr
  unable to boot from SDCard Charles Tarkowski 4 773 12-16-2020, 11:11 AM
Last Post: Charles Tarkowski
  Rockpro64 boot issues larsgn 14 6,239 10-21-2020, 07:54 AM
Last Post: quinterro
  fan continously runs on kernel 5.8 but I need to use 5. kernel for PCIe sata card GreyLinux 4 1,246 10-20-2020, 10:52 AM
Last Post: GreyLinux
  RockPro64 SSD Expansion Board/SATA Shield as0zial 5 1,970 10-18-2020, 08:05 PM
Last Post: revoman
  RockPro64 eMMC boot euu 4 2,368 08-24-2020, 11:07 PM
Last Post: t4_4t
  4pin Connector for dual SATA m.ekstrom 4 1,848 07-28-2020, 07:07 AM
Last Post: mabs
  RockPro64 so problematic! Boot issues PorterDon 1 1,251 06-04-2020, 12:25 PM
Last Post: dukla2000
  Failure to boot atcwells 1 1,065 05-10-2020, 03:06 PM
Last Post: atcwells

Forum Jump:


Users browsing this thread: 2 Guest(s)