ALIGMSTEN

Correct, I suspect its something to do with crust implementation. Edit: 2023.01 9525b2d16c0aa0ec5cf446322e58a0dabb26c857 not booting (for clarity) 2022.10 bc46fd509a50db4bcef014d79569b68287ecc19b boots config/boards/orangepi3-lts.csc @@ -7,6 +7,7 @@ KERNEL_TARGET="current,edge" MODULES="sprdbt_tty sprdwl_ng" MODULES_BLACKLIST_LEGACY="bcmdhd" ATFBRANCH="tag:v2.2" + CRUSTCONFIG="h6_defconfig" function post_family_tweaks_bsp__orangepi3-lts_BSP() { display_alert "Installing BSP firmware and fixups" @@ -20,4 +21,4 @@ function post_family_tweaks_bsp__orangepi3-lts_BSP() { fi return 0 - } + } Let me know what else you may need from me and will gladly assist

Hello @Gunjan Gupta .... as discussed emmc got in the way of initial boot above hence serial output. The following boots: bc46fd509a50db4bcef014d79569b68287ecc19b Output as follows: alistair@h616-hdmi:~/build$ git rev-parse HEAD 6dd7067c79bb04aa2b17eddcfc3730639c070267 Will have a look around, when a moment.

Hello @Gunjan Gupta thanks for being explicit to OP, I would have been far to terse with minimal instructions. Anyways, as this seems to stuck for user's here what found. alistair@h616-hdmi:~/build$ git status HEAD detached at f2257004a Untracked files: (use "git add <file>..." to include in what will be committed) ptmain.sh nothing added to commit but untracked files present (use "git add" to track) alistair@h616-hdmi:~/build$ git branch * (HEAD detached at f2257004a) AGM1968/build cpu-frequency-scaling h616-DE main sunxi alistair@h616-hdmi:~/build$ git rev-parse HEAD f2257004a8fe147cd40dc03384435553ca890bf2 alistair@h616-hdmi:~/build$ U-Boot SPL 2022.07-armbian (Nov 30 2022 - 10:44:41 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):a04808c1-dirty NOTICE: BL31: Built : 10:44:34, Nov 30 2022 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc086990, model: OrangePi 3 LTS INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2022.07-armbian (Nov 30 2022 - 10:44:41 +0000) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 LTS DRAM: 2 GiB Core: 50 devices, 14 uclasses, devicetree: separate WDT: Not starting watchdog@7020400 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet 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 3259 bytes read in 2 ms (1.6 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 203 bytes read in 2 ms (98.6 KiB/s) 37640 bytes read in 6 ms (6 MiB/s) 3844 bytes read in 5 ms (750 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 45000000 17114322 bytes read in 3058 ms (5.3 MiB/s) ** fs_devread read error - block Failed to mount ext2 filesystem... Can't set block device Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 switch to partitions #0, OK mmc1(part 0) is current device 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 No ethernet found. No ethernet found. =>

Hi Chaps, Yes I do have an idle device, unfortunately absolutely zero time atm. I'll read the thread this evening and see if can help debug. Rgds, Alistair

The only solution for legacy images is to downgrade to cgroups v1 with kernel parameter You add this in armbianEnv.txt extraargs=systemd.unified_cgroup_hierarchy=0 To use cgroup v2, you need to have kernel 4.15 or later https://github.com/opencontainers/runc/blob/v1.0.0-rc95/docs/cgroup-v2.md#host-requirements. Other requirements you might need to set iptables debian os The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables. sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy As for non booting zero2 images please check latest, builds are working fine for me at this point, although I will check, (limited time atm, also 'not sure about mirrors synching').

All well. Obvious, though might be best here. Interested users and contributors are encouraged to join #linux-sunxi on OFTC to discuss the firmware and its integration with other software.

Hi Gunjan, focused on H616 right now. Sorry, although very interested, cant add, don't have any experience!

Yes that's right you must include the file in the directory /sunxi-6.1/patches.armbian and then manually edit the file at patch/kernel/archive/sunxi-6.1/series.conf series.armbian to include your new patch. I've not tried userpatches and don't know if it functions or not - perhaps raise an issue if you are sure it not currently working. ADD: I think its correct that placing the file in the top directory series.conf picks it up (was smth like that master)

