XFer012

understood

I'm an Armbian newbie. As for now, following the guide at https://docs.armbian.com/Developer-Guide_Build-Preparation/ , I think I have a working build environment. Where should I copy your kernel source, config etc. (from https://github.com/hexdump0815/linux-mainline-and-mali-allwinner-h6-kernel) within the Armbian "build/" folder? It looks like: -rwxrwxr-x 1 8569 Apr 5 15:07 compile.sh drwxrwxr-x 13 4096 Apr 5 15:07 config drwxrwxr-x 2 4096 Apr 5 15:07 lib -rw-rw-r-- 1 18026 Apr 5 15:07 LICENSE drwxrwxr-x 3 4096 Apr 5 15:08 output drwxrwxr-x 5 4096 Apr 5 15:07 packages drwxrwxr-x 6 4096 Apr 5 15:07 patch -rw-rw-r-- 1 13703 Apr 5 15:07 README.md drwxr-xr-x 2 4096 Apr 5 15:08 userpatches -rw-rw-r-- 1 14 Apr 5 15:07 VERSION Thanks!!

You mean, on my lowly 512 MB OrangePiZero2? Aren't 512 MB too scarce to build a kernel? That's good to know! I mean, back in the times I used to build 1.x on a 32 MB 80386, but Linux kernels were tiny in comparison

Thank you! Will study how to cross-compile a kernel, outside the "standard" Armbian scripts. I'm new to cross-compiling and also to kernel building for ARM boards (u-boot, DTB etc.), so it's going to be fun

Good catch. Added the phys references to usb@5101000 and usb@5101400, but unfortunately it does not work yet. Host controllers show up in dmesg, but the USB port remains "dead": does not even power peripherals. It will take a longer wait it seems, thanks anyway!

First of all, thanks for your support. Much appreciated. It seems to me, that changes in that commit are already present in my decompiled DTS (from kernel 5.11.11-sunxi64 Thu Apr 1): I see the same phys references in USB nodes. It's a bit hard without the labels, but phys = <0x15 0x01> seem to correspond to your phys = <&usbphy 1> and so on usb@5100000 { compatible = "allwinner,sun50i-h616-musb\0allwinner,sun8i-a33-musb"; reg = <0x5100000 0x400>; clocks = <0x02 0x72>; resets = <0x02 0x32>; interrupts = <0x00 0x19 0x04>; interrupt-names = "mc"; phys = <0x15 0x00>; phy-names = "usb"; extcon = <0x15 0x00>; status = "okay"; dr_mode = "otg"; phandle = <0x35>; }; phy@5100400 { compatible = "allwinner,sun50i-h616-usb-phy"; reg = <0x5100400 0x24 0x5101800 0x04 0x5200800 0x04 0x5310800 0x04 0x5311800 0x04>; reg-names = "phy_ctrl\0pmu0\0pmu1\0pmu2\0pmu3"; clocks = <0x02 0x63 0x02 0x65 0x02 0x67 0x02 0x69>; clock-names = "usb0_phy\0usb1_phy\0usb2_phy\0usb3_phy"; resets = <0x02 0x26 0x02 0x27 0x02 0x28 0x02 0x29>; reset-names = "usb0_reset\0usb1_reset\0usb2_reset\0usb3_reset"; status = "okay"; #phy-cells = <0x01>; usb0_vbus-supply = <0x16>; usb1_vbus-supply = <0x17>; phandle = <0x15>; }; usb@5101000 { compatible = "allwinner,sun50i-h616-ehci\0generic-ehci"; reg = <0x5101000 0x100>; interrupts = <0x00 0x1a 0x04>; clocks = <0x02 0x6a 0x02 0x6e 0x02 0x62>; resets = <0x02 0x2a 0x02 0x2e>; status = "okay"; phandle = <0x36>; }; usb@5101400 { compatible = "allwinner,sun50i-h616-ohci\0generic-ohci"; reg = <0x5101400 0x100>; interrupts = <0x00 0x1b 0x04>; clocks = <0x02 0x6a 0x02 0x62>; resets = <0x02 0x2a>; status = "okay"; phandle = <0x37>; }; usb@5200000 { compatible = "allwinner,sun50i-h616-ehci\0generic-ehci"; reg = <0x5200000 0x100>; interrupts = <0x00 0x1c 0x04>; clocks = <0x02 0x6b 0x02 0x6f 0x02 0x64>; resets = <0x02 0x2b 0x02 0x2f>; phys = <0x15 0x01>; phy-names = "usb"; status = "okay"; phandle = <0x38>; }; usb@5200400 { compatible = "allwinner,sun50i-h616-ohci\0generic-ohci"; reg = <0x5200400 0x100>; interrupts = <0x00 0x1d 0x04>; clocks = <0x02 0x6b 0x02 0x64>; resets = <0x02 0x2b>; phys = <0x15 0x01>; phy-names = "usb"; status = "okay"; phandle = <0x39>; }; usb@5310000 { compatible = "allwinner,sun50i-h616-ehci\0generic-ehci"; reg = <0x5310000 0x100>; interrupts = <0x00 0x1e 0x04>; clocks = <0x02 0x6c 0x02 0x70 0x02 0x66>; resets = <0x02 0x2c 0x02 0x30>; phys = <0x15 0x02>; phy-names = "usb"; status = "okay"; phandle = <0x3a>; }; usb@5310400 { compatible = "allwinner,sun50i-h616-ohci\0generic-ohci"; reg = <0x5310400 0x100>; interrupts = <0x00 0x1f 0x04>; clocks = <0x02 0x6c 0x02 0x66>; resets = <0x02 0x2c>; phys = <0x15 0x02>; phy-names = "usb"; status = "okay"; phandle = <0x3b>; }; usb@5311000 { compatible = "allwinner,sun50i-h616-ehci\0generic-ehci"; reg = <0x5311000 0x100>; interrupts = <0x00 0x20 0x04>; clocks = <0x02 0x6d 0x02 0x71 0x02 0x68>; resets = <0x02 0x2d 0x02 0x31>; phys = <0x15 0x03>; phy-names = "usb"; status = "okay"; phandle = <0x3c>; }; usb@5311400 { compatible = "allwinner,sun50i-h616-ohci\0generic-ohci"; reg = <0x5311400 0x100>; interrupts = <0x00 0x21 0x04>; clocks = <0x02 0x6d 0x02 0x68>; resets = <0x02 0x2d>; phys = <0x15 0x03>; phy-names = "usb"; status = "okay"; phandle = <0x3d>; }; Anyway, I don't want to waste your time; you was very kind already, and I am new to this DTS stuff, most probably I'm missing something. I will keep looking at your commits and will keep trying new nightly images. This board looks nicer and nicer by the day. Quite fast, feature rich for the price and does not run hot, a welcome change vs. other SBCs.

