All Activity

Thanks Nick A, that was an unclear part of reboot magic. After playing with installation, I noticed that: bluetooth doesn't work (looks like a bug you mentioned), HDMI doesn't detect the tv, hdmi sound also doesn't work, wifi doesn't even appear in kernel log. I boot minimal image, without xfce. Is there any difference?

@pocosparc Today i'm trying to fix wifi rk3566-h96-tvbox.dts

https://www.armbian.com/amlogic-s9xx-tv-box/ Armbian Bookworm XFCE Armbian_community 24.5.0-trunk.537 Bookworm with Linux 6.6.30-current-meson64

What build of Armbian are you running?

@gen ha what kernel are you using? 6.6 mainline? 6.2 mainline? 5.1 legacy? 6.1 vendor?

yes Sune, I tried with the 'serial adapter, but the console won't boot (connection parameters are correct)

hi i currently using bookworm with xfce this is the dtb file im using https://github.com/ophub/amlogic-s9xxx-armbian/files/8715826/meson-gxm-tx9-pro.dtb.zip i put in /boot/dtb/amlogic edit the conf file in /extlinux/extlinux.conf, I add the line FDT=/dtb/amlogic/the name of the dtb file, I Don't know what is the issue but the wifi sometimes works sometimes Don't I have to reset the box to get it to work, and I do apt upgrade the box won't turn on until put back the the dtb file in the folder and edit the conf file and the emmc boot file