No it creates your patch, then you have to manually apply. [🌱] You will find your patch here: [ /home/alistair/build/output/patch/kernel-sunxi64-edge.patch ] [✨] Now you can manually move the produced patch to your userpatches or core patches to have it included in the next build [ /home/alistair/build/output/patch/kernel-sunxi64-edge.patch ] [💖] Stopping after creating kernel patch [🌱] Runtime [ 2:27 min ] I do it this way for sunxi kernels as an example: git -C cache/sources/linux-kernel-worktree/6.2__sunxi64__arm64 format-patch -1 -o ~/build/patch/kernel/archive/sunxi-6.2/patches.armbian/ /home/alistair/build/patch/kernel/archive/sunxi-6.2/patches.armbian/0001-Patching-kernel-sunxi64-files-arch-arm64-boot-dts-al.patch cd into the directory: mv 0001-Patching-kernel-sunxi64-files-arch-arm64-boot-dts-al.patch <name of your new patch>.patch In order to apply the patch during the build you have to change the series files to include your patch. You include(commit) or discard your changes to git as you chose. I don't have a use for userpatches (can't comment whether or not it works 'as expected' in main) as I'm normally doing a specific task that will lead to a commit. I found inconsistencies (1st weeks of main) where patches (output/patch) were included in build even though not implicitly stated with cmd. Hope this somewhat helps!

cmd line is one parameter at a time, in this case kernel-patch other patching options, atf and uboot same approach

PLEASE NOTE: This topic is for the Legacy images 4.9 kernel. @Werner I think we need to make distinction between Legacy and then mainline kernels for Issues not sure if you have time to help move things around possibly? For edge not yet available, this is in development/testing! I will investigate, quickly looks like device tree is failing to load!

My humble apologies, in haste copy/paste incorrectly! have amended the example. Correct I've found that change to be visually appealing and closest to the 4.9 legacy kernels Thanks, valid points, noted the on-page posting last couple, instead of correctly formatted text in attachments or links, agreed that might be easier read. Trigger Options: usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlo ck kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-di sk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic mmc 0 rfkill-any rfkill-none stmmac-0:01:link stmmac-0:01:1Gbps stmmac-0:01:100Mbps stmmac-0:01:10Mbps Lets see, perhaps doing this in a 'democratic-manner' here is not the way. Merged - https://github.com/armbian/build/pull/5270 As above your preferences can be altered when you build!

Simple led change proposal As development gains traction here I would like to propose a change to the way the onboard led's trigger. Please state your preference! Personal preference over time spent working with edge here. diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts b/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts index 159ffe654..23349c6ec 100644 --- a/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts +++ b/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts @@ -28,16 +28,17 @@ leds { compatible = "gpio-leds"; led-0 { - function = LED_FUNCTION_POWER; + function = LED_FUNCTION_STATUS; color = <LED_COLOR_ID_RED>; gpios = <&pio 2 12 GPIO_ACTIVE_HIGH>; /* PC12 */ - default-state = "on"; + linux,default-trigger = "heartbeat"; }; led-1 { - function = LED_FUNCTION_STATUS; + function = LED_FUNCTION_POWER; color = <LED_COLOR_ID_GREEN>; gpios = <&pio 2 13 GPIO_ACTIVE_HIGH>; /* PC13 */ + default-state = "on"; }; };

@dziekon I've left current open, please go ahead and continue experimenting, and happy to collaborate. (If you can help with adding DE let us know? that is now priority) Zero2 needs people here to help! Armbian-next commits 26th May 2023 https://github.com/armbian/build/commit/e08645740bc75f456e51b785ad4555fbce4f40fd

