wha

linux-u-boot-beelinkx2-default=5.35 , which gives U-Boot prompt of: "U-Boot SPL 2017.09-armbian (Nov 22 2017 - 13:55:46)" will boot Linux kernel (I'm currently running linux-image-sun8i=5.37.180112). Anything AFTER that version will not boot a Linux kernel. Complains about missing files. I didn't capture [debug serial] output of "bad" u-boots. But I can if anyone needs them.

Updated legacy kernel on a Beelinkx2 , to: linux-image-sun8i 5.32.170824 armhf Linux kernel, version 3.4.113-sun8i wifi, HDMI works. ==== Then I updated to: linux-image-dev-sun8i 5.32.170824 armhf Linux kernel, version 4.11.12-sun8i linux-u-boot-beelinkx2-dev 5.32.170824 armhf Uboot loader 2017.07 linux-stretch-root-dev-beelinkx2 5.32.170824 armhf Armbian tweaks for stretch on beelinkx2 (dev branch) wifi works. But (as expected), no HDMI output (none during boot, nor after Linux was running) only one cpu running so I reverted to 3.4.113 kernel (left newer u-boot active). OrangePiPlus2e shows same results. ==== I've also been running testing/buster for a couple of weeks. Everything works, except for systemd stuff. Newer systemd expects cgroups (which is not available on 3.x kernels). So I hold systemd [& udev] stuff at version 232-25. If you try & update to 234-2, you'll get weird mount errors during boot, then the kernel [intentionally] crashes.

See: http://forum.armbian.com/index.php/topic/1702-orange-pi-plus-2e-where-is-16ghz-and-sd/#entry13163 about 1/2 way down the page. It works for my orangepi+2e. Just make sure that the sdhc card does NOT have a system image/u-boot on it. I usually (on my desktop PC) 'dd' a couple megabytes of zeros (i.e. dd if=/dev/zero of=/dev/sdhc_device_name bs=1M count=20 ), then (re-)format the card.

uInitrd is good. Note that ALL I did to get system to boot, is it to re-write uboot block(s) to start of eMMC: ==== wha@orangepiplus2e:~$ sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1k count=1023 seek=1 status=noxfer wha@orangepiplus2e:~$ sudo dd if=/usr/lib/linux-u-boot-orangepiplus_5.16_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 status=noxfer ==== (just manually typed install script from deb) So I believe that the u-boot [executable] code, for the '2e' is wrong. To verify that assumption, I wrote the SPL from linux-u-boot-orangepiplus2e_5.16_armhf , once again, boot CRC error. Thanks, wha

updated to 5.15 (then 5.16) release using aptitude. Kernel update worked. But when I updated u-boot ( linux-u-boot-orangepiplus2e-default ) , the system will no longer boot (see attached). But if I use linux-u-boot-orangepiplus-default , it will boot. (Note that the install script, to write/dd SPL , is hardcoded to mmcblk0, which is usually correct, but for this fix, I start boot on SDHC then pivot-root to eMMC. My running root is mmcblk1 during this "rescue" boot). Both 5.15 & 5.16 exhibit this behavior. Thanks, wha bad-uboot.txt

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

I haven't read through all of the issues, so haven't picked anything to do yet. But I'm willing to help. I've ran Debian since 'Ham' (early 2000's). And have done embedded (8 & 16 bit) off & on for years. Recently I've started to play with [8 bit] AVR & [32 bit] Arm (Teensy 3/LC). Haven't done Linux drivers (never had a need to at work). I've an Orange Pi Plus 2E, will probably get a Orange Pi PC, One, & Lite for misc home projects/experiments/learning. Thanks, wha

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