Active threads

@helix afaik, no tool for that. phandles are the way how kernel navigates the device tree. BTW, you may wish to try to enable box-wlan-ap6330 or box-wlan-ap6334 device tree overlay in /boot/armbianEnv.txt and see if you advance in getting bluetooth: broadcom chips have the need for some bits in the device tree to load the driver and attach the communication "bus" (which is usually a simple UART port). Also they are very similar chips. the driver is usually capable of handling the detection of features despite you declare a different chip in device tree. You can see the source of the ap6330 overlay here And yes, you definitely need to enable the led-conf3 because the dtb declares that your board definitely has a rk805 PMIC: that's why the photo of the board is heavily suggested in the first page to get help.

Description After testing, it was found that Firefly-RK3399 cannot boot using the mainline device tree due to issues with the PMU (Power Management Unit). Even after fixing the PMU problem, Bluetooth still cannot be used. Therefore, the original patch has been optimized by removing unnecessary parts. How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Cannot tell for sure since I do not have this board. However I would use a multimeter and measure the voltage between the outer pins to determ which is GND and which is 5V. Then I'd hook ground to ground and randomly connect rxd and txd. The chances are 50:50 to get it right the first try. If there is no output, swap rxd and txd and try again.

@going thank you for your time - I tried your suggestion and got this ../fix-6.6.30-version.patch diff: unrecognized option '--git' diff: Try 'diff --help' for more information. ../fix-6.6.30-version.patch: line 2: index: command not found ../fix-6.6.30-version.patch: line 3: ---: command not found ../fix-6.6.30-version.patch: line 4: +++: command not found ../fix-6.6.30-version.patch: line 5: @@: command not found ../fix-6.6.30-version.patch: line 7: syntax error near unexpected token `)' ../fix-6.6.30-version.patch: line 7: ` current)

lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references in preparation for tightening the shellcheck severity level it needs to be able to follow all sources; dynamic ones are ignored, static ones need root-relative prefix View the full article

t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox we've had kernel patches/DT (from chewitt) for this in meson64 for a long time, but I never sent the board uses blobs for the tartiflette-s912 which is also an DDR3 S912 (VIM2's blobs are DDR4 and won't boot) this adds u-boot 2024.04 support, using chewitt's DT & 000.patching_config.yaml & a specific BOOTPATCHDIR this is a full board as-if it was an SBC, and expects to boot from mainline u-boot; for that to work you've to wipe the eMMC and get rid of the vendor-supplied u-boot if this is not what you want/need, you can use the aml tvbox "board" instead, together with Android u-boot View the full article

khadas-vim3: fix stray closing brace in board file khadas-vim3: fix stray closing brace in board file a stray closing brace, meant for the function, that ends up doing the wrong config change View the full article

"OLED stats working also in debian, you need to activate I2C5 M3 overlay in orangepi-config" By doing above, do you still need to execute point #1 (add overlay) from original instructions?

try https://github.com/armbian/build/pull/6610

@JohnTheCoolingFan neither am I familiar with much of that. I'd just like to say that H618 support evolves out of H616 and the DTS for Orange Pi Zero 3 and Zero 2W is contributed by Andre Przywara from 6.6 mainline kernel. But that various contributors here worked the DTS further, check in the thread for details. Note that there are also change in *u-boot* for Orange Pi Zero 3, mainly to add the PMIC and DDR4 support for Orange Pi Zero 3 I think some key difference between Orange Pi Zero 2 (H616) vs Orange Pi Zero 3 (H618) are : - PMIC the power management IC is different - Orange Pi Zero 3 uses lpddr4 vs Orange Pi Zero 2 lpddr3 various other 'small' differences and that H618 is after all based on H616 codebase. Hence, my guess is to attempt to use the 6.6 and up mainline kernel and do a rebuild for CB1. One thing I'm not sure is where to configure that so that the build would use the 6.6.x mainline kernel during the build. It would likely 'not build cleanly' (e.g. without errors) and the build errors especially if the 'old' patches for the same board is applied and those would need to be resolved. You would take into account the actual hardware differences vs Orange Pi Zero 2 or Orange Pi Zero 3 if after all they are different on the CB1.

Description Issue reported from radxa's forum: https://forum.radxa.com/t/the-changable-wifi-interface-name-of-rock-5c-lite/20921 Rock5c has an onboard aic8800 usb wifi/bt module, which has random wifi interface name by default, which will cause non-static connection name created by networkmanager. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] PREFER_DOCKER=no ./compile.sh kernel BOARD=rock-5c BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=jammy KERNEL_GIT=shallow DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

You will only get the resolution that you TV is capable of supporting. I always use high quality cables.

