Active threads

IMO the best choice is something with hdmi port.

I do verify what is written to the SD card. It's a homegrown script I have used for at least ten years. It's not the cause of my problem. And as for all those shiny clicky-clickity tools, no thanks! I prefer to know what is going on on my computer. Any comments on my question, anyone? If anybody could write one of the images using his his preferred/recommended imaging tool and run fsck on the resulting partition it would help me much. Thank you.

Hi pochopsp - I have the same issue on my Vontar X3. The frustrating thing is that it used in the past and now for some reason it doesn't detect the eMMC installation anymore. I haven't done a deep dive but probably (as the other participants in this thread suggest) it's only solvable with a new u-boot. Have you tried something out there? I guess if we get a new build running that new u-boot could be bundled with the releases to solve this issue for other users as well

AFAIK this can mean the ROCK3C (and software running on it) failed on interpreting HDMI info from your specific HDMI monitor (too old, buggy, not according spec, strange timing, too new, maybe more). See things w.r.t. EDID. One can set a certain video= statement on the kernel cmdline, you need to read docs etc what the options are. Easier might be to use an newer kernel, rockchip64 edge kernel is 6.18.x, that one much better RK35xx support than the 6.12.x one in the image. See armbian-config for selecting edge/beta kernel. Or change sources.list yourself so that you can just do apt install linux-image-edge-rockchip64

@Malay delete patch/u-boot/u-boot-aw/99-dump-dram-controller-regs.patch. Using your compiler it causes a fatal error. The compiler I'm using it creates a warning. You don't need it anyways, it's for ram debug messages. I removed it from my repository,

I assume you are not blind and need some screen to see what data you enter into computers. I am not saying the N2+ is HDMI connected, but sure you do use some serial console cable and terminal program or ssh or maybe even telnet. But jokes aside, I think you do not get the point that it is you yourself who needs to get your own device working if you want Debian (because Armbian is busted according to you). I mean vanilla Debian, so only Debian packages that can be fetched via apt from Debian repositories. So that means no Armbian kernel+DeviceTree and no Armbian U-Boot. That is what I show you essentially. But read info on debian.org. Up to you to jump into the cold water and swim. You already figured out it is something with I2C busses/numbering, so that is DeviceTree and/or DeviceTree overlays. Vanilla Debian is roughly 1 year older than 25.11.1 Armbian Trixie, so if no-one who owns an N2+ (and is willing to do testing/trials for you) is reacting, you are the only. You can send your N2+ to me, maybe I can make it work, but I won't send it back as I need some sort of salary for the work done of course. Other option is Ubuntu Jammy image (with custom/vendor kernel) from odroid.com or so.

I expect 2x the figure: dmesg | grep PCIe pci 0004:41:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0004:40:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link) lspci -vv | grep LnkSta LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)

You can remove Xfce from an installation, via apt purge --autoremove options, may just by un-ticking it in tasksel, and systemctl set-default multi-user.target Done that kind of trick to get rid of RPi PiXel DE in the past when they had no -Lite images and/or I wanted to keep my rootfs while upgrading in-place to newer Debian main release. Same Actuallt recently for ROCK3A Armbian Bookworm cloned from NanoPi-R6C to Armbian Trixie just headless/CLI. My last run/config of a Armbian 25.11.1 image was with autologin root and doing 1st run config, the usual I know from Armbian. So the image you use is wrongly generated maybe, but the big question mark is what image? URL+sha256sum enables others to check/confirm without guessing and maybe picking a newer/different 'latest' image or so, else DIY.

