ALIGMSTEN

Thanks, Help for h616 always welcome, there is a small amount of mainline development going on. Seems a shame if that happens to be the vendors objective the latest release. Might be useful to collect photos of the different board versions for comparison, as there is no reference right now (just a thought!)

Hello @elliotmatson Welcome. Would you mind to please elaborate on the hardware differences you can see. Unfortunately, you are correct, there do not seem to be schematics readily available for newer revisions. I have worked on V1.3 boards and have been used to having to power cycle occasionally, this might likely be tied to the current development, mainline, edge(here), and the fact that all is WIP. I did look into the power cycling more thoroughly, and although there are a few 'net crumbs' to be found, nothing indicative that I have yet seen or tried. At the moment I've had stable power on's with latest minimal build. Some of the work I've done in isolation has also improved boots. Right now am testing cpu-frequency-scaling, I will add that v1 to main 6.1.11 fairly shortly its ready, I am adding proper current sensing to my test bench, for more elaborate stability testing, hopefully resulting in better v2 Next will most likely follow the progress with DRAM. I also prefer to work with debian os so not entirely sure if ubuntu has some difference. While this doesn't answer your questions, these are known problems, and do not have definitive solutions anywhere right now.

Hi, Simply noting here, realise the busyness, right now, some config packages missing by the looks of it. [🌱] Configuration prepared for BOARD build [ orangepizero2.conf ] [✨] Repeat Build Options (early) [ ./compile.sh BOARD=orangepizero2 BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img ] armbian-firstlogin timezone misgivings. Please use this account for your daily work from now on. /usr/lib/armbian/armbian-firstlogin: line 111: curl: command not found /usr/lib/armbian/armbian-firstlogin: line 114: nmcli: command not found /usr/lib/armbian/armbian-firstlogin: line 147: curl: command not found /usr/lib/armbian/armbian-firstlogin: line 147: jq: command not found Detected timezone: Set user language based on your location? [Y/n] Y Gladly attend to it, confirm file with pointers, so Im sure please!

Hello, Interesting, have just got one, for my own research purposes and not yet seen this behavior. IMAGE: Armbian 22.11.4 Bullseye with Linux 5.15.80-sunxi64. CORRECT: @going except I have different inscriptions. SEC 113 K4E6E30 4EDEGCG JICVP59L INFO: f.y.i

Hello @mcerveny, I would like to include your thermal changes in a PR to armbian 6.1. Would this be agreeable and how can I best credit you <@users.noreply.github.com>, ofc should you be agreeable? Incidentally the switch case is finding the bins in the same manner, the sign(u32) has been noted. The intended patch is V1 as WIP and will evolve, so all constructive input very welcome please. Here are graphs called from sbc-bench sbc-bench-v0.9.13-orangepi-zero2-.YxRzeH.pdf

@going and @Igor checking the H616 mainlining thread, the x_late patch is running currently unoptimized WIP, we can improve on this as testing play's out. I will add the recommended thermal changes for now and can submit a pr to 6.1 they will be fine if that is good.

Generating locales: en_ZA.UTF-8 root@orangepizero2:~# htop --version htop 3.0.5 root@orangepizero2:~#

Tested: Armbian_23.02.1_Orangepizero2_bullseye_edge_6.1.11.img.xz Normal, first start, boot and reboot. DT known parts missing as expected. htop - can add temp and cpu frequency, however not in DT (forgot to check version) Armbian_23.02.1_Orangepizero2_bullseye_legacy_4.9.318.img.xz Does not boot. (am sure serial output will be booti error - will check if you need) boot.cmd is incorrect (copied direct from image sd card) # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # default values setenv load_addr "0x45000000" setenv overlay_error "false" setenv rootdev "/dev/mmcblk0p1" setenv verbosity "1" setenv rootfstype "ext4" setenv console "both" setenv docker_optimizations "on" setenv bootlogo "false" # Print boot source itest.b *0x10028 == 0x00 && echo "U-boot loaded from SD" itest.b *0x10028 == 0x02 && echo "U-boot loaded from eMMC or secondary SD" itest.b *0x10028 == 0x03 && echo "U-boot loaded from SPI" echo "Boot script loaded from ${devtype}" if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt env import -t ${load_addr} ${filesize} fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi if test "${bootlogo}" = "true"; then setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}" else setenv consoleargs "splash=verbose ${consoleargs}" fi # get PARTUUID of first partition on SD/eMMC it was loaded from # mmc 0 is always mapped to device u-boot (2016.09+) was loaded from if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} fdt addr ${fdt_addr_r} fdt resize 65536 for overlay_file in ${overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done for overlay_file in ${user_overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then echo "Applying user provided DT overlay ${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done if test "${overlay_error}" = "true"; then echo "Error applying DT overlays, restoring original DT" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} else if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)" source ${load_addr} fi if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr echo "Applying user provided fixup script (fixup.scr)" source ${load_addr} fi fi load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