Hi @dziekon yeah I've been a bit too much on the experiential side with this, which caused some problems with the probe failing during those tests. I wasn't wanting to progress further myself until finished with v2-opp points, xlate alternative structure and PLL_CPUX experimentation. Your PR proposal is exactly how the xlate patch is transferred to 6.x.y, there is nothing magic about the change, I am experimenting with alternative ways of doing that. Best, Alistair Patch below as reference: (Nonetheless just to note I was about to 'finally' submit V1 in light of the comments 12 May) From 7aee19c8c4a6c400dc45556e138d577d5453661d Mon Sep 17 00:00:00 2001 From: AGM1968 <AGM1968@users.noreply.github.com> Date: Wed, 1 Mar 2023 14:16:30 +0200 Subject: [PATCH] Add-h616-efuse_xlate-cpu-freq-scaling-v1 Signed-off-by: AGM1968 <AGM1968@users.noreply.github.com> --- .../dts/allwinner/sun50i-h616-cpu-opp.dtsi | 75 ++++++++++++++++ .../allwinner/sun50i-h616-orangepi-zero2.dts | 6 ++ drivers/cpufreq/cpufreq-dt-platdev.c | 4 + drivers/cpufreq/sun50i-cpufreq-nvmem.c | 87 ++++++++++++++----- 4 files changed, 150 insertions(+), 22 deletions(-) create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi new file mode 100644 index 000000000000..36f2950367c6 --- /dev/null +++ b/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi @@ -0,0 +1,75 @@ +//SPDX-License-Identifier: (GPL-2.0+ OR MIT) +//Testing Version 1 from: AGM1968 <AGM1968@users.noreply.github.com> +//Noted: PLL_CPUX = 24 MHz*N/P (WIP) + +/ { + cpu_opp_table: opp-table-cpu { + compatible = "allwinner,sun50i-h616-operating-points"; + nvmem-cells = <&cpu_speed_grade>; + opp-shared; + + opp-480000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <480000000>; + opp-microvolt-speed0 = <820000 820000 1100000>; + opp-microvolt-speed1 = <880000 880000 1100000>; + opp-microvolt-speed2 = <880000 880000 1100000>; + }; + + opp-600000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <600000000>; + opp-microvolt-speed0 = <820000 820000 1100000>; + opp-microvolt-speed1 = <880000 880000 1100000>; + opp-microvolt-speed2 = <880000 880000 1100000>; + }; + + opp-792000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <792000000>; + opp-microvolt-speed0 = <860000 860000 1100000>; + opp-microvolt-speed1 = <940000 940000 1100000>; + opp-microvolt-speed2 = <940000 940000 1100000>; + }; + + opp-1008000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <1008000000>; + opp-microvolt-speed0 = <900000 900000 1100000>; + opp-microvolt-speed1 = <1020000 1020000 1100000>; + opp-microvolt-speed2 = <1020000 1020000 1100000>; + }; + + opp-1200000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt-speed0 = <960000 960000 1100000>; + opp-microvolt-speed1 = <1100000 1100000 1100000>; + opp-microvolt-speed2 = <1100000 1100000 1100000>; + }; + + opp-1512000000 { + clock-latency-ns = <244144>; /* 8 32k periods */ + opp-hz = /bits/ 64 <1512000000>; + opp-microvolt-speed0 = <1100000 1100000 1100000>; + opp-microvolt-speed1 = <1100000 1100000 1100000>; + opp-microvolt-speed2 = <1100000 1100000 1100000>; + }; + }; +}; + +&cpu0 { + operating-points-v2 = <&cpu_opp_table>; +}; + +&cpu1 { + operating-points-v2 = <&cpu_opp_table>; +}; + +&cpu2 { + operating-points-v2 = <&cpu_opp_table>; +}; + +&cpu3 { + operating-points-v2 = <&cpu_opp_table>; +}; diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts b/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts index b78941d290ad..4babfac99043 100644 --- a/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts +++ b/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts @@ -6,6 +6,7 @@ /dts-v1/; #include "sun50i-h616.dtsi" +#include "sun50i-h616-cpu-opp.dtsi" #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/interrupt-controller/arm-gic.h> @@ -216,6 +217,11 @@ &pio { vcc-pi-supply = <&reg_aldo1>; }; +&cpu0 { + cpu-supply = <&reg_dcdca>; + status = "okay"; +}; + &spi0 { status = "okay"; pinctrl-names = "default"; diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 69a8742c0a7a..7fadcbe0c3c6 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++ b/drivers/cpufreq/cpufreq-dt-platdev.c @@ -2,6 +2,9 @@ /* * Copyright (C) 2016 Linaro. * Viresh Kumar <viresh.kumar@linaro.org> + * + * ADD cpufreq nvmem for allwinner h616 SoC, known to be analagous to h6 + * Version 1 AGM1968 <AGM1968@users.noreply.github.com> */ #include <linux/err.h> @@ -102,6 +105,7 @@ static const struct of_device_id allowlist[] __initconst = { */ static const struct of_device_id blocklist[] __initconst = { { .compatible = "allwinner,sun50i-h6", }, + { .compatible = "allwinner,sun50i-h616", }, { .compatible = "arm,vexpress", }, diff --git a/drivers/cpufreq/sun50i-cpufreq-nvmem.c b/drivers/cpufreq/sun50i-cpufreq-nvmem.c index 1acec58c33c3..690ae956659b 100644 --- a/drivers/cpufreq/sun50i-cpufreq-nvmem.c +++ b/drivers/cpufreq/sun50i-cpufreq-nvmem.c @@ -6,6 +6,9 @@ * provide the OPP framework with required information. * * Copyright (C) 2019 Yangtao Li <tiny.windzz@gmail.com> + * + * ADD efuse_xlate to extract SoC version so that h6 and h616 can coexist. + * Version 1 AGM1968 <AGM1968@users.noreply.github.com> */ #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt @@ -19,25 +22,61 @@ #define MAX_NAME_LEN 7 -#define NVMEM_MASK 0x7 -#define NVMEM_SHIFT 5 +#define SUN50I_H616_NVMEM_MASK 0x22 +#define SUN50I_H616_NVMEM_SHIFT 5 +#define SUN50I_H6_NVMEM_MASK 0x7 +#define SUN50I_H6_NVMEM_SHIFT 5 + +struct sunxi_cpufreq_soc_data { + u32 (*efuse_xlate) (void *efuse); +}; static struct platform_device *cpufreq_dt_pdev, *sun50i_cpufreq_pdev; +static u32 sun50i_h616_efuse_xlate(void *efuse) +{ + u32 efuse_value = (*(u32 *)efuse >> SUN50I_H616_NVMEM_SHIFT) & + SUN50I_H616_NVMEM_MASK; + + /* Tested as V1 h616 soc. Expected efuse values are 1 - 3, + slowest to fastest */ + if (efuse_value >=1 && efuse_value <= 3) + return efuse_value - 1; + else + return 0; +}; + +static u32 sun50i_h6_efuse_xlate(void *efuse) +{ + u32 efuse_value = (*(u32 *)efuse >> SUN50I_H6_NVMEM_SHIFT) & + SUN50I_H6_NVMEM_MASK; + + /* + * We treat unexpected efuse values as if the SoC was from + * the slowest bin. Expected efuse values are 1 - 3, slowest + * to fastest. + */ + if (efuse_value >= 1 && efuse_value <= 3) + return efuse_value - 1; + else + return 0; +}; + /** * sun50i_cpufreq_get_efuse() - Determine speed grade from efuse value + * @soc_data: pointer to sunxi_cpufreq_soc_data context * @versions: Set to the value parsed from efuse * * Returns 0 if success. */ -static int sun50i_cpufreq_get_efuse(u32 *versions) +static int sun50i_cpufreq_get_efuse(const struct sunxi_cpufreq_soc_data *soc_data, + u32 *versions) { struct nvmem_cell *speedbin_nvmem; struct device_node *np; struct device *cpu_dev; - u32 *speedbin, efuse_value; + u32 *speedbin; size_t len; - int ret; cpu_dev = get_cpu_device(0); if (!cpu_dev) @@ -47,9 +86,9 @@ static int sun50i_cpufreq_get_efuse(u32 *versions) if (!np) return -ENOENT; - ret = of_device_is_compatible(np, - "allwinner,sun50i-h6-operating-points"); - if (!ret) { + if (of_device_is_compatible(np, "allwinner,sun50i-h6-operating-points")) {} + else if (of_device_is_compatible(np, "allwinner,sun50i-h616-operating-points")) {} + else { of_node_put(np); return -ENOENT; } @@ -65,17 +104,7 @@ static int sun50i_cpufreq_get_efuse(u32 *versions) if (IS_ERR(speedbin)) return PTR_ERR(speedbin); - efuse_value = (*speedbin >> NVMEM_SHIFT) & NVMEM_MASK; - - /* - * We treat unexpected efuse values as if the SoC was from - * the slowest bin. Expected efuse values are 1-3, slowest - * to fastest. - */ - if (efuse_value >= 1 && efuse_value <= 3) - *versions = efuse_value - 1; - else - *versions = 0; + *versions = soc_data->efuse_xlate(speedbin); kfree(speedbin); return 0; @@ -83,18 +112,23 @@ static int sun50i_cpufreq_get_efuse(u32 *versions) static int sun50i_cpufreq_nvmem_probe(struct platform_device *pdev) { + const struct of_device_id *match; int *opp_tokens; char name[MAX_NAME_LEN]; unsigned int cpu; u32 speed = 0; int ret; + match = dev_get_platdata(&pdev->dev); + if (!match) + return -EINVAL; + opp_tokens = kcalloc(num_possible_cpus(), sizeof(*opp_tokens), GFP_KERNEL); if (!opp_tokens) return -ENOMEM; - ret = sun50i_cpufreq_get_efuse(&speed); + ret = sun50i_cpufreq_get_efuse(match-> data, &speed); if (ret) { kfree(opp_tokens); return ret; @@ -160,8 +194,17 @@ static struct platform_driver sun50i_cpufreq_driver = { }, }; +static const struct sunxi_cpufreq_soc_data sun50i_h616_data = { + .efuse_xlate = sun50i_h616_efuse_xlate, +}; + +static const struct sunxi_cpufreq_soc_data sun50i_h6_data = { + .efuse_xlate = sun50i_h6_efuse_xlate, +}; + static const struct of_device_id sun50i_cpufreq_match_list[] = { - { .compatible = "allwinner,sun50i-h6" }, + { .compatible = "allwinner,sun50i-h6", .data = &sun50i_h6_data }, + { .compatible = "allwinner,sun50i-h616", .data = &sun50i_h616_data }, {} }; MODULE_DEVICE_TABLE(of, sun50i_cpufreq_match_list); @@ -197,8 +240,8 @@ static int __init sun50i_cpufreq_init(void) return ret; sun50i_cpufreq_pdev = - platform_device_register_simple("sun50i-cpufreq-nvmem", - -1, NULL, 0); + platform_device_register_data(NULL, + "sun50i-cpufreq-nvmem", -1, match, sizeof(*match)); ret = PTR_ERR_OR_ZERO(sun50i_cpufreq_pdev); if (ret == 0) return 0; -- Created with Armbian build tools https://github.com/armbian/build