Good that this is made default now for various boards. If a board/computer has no factory written bootloader, so only bootROM/maskROM, then this allows way more flexibility and also will get rid of endless topics and support issues that have their root cause in SD-card (failing, or worse fakes, fake brands, etc). As a scrub either done automatically or as support request on-demand/ad-hoc will tell. Also many operations can be done while the board/computer is kept running, no reboot needed. Like transferring rootfs OS from SD-card to NVME and many more great things. Like replacing an SD-card without reboot. Or rollback to know-good older snapshot after faulty update. I see I wrote some things about it here: https://forum.armbian.com/search/?q=CONFIG_CMD_BTRFS&quick=1 For boards/computers with factory written bootloader, so PCs with UEFI or BIOS or the strange Raspberries with their boot(EEP)ROM that need a 1st FAT, it is a different story. I figured out that for my computers that already use Btrfs for rootfs for years, even tiny/old RPi0/1, it is currently better alignment, so that I stick to heaving an extra boot partition still. It can be very small, I had defaulted to 40MiB some years ago for a single Linux OS VM (x86 or ARM), but just for some bootaa64.efi file that is already a lot. For RPi, 3MiB was enough, so you store only a bootcode.bin start* fixup* config.txt uboot.bin bootaa64.efi. But that extra boot partition is also easily very confusing, especially for RPi like methods where kernel+initramfs+DTB are copied. Also, I had Btrfs enabled U-Boot, an Ext4 bootpartition and Btrfs rootpartition while doing experiments (booting from Btrfs raid1 straight from U-Boot) on QEMU and AllwinnerH3. kernel+initramfs+DTB were accidentally read from Ext4 (/) instead of Btrfs (/boot) and more such confusion. So then I recompiled U-Boot without Ext4 (so only FAT,Btrfs), then fine. But generally I would keep Ext4 of course. With just 1 partition, then those issues are is avoided. Then simply 'U-Boot object' and 'rootfs object', where the latter can still be chosen Ext4. Btrfs U-Boot + rootfs also would make raw/flat images viable maybe. xz-compressed will certainly have smaller download file, but for full desktop variant images, there might be an overall advantage. If rootfs is written by Armbian build with let's say compress-force=zstd:9, only first MBR+bootloader sectors, the Btrfs metadata and some filesystem slack is not compressed. I think some statistics are needed first, maybe it is not worth the effort for mass-downloads also via torrents, mirrors, etc, but for own local builds I certainly see benefits. At least I force compress almost all newly written block-devices, so also a restore from backups. It can keep thin-provisioned volumes/images very small, also roughly halves the write-time for (slower/older) SD-cards.

HI. I had same issue. For all others that might hit same issue bellow are instructions: 1. Supply yourself with known good SD card. 2. Go to KickPi website, download an image supplied by them and write it to the card using dd or balena-etcher. 2.1 Make sure that you are able to boot the image from above. 3. If you are under widows it is good to have a Virtual Machine (I have Debian 13 running inside virtual box). If you are a Linux user, just skip this step 4. Clone Armbian build project git clone https://github.com/armbian/build 4.1. Build an image: cd build ./compile.sh build BOARD=kickpik2b BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=yes RELEASE=trixie 4.2. Write the image to SD card from above. sudo dd if=output/images/Armbian-unofficial_25.11.0-trunk_Kickpik2b_trixie_current_6.12.58_minimal.img of=/dev/mmcblk0 bs=1M status=progress 5. Clone Debian Image builder git clone https://github.com/pyavitz/debian-image-builder cd debian-image-builder 5.1 Follow the instructions from Readme.md: ./install.sh make menu 5.2 In the menu adjust uboot version to 2025.7 5.2 Build the uboot make uboot board=kickpik2b-v2 6. Write Uboot to your sdcard sudo dd if=output/kickpik2b-v2/u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 conv=fsync bs=1024 seek=8 7. Congratulations: Now you would have working board, but now WiFi or Ethernet.

Hello! Is there any progress? I need to grab raw CSI2 camera on kernel 6.12 but Armbian has no CSI2-ISP stack at all at this kernel. I try to port CSI2-phy, ISP and CIF drivers from 6.1, fix compile errors, add DTS bindings but have to lack yet (need to learn new v4l2 media framework).

With the latest changes in Armbian and most importantly the update of u-boot to v2025.10 for Helios4, it is now possible to boot SATA and USB from u-boot flashed to SPI NOR flash, with the dip switch set to SPI boot mode. This even includes booting straight from u-boot to btrfs now.