It would be interesting, well sort-of, what the output of uname -a is, after holding back >> build/config/bootscripts/boot-sun50iw9.cmd and specifically line 67 is what legacy expects bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} implicitly build/config/bootscripts/boot-sun50i-next.cmd referencing line 77 is what boot found booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} I can only posit that build/config/boards/orangepizero2.conf line 12 is a culprit # Allwinner H616 quad core 512MB/1GB RAM SoC WiFi SPI USB-C BOARD_NAME="Orange Pi Zero2" BOARDFAMILY="sun50iw9" BOOTCONFIG="orangepi_zero2_defconfig" MODULES_LEGACY="uwe5622_bsp_sdio sprdbt_tty sprdwl_ng" MODULES_BLACKLIST="lima" DEFAULT_CONSOLE="serial" HAS_VIDEO_OUTPUT="no" SERIALCON="ttyS0" KERNEL_TARGET="legacy,current,edge" PACKAGE_LIST_BOARD="rfkill bluetooth bluez bluez-tools" FORCE_BOOTSCRIPT_UPDATE="yes" and again surmise that bsp-cli.sh from lines 172 in particular from lines 186, would need looking at. EOF # install bootscripts if they are not present. Fix upgrades from old images if [[ $FORCE_BOOTSCRIPT_UPDATE == yes ]]; then cat <<- EOF >> "${destination}"/DEBIAN/postinst if [ true ]; then # this package recreate boot scripts EOF else cat <<- EOF >> "${destination}"/DEBIAN/postinst if [ ! -f /boot/$bootscript_dst ]; then # if boot script does not exits its recreated EOF fi I rarely go very deep into the build scripts, so please correct if completely wrong. I also would not intend to look much myself on this right now, and rather focus on mainline and putting what time have towards improving that. Armbian-next is the future with master code freeze anyhow.

Upgrade overwrites: build/config/bootscripts/boot-sun50iw9.cmd

Very interesting, thanks for your work. Personally still making changes during my testing atm, better understanding uboot registers, static const struct sunxi_cpufreq_soc_data sun50i_h616_data.. . etc... I see 10 Members have downloaded , Add-h616-efuse_xlate-cpu-freq-scaling - any other feedback? Here as is sbc-bench output ( no extended thermal and gpu-sys set as manual recommends)

