going

sunxi-6.12: leo@bananapim4berry:~$ uname -r 6.12.19-current-sunxi64 leo@bananapim4berry:~$ dmesg | grep -iE 'audio|ahub|video|codec|hdmi|drm' [ 0.099396] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.099455] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.104244] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.104620] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.104780] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.107433] /soc/hdmi@6000000: Fixed dependency cycle(s) with /connector [ 0.107516] /connector: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 1.946257] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff80008119ae90) [ 1.946454] sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff80008119fc60) [ 1.946768] sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xffff800081197ab0) [ 1.947062] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.949760] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.950030] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff800081199f58) [ 1.950535] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.950566] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 2.438265] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 4.012109] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device [ 9.311566] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 9.583263] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 9.590683] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 11.222612] [drm] Initialized panfrost 1.2.0 for 1800000.gpu on minor 1 [ 11.336128] videodev: Linux video capture interface: v2.00 [ 11.672804] cedrus 1c0e000.video-codec: Device registered as /dev/video0 [ 36.607644] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 37.501202] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 39.278755] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 39.278791] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 39.278816] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 [ 57.559744] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 57.559772] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 57.559789] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 pkg for test: sunxi64-6.12.19

boot> grep -n CEDRUS config-* 7001:CONFIG_VIDEO_SUNXI_CEDRUS=m leo@bananapim4berry:~$ dmesg | grep cedrus [ 11.499288] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. [ 11.522089] cedrus 1c0e000.video-codec: Device registered as /dev/video0 leo@bananapim4berry:~$ ls -al /dev/video0 crw-rw----+ 1 root video 81, 0 �м�а�р 18 11:53 /dev/video0 leo@bananapim4berry:~$ uname -r 6.13.7-edge-sunxi64 leo@bananapim4berry:~$ lsmod | grep cedrus sunxi_cedrus 49152 0 v4l2_mem2mem 28672 1 sunxi_cedrus videobuf2_dma_contig 20480 1 sunxi_cedrus videobuf2_v4l2 20480 2 sunxi_cedrus,v4l2_mem2mem videodev 249856 3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem videobuf2_common 53248 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_v4l2,v4l2_mem2mem,videobuf2_memops mc 53248 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem P.S. add more

Greetings to all participants. Before configuring the software, we need to properly configure the hardware nodes on the chip that are responsible for video/audio processes. Turn on the power, make a reset, adjust the clock, etc. This should be done by the kernel driver. Currently, in the sunxi(64) family for h616-h618 chips, I see a mess in the drivers. There are several of them for the same thing. They were added by different people at different times. Today, these drivers do not want to work correctly. On at least one BPI-m4-berry (h618) board. I'm trying to fix this situation right now. Please write here whatever you think is necessary to speed up the process. After applying all the sunxi-6.12 patches, the core looks like sunxi-6.12-rebase sunxi-6.13-rebase

