Search the Community

I have a development board, model eaidk-310, with soc rk3228h (which is said to be the same as rk3328). The official website of the board has been closed, so I cannot obtain more related information. However, I found the official firmware and can use rockchip's official tool for burning. The file structure is as follows. 190798 Jun 8 2020 MiniLoaderAll.bin 33554432 Jun 8 2020 boot_linux.img 374 Jun 8 2020 parameter-linux.txt 6815744000 Jun 8 2020 rootfs.img 4194304 Jun 8 2020 trust.img 4194304 Jun 8 2020 uboot.img parameter-linux.txt is: FIRMWARE_VER:8.1 MACHINE_MODEL:RK3328 MACHINE_ID:007 MANUFACTURER:Rockchip MAGIC: 0x5041524B ATAG: 0x00200800 MACHINE: 3328 CHECK_MASK: 0x80 PWR_HLD: 0,0,A,0,1 TYPE: GPT CMDLINE:mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00010000@0x00006000(boot_linux:bootable),-@0x00016000(rootfs:grow) uuid:rootfs=614e0000-0000-4b53-8000-1d28000054a9 I tried to install armbian's image based on rk3328, which is officially supported. Some of them can boot up but neither network nor Bluetooth works properly. Therefore, I want to compile my own version to support these peripherals. My question is whether I can use the pre-compiled .img files in these official images to compile my own armbian? If possible, how should I configure ./compile.sh? Thank you all. Translated from:

Hi all, I try to use SPI on the BananaPi M2 Berry. The devices are activated in the configfile and the devices spidev0,0 and spidev1.0 are shown in the /dev .directory but the spi-bus did not work. DMESG shows the following error - messages : [ 0.944871] sun6i-spi 1c05000.spi: Failed to request TX DMA channel [ 0.944893] sun6i-spi 1c05000.spi: Failed to request RX DMA channel [ 0.945987] sun6i-spi 1c06000.spi: Failed to request TX DMA channel [ 0.946006] sun6i-spi 1c06000.spi: Failed to request RX DMA channel OS version is 6.2.12-sunxi Any idea what's wrong ?

I'd like to run usbdux usb hardware with armbian but have no experience so far in building modules. I compiled the current armbian branch form github. But I could not figure out how to compile the comedi drivers and include it in the kernel. help appreciated Thomas

Hello everyone, Would like to ask for some guidance regarding how to install armbian on a t507 processor. as written here in this post allwinner 507 processor it says For this reason I have tried to burn an image for orangepi zero 2 but it doesn't boot, it just get frozen and I can't get any logs because the serial console do not prints anything all black. Does someone could maybe have some suggestion of what I could try? anything is more than welcome. Thank you in advance

Is there any support for this platform. https://wiki.seeedstudio.com/Quantum-Mini-Linux-Development-Kit/ Devicetree https://github.com/coolflyreg/quark-n If not. Where can I see how to add a new platform. If template or tutorial. Original system is Ubuntu 18 and very old kernel. I like Debian better.

I have an Orange Pi Mini 2. As far as i know there is no official/ unofficial armbian build for this. there are other boards like orange pi pc, orange pi 2 and tritium h3 board whose images run fine for this board. I have also made armbian image builds with orange pi pc as target and these images work on opi mini 2. I would like to know how could i make a build exclusively for orange pi mini 2.

Hello, my name is Wolfgang and I´m from Germany and hope you can maybe help me. First I have no knowledge related to the nano PIs. I bought an R2D2 from Deagostini. The R2 has a board which looks like an nano PI air. It´s called DRCC H3 V2.0. The R2 has different sounds and video seqeunces which can be played by R2. My quetsion is now do you think it´s possible to change or add sounds to the board? Thanks in advance Wolfgang

