ChrisArena52 Posted June 11, 2016 Posted June 11, 2016 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
ChrisArena52 Posted June 11, 2016 Author Posted June 11, 2016 Mounting the SD Card on a CB2 I have running, I see the SD card has no uInitrd file under /boot ... ??
ChrisArena52 Posted June 11, 2016 Author Posted June 11, 2016 Moving a copy of uInitrd to the malfunctioning image allows it to boot ... Igor, what happened to that file? Chris
Igor Posted June 11, 2016 Posted June 11, 2016 I did not check those images but rebuilt them 30 minutes ago, kernel 4.6.2. Those are tested. Check download page - I also replaced Ubuntu with Xenial build for the first time.
wha Posted June 11, 2016 Posted June 11, 2016 I had somewhat similar problem with Orange Pi Plus 2E images. Kept getting CRC error (during u-boot). I tried: Armbian_5.14_Orangepiplus2e_Debian_jessie_3.4.112.7z Armbian_5.14_Orangepiplus2e_Debian_jessie_3.4.112_desktop.7z (all built June 1, 2016). Then, since Igor says all/most H3 builds are basically the same, I tried: Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop.7zIt worked/booted. Everything is working: gigabit ethernet worked wifi worked all 3 USB ports worked (haven't tried OTG port yet) HDMI & X came up I note that the PI+ build was done June 5, 2016. So maybe there was a problem with (at least the Orange PI) builds June 1? Anyway, once up, I quickly ran: nand-sata-install , to install SDHC image to eMMC. Boots (fast) from eMMC. And is "disk" I/O is fast. Now awaiting 4.x kernel(s)! Thanks, wha
Igor Posted June 11, 2016 Posted June 11, 2016 You mean this: http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment
ChrisArena52 Posted June 13, 2016 Author Posted June 13, 2016 I tried the Xenial this time. root@cubieboard:/boot# uname -a Linux cubieboard 4.6.2-sunxi #1 SMP Sat Jun 11 15:28:33 EDT 2016 armv7l armv7l armv7l GNU/Linux root@cubieboard:/boot# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial root@cubieboard:/boot# That booted normally the first time. Nice! Thanks! Chris
wha Posted June 14, 2016 Posted June 14, 2016 You mean this: http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment Yes, that's one of two CRC errors. The environment CRC: U-Boot 2016.05-armbian (Jun 01 2016 - 20:28:42 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment If I do "saveenv" , then reboot, that CRC goes away...for awhile. After a couple of power-cycles, it comes back. And it looses any changes to the u-boot environment that I may have made. Might be a hardware issue with my board (Orange Pi Plus 2E)? ================= But I also get a CRC error when trying to boot ANY Plus 2E image, be it downloaded: http://mirror.igorpecovnik.com/Armbian_5.14_Orangepiplus2e_Debian_jessie_3.4.112_desktop.7z Or if I build it. mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2444 bytes read in 182 ms (12.7 KiB/s) ## Executing script at 43100000 gpio: pin PL10 (gpio 298) value is 1 gpio: pin PG11 (gpio 203) value is 1 0 bytes read in 131 ms (0 Bytes/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 37820 bytes read in 529 ms (69.3 KiB/s) 3112461 bytes read in 3230 ms (940.4 KiB/s) 5064616 bytes read in 5191 ms (952.1 KiB/s) Kernel image @ 0x48000000 [ 0x000000 - 0x4d47a8 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3112397 Bytes = 3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid ========================== If I download or build an Orange Pi Plus kernel, it works fine: mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2347 bytes read in 182 ms (11.7 KiB/s) ## Executing script at 43100000 gpio: pin PL10 (gpio 298) value is 1 gpio: pin PG11 (gpio 203) value is 1 ** File not found /boot/.verbose ** ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 38056 bytes read in 540 ms (68.4 KiB/s) 3113965 bytes read in 3216 ms (945.3 KiB/s) 5064616 bytes read in 5176 ms (955.1 KiB/s) Kernel image @ 0x48000000 [ 0x000000 - 0x4d47a8 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3113901 Bytes = 3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 2048MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2004620! ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]! Debian GNU/Linux 8 orangepiplus ttyS0 ======================= Thanks, wha
Recommended Posts