To do this, you will need to open two sessions in the terminal. The test here is my configuration file 1 session ~/armbian$ ./compile.sh test kernel-patch ...... # build system printed: [✨] Starting [ interactive patching process for kernel ] [🌱] Creating commit to start from clean source [🌱] Patches will be created [ with the following maintainer information ] [🌱] MAINTAINER (Real name): [ The-going ] [🌱] MAINTAINERMAIL (Email): [ 48602507+The-going@users.noreply.github.com ] [🌿] If those are not correct, set them in your environment, command line, or config file and restart the process [🚸] Make your changes in this directory: [ /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ] [🚸] Press <ENTER> after you are done [ editing files in /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ] Press ENTER to show a preview of your patch, or type 'stop' to stop patching... The build system will apply all the patches and make a commit that will include all the changes. Leave this session alone. In the second session, you make your changes and record the results. 2 session leo@armbuild:~/armbian$ cd /home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64 ### open root session leo@armbuild:~/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64$ sudo su root@armbuild:/home/leo/armbian/cache/sources/linux-kernel-worktree/6.13__sunxi64__arm64# ls arch/arm64/boot/dts/rockchip/rk3399-* linux-kernel-worktree/6.13__sunxi64__arm64# nano arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts linux-kernel-worktree/6.13__sunxi64__arm64# git add --all linux-kernel-worktree/6.13__sunxi64__arm64# git commit -m "Add a comment" ###close root session: linux-kernel-worktree/6.13__sunxi64__arm64# exit linux-kernel-worktree/6.13__sunxi64__arm64$ git format-patch -1 -o /home/leo/armbian/userpatches/ /home/leo/armbian/userpatches/0001-Add-a-comment.patch linux-kernel-worktree/6.13__sunxi64__arm64$ cat /home/leo/armbian/userpatches/0001-Add-a-comment.patch From 4dad6a3fa967235ea7eef35f81733bdafd806b53 Mon Sep 17 00:00:00 2001 From: The-going <48602507+The-going@users.noreply.github.com> Date: Tue, 18 Mar 2025 12:54:11 +0000 Subject: [PATCH] Add a comment --- arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts index 2ddd4da15..29eec7e65 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts +++ b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts @@ -78,6 +78,7 @@ keys: gpio-keys { compatible = "gpio-keys"; autorepeat; + /* key-power */ key-power { debounce-interval = <100>; gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>; -- 2.34.1 What should I do with the first session? Decide for yourself!!

Printed on the chip itself: SEC 913 K4F8E30 4HBMGCJ Now we know about this chip. There is a similar discussion here 25244-ram-problem/#findComment-160334 Unfortunately, Armbian will not be able to support all the variety of chips. Only the user can independently add changes for their device and test them. If you want to build the u-boot package yourself, then Configuration for your device: config/boards/orangepizero3.csc Similarly, add the following lines to your configuration file config/boards/orangepizero2w.csc#L5-L8 Place the required set of patches in the appropriate folder.

Please post the name of the memory chip. Literally what it says on it. This issue has already been raised here on the forum. Two different users had different chips soldered on the same boards. Memory chips from different manufacturers. In one case, the memory was defined as 2GB, in the other as 1GB.

This patch is not complete. A solution already seems to exist in this discussion. I will add these changes to this PR#7705 tomorrow.

Maybe you can describe the problem/goal that you want to solve using RT Core. First you need to figure out what is required. There are several real-time Cores. And each solves its own problems.

I understood. Thank you.

[ 9.527925] videodev: Linux video capture interface: v2.00 [ 9.539551] panfrost 1800000.gpu: clock rate = 432000000 [ 9.539593] panfrost 1800000.gpu: bus_clock rate = 200000000 [ 9.540215] panfrost 1800000.gpu: mali-g31 id 0x7093 major 0x0 minor 0x0 status 0x0 [ 9.540250] panfrost 1800000.gpu: features: 00000000,000027f7, issues: 00000000,00000400 [ 9.540262] panfrost 1800000.gpu: Features: L2:0x07100206 Shader:0x00000000 Tiler:0x00000209 Mem:0x1 MMU:0x00002821 AS:0xff JS:0x7 [ 9.540274] panfrost 1800000.gpu: shader_present=0x1 l2_present=0x1 [ 9.544584] [drm] Initialized panfrost 1.2.0 for 1800000.gpu on minor 1 Thank you for the information provided! A simple clarification. Does it work on an h616 processor with the patch disabled? For the h618 processor, I was unable to get the GPU to work with or without this patch. It remains to be seen whether this patch plays a positive role for the h6 processor. If there is no positive effect, then I'd better turn it off.

Is the GPU node enabled for your board?

Try to set the disabled status for the GPU node. or temporarily disable this patch: patch/kernel/archive/sunxi-6.12/series.conf#L472

The kernel has a driver for i2s: sound/soc/sunxi/sun4i-i2s.c It works for the h6 processor. Try adding the line compatible = "allwinner,sun50i-h6-i2s" to the DTS node so that the driver can be called. This driver may also work for the h618.

