Posts by myxal

myxal · Support for A10/A20 myxal February 13, 2020 at 9:33 PM

Quote from jernej

> which /init..

Yes.

Is there a way to check that it (and busybox executable) is actually on the built image..? (My understanding is that this is the early rootfs - like initramfs on a PC Linux distro - and on these images, that's embedded in the KERNEL image file.) I tried the binwalk method of extraction, but for every xz file it finds in the KERNEL file, unxz reports it as corrupted.

Code

binwalk /mnt/LEcard/KERNEL

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
36            0x24            Linux kernel ARM boot executable zImage (little-endian), load address: "0x00000000", end address: "0x00855668"
82818         0x14382         SHA256 hash constants, little endian
1001768       0xF4928         Certificate in DER format (x509 v3), header length: 4, sequence length: 4688
4588447       0x46039F        Certificate in DER format (x509 v3), header length: 4, sequence length: 773
5235356       0x4FE29C        mcrypt 2.5 encrypted data, algorithm: "H", keysize: 3625 bytes, mode: "T",
5486560       0x53B7E0        xz compressed data
5563871       0x54E5DF        Unix path: /505V/F505/F707/F717/P8(
6313659       0x6056BB        Unix path: /usr/share/plymouth/splash.png
6314139       0x60589B        Copyright string: "Copyright (c) 2018-2019 Cosmin Truta%"
6502906       0x6339FA        Copyright string: "copyrighted by many authors between 1998-2015."
6519234       0x6379C2        xz compressed data
6579912       0x6466C8        ELF, 32-bit LSB processor-specific, no machine,
6850378       0x68874A        Certificate in DER format (x509 v3), header length: 4, sequence length: 5384
7286238       0x6F2DDE        ELF, 32-bit LSB processor-specific,
7543244       0x7319CC        Certificate in DER format (x509 v3), header length: 4, sequence length: 9476
7864179       0x77FF73        Copyright string: "Copyright (C) 2019 Free Software Foundation, Inc."
8605147       0x834DDB        Unix path: /virtual/graphics/fbcon/5

Display More

myxal · Support for A10/A20 myxal February 12, 2020 at 8:06 PM

Am I doing this right? I decompiled the DTB, set status="disabled" on the first enabled usb node (and the phy which the subsequent attempt to boot complained about), compiled and replaced sun4i-a10-a1000.dtb. Diff:

Display Spoiler

Code

                phy@1c13400 {
                        #phy-cells = <0x1>;
                        compatible = "allwinner,sun4i-a10-usb-phy";
                        reg = <0x1c13400 0x10 0x1c14800 0x4 0x1c1c800 0x4>;
                        reg-names = "phy_ctrl", "pmu1", "pmu2";
                        clocks = <0x2 0x7d>;
                        clock-names = "usb_phy";
                        resets = <0x2 0x1 0x2 0x2 0x2 0x3>;
                        reset-names = "usb0_reset", "usb1_reset", "usb2_reset";
-                       status = "okay";
+                       status = "disabled";
                        usb1_vbus-supply = <0x1c>;
                        usb2_vbus-supply = <0x1d>;
                        phandle = <0x1a>;
                };
 
                usb@1c14000 {
                        compatible = "allwinner,sun4i-a10-ehci", "generic-ehci";
                        reg = <0x1c14000 0x100>;
                        interrupts = <0x27>;
                        clocks = <0x2 0x1b>;
                        phys = <0x1a 0x1>;
                        phy-names = "usb";
-                       status = "okay";
+                       status = "disabled";
                };
 
                usb@1c14400 {
                        compatible = "allwinner,sun4i-a10-ohci", "generic-ohci";
                        reg = <0x1c14400 0x100>;
                        interrupts = <0x40>;
                        clocks = <0x2 0x7b 0x2 0x1c>;
                        phys = <0x1a 0x1>;
                        phy-names = "usb";

Display More

That did get rid of detecting the USB wifi (didn't have anything else attached), but the error message is the same:

Quote

[ 4.084220] Run /init as init process

[ 4.095837] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

[ 4.109445] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

jernej, which /init is this referring to? This one?

myxal · Support for A10/A20 myxal February 8, 2020 at 12:39 PM

I've tried the ready-made image linked here, which should be a mainline kernel, albeit an old one: Mainline Debian HowTo - linux-sunxi.org (image link). I didn't go into installing UBoot and full-featured boot - I think that nukes the onboard android, which I don't want to do yet (want to back up the partitions first, and don't have an ADB cable yet). But the pre-install environment did boot successfully, with even the USB ports working (there was no driver for the onboard wifi, but it did show up in lsusb.

What would be a simple way to prevent jernej's build from loading the Realtek wifi drivers, to check if that's the culprit here?

myxal · Support for A10/A20 myxal February 7, 2020 at 9:48 AM

Quote from roel

OK usbc0 is disabled in the fex. So dtb should be OK. I don't see any differences.

Hmm, maybe this is the problem - what would be the DTS equivalent of usb_host_init_state in FEX?

Quote

various: Set usbc2 usb_host_init_state to 1

Code

usb_host_init_state for usbc2 needs to be 1 for the wifi driver to properly
auto-load. I don't have these boards to verify, but these are 512Mb RAM
variants of 1Gb boards I do have, so it is safe to assume this is necessary
with their 512Mb counter-parts too.

Signed-off-by: Hans de Goede <[email protected]>

myxal · Support for A10/A20 myxal February 6, 2020 at 6:53 PM

Quote from jernej

Can anyone test that? other SoCs don't need that.

Just did moments ago, didn't help anything.

myxal · Support for A10/A20 myxal February 6, 2020 at 5:52 PM

Quote from roel

Code

&usbphy {
    usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */
    usb1_vbus-supply = <&reg_usb1_vbus>;
    usb2_vbus-supply = <&reg_usb2_vbus>;
    status = "okay";
};

Not quite sure what that does, but here's what looks relevant from A1000 fex file:

Code

[usbc0]
usb_used = 0
usb_port_type = 0
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PB09<1><0><default><0>
usb_host_init_state = 0

[usbc1]
usb_used = 1
usb_port_type = 1
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PH06<1><0><default><0>
usb_host_init_state = 1

[usbc2]
usb_used = 1
usb_port_type = 1
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PH03<1><0><default><0>
usb_host_init_state = 1

Display More

myxal · Support for A10/A20 myxal February 6, 2020 at 11:36 AM

A note to self, or possibly others running into the panic on boot: try the rootwait nousb kcmd options or combinations thereof.

myxal · Support for A10/A20 myxal February 5, 2020 at 7:08 PM

Hmm, seems to happen after finding the built-in USB WLAN:

Display Spoiler

[ 4.912460] hub 1-1:1.0: USB hub found

[ 4.934579] Freeing unused kernel memory: 5120K

[ 4.945656] hub 1-1:1.0: 4 ports detected

[ 4.955567] Run /init as init process

[ 4.966350] usb 2-1: New USB device found, idVendor=0bda, idProduct=8176, bcdDevice= 2.00

[ 4.980619] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 4.993523] usb 2-1: Product: 802.11n WLAN Adapter

[ 5.003979] usb 2-1: Manufacturer: Realtek

[ 5.013694] usb 2-1: SerialNumber: 00e04c000001

[ 5.026467] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

[ 5.040015] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

myxal · Support for A10/A20 myxal February 5, 2020 at 6:54 PM

Re: A2000, not quite there yet...

Code

## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Device Tree to 49ff7000, end 49fffb32 ... OK

Starting kernel ...

[    0.165777] sun4i-usb-phy 1c13400.phy: Couldn't get regulator usb1_vbus... Deferring probe
[    1.376003] debugfs: Directory '1c22c00.codec' with parent 'sun4i-codec' already present!
[    1.746350] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    1.754214] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

myxal · Support for A10/A20 myxal February 4, 2020 at 8:52 PM

Output on HDMI shows a short white line in the top left corner. My monitor is 1440p, and is showing that the input signal has the full resolution, but I don't think the A10 is capable of 2560x1440@60Hz..? Seems like it's being driven beyond capabilities. Tried again on another monitor with 1920x1200, works OK.

VGA output works (1024x768@60), shows Linux console (same as observed on UART). Doesn't appear to actually boot, see attached log.

log.txt

myxal · Support for A10/A20 myxal February 4, 2020 at 9:56 AM

I'm also at a loss as to how to go about the display output DT patch - never did anything with DT, only know that it "describes HW" in lieu of autodiscovery like ACPI.

Do you mean something like this, but for the sun4i-a10-a1000.dts ? Or is some other info needed?

myxal · Support for A10/A20 myxal February 2, 2020 at 11:25 AM

Hello. I have an A2000 box with the A10 chip. Didn't see any Allwinner nightly builds, as the blog post implied, and the most recent posts here suggest that the board's specs are just too low to even bother.

So.. what's the current status/intention/plan of A10 support? (Waiting for driver fixes? Looking for testers/hardware? Unsupported permanently? Lack of maintainer time/interest?)

myxal

Hi all,

I'm considering getting a Rockchip TV-box or SBC, considering the early positive results for Hi10P H264 (a.k.a. 10-bit H264 "anime release") playback test by CNX on RK3229: Rockchip RK3229 Video Playback Take 2 – 10-bit H.264 & H.265, Audio HD Pass-through with Zidoo X1 II

The trouble is, I haven't found much verified information regarding the following:

Is the MPP in the RK3399 equal, or superset of the one in RK3229?
Will KODI in LibreELEC handle Hi10P files?? (The CNX article doesn't mention any specific players, so I assume it was tested on bundled players, running on Android.)