Hello, I'am recently install Armbian_community 24.5.0-trunk.563 Bookworm with Linux 6.6.30-current-rockchip64 on RKM v3 tv-stick and it works good, excepting wireless: root@rk3318-box:~# dmesg | grep brcmfmac [ 10.596796] brcmfmac: F1 signature read @0x18000000=0x1532a9a6 [ 10.609573] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430b0-sdio for chip BCM43430/2 [ 10.610733] usbcore: registered new interface driver brcmfmac [ 10.611292] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.rockchip,rk3318-box.bin failed with error -2 [ 10.611486] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.bin failed with error -2 [ 11.619242] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 RKM v3 is tv-stick with rk3328 cpu 2g ram 16g emmc (https://www.rikomagic.com/en/showgoods/90.html) Inside the stick has rk805-1 power chip and klmag1jetd emmc chip. Not sure about memory because it under the same heat sink with cpu. Stock image, extracted from eMMC with help of multitool looks like this: /dev/loop0p1 16384 24575 8192 4M /dev/loop0p2 24576 32767 8192 4M /dev/loop0p3 32768 40959 8192 4M /dev/loop0p4 40960 43007 2048 1M /dev/loop0p5 43008 75775 32768 16M /dev/loop0p6 75776 141311 65536 32M /dev/loop0p7 141312 149503 8192 4M /dev/loop0p8 149504 157695 8192 4M /dev/loop0p9 157696 190463 32768 16M /dev/loop0p10 190464 192511 2048 1M /dev/loop0p11 192512 258047 65536 32M /dev/loop0p12 258048 389119 131072 64M /dev/loop0p13 389120 421887 32768 16M /dev/loop0p14 421888 946175 524288 256M /dev/loop0p15 946176 9334783 8388608 4G /dev/loop0p16 9334784 9367551 32768 16M /dev/loop0p17 9367552 13561855 4194304 2G /dev/loop0p18 13561856 13692927 131072 64M /dev/loop0p19 13692928 13693951 1024 512K /dev/loop0p20 13693952 13698047 4096 2M /dev/loop0p21 13698048 30535646 16837599 8G some partitions have dtbs: rkm_android7_dtbs/ ├── p1 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb.dtb │ ├── 02_dtbdump_rockchip,rk3328-evb.dtb │ ├── 03_dtbdump_rockchip,rk3328-evb.dtb │ ├── 04_dtbdump_rockchip,rk3328-evb.dtb │ └── offset ├── p11 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb-avb.dtb │ └── offset ├── p12 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb-avb.dtb │ ├── 02_dtbdump_Rockchip_RK3128h_liantong_board.dtb │ └── offset └── p8 ├── 00_kernel ├── 01_dtbdump_Rockchip_RK3128h_liantong_board.dtb └── offset p1 01..04 files contain the same and look like for bootloader (very brief) p11 and p12 partition contain bigger one - 01_dtbdump_rockchip,rk3328-evb-avb.dtb (same content in both p11 and p12 partitions as i see). it contains such nodes: wireless-bluetooth { compatible = "bluetooth-platdata"; clocks = <0x9a 0x01>; clock-names = "ext_clock"; uart_rts_gpios = <0x76 0x0a 0x01>; pinctrl-names = "default\0rts_gpio"; pinctrl-0 = <0x9b>; pinctrl-1 = <0x9c>; BT,power_gpio = <0x76 0x15 0x00>; BT,wake_host_irq = <0x76 0x1a 0x00>; status = "okay"; }; wireless-wlan { compatible = "wlan-platdata"; rockchip,grf = <0x1c>; wifi_chip_type = "ap6354"; sdio_vref = <0x708>; WIFI,host_wake_irq = <0x76 0x13 0x00>; status = "okay"; }; inside the stick there is a chip with metal cap marked AP6212 but in the last_kmsg from stock firmware there is such a line: <6>[ 2.304427] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6354 partition 17 have firmwares: ls rkm_v3_p17/etc/firmware/ 4343A0.hcd fw_bcm4334b1_ag_apsta.bin fw_RK903_p2p.bin rtl8723b_fw awnb108.hcd fw_bcm4334b1_ag.bin monet.bin rtl8723bs_config bcm20710a1_24M.hcd fw_bcm4334b1_ag_p2p.bin nh660.hcd rtl8723bs_fw bcm20710a1_26M.hcd fw_bcm4339a0_ag_apsta.bin nvram_4330_oob.txt rtl8723bs_VQ0_config bcm20710a1.hcd fw_bcm4339a0_ag.bin nvram_4330.txt rtl8723bs_VQ0_fw BCM20710A1.hcd fw_bcm4339a0_ag_p2p.bin nvram_AP6181.txt rtl8723bu_config bcm2076b1.hcd fw_bcm43436b0_apsta.bin nvram_AP6210_24M.txt rtl8723d_config bcm40183b2.hcd fw_bcm43436b0.bin nvram_AP6210.txt rtl8723d_fw bcm43241b4.hcd fw_bcm43436b0_p2p.bin nvram_ap6212a.txt rtl8723ds_config bcm4329.hcd fw_bcm43438a0_apsta.bin nvram_ap6212.txt rtl8723ds_fw BCM4330B1.hcd fw_bcm43438a0.bin nvram_ap6233f.txt rtl8761a_config bcm43341b0.hcd fw_bcm43438a0_p2p.bin nvram_AP6234.txt rtl8761a_fw bcm4339a0.hcd fw_bcm43438a1_apsta.bin nvram_ap6236.txt rtl8761at8192er_fw bcm43438a0.hcd fw_bcm43438a1.bin nvram_ap6255.txt rtl8761at_config bcm43438a1.hcd fw_bcm43438a1_p2p.bin nvram_ap62x2.txt rtl8761at_fw BCM4343A0.hcd fw_bcm43455c0_ag_apsta.bin nvram_AP6330.txt rtl8761au8192ee_fw BCM4343A1.hcd fw_bcm43455c0_ag.bin nvram_AP6335.txt rtl8761au8812ae_fw BCM4343B0.hcd fw_bcm43455c0_ag_p2p.bin nvram_ap6354.txt rtl8761au_fw BCM4345C0.hcd fw_bcm4354a1_ag_apsta.bin nvram_ap6356s.txt rtl8761aw8192eu_config bcm4354a1.hcd fw_bcm4354a1_ag.bin nvram_ap6356.txt rtl8761aw8192eu_fw BCM4354A2.hcd fw_bcm4354a1_ag_p2p.bin nvram_ap6398s.txt rtl8821a_config BCM4356A2.hcd fw_bcm4356a2_ag_apsta.bin nvram_AP6441.txt rtl8821a_fw BCM4359C0.hcd fw_bcm4356a2_ag.bin nvram_ap6452.txt rtl8821as_config fw_awnb108_ap.bin fw_bcm4356a2_ag_p2p.bin nvram_AP6476.txt rtl8821as_fw fw_awnb108.bin fw_bcm4359c0_ag_apsta.bin nvram_AP6493.txt rtl8821c_config fw_bcm40181a2_apsta.bin fw_bcm4359c0_ag.bin nvram_awnb108.txt rtl8821c_fw fw_bcm40181a2.bin fw_bcm4359c0_ag_p2p.bin nvram_B23.txt rtl8821cs_config fw_bcm40183b2_ag_apsta.bin fw_info.txt nvram_GB86302I.txt rtl8821cs_fw fw_bcm40183b2_ag.bin fw_RK901a0_apsta.bin nvram_RK901.txt rtl8822b_config fw_bcm40183b2_ag_p2p.bin fw_RK901a0.bin nvram_RK903_26M.cal rtl8822b_fw fw_bcm40183b2_apsta.bin fw_RK901a2_apsta.bin nvram_RK903.cal rtl8822bs_config fw_bcm40183b2.bin fw_RK901a2.bin nvram_RK903.txt rtl8822bs_fw fw_bcm40183b2_p2p.bin fw_RK901a2_p2p.bin nvram_WL211.txt ssv6051-sw.bin fw_bcm43241b4_ag_apsta.bin fw_RK901.bin otp.bin.z77 ssv6051-wifi.cfg fw_bcm43241b4_ag.bin fw_RK903_ag_apsta.bin rk903_26M.hcd TV_Firmware.mk fw_bcm43241b4_ag_p2p.bin fw_RK903_ag.bin rk903.hcd wifi_efuse_8189e.map fw_bcm4330_apsta.bin fw_RK903_ag_p2p.bin RT2870APCard.dat wifi_efuse_8723bs-vq0.map fw_bcm4330.bin fw_RK903b2_apsta.bin RT2870AP.dat wifi_efuse_8723cs.map fw_bcm43341b0_ag_apsta.bin fw_RK903b2.bin RT2870STACard.dat wifi_efuse_8723ds.map fw_bcm43341b0_ag.bin fw_RK903b2_p2p.bin RT2870STA.dat fw_bcm43341b0_ag_p2p.bin fw_RK903.bin rtl8723b_config I have not yet understood how the kernel determines device to contact at which address and what firmware to load into it and i'm asking for advice on what I should learn to make it work. 01_dtbdump_rockchip,rk3328-evb-avb.dts