Hello, I have the same issue. UART output: Trying a 2023 build to see if it starts, but looking online it looks like this is caused by a kernel build being incomplete and when it's wrong the device specific kernel files are smaller than usual. I noticed the 2023 image is about double the size. Same error on that, though channel 0 CS = 0 MR0=0x98 MR4=0x3 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0xS = 1 MR0=0x18 MR4=0x3 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 R0=0x988 MR4=0x1 MR5=0xFF MR8=nel 1 training pass! change freng done channel 0, cs 1, advanced training done ng done ng done change freq to 856MHz 1ng done ng done ng done ng done ddr_set_rate to 416MHZ,Boot1 Release Time: May 29 2020 17:36:36, version: 1.26 CPUId =mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card dOR: SDHCI ERR:cmd:0x102,stat:0x1mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 Us2000 , 0 StorageInit ok = 58036adLba = 2000 8fa0 NOTICE: BL31: v1.3(release):845ee93 NOTICE: BL31: Built : 15:INFO: plat_rockchip_pmu_init(1196): pd status 3e INFO: BLded by BL2 boot loader, Booting device without OPTEE initializatError initializing runtime service opteed_fast INFO: BL31: Pit to normal world INFO: Ent U-Boot 2022.04-armbian-2022.04-Se4b6-Pbcc6-Hc48d-V50f4-Bb703Model: Clockworkpi A06 DRAM: 3.9 GiB PMIC: RK808 Core: 215 devices, 18 uclasses, devicetree: separate MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC..USB EHCI 1.00 Bus usb@fe3c0000: USB EHCI 1.00 scanning bus usb@3 USB Device(s) found scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found scce Scanning mmc 1:1...s #0, OK Found U-Boot script /boot/boot.scr 3906 bytes read in 5 ms (762.7 K500000 Boot script loaded from 144 bytes read in 4 ms (35.2 KiB/s) 16738941 bytes read in 711 ms (22.5 MiB/s) 38343168 bytes read in 1625 ms (22.5 MiB/s) ip/rk3399clockw_qkpi-a06.dtb' 2825 bytes read in 12 ms (229.5 ## Loading init Ramdisk from Legacy Image at 06000000 ... ImOK ERROR: Did not find a cmdline Flattened Device Tree

You can find them here https://imola.armbian.com/cache/artifacts/ In case you / someone want to help fixing this - this script https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-web-index.yml needs to be adjusted to add additional entries to the download JSON file for those three variants https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-web-index.yml#L140-L142 Few months ago GitHub introduced limitations on number of artifacts per release to 1000. And in order to keep providing CLI + desktop combo - especially for - community targets, we had to drop uploading sha, asc and torrent files to GitHub release storage. Instead, they are moved to cache.armbian.com under predicted structure, but links are missing from JSON as they don't exists on the release page where current script is scrapping from.

As a follow up. Armbian doesnt seem to have proper pinebook pro support in its firmware package (i.e `armbian-firmware`) Someone was up until recently keeping track of different firmwares on the pinebook pro (link https://github.com/cobratbq/pinebook-pro) On mine I have just symlinked the raspberry pi4 versions, which has improved wifi and bluetooth. As far as i can tell, an appropriate pull request is needed against this repo? https://github.com/armbian/firmware/tree/master/brcm I was also able to update to trixie without any problems.

Ok, will try wiFi by doing that. I posted more testing in the thread of my device.

thanks~

I guess this should do:

As the wifi device is the same please see my last post in this thread : Viz : Also to fix BT : sudo crontab -e then add the line : @reboot sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep It could also be your dtb though. You could decompile my dtb from this thread and use the Bluetooth related section.

`idbloader.img` is device-specific code that is created from firmware build artifacts with U-Boot as payload using proprietary tools available only in binary form. SBC providers rarely offer ready-to-use code. I therefore prefer to load my firmware from microSD cards. Since it has apparently become increasingly common lately to provide only the MASKROM mode as the sole reliable recovery method, I have started building my firmware for Rockchip devices as RAM images as well. I can then simply upload them using MASKROM mode and start my work from there without having to rely on proprietary, binary-only tools.

While having this sent to mainline would be overall best, the faster approach in the mean time would be to send a patch via PR to this location to have it included into Armbian kernel packages: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18

At this time we do not have plans to support it. However anyone is free to step up and provide support with a pull request. We'll happily review. Perhaps chainxs will do this since they're an active volunteer contributor already

Probably more experienced users will not have similar issues, but I'll provide my solution just for for the record: Power off devide. Insert SD card into the slot. Hold 'boot' button on the mainboard. Plug in device. Release 'boot' after 5 seconds. Power off and power on. in my case it took up to 60 seconds before my device boot from SD card. I checked the same with USB and it also work (*it ust be plugged into one of USB2.0 ports). Thank you for your suggestion. I'll close the thread.

Some updates... After rebooting (power off and power on) the device.... this appears and Armbian won't boot anymore...

You don’t actually need a static route on PC1. Since PC1 already has a default gateway (192.168.100.254), anything outside 192.168.100.0/24 is automatically sent there. So PC1 isn’t the source of the routing problem. The real issue is on the 10.10.10.x side: Device1 has no gateway. Without a gateway, it can receive packets coming from the Linux box, but it has no way to send replies back to a different subnet. That’s why the communication fails. The fix is simply to give Device1 a valid gateway pointing to the Linux box. Device1: IP: 10.10.10.2 Mask: 255.255.255.0 Gateway: 10.10.10.1 On the Linux box: sudo sysctl -w net.ipv4.ip_forward=1 This is enough to route between NIC1 and NIC2. If Device1 cannot be configured manually, the Linux box can offer a small DHCP service on NIC2. A minimal dnsmasq example: interface=enp4s0 dhcp-range=10.10.10.50,10.10.10.150,255.255.255.0,12h dhcp-option=3,10.10.10.1 This simply ensures Device1 learns “send everything through 10.10.10.1”. Once Device1 has a gateway, the Linux box will forward traffic correctly and PC1 will reach it without needing any static route at all. Useful resources: https://wiki.archlinux.org/title/Router https://askubuntu.com/questions/205017/how-to-define-the-range-of-ips-using-dhcp https://pingmynetwork.com/network/ccna-200-301/dhcp-dynamic-host-configuration-protocol