@ Hqnicolas The network card is still unable to receive data, and the reason is unclear. In the past, connecting the network port was a simple task, but now it seems very difficult😂 [ 25.313329] rk_gmac-dwmac fe010000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 25.318206] rk_gmac-dwmac fe010000.ethernet eth0: PHY [stmmac-1:00] driver [Generic PHY] (irq=POLL) [ 25.321898] dwmac4: Master AXI performs any burst length [ 25.324480] rk_gmac-dwmac fe010000.ethernet eth0: No Safety Features support found [ 25.327033] rk_gmac-dwmac fe010000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported [ 25.329956] rk_gmac-dwmac fe010000.ethernet eth0: registered PTP clock [ 25.333601] rk_gmac-dwmac fe010000.ethernet eth0: configuring for phy/rmii link mode

Sorry - I am probably the only one who is interested in network performance using the 2.5G interface (theoretical max 2.35Gbit/s). (iperf3.17.1 measurements attached, download and upload) # ./iperf3 -c 192.168.240.30 -p 5201 Connecting to host 192.168.240.30, port 5201 [ 5] local 192.168.240.54 port 54011 connected to 192.168.240.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.01 sec 284 MBytes 2.37 Gbits/sec [ 5] 1.01-2.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.01-3.01 sec 281 MBytes 2.36 Gbits/sec [ 5] 3.01-4.00 sec 278 MBytes 2.34 Gbits/sec [ 5] 4.00-5.01 sec 280 MBytes 2.34 Gbits/sec [ 5] 5.01-6.01 sec 281 MBytes 2.36 Gbits/sec [ 5] 6.01-7.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.01-8.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 8.01-9.01 sec 281 MBytes 2.36 Gbits/sec [ 5] 9.01-10.01 sec 281 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec sender [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec receiver iperf Done. # ./iperf3 -c 192.168.240.30 -p 5201 -R Connecting to host 192.168.240.30, port 5201 Reverse mode, remote host 192.168.240.30 is sending [ 5] local 192.168.240.54 port 54013 connected to 192.168.240.30 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.01 sec 276 MBytes 2.30 Gbits/sec [ 5] 1.01-2.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.01-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.01-5.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.01-6.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 6.00-7.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 7.01-8.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 8.00-9.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 9.01-10.01 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec 16 sender [ 5] 0.00-10.01 sec 2.73 GBytes 2.35 Gbits/sec receiver iperf Done.

-Clean, remove params for old kernel -Add option to disable usb autosuspend -Add display console replace rootdev with "LABEL=armbi_root" to boot from sd card an emmc with same boot.ini View the full article

After releasing the button, then remove the power and plug the power back in. What happens then? Also what dtbs have you tried?