Probably there should be a driver for this device in the kernel. For 6.12.16: linux-sf> grep -nr 'compatible = "maxim,max9' drivers/media/* drivers/staging/media/* drivers/media/i2c/max9286.c:1666: { .compatible = "maxim,max9286" }, drivers/media/i2c/max96714.c:1006: { .compatible = "maxim,max96714f" }, drivers/media/i2c/max96717.c:1085: { .compatible = "maxim,max96717f" }, drivers/staging/media/max96712/max96712.c:465: { .compatible = "maxim,max96712" },

I think he won't give much information in this situation. I have these two boards (OPI-5, OPI-5-plus). They both arrived with a pre-installed loader in SPI-Flash. The loading order on both boards is the same. BootRom searches for the boot code on SPI-flash and downloads it. In other words. If u-boot v2019 is written to the SPI-flash and the bootloader v2025.01 is written to the SD card, I will see the v2019 message in the UART console. Maybe the documentation will give you a hint? This is part of the wiring diagram.

I still recommend restoring the original circuit.

OPI-5, OPI-5-plus - The connection scheme of the SPI flash memory chip is similar. I did an experiment with OP-5-plus. On a running OS, I erased all mtd-flash using the dd if=/dev/zero of=/dev/mtd command. The device turned into a brick. Downloading from an SD card or NVME has become impossible. Recovery: I downloaded this archive from the official orangepi website: MiniLoader - what is needed for burning Linux images-20241230T170815Z-001.zip The device is in MaskRom mode and the MaskRom button is not pressed. MiniLoader> ls -al итого 6136 drwxr-xr-x 2 leo users 208 янв 1 20:33 . drwxr-xr-x 4 leo users 45 дек 31 16:30 .. -rw-r--r-- 1 leo users 448960 янв 1 1980 MiniLoaderAll.bin -rw-r--r-- 1 leo users 1249 янв 1 1980 rk3588_linux_emmc.cfg -rw-r--r-- 1 leo users 1859 янв 1 1980 rk3588_linux_pcie.cfg -rw-r--r-- 1 leo users 1249 янв 1 1980 rk3588_linux_spiflash.cfg -rw-r--r-- 1 leo users 1249 янв 1 1980 rk3588_linux_tfcard.cfg -rw-r--r-- 1 leo users 4194304 янв 1 1980 rkspi_loader.img -rw-r--r-- 1 leo users 1620480 янв 1 18:53 u-boot-rockchip-spi.bin rkdeveloptool db MiniLoaderAll.bin If your device switches to MaskRom mode on its own and the command returns an error at this stage, the MaskRom button may be defective (it is always pressed). This is an assumption. In my case, I had to press a button, then turn on the power and release the button. Nothing is connected to the device. There is no SD card. There is no HDMI cable. There is no UART. Only the power cable and the USB cable to the PC. Boot_option It is not possible to boot this device if the mtd chip is clean. In my case, I wrote the entire u-boot v2025.01 code to mtd. I built it myself in the Armbian build system without any additional patches. Today, my device loads any image (OS) from all the memory devices I have. Well good luck. With respect to you as a person who knows how to operate a soldering iron.

Help: Rkdeveloptool Rockusb rk3588_spl_loader_v1.15.113.bin as miniloader I assume that you have a computer with Linux OS installed. The rkdeveloptool utility is installed or built. Connect your device to this computer using a USB cable. Press the Maskrom button and hold it down to turn on the power on the device. In the next step, you should download the mini loader to your device using the rkdeveloptool utility. rkdeveloptool db rkxx_loader_vx.xx.bin Now the device should come to life and should respond to requests and perform some actions. If you have pre-downloaded and unpacked the u-boot armbian binary package for your device (extract the bootloader file from the package), you can do the following: Just in case, run the clear command. Write the armbian bootloader to the memory chip. For tips on the offset, see the u-boot package script.

https://stpete-mirror.armbian.com/ (St. Petersburg) This mirror works well in the Russian Federation. But how do I make sure that this mirror is automatically selected in the build system itself at the image creation stage? I mean the phase of installing packages in a future image. ... [🔨] Err:5 http://mirror.hostiko.network/armbian bookworm InRelease ... [🔨] Err:5 http://fastmirror.pp.ua/armbian bookworm InRelease ...

leo@bananapim64:~$ sudo nano /etc/apt/sources.list.d/armbian.list http://apt.armbian.com =>> https://stpete-mirror.armbian.com/apt leo@bananapim64:~$ cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] https://stpete-mirror.armbian.com/apt bookworm main bookworm-utils bookworm-desktop leo@bananapim64:~$ sudo apt update Сущ:1 http://deb.debian.org/debian bookworm InRelease Сущ:2 http://security.debian.org bookworm-security InRelease Сущ:3 http://deb.debian.org/debian bookworm-updates InRelease Сущ:4 http://deb.debian.org/debian bookworm-backports InRelease Сущ:5 https://github.armbian.com/configng stable InRelease Пол:6 https://stpete-mirror.armbian.com/apt bookworm InRelease [53,3 kB] Пол:7 https://stpete-mirror.armbian.com/apt bookworm/main all Packages [17,5 kB] Пол:8 https://stpete-mirror.armbian.com/apt bookworm/bookworm-utils arm64 Packages [37,4 kB] Пол:9 https://stpete-mirror.armbian.com/apt bookworm/bookworm-desktop all Packages [7 526 B] Пол:10 https://stpete-mirror.armbian.com/apt bookworm/main arm64 Packages [1 168 kB] Пол:11 https://stpete-mirror.armbian.com/apt bookworm/bookworm-desktop arm64 Packages [15,9 kB] Пол:12 https://stpete-mirror.armbian.com/apt bookworm/bookworm-utils all Packages [3 965 B] Получено 1 304 kB за 9с (149 kB/s) Чтение списков пакетов… Готово Построение дерева зависимостей… Готово Чтение информации о состоянии… Готово Может быть обновлено 4 пакета. Запустите «apt list --upgradable» для их показа.

Yesterday, at my test stand, I discovered a malfunction on the banana pi M64. The behavior is exactly the same as that of your board. I found the reason quickly. These were oxidized/weakened contacts on the power supply. When the board starts, the consumption is low. But then all the regulators are turned on, and when the OS starts setting up, consumption increases dramatically. In that place of bad contact, a voltage drop occurs and the board turns off. Soldering iron + screwdriver solved the problem. My power supply is open and I have access to it.

I think that there are no nodes in this DTS that can be deleted. Most likely, on the contrary, something needs to be added/changed. In fact, this is quite a difficult job even for an experienced developer. Some things may depend on the firmware. Try to look towards devices officially supported by Armbian.

https://docs.banana-pi.org/en/BPI-M2_Ultra/BananaPi_BPI-M2_Ultra Have you tried running any of these many old images? https://docs.banana-pi.org/en/BPI-M2_Ultra/BananaPi_BPI-M2_Ultra#_linux_2

Here it may be necessary to check the nodes in the DTS. It may be necessary to add additional missing ones. This is an assumption. Possible reasons for the hangup: 1) The config/boards/bananapim2ultra.csc configuration file for your boards is very simple. The build system applies patches from the patch/u-boot/u-boot-sunxi/ folder. Maybe some are breaking the settings for your board. Try adding these lines to the board configuration file: BOOTBRANCH="tag:v2024.01" BOOTPATCHDIR="u-boot-sunxi/board_${BOARD}" This will force the build system to apply only patches from this folder. 2) We need to make sure that the SD card is working properly. A larger card can be limited in advance. After you have written the image to the card, you can open the gnome-disk utilities and expand the first partition to 16 GB, and then create another new partition from the remaining empty space. 3) You have supplied the power. The board has started loading and the indicator is on. The board stopped loading and the indicator went out. Perhaps the CPU or GPU temperature is detected incorrectly (high) and the OS turns off the power. /boot/armbianEnv.txt file verbosity=10 All that I have written is my assumptions.

This is an old core and Armbian does not support it. If for some reason you need version 6.1, then try to build with the BRANCH="legacy" parameter. But I warn you that version 6.1 will be deleted after a while. Recommendations: Assemble the image using BRANCH="edge". Today it is the 6.12 kernel and it will become the current one soon. If you have problems downloading, try changing the debug level to 10. Post it here under the spoiler and please call me as @going.