I'm having trouble trying to do a custom kernel configuration using this image on my hc4. It's just not opening menuconfig, I get the screen to select the board ( odroid hc4), then the LTS/Edge kernel screen, then this is the only output: ~/build$ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img [🌿] Applying cmdline param [ 'BUILD_MINIMAL': '(empty)' --> 'no' early ] [🌿] Applying cmdline param [ 'COMPRESS_OUTPUTIMAGE': '(empty)' --> 'sha,img' early ] [🌿] Applying cmdline param [ 'BUILD_DESKTOP': '(empty)' --> 'no' early ] [🌿] Applying cmdline param [ 'BRANCH': '(empty)' --> 'current' early ] [🌿] Applying cmdline param [ 'BOARD': '(empty)' --> 'odroidhc4' early ] [🌿] Applying cmdline param [ 'KERNEL_ONLY': '(empty)' --> 'yes' early ] [🌿] Applying cmdline param [ 'KERNEL_CONFIGURE': '(empty)' --> 'yes' early ] [🚸] This script requires root privileges; Docker is unavailable [ trying to use sudo ] [🌿] Applying cmdline param [ 'PREFER_DOCKER': '(empty)' --> 'no' early ] [🌿] Applying cmdline param [ 'BUILD_MINIMAL': '(empty)' --> 'no' early ] [🌿] Applying cmdline param [ 'COMPRESS_OUTPUTIMAGE': '(empty)' --> 'sha,img' early ] [🌿] Applying cmdline param [ 'BUILD_DESKTOP': '(empty)' --> 'no' early ] [🌿] Applying cmdline param [ 'ARMBIAN_RELAUNCHED': '(empty)' --> 'yes' early ] [🌿] Applying cmdline param [ 'BRANCH': '(empty)' --> 'current' early ] [🌿] Applying cmdline param [ 'BOARD': '(empty)' --> 'odroidhc4' early ] [🌿] Applying cmdline param [ 'SET_OWNER_TO_UID': '(empty)' --> '1000' early ] [🌿] Applying cmdline param [ 'KERNEL_ONLY': '(empty)' --> 'yes' early ] [🌿] Applying cmdline param [ 'KERNEL_CONFIGURE': '(empty)' --> 'yes' early ] [🌱] Starting single build process [ odroidhc4 ] [🌱] Checking [ basic host setup ] [🌱] Build host OS release [ jammy ] [🌱] Build host architecture [ arm64 ] [🌱] Sourcing board configuration [ /home/steve/build/config/boards/odroidhc4.conf ] [🌱] Starting main configuration [🌱] Sourcing family configuration [ /home/steve/build/config/sources/families/meson-sm1.conf ] [🌱] Sourcing arch configuration [ arm64.conf ] [🌱] Extension manager [ processed 4 Extension Methods calls and 4 Extension Method implementations ] [🌱] Configuration prepared for BOARD build [ odroidhc4.conf ] [✨] Repeat Build Options (early) [ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img ] [🌱] Checked directory OK for mount options [ /home/steve/build/.tmp ('main temporary dir') ] [🌱] Preparing [ host ] [🌱] Syncing clock [ host ] [🔨] 4 Mar 18:52:16 ntpdate[41836]: adjust time server 38.229.56.9 offset -0.001440 sec [🌱] artifact [ uboot :: uboot() ] [🌱] Using cached [ GIT_INFO_UBOOT ] [💖] artifact [ present in local cache: uboot-odroidhc4-current 2023.01-S62e2-P1cd3-B680b ] [🌱] artifact [ kernel :: kernel() ] [🌱] Using cached [ GIT_INFO_KERNEL ] [🌱] Using kernel config file [ config/kernel/linux-meson64-current.config ] [💖] artifact [ present in local cache: kernel-meson64-current 6.1.15-S4261-De511-Pb8ce-C072bHfe66-Bb436 ] [🌱] artifact [ firmware :: firmware() ] [🌱] Using cached [ GIT_INFO_ARMBIAN_FIRMWARE ] [💖] artifact [ present in local cache: armbian-firmware 1-SA56ad-B6be6 ] [🌱] Building deb [ armbian-plymouth-theme ] [🌱] shellcheck found no problems in package scripts [ shellchecked 3 scripts in 'armbian-plymouth-theme' ] [🔨] dpkg-deb: building package 'armbian-plymouth-theme' in '/home/steve/build/.tmp/work-5237001b-8933-4274-b02b-98b6ec67e71c/tmp.exL1KIf5bj/armbian-plymouth-theme_23.05.0-trunk_all.deb'. [🚸] using legacy option [ KERNEL_ONLY=yes; stopping build mid-packages ] [🌱] Runtime [ 0 min ] [✨] Repeat Build Options [ ./compile.sh BOARD=odroidhc4 BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,img ] [🌱] Cleaning up [ please wait for cleanups to finish ] [🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-5237001b-8933-4274-b02b-98b6ec67e71c.log.ans ] [🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-5237001b-8933-4274-b02b-98b6ec67e71c.log.ans https://paste.next.armbian.com/log ] steve@odroidhc4:~/build$

I think we should do exactly the opposite. As soon as the author realizes that his codebase has begun to create stable images for the family\branch, he can invite the most active members of this group to test and fix bugs. That is, errors, changes must be made in this branch. While the master should remain stable and not create problems for the current work.

Hello dear armbianites, I'm trying to make the hc1 optimization for the odroid HC2 board permanent, every time the kernel is updated, armbiam loses the optimization and an admin action is needed to apply the optimization again via ambianconfig > System DTB > optimized board configuration, followed by a reboot. My Odroid HC2 suffers from temperature sensor problems, which can be easily bypassed. But I avoid restarts of this server which hosts an OMV instance for personal needs. I understand that the /boot/armbianEnv.txt file passes the information to /boot/boot.ini, but this file seems to be overwritten when the kernel is updated! is there any possibility of upstream action like 'first.boot' after update? konki

Does anyone know of an ARM-based single board computer that stores its boot firmware in SPI flash and has write protection mechanisms (e.g., screws, pins, jumpers, etc.) for said SPI flash? The ROCK 3A has something like it, but I don't think the mechanism uses an SPI flash chip's intended WP control pin.

I just installed armbian buster on my NAS (odroid HC2). Everything works perfectly. However, as debian bullseye has become stable and I expect this to happen for armbian also in the near future, I am thinking about how to do the upgrade. This is mainly because all my other boxes run bullseye and administration becomes a lot easier if all systems run the same version. In addition, I will have to do the update anyways at some point in time and therefor I want do it when armbian bullseye becomes stable. Reading through the forum I found out it is not supported. However, I am using debian now since woody and have done a lot of upgrades since then, I think I will try it for armbian also (of course after making a full backup). I already read that i should do a freeze in armbian-config (disable kernel upgrades). Having done this, can I just start upgrading to bullseye the debian way (as it is described in the bullseye release notes). And after finishing this I would disable the freeze, which would allow the kernel update also? Any thoughts on this procedure? Anything else I have to do and that would be different to vanilla debian? Regards, Jürgen

Hello everyone! I recently heard about running x86_64 programs on ARM using box64, and decided to give it a try. I get the impression that most people are just using it for games but I would like to use it to run Quartus (a program to work with Intel FPGAs). The issue I see is getting the USB drivers to work. Quartus includes drivers for several programming cables (I am only interested in the USB blaster cable), and as far as I know there are no drives available that run on ARM. Is there any hope at all of getting the x86 drivers to work on ARM? Thanks in advance.

Hi, just got a Nanopi R5C (waiting for an RPi for more than a year, yet...) but I couldn't find any headless images for this little box. There's an official debian-image available running LDXE, but open media vault isn't able to run on an Desktop linux... Any chances there will be support for the Nano Pi R5C / Rockchip RK3568B2? btw: can't choose R5C or just 'others' from the drop-down when creating a new post...

Hi, i can't get usbip work, there's a tutorial or something else that i can follow to make usbip working over that soc board? cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" #/usr/bin/usbip WARNING: usbip not found for kernel 4.14.84 You may need to install the following packages for this specific kernel: linux-tools-4.14.84-sunxi linux-cloud-tools-4.14.84-sunxi You may also want to install one of the following packages to keep up to date: linux-tools-sunxi linux-cloud-tools-sunxi The board is a orange pi r1 how i can make that working?

Hi everyone, Here an idea: It may be useful to know which board and wich compilation environment has already been tested with armbian-next, i.e.: Board User space Kernel Interface Environment Compilation Boot Hardware peripherals Hardware features Apps uefi-x86 Bullseye Current Desktop XFCE ✅ ✅ uefi-x86 Bullseye Edge Desktop XFCE ✅ ✅ bananapim5 Bullseye Edge Desktop XFCE ✅ ❎ And for the compilation environment: Host Container Guest Compilation Windows 10 VirtualBox Ubuntu Jammy 22.04.1 Desktop amd64 ✅ Ubuntu Jammy 22.04.1 Desktop amd64 -- -- ✅ The goal would be not to test every possible combination, but just to not waste time (test something that has already been tested) and as a bonus have an overview. "We" neither should fix images in next that aren't working in master too, but next should be at least on par with master. The forum is probably not the right place to host such a document. Maybe Jira? What do you think about this idea? Feel free to reject it or propose modifications.

Hi everyone! I'm software developer but have no (or little) clue about electronics & electricity, and would like to dive into the SBC world. I still don't have a goal other than have fun and support this community during my free time. I probably need to buy some devices (my budget is limited): A voltmeter A soldering station. Which filler material is more appopriate? An USB-to-TTL adapter to debug the serial output. Specs? Last but not least: an SBC! Which one is good but currently lacks support from this community? Something else? Thank you for your advices!

I am currently attempting to compile a device tree overlay, in connection with an OPi Zero 2. But my questions here are of rather general nature (with regards to DT compiling), so I posted it here. ------- Goal: Creating a DT overlay to enable certain hardware currently not working on the board: wifi and HDMI output. Alternatively, compiling a "full" .dtb file for the board, replacing the one currently used during boot. For completeness: In the below I experimented starting from the Armbian_22.08.7_Orangepizero2_bullseye_edge_5.19.16.img.xz image, 406585908 bytes. uname -a: "Linux orangepizero2 5.19.16-sunxi64 #22.08.6 SMP Tue Oct 18 06:56:22 UTC 2022 aarch64 GNU/Linux" Boot-up (at times shaky), UART and USB (via type A socket) is working with this image. ------- I have tried to assemble a dts file, to be made into an overlay, from snippets seen at https://github.com/jernejsk/linux-1/commit/e7222b1f0dfde22a3b60de7f3add6599fd942e84 But this runs into errors, as references are missing, in this case for example "reg_aldo2". I can look at the complete file, https://github.com/jernejsk/linux-1/blob/e7222b1f0dfde22a3b60de7f3add6599fd942e84/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts and see that it includes #include "sun50i-h616.dtsi", which I can copy from the tree. Further I can make additional code additions that all missing references are resolvable. Nevertheless, even then errors (or to be exact: warnings) remain that look as if the resulting .dtbo will not be functional. Thus: What is the typical workflow in compiling overlays? 1. How much of existing code needs to be included? (I also tried, as alternative to above, to decompile the existing dtb and use it as included file in my compilation - is this a reasonable avenue?) 2. What are negligible warnings? 3. If I compiled something resulting in an erroreous .dtbo, could it be harmful to the hardware? (Or asked differently: tinkering with what parts of the device tree is potentially damaging to the board?) ------- Example warnings: sun50i-h616.dtsi:109.6-1009.4: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name also defined at orangepi-zero2_wifi_and_hdmi.dts:61.13-81.11 sun50i-h616.dtsi:375.21-395.5: Warning (avoid_unnecessary_addr_size): /soc/mmc@4021000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property also defined at orangepi-zero2_wifi_and_hdmi.dts:63.25-79.15 Thanks to the knowledgable.

I was doing some testing today on aml-s9xx-box builds and noticed that with meson64-current (6.0.13) kernels the boot logo is showing, but with meson64-edge (6.1.0) kernels it does not. I know there was a recent commit that probably is causing this, something about removing the old way of handling boot logos. So my question is, what needs to change to convert to the new way? I suspect it has something to do with the append line that the build process is inserting into the extlinux.conf file: append root=UUID=0ffde9aa-5a6a-4d6f-bbef-0d8daf439537 rw no_console_suspend c onsoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=boo tsplash.armbian

Hi Team, i have a lcd touchscreen android rockchip rk3288 ( armeabi-v7a ) and i want change the OS with armbian and install it on sd card , which image that should i use? regards, Adrian

Hi all, I have a bit of an odd application, but given the recent effort being put into UEFI boot, I thought I'd ask for some help. I have a Gigabyte R152-P30, which is an Ampere 80 core, single socket server. Flash drive boot works just fine, but nand-sata-install onto the server's NVMe SSD has been troublesome. I've tried several permutations of having partitions and not having partitions on the NVMe drive, but none seem to actually create a bootable result. I see on the generic armbian image page that it suggests creating an EFI partition which I do (nvme0n1p1). It then proceeds to leave that partition empty. I also have another btrfs partition on the same nvme drive (nvme0n1p2). The second partition is the one that shows up in the nand-sata-install config menu. The script sucessfully moves all files onto this new btrfs drive, and I can see it all when I mount it. If I remove the EFI partition, nothing shows up in the servers boot optoins menu. If I leave the EFI partition in, I get an option in the boot options menu, but it does nothing (black screen). I assume this is because the EFI partition is empty. I'm still pretty new to understanding the Linux boot sequence, so please forgive me if I've forgotten anything trivial. My best guess was simply CP-ing over the flash drives efi folder to the nvme drive's but naturally that didn't work (unknown filesystem) and just dropped me into grub rescue. Attaching logs from the servers BMC (apologies that they're screenshots). If needed I can figure out a way to get armbianmonitor -U out to you guys. Thanks! pics: https://imgur.com/a/yunzvJy

