On a fresh download, configuring a CB1, Desktop Vanilla system, I get:
U-Boot 2016.05-armbian (Jun 10 2016 - 17:25:48 -0400) Allwinner Technology
CPU: Allwinner A10 (SUN4I)
Model: Cubietech Cubieboard
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment
HDMI connected: Setting up a 1280x720 hdmi console (overscan 0x0)
In: serial
Out: vga
Err: vga
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@01c0b000
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... 5 USB Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2447 bytes read in 211 ms (10.7 KiB/s)
## Executing script at 43100000
0 bytes read in 151 ms (0 Bytes/s)
0 bytes read in 161 ms (0 Bytes/s)
25257 bytes read in 284 ms (85.9 KiB/s)
** File not found /boot/uInitrd **
** Unrecognized filesystem type **
** File not found uInitrd **
6132416 bytes read in 714 ms (8.2 MiB/s)
Kernel image @ 0x46000000 [ 0x000000 - 0x5d92c0 ]
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...
scanning bus for devices...
Found 0 device(s).
SCSI device 0:
Device 0: not available
USB device 0: unknown device
ENET Speed is 100 Mbps - FULL duplex connection
BOOTP broadcast 1
DHCP client bound to address 192.168.20.16 (48 ms)
*** Warning: no boot file name; using 'C0A81410.img'
Using ethernet@01c0b000 device
TFTP from server 0.0.0.0; our IP address is 192.168.20.16; sending through gateway 192.168.20.1
Filename 'C0A81410.img'.
Load address: 0x42000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
I'm going to clear the decks and do a completely fresh, unmodified git clone. The first time I did that, I made some small changes in the kernel config for lcd backlight & pwm control, second time I just exited out of the kernel config and let it run to completion. I have a serial console set up to watch the boot. After the first failure, I did a badblocks check --- no bad blocks, This same hardware ran a legacy version with the modified u-boot just before this failure with a Vanilla image.
After a pristine download, and not requiring any kernel configuration changes, I get the same failure. Selection: Full OS image, Cubieboard, next, Trusty, Image with Desktop environment --> boot fail.
Anyone else seeing this?
Chris