wvthoog

Would be my guess as well. But now something strange happened. Loaded an image for a Orange Pi Zero Plus (not Plus2 H5) and it booted. To be clear my board is definitely a Orange Pi Zero Plus2 H5 See log here: https://pastebin.com/SR3hywPM

So it seems it does boot from SD, but hangs somewhere during kernel loading. Could the Orange Pi be broken ?

The last time I've used this board was around December 2019. Building images or downloaded from Armbian.com and burning them on a SD card worked fine. Now i'm struggling to get it to boot from SD. Tried these images: https://redirect.armbian.com/orangepizeroplus2-h5/Buster_current https://redirect.armbian.com/orangepizeroplus2-h5/Focal_current Also build my own image (to include some extra modules) Armbian_20.08.0-trunk_Orangepizeroplus2-h5_bionic_current_5.7.12 All of them won't get passed "Starting kernel" Serial log: U-Boot SPL 2020.04-armbian (Aug 05 2020 - 07:58:29 +0200) DRAM: 512 MiB Trying to boot from MMC1 NOTICE: BL31: v2.3(debug):8dd1c3c-dirty NOTICE: BL31: Built : 07:58:26, Aug 5 2020 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x40908e8, model: OrangePi Zero Plus2 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller NOTICE: PMIC: Assuming H5 reference regulator design INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied NOTICE: PSCI: System suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2020.04-armbian (Aug 05 2020 - 07:58:29 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi Zero Plus2 DRAM: 512 MiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial Out: serial Err: serial Net: No ethernet found. ** Reading file would overwrite reserved memory ** starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3173 bytes read in 2 ms (1.5 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 201 bytes read in 2 ms (97.7 KiB/s) 31003 bytes read in 6 ms (4.9 MiB/s) 504 bytes read in 4 ms (123 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo 504 bytes read in 5 ms (97.7 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo 4191 bytes read in 5 ms (818.4 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 45000000 11032058 bytes read in 528 ms (19.9 MiB/s) 18784264 bytes read in 897 ms (20 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11031994 Bytes = 10.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 4957a000, end 49fff5ba ... OK Loading Device Tree to 000000004950a000, end 0000000049579fff ... OK Starting kernel ... Double checked that the SD card reader switch was not broken according to this link Switch is working fine. Am at a loss here. Can someone shed some light on howto resolve this. From the serial log it seems it wants to boot from emmc Power supply: 5v 3A Complete log with Verbosity set to 10 located at https://pastebin.com/Cq8BaKLK

Hi, as many did, I've bought a (CSI) OV5647 camera from AliExpress and am struggling to get it to work. Been at it for a week now and am at a loss. So i'm trying to get some clarification via this thread on how to get this camera to work. What I've done so far is to compile a mainline kernel (Ubuntu Bionic) and edited the kernel config file to include sun6i_csi and ov5647 driver. Build finishes successfully and am able to boot and load the drivers Unfortunately the OV5647 isn't recognized and /dev/video0 isn't created. Second build included a userpatch I've found online which i applied to no avail to the kernel https://lore.kernel.org/patchwork/patch/743268/ So my question is, what am i missing here ? Do i need an overlay, or patch the kernel/driver in some way ? Any help will be appreciated. Regards. Wim