Marvin-03 Posted January 4 Posted January 4 (edited) Am 3.1.2026 um 22:15 schrieb L. Jorge Soares: resetting ... sunxi_set_gate: (CLK#35) unhandled U-Boot SPL 2026.01-rc4_armbian-2026.01-rc4-S0e0a-P5fd4-H5aa4-Vd69a-B4d1d-R448a (Jan 03 2026 - 15:39:28 -0500) DRAM: 4096 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC1 NOTICE: BL31: v2.12.0(debug):armbian NOTICE: BL31: Built : 14:33:47, Jan 3 2026 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0a8d48, model: OrangePi 4A INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 287 INFO: Configuring SPC Controller INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a55: CPU workaround for erratum 1530923 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2026.01-rc4_armbian-2026.01-rc4-S0e0a-P5fd4-H5aa4-Vd69a-B4d1d-R448a (Jan 03 2026 - 15:39:28 -0500) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: OrangePi 4A DRAM: 4 GiB Core: 65 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0, mmc@4021000: 1, mmc@4022000: 2 Loading Environment from FAT... ** No valid partitions found ** In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: No ethernet found. Hit any key to stop autoboot: 0 PCIe: Acquiring resources... PCIe: Failed to parse num-lanes, using default: 1 PCIe: Failed to get switch-sel GPIO: -2 PCIe: Hardware init failed with error -2 Device 0: unknown device switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** Couldn't find partition mmc 0:1 PCIe: Acquiring resources... PCIe: Failed to parse num-lanes, using default: 1 PCIe: Failed to get switch-sel GPIO: -2 PCIe: Hardware init failed with error -2 No ethernet found. missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/00000000 No ethernet found. Retrieving file: pxelinux.cfg/0000000 No ethernet found. Retrieving file: pxelinux.cfg/000000 No ethernet found. Retrieving file: pxelinux.cfg/00000 No ethernet found. Retrieving file: pxelinux.cfg/0000 No ethernet found. Retrieving file: pxelinux.cfg/000 No ethernet found. Retrieving file: pxelinux.cfg/00 No ethernet found. Retrieving file: pxelinux.cfg/0 No ethernet found. Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi No ethernet found. Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. Retrieving file: pxelinux.cfg/default-arm No ethernet found. Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found PCIe: Acquiring resources... PCIe: Failed to parse num-lanes, using default: 1 PCIe: Failed to get switch-sel GPIO: -2 PCIe: Hardware init failed with error -2 No ethernet found. No ethernet found. Can you test these commands in u-boot? mmc list mmc info mmc dev 0 mmc part fatls mmc 0:1 ext4ls mmc0:2 mmc read 0x40000000 0 1 It seems like mega doesnt work anymore without login. Here are the images on gdrive: https://drive.google.com/drive/folders/1jEIWmzZgT5t39jRz7GwZpFOAdjdQBLtG?usp=drive_link Edited January 4 by Marvin-03 0 Quote
L. Jorge Soares Posted January 4 Posted January 4 @Marvin-03 Here are the results of the commands provided, hope this help. Thanks for the link of your image builds, will try them out. Quote => mmc list mmc@4020000: 0 (SD) mmc@4021000: 1 mmc@4022000: 2 => mmc info Device: mmc@4020000 Manufacturer ID: 3 OEM: 5344 Name: AFGCD Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.7 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 0 switch to partitions #0, OK mmc0 is current device => mmc part Partition Map for mmc device 0 -- Partition Type: EFI => fatls mmc 0:1 ** Invalid partition 1 ** Couldn't find partition mmc 0:1 => ext4ls mmc 0:2 ** Invalid partition 2 ** Couldn't find partition mmc 0:2 => fatls mmc0:1 ** No device specified ** Couldn't find partition mmc0:1 <NULL> => ext4ls mmc0:2 ** No device specified ** Couldn't find partition mmc0:2 <NULL> => mmc read 0x40000000 0 1 MMC read: dev # 0, block # 0, count 1 ... 1 blocks read: OK => 0 Quote
Marvin-03 Posted January 5 Posted January 5 vor 15 Stunden schrieb L. Jorge Soares: => mmc list mmc@4020000: 0 (SD) mmc@4021000: 1 mmc@4022000: 2 => mmc info Device: mmc@4020000 Manufacturer ID: 3 OEM: 5344 Name: AFGCD Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.7 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 0 switch to partitions #0, OK mmc0 is current device => mmc part Partition Map for mmc device 0 -- Partition Type: EFI => fatls mmc 0:1 ** Invalid partition 1 ** Couldn't find partition mmc 0:1 => ext4ls mmc 0:2 ** Invalid partition 2 ** Couldn't find partition mmc 0:2 => fatls mmc0:1 ** No device specified ** Couldn't find partition mmc0:1 <NULL> => ext4ls mmc0:2 ** No device specified ** Couldn't find partition mmc0:2 <NULL> => mmc read 0x40000000 0 1 MMC read: dev # 0, block # 0, count 1 ... 1 blocks read: OK => Did you get an error when using balena etcher? I tried flashing the image myself and it wouldnt create any partitions. I uploaded an image with a repaired partition table to gdrive and mega. Alternatively, you can use gparted to repair the image yourself. Just put: sudo gdisk /path/to/Armbian-unofficial_26.02.0-trunk_Orangepi4a_trixie_edge_6.18.0.img r (recovery), then d (recreate primary header), then w (write) into wsl or linux. 0 Quote
L. Jorge Soares Posted January 5 Posted January 5 I did get an alert from BalenaEtcher, when writting the IMG file to SD. It reported not having a BOOT partition. I continued through the alert and the PI board did boot to the prompt results I originally reported. I am going try you image now and will let you know. 0 Quote
L. Jorge Soares Posted January 5 Posted January 5 (edited) @Marvin-03 ** run the commands to fix partitions on my IMG build, just like you mentioned and it fixed it.** Your Orangepi4a img is working, I am able to BOOT. But I am accessing the board through the console. Confirmation of the boot is below. I also had a look at the partitions from the IMG created of the GIT build and your own image. See details below. Quote _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v26.02 rolling for Orange Pi 4a running Armbian Linux 6.18.0-edge-sun55iw3 Packages: Debian stable (trixie) Support: DIY (custom image) IPv4: (LAN) 10.10.10.191 (WAN) ##.##.##.## Performance: Load: 14% Uptime: 4 minutes Memory usage: 4% of 3.83G Usage of /: 7% of 29G Tips: Armbian config utility https://tinyurl.com/yc39n6m3 Commands: Configuration : armbian-config Monitoring : htop root@orangepi4a:~# This is the partitions list of the IMG build of GIT Quote Disk /dev/sdc: 29.72 GiB, 31914983424 bytes, 62333952 sectors Disk model: MassStorageClass Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 1 62333951 62333951 29.7G ee GPT This is the partition list of your IMG for comparison Quote Disk /dev/sdc: 29.72 GiB, 31914983424 bytes, 62333952 sectors Disk model: MassStorageClass Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 09A4CB82-9D1D-424A-BA48-7D406DF8EF24 Device Start End Sectors Size Type /dev/sdc1 8192 1056767 1048576 512M Linux extended boot /dev/sdc2 1056768 5683199 4626432 2.2G Linux root (ARM-64) Edited January 5 by L. Jorge Soares 0 Quote
L. Jorge Soares Posted January 5 Posted January 5 @Marvin-03 Looks like your GIT no longer has the changes for OrangePI4a board available. 0 Quote
Werner Posted January 6 Posted January 6 Looks like stuff got lost due to force-push. Check this how it looked before: https://github.com/rvdr/build/activity?ref=spi-nvme-patches 1 Quote
Marvin-03 Posted January 6 Posted January 6 (edited) Am 5.1.2026 um 22:26 schrieb L. Jorge Soares: Looks like your GIT no longer has the changes for OrangePI4a board available. I updated my patches to the new style (using series.conf) and that took some time. They are back online, as are some new images. I post more updates at the opi discord btw. The image doesnt work stable atm. Network works, pcie and spi flash doesnt. Edited January 8 by Marvin-03 1 Quote
JuanEsf Posted January 8 Posted January 8 (edited) https://drive.google.com/drive/folders/1dx0TApPAEjFDz24Rm22J4jgtIbJrYYHC?usp=drive_link build log: url for test... https://github.com/armbian/build/pull/9185 Edited January 9 by JuanEsf Add github pull-req. 1 Quote
Edmilson Santos Posted January 14 Posted January 14 (edited) @JuanEsf Is possible first acces via SSH? no HDMI for me 😞 Just led of network activity. But no dhcp Edited January 14 by Edmilson Santos 0 Quote
Marvin-03 Posted January 14 Posted January 14 vor 19 Stunden schrieb Edmilson Santos: Is possible first acces via SSH? no HDMI for me 😞 Just led of network activity. But no dhcp Ethernet should be working (after rebooting), but wifi doesnt work out of the box. 1 Quote
thanh_tan Posted February 1 Posted February 1 Quote Ethernet should be working (after rebooting), but wifi doesnt work out of the box. does emmc working yet? 0 Quote
Edmilson Santos Posted February 11 Posted February 11 (edited) Any news or predictions on when HDMI and VAAPI will work? I want to use the board as a Jellyfin server! Edited February 12 by Edmilson Santos 0 Quote
Timax Posted 3 hours ago Posted 3 hours ago Hi all, I've spend a few evenings playing with the Armbian build-system and OPI4a, mainly trying to get Ethernet working reliably. There are two issues I've found: (almost) every second boot there are errors with PHY access (as if there was a race somewhere), neither DHCP nor static IPs are working (in scnerios when there are no issues with PHY). I've mainly focused on comparing Devicetrees to OrangePis' sources, and from newbie perspective, at least Ethernet part seems pretty complete. The next logical step would be to focus on the driver, but I figured, I'd ask if maybe someone has also been trying to work it out, and proceeded further? I'd appreciate any ideas of what I should check next. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.