Mainline U-Boot with SPI, NVMe and SATA boot support

Mainline U-Boot with SPI, NVMe and SATA boot support - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: General Discussion on ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=99)
+--- Thread: Mainline U-Boot with SPI, NVMe and SATA boot support (/showthread.php?tid=8685)

Pages: 1 2 3 4 5 6 7 8 9 10 11

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - jja2000 - 10-04-2020

(09-18-2020, 01:33 PM)sigmaris Wrote:
(09-17-2020, 11:45 AM)jja2000 Wrote: So from what I can tell the HDMI patch for u-boot has been merged. Is hdmi actually working now @sigmaris ? How about the usb-keyboard driver? What would need to be done to get that working?

HDMI output and USB keyboard support are both enabled in mainline U-Boot.

Very cool, excuse me for asking, but do you know how to install that version? Is there a proper repo for me to download those from?

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - voltagex - 10-18-2020

Hi sigmaris,

The builds on Azure seem to have expired - would it be possible for a new image to be created with the SPI installer and compressed image support?

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - sigmaris - 10-18-2020

(10-18-2020, 12:51 AM)voltagex Wrote: The builds on Azure seem to have expired - would it be possible for a new image to be created with the SPI installer and compressed image support?

I've pushed a new branch based on v2020.10, with a build here. There was some breakage of the SPI support in 2020.10 which I worked around by deleting the alias added in that commit. Treat this as a beta or pre-release - when ARM Trusted Firmware v2.4 is released next month, I'll make a proper tagged release including that.

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - voltagex - 10-18-2020

(10-18-2020, 01:12 PM)sigmaris Wrote:
(10-18-2020, 12:51 AM)voltagex Wrote: The builds on Azure seem to have expired - would it be possible for a new image to be created with the SPI installer and compressed image support?

I've pushed a new branch based on v2020.10, with a build here. There was some breakage of the SPI support in 2020.10 which I worked around by deleting the alias added in that commit. Treat this as a beta or pre-release - when ARM Trusted Firmware v2.4 is released next month, I'll make a proper tagged release including that.

Am I completely missing where the binaries are for this? You've skipped the GitHub release for that branch.

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - voltagex - 10-18-2020

Additionally, is it possible to increase u-boot's debug level? It might help me solve an unrelated issue.

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - sigmaris - 10-19-2020

(10-18-2020, 07:56 PM)voltagex Wrote: Am I completely missing where the binaries are for this? You've skipped the GitHub release for that branch.

Additionally, is it possible to increase u-boot's debug level? It might help me solve an unrelated issue.

The binaries are published as build artefacts, attached to the build in Azure Pipelines - click on the "3 published" link on the build page I linked to before, to download them. As I said above, when v2.4 of ARM Trusted Firmware is released, I'll tag a Github release.

If you want a debug build, look at the build pipeline script (reference for the pipeline syntax) and other guides to building U-Boot from source, modify the source code to set the debugging/logging you want, and build it according to the same process.

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - idontgetit - 10-21-2020

used rockpro64 u-boot v2020.01-ci but it does not detect storage on usb 3.0. It does detect the JMS578 on usb 2.0 however, but so does literally every other uboot version I've ever flashed - aka this is nothing special.

I want the usb 3.0 port to work for 2 reasons:
1. it's faster transfer speed
2. it actually manages to power a spinning drive as opposed to usb2.0 which screws up and you have to unplug and replug to get a successful spin-up. No, it's not the damn power supply, I can do that with a 12V 1.5A lying around just as well as the 12V 3.5A. It's not lack of power, it's whatever the board instructs the controller to do, which is to cycle power repeatedly for some weird reason.

Here it is when I unplug and plug back in on usb 2.0:

Device NOT ready
Request Sense returned 02 04 01
2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: JMicron Rev: 3102 Prod: Generic
Type: Hard Disk
Capacity: not available
... is now current device
Device NOT ready
Request Sense returned 02 04 01
2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: JMicron Rev: 3102 Prod: Generic
Type: Hard Disk
Capacity: not available
... is now current device
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - idontgetit - 10-21-2020

Ok there's some progress with U-Boot SPL 2020.10-07965-g0ce9b07852 (Oct 12 2020 - 21:45:42 +0000).

One of the coolest features: switched console output to video and I can actually use a keyboard to type commands to u-boot rather than time the plugging in of pin #10 just right so rockpro64 won't freak out on me and not boot.

Code:
Trying to boot from SPI

NOTICE:  BL31: v2.3(release):v2.3-797-g7ad39818b

NOTICE:  BL31: Built : 21:43:53, Oct 12 2020

U-Boot 2020.10-07965-g0ce9b07852 (Oct 12 2020 - 21:45:42 +0000)

It now seems to stop the usb2.0 power-cycle after 3x of them, disk gets detected and it tries to load stuff off of it. It doesn't actually boot, it gets stuck here:

Code:
Scanning usb 0:3...

Found /extlinux/extlinux.conf

Retrieving file: /extlinux/extlinux.conf

937 bytes read in 15 ms (60.5 KiB/s)

select kernel

1: kernel-5.6.0-1137-ayufan-ge57f05e7bf8f

2: kernel-5.6.0-1137-ayufan-ge57f05e7bf8f-memtest

Enter choice: 1: kernel-5.6.0-1137-ayufan-ge57f05e7bf8f

Retrieving file: /initrd.img-5.6.0-1137-ayufan-ge57f05e7bf8f

21658962 bytes read in 556 ms (37.1 MiB/s)

Retrieving file: /vmlinuz-5.6.0-1137-ayufan-ge57f05e7bf8f

22915584 bytes read in 553 ms (39.5 MiB/s)

append: rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=2e:68:c4:77:e9:11 eth1addr= serial=f671f593e6dba571 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4

Retrieving file: /dtbs/5.6.0-1137-ayufan-ge57f05e7bf8f/rockchip/rk3399-rockpro64.dtb

56725 bytes read in 21 ms (2.6 MiB/s)

## Flattened Device Tree blob at 01f00000

  Booting using the fdt blob at 0x1f00000

On USB 3.0 there's still no device detection. For comparison:

Code:
USB 3.0:

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

USB 2.0:

scanning bus usb@fe380000 for devices... 2 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... 1 Storage Device(s) found

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - idontgetit - 10-21-2020

On U-Boot TPL 2020.10-07965-g0ce9b07852 (Oct 12 2020 - 21:45:42), if you issue "usb reset" U-boot will freeze. It does not respond to anything, the only option is to power cycle the sbc.

RE: Mainline U-Boot with SPI, NVMe and SATA boot support - diskers - 10-29-2020

Hi,
How to get ride of this problem?

Device 0: unknown device

Device 0: unknown device
failed to find ep-gpios property

I have the appropriate PCI-Express card (pcie to nvme) but get this error
Any help is welcome

Thanks in advance