CHANGE: armbianEnv DOCKER FORCE CGROUPS V1: [working docker for legacy builds] extraargs=systemd.unified_cgroup_hierarchy=0 alistair@orangepizero2:~$ sudo docker run hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (arm64v8) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ Possibly also (if you haven't): Debian builds update-alternatives --set iptables /usr/sbin/iptables-legacy Rootless: haven't tried.

'Green Light occasionally', your operating system, is from Orange Pi and not Armbian. Take a look at the downloads page.

The pointer is correct and what got me through the traps before differentiating with xlate, I am uncertain about the exact shift. What do you suggest?

Thank you @mcerveny, refreshing to have such constructive input. Was aware that gpu was at max, I should have changed that back. To clarify how are you compiling, xunlong?

If you addressing me and above patch @mcerveny I'm happy to play here, its not serious. I cant speak for mainline process. In similar vein could quite happily carry on and not 'contribute' getting the 'stuffs' I need working and abuse. However I am completely against that type of behavior, and why I choose to donate and contribute.

Hi nope, fun in spare time approach here, arm64-dts-allwinner-h616-Add-efuse_xlate-cpufreq.patch. Will submit pr to armbian 5.19.17 this week, if @going and @mcerveny can please review.

Nice, looks like you standing up on Orangepi there? Interesting, I've been working low down your list, testing cpu-frequency-scaling for a while, which I think now will submit PR to 5.19 for others to try. The patch addresses all variants, but is not optimized, limited to 1512 Mhz, still WIP is the frequency calc's and micro-volt testing. All that you list has been in progress for a while, but has not seen the light here for lack of someone knowledgeable having time or perhaps interest, and that it seems there are still issues to be worked out in some parts. @going is doing an incredible job at maintaining sunxi here for us to develop off.

Hi @carlos8agomez, which module are you using, assuming w1_gpio? There is an alternative that supports your sensor type, kernel driver w1_therm (W1_THERM_DS18B20, 0x28). For example, you could try MOSI, PH7, pin 19, gpio 231 (apparently better transfer, I have no clue though, can’t verify, not tried anything) this is SPI 1 bus, which could add to your complications. Unfortunately that is not enabled by default in the current or edge images, and will require you to do this. @orangepizero2:~ $ ls -l /dev/spidev* ls: cannot access '/dev/spidev*': No such file or directory @orangepizero2:~ $ dmesg | grep spi* [ 1.599280] sun6i-spi 5010000.spi: Failed to request TX DMA channel [ 1.599290] sun6i-spi 5010000.spi: Failed to request RX DMA channel For a user to do that you will have added an overlay, this is again not by default for Zero2 here now, and note what @lampra advised at the beginning of mainline development. You could probably be better off looking at PC10, however there could also be issues that would require you to dig deeper, and there is an overlay to write, paying attention to compatible = "allwinner,sun50i-h616 "; and its nodes. If you struggle with any of this I would suggest at least, reading the documentation, pin outs and their respective assignments, and trying @lampra suggestion above. Sorry I can’t be more helpful, than suggestions, I have not actually tried to do this for One wire sensors on opiz2.

Hi, You can compile with: ./compile.sh CREATE_PATCHES="yes" The build will pause; atf, uboot, kernel, with each stop you can make your respective changes. Haven't looked much at boot options - perhaps someone with experience can chime in?

Hi, haven't tried myself, think you have to add these lines to /boot/armbianEnv.txt. Check https://linux-sunxi.org/1-Wire regards hardware, reading further not sure which pin opiz2, have you looked at manual? What have you tried? Tell us a bit more and perhaps we can help, .. uname -a etc. Which sensor? what protocol(com can be different), hook up etc.. Also read up about overlays and MOSI PH7. There's lots of info in the forums. Might not be possible with current or edge configurations etc .. without personal efforts.... overlays=w1-gpio param_w1_pin=???? param_w1_pin_int_pullup=0

Building from htop source on the board and configuring very simple exercise. alistair@orangepizero2:~$ htop --version htop 3.2.2-dev libsensors finds thermal on device 'opiz2' without configuration. I had a try to use the library by writing to it in c++, unfortunately had numerous compile issues, have not been able to extract the info I wanted yet. Time intervals are as @going has noted I did not look at source, beyond build at all and did not find configuration option, could easily missed if there.

Thank you @going, will have a go later this evening.

Right thank you both for the reasons and solutions, to add must be bullseye here, because same issue with new build. Other info: from htop-dev

If am doing this right here result. Cpufreq and temperature not displaying. alistair@orangepizero2:~$ sudo apt remove htop Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: htop 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 257 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 131780 files and directories currently installed.) Removing htop (3.1.0-0~armbian20.08.2+1) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for mailcap (3.69) ... Processing triggers for desktop-file-utils (0.26-1) ... alistair@orangepizero2:~$ sudo apt install htop Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: strace The following NEW packages will be installed: htop 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 88.5 kB of archives. After this operation, 257 kB of additional disk space will be used. Get:1 http://apt.armbian.com bullseye/bullseye-utils arm64 htop arm64 3.1.0-0~armbian20.08.2+1 [88.5 kB] Fetched 88.5 kB in 3s (34.7 kB/s) Selecting previously unselected package htop. (Reading database ... 131772 files and directories currently installed.) Preparing to unpack .../htop_3.1.0-0~armbian20.08.2+1_arm64.deb ... Unpacking htop (3.1.0-0~armbian20.08.2+1) ... Setting up htop (3.1.0-0~armbian20.08.2+1) ... Processing triggers for mailcap (3.69) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for man-db (2.9.4-2) ... alistair@orangepizero2:~$ htop --version htop 2.2.0 - (C) 2004-2020 Hisham Muhammad Released under the GNU GPL.