Tried several /etc/asound.conf upmix settings, no luck. Made absolutely sure my audio jack isn't bridging anything by soldering straight to the board. No luck, I cannot separate the outputs. (no, the loose floating wire on the bottom is not the cause)

@madeofstown try out the orange pi zero 3 community images to see if it helps https://www.armbian.com/orange-pi-zero-3/ zero 2w don't have the motorcomm ethernet (requires an extension/expansion board accordingly), that's what I understand it to be. hopes that works still on zero 2w

In general you are going to need to find or fix a dtb file to correspond to the hardware you are running.

Hi, I'm using the image Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img on my Box TV Tigre 2 with Amlogic S905x processor and the dtb meson-gxl-s905x-p212.dtb and all the things I need are working, except the HDMI Audio output. Using the command "aplay -l" it shows no soundcards found but using the command lsmod | grep snd it shows different sound modules so I think it's a driver problem Also using armbian-config and going to system->hardware it shows an empty list. Any ideas on how to make it work?

https://forum.armbian.com/topic/29202-orange-pi-zero-3 @madeofstown If you care there was a discussion the last week on this topic in the above thread (the 2w and 3 are similar).

Why not use libgpiod? Or try to port mraa?

Works for me since ages. glmark2-wayland-nanopc-t4.logclinfo-fp-nanopc-t4.log

There are new Armbian 24.05 images available on the Helios64 download page: both images Bookworm minimal and Jammy Desktop are based on linux 6.6.30 (download them !). I will test the Bookworm image and see what needs to be modified (dtb, rtl_nic firmware, bootloader) and post a summary here.

I'll take your word for it @SteeMan, thank you. When I search for "orangepi 1.5GB" my post is the only one that comes up. Ill try different combinations but you already gave me my answer.

Do you have a USB to TTL/UART device? You would then be able to check what happens, you might even get a console through the serial connection if it starts up.

Collabora's engineers continue to be involved in the hardware enablement for a few different system-on-chips (SoCs) and platforms, and have also contributed significant improvements to kernel testing. View the full article

I used simple dts file as possible : /dts-v1/; /plugin/; / { model = "OrangePi Zero3"; compatible = "xunlong,orangepi-zero3", "allwinner,sun50i-h618"; fragment@0 { target-path = "/"; __overlay__ { w1: onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; gpios = <&pio 2 7 0>; status = "okay"; }; }; }; }; compiled: armbian-add-overlay w1-gpio.dts and works 🙂 with armbianEnv.txt user_overlays=w1-gpio param_w1_pin=PC10 param_w1_pin_int_pullup=0 demsg show [ 5.015541] Driver for 1-wire Dallas network protocol. [ 5.019754] gpio-74 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 5.046831] w1_master_driver w1_bus_master1: Attaching one wire slave 28.03165129ecff crc 24 and cat /sys//bus/w1/devices/28-03165129ecff/w1_slave 76 01 4b 46 7f ff 0c 10 d3 : crc=d3 YES 76 01 4b 46 7f ff 0c 10 d3 t=23375 SBC DS18B20 VCC (3V3) Pin 1 ---------- VCC DS18B20 | R1 = 4k7 | GPIO74 Pin 26 --------- Data DS18B20 GND Pin 6 ---------- GND DS18B20