Personally I've not traveled into those areas, there are patches to study.

Hello, I see that the original xlate patch has been followed and adopted by other known kernel developers for 6.x.y. For the 6.x.y kernels there is a hard study to utilize the patch due to a change to tokens from tables. The probe fails because of these changes. I did not want to do the obvious, and have been working through some options. However for the sake of progress to 6.x.y perhaps that might be the way to go for now, I am more comfortable doing that, seeing that was a solution adopted by well known dev. [ 2.335847] Internal error: Oops: 0000000096000004 [#1] SMP [ 2.341864] Modules linked in: [ 2.345158] CPU: 1 PID: 50 Comm: kworker/u8:1 Not tainted 6.1.19-sunxi64 #trunk [ 2.353065] Hardware name: OrangePi Zero2 (DT) [ 2.357848] Workqueue: events_unbound deferred_probe_work_func [ 2.364173] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.371706] pc : sun50i_cpufreq_nvmem_probe+0xd4/0x2e8 [ 2.377270] lr : sun50i_cpufreq_nvmem_probe+0xcc/0x2e8 [ 2.382847] sp : ffff8000097abad0 [ 2.386405] x29: ffff8000097abad0 x28: 0000000000000000 x27: 0000000000000000 [ 2.394143] x26: ffff0000020b8a74 x25: 0000000000000000 x24: ffff0000022e0000 [ 2.401889] x23: ffff00003fd780b8 x22: ffff0000049c3300 x21: ffff0000049c3380 [ 2.409627] x20: ffff0000049c3400 x19: ffff8000090bbe18 x18: 0000000000000014 [ 2.417338] x17: 00000000413cc101 x16: 0000000042260e86 x15: 000066b8303dd330 [ 2.425076] x14: 0000000000000001 x13: 000000000000006e x12: 0000000000000001 [ 2.432778] x11: 0000000000000001 x10: 0000000000000050 x9 : ffff8000097ab890 [ 2.440480] x8 : 0000000000000050 x7 : ffff00003fd92240 x6 : ffff0000049c3480 [ 2.448199] x5 : ffff0000022e1304 x4 : 0000000000000000 x3 : 0000000000000001 [ 2.455910] x2 : 0000000000000001 x1 : 0000000000000002 x0 : ffff0000022e1304 [ 2.463612] Call trace: [ 2.466253] sun50i_cpufreq_nvmem_probe+0xd4/0x2e8 [ 2.471442] platform_probe+0x68/0xd8 [ 2.475378] really_probe+0xc0/0x3a0 [ 2.479265] __driver_probe_device+0x7c/0x188 [ 2.483967] driver_probe_device+0x3c/0x108 [ 2.488479] __device_attach_driver+0xbc/0x158 [ 2.493268] bus_for_each_drv+0x7c/0xd0 [ 2.497414] __device_attach+0xec/0x1a8 [ 2.501560] device_initial_probe+0x14/0x20 [ 2.506071] bus_probe_device+0x9c/0xa8 [ 2.510209] deferred_probe_work_func+0x9c/0xf0 [ 2.515101] process_one_work+0x220/0x3e8 [ 2.519420] worker_thread+0x258/0x500 [ 2.523477] kthread+0xd8/0xe8 [ 2.526758] ret_from_fork+0x10/0x20 [ 2.530605] Code: aa1503e0 9402276a b140069f 54000608 (f9400321) [ 2.537200] ---[ end trace 0000000000000000 ]---

Armbian-next commits Commits on May 3, 2023 h616 Cpu frequency scaling (#5123) * Add-h616-efuse_xlate-cpu-freq-scaling * series_additions_h616-cpu-freq-scaling * series_armbian_changes_h616-cpu-freq-scaling --------- Co-authored-by: AGM1968 <AGM1968@users.noreply.githib.com> https://github.com/armbian/build/commit/250a9c2cc0206c586557f37bc3db820d3750da39 Commits on May 5, 2023 sunxi-6.2 h616: Fix thermal zones (add missing trips) main (#5135) @mdziekon @igorpecovnik mdziekon authored and igorpecovnik committed last week https://github.com/armbian/build/commit/7167d5c4200de30f7b103e5f9b478dcec78642ec sunxi-6.1 h616: Fix thermal zones (add missing trips) main (#5135) @mdziekon @igorpecovnik mdziekon authored and igorpecovnik committed last week https://github.com/armbian/build/commit/613234a75cebd4de421e8b832a4efc8bc23eeac2

SEE: fellow member @mcerveny efforts I tried to setup/enable some other components and I am successful with upstream linux kernel 6.2RC5: - displayengine (drm, fb, mixer, tcon, hdmi) (seems to have some I2C/EDID problems) - videoengine (cedrus) (in testing now) - gpu (3d mali, panfrost)

A suggestion would be to check the status of uart on the board. dmesg | grep tty* ls -l /dev/ttyS5 ls -l /dev/ttyS* ps -ef | grep tty etc, to start with, and report. If you are more specific what you have tried, a fellow member may offer assistance, should they have a working solution.

Hello @Nacho Blanco ,I assume for the legacy images, (don't spend time with there), you would also have to add an overlay & its prefix to /boot/armbianEnv.txt overlay_prefix=sun50i-h616 overlays=uart5 What I sort of recalled for uart5 is that one of the peripheral definitions is disabled allwinner,function = "io_disabled" My understanding is this does not have any bearing other than its disabled, until you set status='okay' enabling the peripheral. Edited: clarification Its 'understood' that just adding the parameters to armbianEnv accomplishes nothing, whether or not the prefix=sun50iw9/sun50i-h616 the necessary, dtb entries, folders and files must exist or be created, right? Option 1: de-compile the dts and make the changes and recompile on the board (no overlay). Option 2: create the overlay and add to /boot/dtb/sunxi/overlay (think that's right) then adding the parameters to armbianEnv does the dynamic loading for you (again assuming) Option 3: dynamic load manually (something like this) mkdir -p /sys/kernel/config/device-tree/overlays/uart5 cat uart5.dtbo > /sys/kernel/config/device-tree/overlays/uart5/dtbo I'm pretty sure the legacy kernel has symbols enabled so all this should be possible for overlays. Best of luck.....

Most Welcome ..... A big tip of the hat to the framework developers @rpardini, @Igor and @Werner for fixing the legacy images. One might have to be careful when upgrading though... I've not had a serious look at the fix to concur what happens should one do so.

Hello @Nacho Blanco I speak under correction, because I cant recall the 4.9 dtb from memory just at the moment, its possible that the nodes are not enabled. With the edge images you should not expect the the green led to light up, we would have to submit a simple patch for that behavior. Unfortunately I've not had much time available lately to continue some work on OPIZ2, nonetheless edge images on the community support page, should be functioning as minimal cli. Best of luck...

Hello @Amol Right now OPIZ2 is community supported only. Images that are booting and behaving as one might expect are the legacy images derived from original vendor sources: https://www.armbian.com/orange-pi-zero-2/ Kernel 4.9.y, Size: 385Mb, Release date: Apr 8, 2023. Mainline based Armbian Edge: https://redirect.armbian.com/region/EU/orangepizero2/Bullseye_edge images are WIP and could have booting and upgrading issues, these and 'features' which might be considered normal may improve as development work happens. Good luck with your progress.

For building from the main branch, you have to add CREATE_PATCHES=yes, ARTIFACT_IGNORE_CACHE=yes