solved. the display on the ST7789V use spi0.1 spidev use spi0.0 Could not run on the built-in driver. I get st7789v spi0.1: error -EINVAL: Failed to setup spi fb_st7789v spi0.1: write() failed and returned -22 did the ST7789V initialization manually /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { st7789v_pins: st7789v_pins { pins = "PA8", "PA9", "PA10", "PA20"; function = "gpio_out", "gpio_out", "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; cs-gpios = <&pio 2 3 1>,<&pio 0 20 1>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0>; spi-max-frequency = <1000000>; }; display: display@1 { /* compatible = "sitronix,st7789v"; */ compatible = "samsung,s6d02a1"; reg = <1>; /* use cs1. required 1 in section display@1 */ pinctrl-names = "default"; pinctrl-0 =<&st7789v_pins>; spi-max-frequency = <16000000>; rotate = <180>; /* in init rotate 0x1000036 0xXX 0(XX=00) 90(XX=a0) 180(XX=36 c0) 270(XX=60) */ width = <240>; height = <320>; spi-cpol; buswidth = <8>; txbuflen = <153600>; reset-gpios = <&pio 0 10 1>; dc-gpios = <&pio 0 9 0>; led-gpios = <&pio 0 8 0>; debug = <0>; init = < 0x1000001 0x2000096 0x1000011 0x100003a 0x05 0x10000b2 0x05 0x05 0x00 0x33 0x33 0x10000b7 0x75 0x10000c2 0x01 0xff 0x10000c3 0x13 0x10000c4 0x20 0x10000bb 0x22 0x10000c5 0x20 0x10000d0 0xa4 0xa1 0x1000029 0x1000021 0x1000036 0xc0 0x100002a 0x00 0x00 0x00 0xef 0x100002b 0x00 0x00 0x01 0x3f 0x100002c 0x10000e0 0xd0 0x05 0x0a 0x09 0x08 0x05 0x2e 0x44 0x45 0x0f 0x17 0x16 0x2b 0x33 0x10000e1 0xd0 0x05 0x0a 0x09 0x08 0x05 0x2e 0x43 0x45 0x0f 0x16 0x16 0x2b 0x33 0x2000064 >; }; }; }; }; everything works perfectly. PS I don't know how to fix the topic header. problem solved

Hi Team, I hope you're all keeping well. I'm into my first foray into armbian, and I'm having trouble just getting it to boot on my Nanopi R6S. Feeling a bit thick, like I'm missing something obvious. I can get FriendlyELEC's rk3588-sd-debian-bookworm-core-6.1-arm64-20240511 to boot without any trouble, but not armbian images. My procedure: Format microSD card with the SD Card Formatter from the SD Association Burn image to SD card with balena etcher Eject microSD reader from my PC Pop microSD into the device and apply power When it boots into the FriendlyELEC image: the SYS light shines solid red for about 3 seconds then the SYS light starts blinking After a short while, the WAN light comes on for about 2 seconds then goes off. The SYS light continues blinking. When I try an armbian image: the SYS light just shines solid red ad infinitum. It also does the same with no SD card at all. Things I've tried: Two separate microSD cards, both will happily boot the FriendlyELEC images Three type-C power supplies (two Lenovo OEM 65W supplies that I use with my laptop + a Belkin 100W PD unit that gets used for everything) Waiting a long time for anything to happen on screen or with the LEDs I have also tried win32diskimager to burn the images to the microSD cards to ensure it's not a problem with balena Cleared any bootloader on the eMMC while booted into the FriendlyELEC image (per the FriendlyELEC wiki) dd if=/dev/zero of=/dev/mmcblk2 bs=8M count=1 Armbian images I've tried: My own built Armbian images - very impressed with armbian-build! Armbian_community_24.5.0-trunk.563_Nanopi-r6s_bookworm_edge_6.8.9_minimal.img.xz from Armbian website (verified SHA of a5e6da3593d221813cc874415b3c1f7f509aca9a09ff008a5bca7eb73313e2e7) Armbian_community_24.5.0-trunk.563_Nanopi-r6s_jammy_edge_6.8.9_gnome_desktop.img.xz from Armbian website (verified SHA of cf2dd5f25f1dae97ea3750e00cf335c1b68dc861b4d5d98b0fc0420050227a88) Am I doing something obviously wrong?

I was downloading minimal/server images. This is an output from serial console: U-Boot SPL 2024.01-armbian (Feb 09 2024 - 18:57:17 +0000) DRAM: 2048 MiB Trying to boot from MMC1 and pretty the same from older armbian version from another memory card: U-Boot SPL 2023.07.02-armbian (Aug 31 2023 - 08:27:30 +0000) DRAM: 2048 MiB Trying to boot from MMC1 I have problem with h2testw on my Windows 11 laptop. Laptop has buildin micro sd card reader that works but windows often shows memory card disk on the disks list but I cant assign drive letter. Additionaly I can't refresh the view. h2testw expects me to select drive. I also tried to use other power supply (5V 2,5A - minimal for Orange Pi Prime) but with no success.

Description Add support for RK3588 based board Cool PI CM5 EVB Jira reference number [AR-9999] How Has This Been Tested? ./compile.sh build BOARD=coolpi-cm5 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DOWNLOAD_MIRROR=bfsu EXPERT=yes EXTRAWIFI=no KERNEL_CONFIGURE=no PREFER_DOCKER=no RELEASE=noble Download the compiled img to sdcard, and can boot. Checklist: Please delete options that are not relevant. [✓ ] My code follows the style guidelines of this project [✓] I have performed a self-review of my own code [✓] I have commented my code, particularly in hard-to-understand areas [✓] My changes generate no new warnings [✓] Any dependent changes have been merged and published in downstream modules View the full article

Two desktops needs additional testing: https://github.com/armbian/build/pull/6626 https://github.com/armbian/build/pull/6625 ... we are high on closing existing tasks and very low on time dealing with this. There are several other bugs that needs attention: https://www.armbian.com/participate/

Description Enabling KDE Neon at Noble How Has This Been Tested? [ ] Build test [ ] Running desktop inspection Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Hey there were you able to run it or not ?

Description Tested only for assembly at this point. It needs further optimisations. How Has This Been Tested? [x] Build test [ ] Booted image with i3wm Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description I'm sorry, the error on the 6.8 kernel occurred because I didn't synchronize my code in time, resulting in patch errors that affected the compilation. Based on the hints here, I am optimizing the device tree for the firefly-rk3399 kernel: https://github.com/armbian/build/pull/6611 How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article