I am at IETF104, and only brought a Cubieboard2 and forgot my sata drive
and sata adapter. Thus all testing is uSD and USB only until next Monday.
I installed minimal on a 4GB uSD and deleted all partitions, leaving
only the uboot.
I installed minimal on a 16GB uSD and expanded the rootfs to the full
size of the card.
First test was uboot only in the uSD slot and the full image USB
connected (uSD USB adapter).
The boot failed. We are still on the rc2 broken uboot:
U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C: ready
DRAM: 1 GiB
MMC: mmc@1c0f000: 0
Loading Environment from FAT... ** No valid partitions found **
In: serial
Out: serial
Err: serial
SCSI: SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net: sunxi_set_gate: (CLK#66) unhandled
eth0: ethernet@1c50000
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
** Invalid partition 1 **
scanning bus for devices...
Found 0 device(s).
Device 0: unknown device
Device 0: 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
Vendor: Mass Rev: Prod: Storage Device
Type: Removable Hard Disk
Capacity: 14992.0 MB = 14.6 GB (30703616 x 512)
... is now current device
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
...
The uboot DID recognize the USB device, but did not boot it.
The second test was to put the full image in the uSD slot. This booted
up properly, went through the console first boot dialog and then I could
log in as root.
Next test used the F29 uboot on the 4Gb uSD in the uSD slot and the full
image on the USB adapter:
U-Boot SPL 2018.09 (Sep 11 2018 - 10:09:46 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
U-Boot 2018.09 (Sep 11 2018 - 10:09:46 +0000) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
Loading Environment from FAT... ** No valid partitions found **
In: serial
Out: serial
Err: serial
SCSI: SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net: eth0: ethernet@01c50000
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
** Invalid partition 1 **
scanning bus for devices...
Found 0 device(s).
Device 0: not available
Device 0: device type unknown
... is now current device
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 10.0.6.251 (20 ms)
*** ERROR: `serverip' not set
etc....
So this uboot seems better, but it is not recognizing the USB drive.
Is there a later uboot than that in F29
(Fedora-Minimal-armhfp-29-1.2-sda) for me to test with?
Otherwise I don't see any other testing I can do until I get back Monday.