The issue is the 1.5gb memory. That particular memory configuration isn't currently working. Look back in the threads for the 2w and 3 and you can see a lot of discussion on this topic.

If you are using an ophub kernel you are not using Armbian. These forums are for Armbian ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. You need to direct your question to their forums/support channels.

Hi team, This is not exactly Armbian related, however I hope to find some help here, also it can be useful for someone else in custom board development (my case). For testing I have Olimex RK3328-SOM-EVB and RK3318 TV box boards. They both behave the same way. As summary I'm trying to boot Linux using the Bootrom and USB OTG only, in other words without any external boot NVM attached. To archive this I build U-Boot SPL (u-boot-spl.bin), which support SDP protocol via USB OTG. For SDP file transfer I'm using imx_usb tool. The binaries used in the process are: rk3328_uboot_v1.19.250.bin - consists of u-boot-tpl.bin and u-boot-spl.bin created with boot_merger tool. u-boot.itb - FIT image (ATF, u-boot.bin and dtb), mainline U-Boot v2023.10 kernel.itb - FIT image (Image.gz and dtb), mainline kernel v6.1 I also prepared a proper sdcard image, from above binaries and wrote it to an SD card. My test setup consists of two booting paths, note the binaries in both are the same: With boot path 1, u-boot-tpl, u-boot-spl loaded via USB OTG: RK3328 in Mask ROM mode, SD card removed rkdeveloptool db rk3328_uboot_v1.19.250.bin insert SD card imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 With boot path 2, u-boot-tpl, u-boot-spl loaded from SD card: insert SD card, power on (or reset) the board imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 The overall description of two boot paths is as follow: boot path 1: rk3328_uboot_v1.19.250.bin (bootrom via OTG)-+ +- -> uboot.itb (imx_usb) -> kernel.itb (from SD card) boot path 2: rk3328_uboot_v1.19.250.bin (bootrom via SD) -+ The issues I have: When the SoC is booted through boot path 1 the kernel hangs soon after starting ... [ 0.016620] smp: Bringing up secondary CPUs ... If boot path 2 is used - The kernel boots and everything works as expected. The Bootrom in RK3318/28 first tries eMMC, SPI NOR, SPI NAND and SD card, if those boot devices failed then USB OTG is used for booting. Since the only difference between two boot paths is the way the TPL/SPL is loaded from the Bootrom - USB OTG or SD card, the only logical explanation I can think of is that there is some "leftover" in SoC state after OTG boot, which causes the kernel to hang. Does anyone have any idea how I can narrow down and eventually find the cause for this issue?

Forgive me if I am missing something. I have a 1.5GB oPiZ2W and I cannot get it to boot with the community builds or the unofficial builds. No green activity light, just the red power light. No output from HDMI. I've let it sit like this for 15 minutes and still nothing. Is there something else I need to do to get this to boot? I've had no issues with the Debian/Ubuntu images provided by OrangePi.

[ 11.309397] panfrost ff9a0000.gpu: clock rate = 500000000 [ 11.316882] panfrost ff9a0000.gpu: EM: OPP:200000 is inefficient [ 11.317248] panfrost ff9a0000.gpu: EM: created perf domain [ 11.320588] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 0x0 status 0x0 [ 11.321594] panfrost ff9a0000.gpu: features: 00000000,00000407, issues: 00000000,24040400 [ 11.322812] panfrost ff9a0000.gpu: Features: L2:0x07120206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7 [ 11.324483] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1 [ 11.357056] [drm] Initialized panfrost 1.2.0 20180908 for ff9a0000.gpu on minor 1 It seems Panfrost driver was loaded, but the GPU doesn't produce any interrupts: 83: 0 0 0 0 0 0 GICv3 51 Level panfrost-gpu 84: 0 0 0 0 0 0 GICv3 53 Level panfrost-mmu 85: 0 0 0 0 0 0 GICv3 52 Level panfrost-job I tried build and install the latest version of `mesa`, which just not work. And `glxinfo -B` still shows that GPU is a virtual GPU. display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0xffffffff) Device: llvmpipe (LLVM 15.0.6, 128 bits) (0xffffffff) Version: 24.0.6 Accelerated: no Video memory: 3792MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 15.0.6, 128 bits) OpenGL core profile version string: 4.5 (Core Profile) Mesa 24.0.6 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.5 (Compatibility Profile) Mesa 24.0.6 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 I am wondering if I can use the GPU on kernel 6.x, because I found that the case in this forum that can enable GPU for rk3399 all use the legacy version kernel, like 4.X. By the way, I am using the kernel from https://github.com/ophub/amlogic-s9xxx-armbian. Anyone can give me some tips or interpretation? Thanks in advanced!!!!