All Activity

🤯 Is there a tool to convert hex pointers (phandle) to human readable names when doing dtc -I dtb -O dts? For example, in original dtb file I have: io-domains { compatible = "rockchip,rk3328-io-voltage-domain"; status = "okay"; vccio1-supply = <0x29>; vccio2-supply = <0x2a>; vccio3-supply = <0x29>; vccio4-supply = <0x2b>; vccio5-supply = <0x29>; vccio6-supply = <0x29>; pmuio-supply = <0x29>; phandle = <0xa3>; }; where <0x29> is: RK805_DCDC4 {}

If you are getting the android recovery you are holding the reset button too long. Have you ever installed and/or run any other OS on this box other than the preinstalled android?

I've only worked with the BPI-M4-ZERO. My personally opinion on the h616/8 line up is that the focus should be on stable and not LTS. Little to none of the official mainline patches are being back ported and the patches being used currently in LTS are kind of hack-a-noodle patches. For example: https://lore.kernel.org/linux-arm-kernel/CA+E=qVeMnQNrT8tNnHBnCL2Efy3VjbRAYQGMXstziCThRsiBDw@mail.gmail.com/T/ https://lore.kernel.org/linux-arm-kernel/20240419071450.7aiheeoyq35yjoo7@vireshk-i7/T/ The ones being currently used in Armbian I believe are either RFC's or taken from OPI. The thermal patch above is already in 6.9.y. But with that said, if you have any questions feel free to hit me up and if I can, I'll help.

[ LINUXFAMILY='rockchip64' ] Try to freeze the kernel version for the target family. Apply this patch to the build system itself. fix-6.6.30-version.patch cd /mnt/music/Armbian/build ls ../fix-6.6.30-version.patch ../fix-6.6.30-version.patch git status git restore file1 file2 .... git pull patch -p1 -i ../fix-6.6.30-version.patch Put the patch in a /mnt/music/Armbian/ folder. Check the status and if there are modified files, do the following: git restore "list files" All this is for the main branch P.S. Try to make an assembly. And please post the log.

@Hqnicolas HDMI:✔ USB2.0 X 2: ✔ USB3.0：✔ Card Reader:✔ Thanks! Effective, all three USB ports can be used now.

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

@Hqnicolas that did the trick thanks for that, presumably this branch predates the breaking change gh pr checkout 6618 the above command didn't work on my Linux box - thanks again. gh pr checkout 6618 fatal: couldn't find remote ref refs/heads/fix-broken-patch

I'm sorry, I forgot that in this SD I have another OS that I found, but in the same way with these installed following the same steps, Linux does not load, is there anything I can do?

I didn't see that let me google that for you message - I'll try specifying the branch as you suggest

https://gprivate.com/6b9kg 1 - Follow the Build Armbian instructions if it doesnt Build your image as espected rm -rf build git clone --depth 1 --branch v24.05 https://github.com/armbian/build try again and again and again and again gh pr checkout 6618

@gen ha it's happnd because you're using a RK3568 DTS to build an RK3566 DTS and it will mess with Mdio this is your solution: &mdio1 { rgmii_phy1: phy@0 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x0>; }; }; &gmac1 { phy-mode = "rgmii"; clock_in_out = "input"; snps,reset-gpio = <&gpio2 RK_PD1 GPIO_ACTIVE_LOW>; snps,reset-active-low; /* Reset time is 20ms, 100ms for rtl8211f */ snps,reset-delays-us = <0 20000 100000>; assigned-clocks = <&cru SCLK_GMAC1_RX_TX>, <&cru SCLK_GMAC1>; assigned-clock-parents = <&cru SCLK_GMAC1_RGMII_SPEED>, <&gmac1_clkin>; pinctrl-names = "default"; pinctrl-0 = <&gmac1m1_miim &gmac1m1_tx_bus2 &gmac1m1_rx_bus2 &gmac1m1_rgmii_clk &gmac1m1_rgmii_bus &gmac1m1_clkinout>; tx_delay = <0x4f>; rx_delay = <0x26>; phy-handle = <&rgmii_phy1>; status = "okay"; };

Find the USB port list and change 1 port USB from OTG to HOST &usbdrd_dwc3 { dr_mode = "otg"; extcon = <&usb2phy0>; status = "okay"; }; &usbdrd_dwc3 { dr_mode = "host"; extcon = <&usb2phy0>; status = "okay"; };

@Werner I ran this from the build folder git fetch origin pull/6618/head and I'm trying to build it again - from what I see on the tty it looks to be compiling and linking

You have to change the mdio ethernet phy from 0 to 1 in your DTB.

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.

Those are not what you have installed on that SD card.

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

Hello. I am taking the task of organizing and performing the BTT Pi and CB1 support update. The plan is to use mainline kernel 6.6 and 6.8 (basically the default sunxi64 config) instead of the BTT fork and use patches to backport kernel patches for drivers and hardware support. The Jira issue is AR-2312, which is a collection of things that will need to be done for this initiative. @Gunjan Gupta @c0rnelius @ag123 @jernej @ALIGMSTEN I'm asking for your help on this, as Igor has said to me that you are more knowledgeable on the state of the board and what it needs. From what I've found, there has been a PR that upgraded the kernel used for BTT CB1 to 6.1.79 using patches, and there's a discussion on reconstructing or copying the BigTreeTech device tree for 6.6.y and up. The BTT's changes are mostly drivers, device tree and other hardware support and backporting. I think BTT's linux 6.2.y branch should be used as the starting point to determine what board-specific patches and changes are needed. Some of the drivers are already in the 6.6.y (CURRENT) and 6.8.y (EDGE) kernel versions, some are added by armbian, some are only in the vendor's fork.

https://www.google.com/search?q=how+do+i+checkout+a+pr+github

On that page at the bottom, I downloaded these, jammy, book, noble in xfce

Just a remark: setting MIN_SPEED to 600 MHz would have NO effect on power consumption but required frequency switching would be less: switching between 408 and 600MHz would be avoided and the system could transition directly from 600 MHz to the highest frequency (essentially switching only between two states for each cpu). The huge power savings are impressive!

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