Hi there, I have been using Ubuntu stock from Hardkernel but it is worse than a kick upon my jewels... As usual only Armbian is the way to go, however I personally dislike Ubuntu therefore I'd like to go with Debian but I didn't get the difference between CLI and Minimal. Can anyone advise me? Thanks in advance, F.

I am new to arm devices. I'm trying to build a fully working armbian system for the pcduino8-uno which uses the Allwinner a83t/h8 soc. I know these are not the best, but I got it from amazon for $18 and it runs home assistant very well. I built a new u-boot which appears to initialize the hardware properly as it sees all the usb port as well as obtains an ip from my dhcp server. Using sun8i-a83t-allwinner-h8homlet-v2 as my starting point.. I built a new kernel from 6.1.0-rc6. Everything seems to work properly except the ethernet controller. I can use a usb ethernet dongle, but I would like to get the onboard working Dmesg shows " [ 1.594628] dwmac-sun8i 1c30000.ethernet: IRQ eth_wake_irq not found [ 1.594656] dwmac-sun8i 1c30000.ethernet: IRQ eth_lpi not found [ 1.594760] dwmac-sun8i 1c30000.ethernet: supply phy not found, using dummy regulator [ 1.595128] dwmac-sun8i 1c30000.ethernet: supply phy-io not found, using dummy regulator [ 1.595363] dwmac-sun8i: probe of 1c30000.ethernet failed with error -22 " I'm assuming something is incorrect in the ethernet driver. Any Ideas how to fix this ? Thanks

I would like to make myself more familiar with the early linx boot process on ARM (u-boot, device trees and co.) and my idea was that I will start tweaking with something which actually works. I tried to figure out how to obtain the source package for u-boot (in my case for linux-u-boot-orangepi3-lts-current) but the armbian package repository seem to contain obly binaries. Any idea wherethe source packages for this binaries are located (e.g. what deb-src line do I need to add to the armbian.list to make "apt-get source" to work)?

does anyone know of a version of armbian that would work on a samsung galaxy book go with a snapdragon 7c gen2? i traid the generic version and it booted to the grub, and then it restarted like all other distros i've tried. i can not find a distro to boot on this dang thing. anyone have any ideas on what to do or try? i've hit a dead end i gotta dig deeper to figure something out, so any thoughts on this would be helpful .. thanks in advance