I failed to enable the USB port. Let's see: 1. I decompiled the DTB of the unstable image to a DTS 2. Examining jernej's DTS and DTSI files, I found all the nodes related to USB in the original DTS; none was missing, there was a good correspondence between the decompiled DTS and jernej's DT sources 3. The USB nodes: usb@5310000 usb@5311000 usb@5311400 had status = "disabled"; and I changed them to status = "okay"; 4. I also changed the model name to model = "OrangePi Zero2 USB v1"; in order to verify it was actually loaded. 5. I rebuilt the DTB (after having saved the original one as .bak) dtc -I dts -O dtb /boot/dtb/allwinner/sun50i-h616-orangepi-zero2_USB.dts -o /boot/dtb/allwinner/sun50i-h616-orangepi-zero2.dtb 6. Rebooted 7. Checked the new DTB was loaded: cat /proc/device-tree/model OrangePi Zero2 USB v1 8. Checked the status of the edited USB nodes (under /proc/device-tree/soc): now all USB nodes have status = okay Despite that, USB port does not work: inserting a pendrive does not trigger anything, no lines on "dmesg" Maybe enabling all the USB nodes is not enough... anyway, it was an interesting task, and I learned a few new things! sun50i-h616-orangepi-zero2_USB.dts

Excellent advice, thanks!

Understood, thank you!

(vs. kernel messages): Thank you! Since the cpufreq driver will be sorted out later, is there a way to fix the CPU frequency to a known working value via DTB? Just to perform a few tests with a fixed, known CPU clock.

I used Putty (Windows) and a CP2104 USB-to-Serial adapter, at 115200. 32 GB Sandisk Ultra card, written with Balena Etcher

I decided to have a bit of fun with the Unstable (Hirsute) from April, 3rd. Kernel is Linux orangepizero2 5.11.11-sunxi64 #trunk.69 SMP Thu Apr 1 21:56:55 My board has 512 MB of RAM. I'm running headless. OK: Well, it boots! That's nice!!! Ethernet works, with DHCP Debug UART (the 3-pins one) works, at 115200 MicroSD works. Looks quite fast too (hdparm clocks at 44.5 MB/s) Load average is 0 when doing nothing!! With original custom image from OrangePi, it shows about 1.00 Not OK yet: USB port does not work (tried with pendrive): inserted device not detected at all (like if USB port is not present) Reboot does not reboot: powers off the board Armbian-config: trying to set CPU speed and governor exits with this error: /usr/lib/armbian-config/jobs.sh: line 1115: Error: Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000: syntax error in expression (error token is ": Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000") Unable to detect (or change) CPU frequency/governor: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. Some dmesg entries indicate the kernel is still alpha-stage, as expected: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pi not found, using dummy regulator dwmac-sun8i 5020000.ethernet: supply phy-io not found, using dummy regulator dwmac-sun8i 5020000.ethernet: Current syscon value is not the default 51fe6 (expect 0) usb1-vbus: disabling vcc3v3-ext: disabling vcc3v3-ext2: disabling cldo1: disabling Summary: To me, the current Unstable image (April, 3rd) looks quite nice already. Lots of stuff work! Great work Armbian! Thanks!! Any tests I may perform, to be of any help?

Could you describe the steps you followed to build your experimental image? I've found generic steps to build Armbian, but it looks like you used a different kernel and custom configuration? What about DTB? I would like to play a little with my Orange Pi Zero2, even if most of the stuff does not work yet.

thanks!

Pardon my newbieness, is there a tutorial I can follow, to build a working Armbian bootable image based upon jernej's kernel? Thanks

undestood

I have a working OrangePI Zero2 with stock Xunlong image; but I'm a total newbie vs. Armbian, DTB, Initramfs etc. If I can help someway, just let me know (unfortunately I need step-by-step instructions or a pointer to a tutorial).