

going
Members-
Posts
815 -
Joined
-
Last visited
Other groups
Contributor/Maintainer
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Please read the documentation on the manufacturer's website (radxa). It really works.
-
If you want to find a request, please publish the UART log. maybe after that we can say recommendations.
-
-
UART console log? In fact, only the u-boot version and the kernel version are interested. On my devices with rk3588 (s) chips, old versions of u-boot were originally installed and they did not allow loading Armbian images. I used the instructions from the manufacturer's official website and recorded the bootloader provided by Armbian on the SPI chip using special software. In other words, Armbian delivers his images from u-boot v2025.XX but my orangepi5plus was loaded using u-boot v2019 recorded on an SPI chip. And that may be the problem. After overwriting the new version, my device loads any images and PCI (NVME) devices register correctly. I checked several of these from different manufacturers. Hope this information helps with your problem.
-
Today it is EDGE v6.15 no v6.16.
- 20 replies
-
- Orange Pi Zero
- Orange Pi Zero 2
-
(and 1 more)
Tagged with:
-
Recommended to upgrade U-Boot to version v2025.07 This version has big changes for allwinner (sunxi) chips. This concerns the initialization of a non-standard size of RAM (1.5; 2.5 GB), downloads from eMMC.....
- 20 replies
-
1
-
- Orange Pi Zero
- Orange Pi Zero 2
-
(and 1 more)
Tagged with:
-
Yes, that's right. This is relevant to the issue under discussion.
- 20 replies
-
- Orange Pi Zero
- Orange Pi Zero 2
-
(and 1 more)
Tagged with:
-
H3 cedrus video acceleration, device tree problem?
going replied to schunckt's topic in Allwinner sunxi
Which OS works well for you? -
H3 cedrus video acceleration, device tree problem?
going replied to schunckt's topic in Allwinner sunxi
v5.1-rc5 v6.12.35 Please use the current documentation for the CURRENT kernel. sun4i-a10-video-engine.yaml sun8i-h3-deinterlace.yaml Documentation/arch/arm/sunxi.rst arch/arm/boot/dts/allwinner/sun8i-h3-nanopi-duo2.dts arch/arm/boot/dts/allwinner/sun8i-h3.dtsi P.S. Please read this. repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner -
It is Allwinner H618, Quad-core ARM Cortex™-A53 processor. I meant which Eth chip is used in your case Bananapi-m4-berry: h618 ==> Eth chip rtl8211f ==> connecting socket Bananapi-m4-zero: h618 ==> Eth chip ???? ==> connecting socket As far as I understand, this is some kind of expansion card for the 26 pin connector. Can you post a diagram of this expansion board here. The brand of the Ethernet chip matters.
-
> sunxi-gmac 5030000.ethernet end0: No PHY found! The first question. What brand of chip is used in your case? The second question. Is this an external device? [ 341.101053] usb 2-1: new high-speed USB device number 2 using ehci-platform [ 341.257994] usb 2-1: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.01 [ 341.258024] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 341.258033] usb 2-1: Product: AX88772B [ 341.258039] usb 2-1: Manufacturer: ASIX Elec. Corp. [ 341.258045] usb 2-1: SerialNumber: E5A1DD [ 341.902647] asix 2-1:1.0 (unnamed net_device) (uninitialized): PHY [usb-002:002:10] driver [Asix Electronics AX88772C] (irq=POLL) [ 341.905987] Asix Electronics AX88772C usb-002:002:10: attached PHY driver (mii_bus:phy_addr=usb-002:002:10, irq=POLL) In order for the ethernet-phy to work, it is necessary to turn on the PWM on the internal pin of the processor. As example see: arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts and arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts#L521-L539
-
OrangePi 3 lts / i2C / overlay / armbian-config ?
going replied to kris777's topic in Allwinner sunxi
This will be fixed soon. -
It appears that the fsck file check reports a clean system then continues to boot? From the above log of the UART console, I see that uboot found the SD card partition and loaded the kernel from it. The kernel saw the root partition of the SD card, but after checking fsck.ext4 -a -C0 /dev/mmcblk0p1, for some reason, it cannot mount it. When you have written the image to the SD card, try to mount it in your running OS and fix it in the file /boot/armbianEnv.txt verbosity=7. After that, boot up and watch the UART. This may provide additional clues.
-
Alternatively, you can try disabling this file system verification service by connecting the SD card to a virtual machine and fixing the appropriate scripts.
-
What have you been updating? Only system files?