Search the Community

Running the command below I have the issue below: I work with armbian-build git repo, tag 23.02.0-trunk.0256 and I run this command to build a armbian .img for my orangepi zero lts. It used to work well in february but now maybe the armbian repositories do not work anymore with this tag version ? ./armbian-build/compile.sh docker USE_MAINLINE_GOOGLE_MIRROR=yes BOARD=orangepizero BRANCH=current BUILD_KSRC=no RELEASE=bullseye BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no ROOTFS_TYPE=ext4 BOOTFS_TYPE=fat COMPRESS_OUTPUTIMAGE=sha,img ' Processing triggers for resolvconf (1.87) ... [ o.k. ] Checking MD5 sum of installed packages [ debsums ] debsums: changed file /usr/share/doc/base-files/changelog.gz (from base-files package) debsums: changed file /etc/os-release (from base-files package) debsums: changed file /etc/issue.net (from base-files package) debsums: changed file /etc/issue (from base-files package) [ error ] ERROR in function create_rootfs_cache [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:0 ] [ error ] MD5 sums check of installed packages failed [ o.k. ] Process terminated [ error ] unmount_on_exit() called! [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:1 -> functions/main/rootfs-image.sh:0 ] [ o.k. ] Unmounting [ /root/armbian/.tmp/rootfs-329b560e-4e99-40c7-bad2-3ddabd8752c8/ ] [ error ] ERROR in function unmount_on_exit [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:1 -> functions/main/rootfs-image.sh:27 -> functions/logging/traps.sh:0 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Thank you for your help

Bookworm 6.1.30 - wi-fi don't work.

First, I have installed latest Armbian 23.8 Bookworm CLI, boot works fine, I can login Then, I have installed wireguard. As a dependency, wireguard install linux-image-6.1.0-12-rt-armmp After reboot device is unavailable in network (orange LAN LED blinking while green does not, I assume ethternet broken with this kernel)

Now that xradio has been enabled on kernel 6.x, I'm ready to upgrade my Orange Pi Zero that I've been keeping on 23.02 with kernel 5.x. With armbian-config I've unfrozen kernel/firmware updates and after apt upgrade and reboot I am on kernel 6.1.53 and wifi is working! But boot message says I'm still on 23.02, and apt says that armbian-bsp-cli-orangepizero is being kept back. Now trying: $ sudo apt install armbian-bsp-cli-orangepizero [...] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: armbian-bsp-cli-orangepizero-current : Depends: base-files (>= 23.8.3) but 23.8.1-bullseye is to be installed E: Unable to correct problems, you have held broken packages. Do I just need to wait for something to be updated in the repositories so that armbian-bsp-cli-orangepizero will be made available, or have I messed up something on my system that I need to fix?

Should it be possible to take a working SD card out of one OrangePi Zero and put it in a new one? Same board and amount of RAM and everything.

Hi, I have a board Orange Pi Zero with modified PAs for power of WiFi module from PA20 to PA02, by soldering a connection on board. This is done to allow connection of I2C DAC. I see that board definition in 'u-boot/configs/orangepi_zero_defconfig' It uses dts definition of: 'arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts' I need to modify one section of this dts file from: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 20 GPIO_ACTIVE_HIGH>; to: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 2 GPIO_ACTIVE_HIGH>; How can I do this and use armbian build script: compile.sh Thanks, Michal

The topic is no longer new, but I have not found the reason and its solution! If you turn off the power (just pull out the wire) then you can get a non-working system. As I noticed, the files opened at the time of launch are broken. And some files such as /etc/boot/armbianEnv.txt in general, they are recorded with some kind of garbage!!! Because of this, your settings fly off! For example, I use ttys1 and this option is registered armbianEnv.txt , but after the power loss, there is just terrible garbage in this file, as if the memory dump fell there!!! For example, I still use dotnet, so it also breaks down and does not start anymore!! When you try to run dotnet from the command line, you get a bus error! Of course, deleting and reinstalling it solves the problem. You may also get problems with apt! I certainly expected this from windows. But for linux to be somewhat unreliable is a tin and a disappointment!! Why does this happen and how to treat it??? Now I have made a sh script to check the integrity of files and restore them. But these are crutches and a shame for linux!!! Maybe arabian is crooked and unreliable? or is it a disease of all systems??? I must say right away that the SD card is normal! This has been tested on 10 minicomputers. It's the same problem everywhere!

Hi, I use an OrangePi Zero as a race timer for a car. It is powered from the car. So when the car starts the OrangePi gets power and boots and when the car is turned off the OrangePi loses power and "turns off". This isn't ideal but I don't have a lot of options. I feel like this is a fairly common use case for electronics in cars especially ones like race timers etc. Unless I have a battery as well. I was wondering what are the best things to do to protect against the sudden power loss so that I don't corrupt anything? Is it possible to make parts of the file system read only maybe? All I do with the OrangePi is run a C++ application, it uses two serial ports and runs a server on port 80. The application does read and write its own configuration files and log files. But these are not OS files, only files that the application created itself. I have noticed that after writing or appending to a file from C++, if the power is pulled and then plugged back in the change to the file does not persist. I can ssh on before the power is pulled and `cat` the file and see that it is updated. Seems that the file data is held in RAM for a little while before actually writing. Is there anyway to force file writes to actually be flushed and written straight away?

Help me, my orangepizero wont work. Every time i try to start ssh it say connection refused. Only sometimes it works. I recently installed Armbian 22.5 bullseye and after that it stopped working. Pls help

I am trying to figure out how to compile and load the Xradio drivers onto an orange pi zero LTS. I am having some troubles with the xradio drivers that came with my image and am hoping that https://github.com/fifteenhex/xradio will add some improvements. There does seem to be some code change so I am remaining optimistic. I am able to compile the drivers with the kernel from https://github.com/orangepi-xunlong/orangepi-build but it crashes network manager and a few other modules when I try to modprobe it, I am guessing it is because this kernel is not an armbian kernel. I am trying to get the kernel https://github.com/armbian/build to work, but it doesn't look like that's what I need to do. I am lost as to how to get this compiled and any help would be appreciated.

I have orange pi zero board ..i searched a lot for changing boot splash screen ( currently "armbian universal operating system" which is enabled by adding bootlogo=true in armbianEnv.txt ) I have tried Plymouth it is not working After searching lot i knew about if we can replace bootsplash.armbian , it can help because then neither we need to change uboot packages nor we have to add quiet splash like words etc in armbianEnv.txt. https://github.com/armbian/build/tree/master/packages/blobs/splash. With help of this bootsplash-packer Can anyone list me some steps ( in short ) How to run this script and create bootsplash.armbian and replace it

My OrangePi Zero is on 23.02 and I intend to stay with it (unless/until xradio wifi works on kernel 6.x). Just ran apt update and it shows these available packages: armbian-config/bullseye,bullseye 23.08.0-trunk--1-SA9048-Baeda all [upgradable from: 23.02.2] armbian-firmware/bullseye,bullseye 23.08.0-trunk--1-SA1251-B226d all [upgradable from: 23.02.2] armbian-zsh/bullseye,bullseye 23.08.0-trunk--1-SAbfee-Baf88 all [upgradable from: 23.02.2] I'm surprised to see anything related to 23.08 seeing as that version hasn't been released yet, so obviously I don't really understand what it means to be seeing this. Should I go ahead and install these even though I don't intend to upgrade to 23.08? Maybe this should be in the "beginners" area; mods please feel free to move if appropriate.

Hello, I would like to know how they reduce the size of the images and then, when the microSD cards are inserted into a card, they expand to fill the entire space. In other words, the same thing that Armbian images do when we use them for the first time: they are small, and then they occupy all the storage space.

Hello all, I'm trying to revive my old OPIZ + cheap expansion board. I've tried all recent images available but I couldn't get it to work. Is there any old version (with repository still alive) available with which I can install sox + alsa. I don't need recent kernel or software (but wifi) Any idea? Thanks for help Pascal

ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.14.34-sunxi, Orange Pi Zero board. Very limited Debian installed, wifi doesn't work. I found lines install xradio_wlan /bin/false install 8189es /bin/false in /etc/modprobe.d/blacklist.conf and removed it. In /etc/modules-load.d/modules.conf I added the lines 8189es xradio_wlan. No help, wi-fi didn't work, nothing about xradio or wifi in dmesg. I figured out that there was no drivers (modules) for wifi. Found this article https://linux-sunxi.org/Wifi I execute the commands from the article, section RTL8189ES / RTL8189ETV The driver has its own repository: git clone https://github.com/jwrdegoede/rtl8189ES_linux.git cd rtl8189ES_linux make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnu- KSRC=../linux This is what it says root@its-02-o:~# git clone https://github.com/jwrdegoede/rtl8189ES_linux.git Cloning into 'rtl8189ES_linux'... remote: Enumerating objects: 2565, done. remote: Counting objects: 100% (807/807), done. remote: Compressing objects: 100% (413/413), done. remote: Total 2565 (delta 432), reused 670 (delta 385), pack-reused 1758. Receiving objects: 100% (2565/2565), 7.29 MiB | 2.32 MiB/s, done. Resolving deltas: 100% (1476/1476), done. root@its-02-o:~# cd rtl8189ES_linux root@its-02-o:~/rtl8189ES_linux# make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnu- KSRC=../linux make ARCH=arm CROSS_COMPILE=arm-linux-gnu- -C ../linux M=/root/rtl8189ES_linux modules make[1]: *** ../linux: No such file or directory. Stop. Makefile:2292: recipe for target 'modules' failed make: *** [modules] Error 2 root@its-02-o:~/rtl8189ES_linux# What am I doing wrong? How do I install WiFi modules (drivers)? And the following is in the dmesg vcc-wifi: disabling What is this wifi power disabling? How do I turn it on? Googling didn't help, I couldn't find anything clear about vcc-wifi: disabling Don't suggest installing a new/other Debian. Important software works on it (everything works over LAN), you just need to enable wi-fi. Translated with www.DeepL.com/Translator (free version) ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.14.34-sunxi, плата Orange Pi Zero. Очень какой-то урезаный Debian установлен, не работает Wi-Fi. Нашел в файле /etc/modprobe.d/blacklist.conf строки install xradio_wlan /bin/false install 8189es /bin/false, удалил. В файле /etc/modules-load.d/modules.conf добавил строки 8189es xradio_wlan. Не помогло, wi-fi не заработал, в dmesg ничего про xradio или wifi нет. Понял что нет драйверов (модулей) Wi-Fi. Нашел такую статью https://linux-sunxi.org/Wifi Выполняю комманды из статьи, раздел RTL8189ES / RTL8189ETV Driver has its own repository: git clone https://github.com/jwrdegoede/rtl8189ES_linux.git cd rtl8189ES_linux make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnu- KSRC=../linux Вот что пишет root@its-02-o:~# git clone https://github.com/jwrdegoede/rtl8189ES_linux.git Cloning into 'rtl8189ES_linux'... remote: Enumerating objects: 2565, done. remote: Counting objects: 100% (807/807), done. remote: Compressing objects: 100% (413/413), done. remote: Total 2565 (delta 432), reused 670 (delta 385), pack-reused 1758 Receiving objects: 100% (2565/2565), 7.29 MiB | 2.32 MiB/s, done. Resolving deltas: 100% (1476/1476), done. root@its-02-o:~# cd rtl8189ES_linux root@its-02-o:~/rtl8189ES_linux# make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnu- KSRC=../linux make ARCH=arm CROSS_COMPILE=arm-linux-gnu- -C ../linux M=/root/rtl8189ES_linux modules make[1]: *** ../linux: No such file or directory. Stop. Makefile:2292: recipe for target 'modules' failed make: *** [modules] Error 2 root@its-02-o:~/rtl8189ES_linux# Что не так делаю? Как установить модули (драйвера) WiFi? А вот такое в dmesg есть vcc-wifi: disabling Что это питание wifi отключено? Как включить? Гугление не помогло, не нашел ничего внятного про vcc-wifi: disabling Не предлагайте установить новый/другой Debian. На нем работает работает важный софт (по LAN все работает), нужно просто включить wi-fi. Если можно на русском. Английский только с переводчиком :-(

Hi all, I need to add some packages to Armbian in the build phase. I tried two ways, both failed: 1. Had run through docs (https://docs.armbian.com/Developer-Guide_User-Configurations/), and the suggestion is to add a var PACKAGE_LIST_ADDITIONAL in userpatches/lib.config PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL watchdog modemmanager iptables iptables-persistent dnsmasq bridge-utils iproute2 openvpn" Building the image I get the following error: [🌱] Using user configuration override [ /home/andrea/armbian/build/userpatches/lib.config ] /home/andrea/armbian/build/userpatches/lib.config: line 1: PACKAGE_LIST_ADDITIONAL: readonly variable [💥] Exiting with error 1 [ at /home/andrea/armbian/build/userpatches/lib.config:1 source() --> userpatches/lib.config:1 do_extra_configuration() --> lib/functions/configuration/main-config.sh:352 do_with_logging() --> lib/functions/logging/section-logging.sh:81 do_with_conditional_logging() --> lib/functions/logging/section-logging.sh:111 prep_conf_main_build_single() --> lib/functions/main/config-prepare.sh:34 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:22 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] 2. Customizing userpatches/customize-image.sh: Added the following lines to the aforementioned file: CUST_PACKAGES="watchdog modemmanager iptables iptables-persistent dnsmasq bridge-utils iproute2 openvpn" apt-get install -yy $CUST_PACKAGES |& tee -a $DEST/${LOG_SUBPATH}/custom.log The build completes, but packages aren't added as the logging prevents the build to fail. Anyway the following info messages are displayed during the build: [🔨] Reading package lists... [🔨] Building dependency tree... [🔨] Reading state information... [🔨] Package modemmanager is not available, but is referred to by another package. [🔨] This may mean that the package is missing, has been obsoleted, or [🔨] is only available from another source [🔨] [🔨] Package iptables is not available, but is referred to by another package. [🔨] This may mean that the package is missing, has been obsoleted, or [🔨] is only available from another source [🔨] However the following packages replace it: [🔨] libxtables12 [🔨] [🔨] E: Unable to locate package watchdog [🔨] E: Package 'modemmanager' has no installation candidate [🔨] E: Package 'iptables' has no installation candidate [🔨] E: Unable to locate package iptables-persistent [🔨] E: Unable to locate package dnsmasq [🔨] E: Unable to locate package openvpn Can you suggest a suitable way to add packages to the build? Thanks very much in advance, kind regards Andrea

Hi all, I need to enable rts/cts on my OrangePi Zero with Armbian buster with Linux 5.4.26-sunxi installed. I added the "param_uart2_rtscts=1" (I'm using /dev/ttyS2) to the /boot/armbianEnv.txt file On mi code I use this initialization of the port. xxxxx.c_cflag |= port_parity | port_bits | port_stop | CLOCAL | CRTSCTS | CREAD; Not only rts/cts but also the tx and rx pin aren't working now. Has anyone managed to enable the port on this board? Am I doing something wrong?

Hi all, I'm trying to put my orange pi zero to talk with a CAN BUS via mcp2515 chip. The chip is SPI controlled. The actual image does not have support for SocketCAN enabled, so I'm compiling the kernel with SocketCan following the kernel configuration shown here https://developer.ridgerun.com/wiki/index.php/How_to_configure_and_use_CAN_bus I'm using the cross-compiler tool from the armian website. After the image is burned to the sdcard and the orange pi zero is booted, I can see the image has can support enabled, but when I load the mcp251x driver it does nothing. I'm sure I'm missing some detail on spi side in order to have the mcp driver pointing to the proper spi. Any hints? Thanks in advance Amauri

I've change OpiZero's cpu from H2+ to H5, and made linux5.4.65 image with the option of "Orangepiplus (H5)" of the Build-Package which described in the Orangepi manual. After the linux startup, the output of command DMESG shows "sunxi-mmc 1c10000.mmc: Cannot do DMA to address 0x00008000514a3870", and TRACE as follows: [ 212.402793] xradio_wlan: version magic '5.15.27-station SMP preempt mod_unload aarch64' should be '5.4.65-sunxi64 SMP mod_unload aarch64' [ 248.019893] xradio_wlan: loading out-of-tree module taints kernel. [ 248.024327] xradio_wlan: module verification failed: signature and/or required key missing - tainting kernel [ 248.027506] xradio: XR819 device discovered [ 248.030479] sunxi-mmc 1c10000.mmc: Cannot do DMA to address 0x0000800051e83870 [ 248.030507] sunxi-mmc 1c10000.mmc: overflow 0x0000800051e83870+8 of DMA mask ffffffff bus mask 0 [ 248.030538] ------------[ cut here ]------------ [ 248.030572] WARNING: CPU: 2 PID: 1513 at kernel/dma/direct.c:35 report_addr+0x38/0xa0 [ 248.030578] Modules linked in: xradio_wlan(OE+) zstd rtl8xxxu rtl8192cu rtl_usb rtl8192c_common rtlwifi mac80211 cfg80211 libarc4 snd_soc_simple_card snd_soc_simple_card_utils sun8i_codec_analog sun8i_adda_pr_regmap sun4i_i2s sun4i_gpadc_iio sun4i_tcon sun8i_tcon_top sun8i_mixer cpufreq_dt zram sch_fq_codel usb_f_acm u_serial g_serial libcomposite ip_tables x_tables autofs4 fixed gpio_regulator [ 248.030691] CPU: 2 PID: 1513 Comm: insmod Tainted: G OE 5.4.65-sunxi64 #2.2.2 [ 248.030697] Hardware name: Xunlong Orange Pi Zero Plus (2pw5, Linux-Kernel Device Tree) (DT) [ 248.030707] pstate: 80000005 (Nzcv daif -PAN -UAO) [ 248.030720] pc : report_addr+0x38/0xa0 [ 248.030731] lr : report_addr+0x98/0xa0 [ 248.030736] sp : ffff800011e833c0 [ 248.030741] x29: ffff800011e833c0 x28: ffff800011e83dd0 [ 248.030752] x27: 0000000000000000 x26: ffff800011e836e8 [ 248.030763] x25: ffff800011e83600 x24: 0000000000000000 [ 248.030773] x23: 0000000000000002 x22: ffff000036706810 [ 248.030782] x21: 0000000000000008 x20: ffff000035ccf000 [ 248.030793] x19: ffff000036706810 x18: 0000000000000020 [ 248.030802] x17: 00000000000012b0 x16: 00000000000012a0 [ 248.030812] x15: ffff800011085000 x14: 6b73616d20414d44 [ 248.030822] x13: 20666f20382b3037 x12: 3833386531353030 [ 248.030832] x11: 3038303030307830 x10: 0000000000000000 [ 248.030842] x9 : 0000000000000003 x8 : 00000000000001b4 [ 248.030851] x7 : 0000000000000001 x6 : 0000000000000001 [ 248.030861] x5 : 0000000000000000 x4 : 0000000000000001 [ 248.030870] x3 : 0000000000000006 x2 : 6eac74d7450f9a00 [ 248.030879] x1 : 6eac74d7450f9a00 x0 : 0000000000000000 [ 248.030889] Call trace: [ 248.030903] report_addr+0x38/0xa0 [ 248.030914] dma_direct_map_page+0x110/0x130 [ 248.030924] dma_direct_map_sg+0x78/0xe0 [ 248.030939] sunxi_mmc_request+0x70/0x4f0 [ 248.030952] __mmc_start_request+0x64/0x130 [ 248.030962] mmc_start_request+0x90/0xb8 [ 248.030973] mmc_wait_for_req+0x6c/0x100 [ 248.030985] mmc_io_rw_extended+0x250/0x2a8 [ 248.030996] sdio_io_rw_ext_helper+0x18c/0x230 [ 248.031007] sdio_memcpy_fromio+0x1c/0x28 [ 248.031072] sdio_data_read+0x1c/0x28 [xradio_wlan] [ 248.031118] __xradio_read+0x28/0x40 [xradio_wlan] [ 248.031166] xradio_reg_read+0x3c/0x60 [xradio_wlan] [ 248.031214] xradio_load_firmware+0x34/0xe18 [xradio_wlan] [ 248.031261] xradio_core_init+0x130/0x460 [xradio_wlan] [ 248.031308] sdio_probe+0x130/0x164 [xradio_wlan] [ 248.031321] sdio_bus_probe+0x12c/0x198 [ 248.031337] really_probe+0xdc/0x430 [ 248.031348] driver_probe_device+0xdc/0x130 [ 248.031358] device_driver_attach+0x6c/0x78 [ 248.031367] __driver_attach+0x9c/0x168 [ 248.031376] bus_for_each_dev+0x6c/0xc0 [ 248.031385] driver_attach+0x20/0x28 [ 248.031394] bus_add_driver+0x138/0x218 [ 248.031404] driver_register+0x60/0x110 [ 248.031414] sdio_register_driver+0x24/0x30 [ 248.031463] xradio_sdio_register+0x14/0x20 [xradio_wlan] [ 248.031510] xradio_core_entry+0xc/0x1000 [xradio_wlan] [ 248.031523] do_one_initcall+0x50/0x1a8 [ 248.031537] do_init_module+0x50/0x1f0 [ 248.031547] load_module+0x1f68/0x2510 [ 248.031558] __do_sys_finit_module+0xac/0x110 [ 248.031568] __arm64_sys_finit_module+0x1c/0x28 [ 248.031583] el0_svc_common.constprop.0+0x68/0x160 [ 248.031594] el0_svc_handler+0x20/0x80 [ 248.031603] el0_svc+0x8/0x1fc [ 248.031610] ---[ end trace d07a211fb8606773 ]--- [ 248.031628] sunxi-mmc 1c10000.mmc: dma_map_sg failed [ 248.031637] sunxi-mmc 1c10000.mmc: map DMA failed [ 248.031662] xradio WRN: FWIO: can't read config register, err=-12. [ 248.043881] xradio PM-DEV: xradio_pm_release root@orangepizeroplus:/home/orangepi# rmmod xradio_wlan.ko rmmod: ERROR: Module xradio_wlan is in use root@orangepizeroplus:/home/orangepi# can give me some hints of clues to solve the problem ? thx.

Tried both Debian and Ubuntu based 23.5 releases on my v1.4 board Boot process stops at "Starting kernel..." Also tried the "minimal CLI" debian release with same results. The previous versions 23.02 are fine. ▒ U-Boot SPL 2022.07-armbian (May 27 2023 - 19:26:49 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (May 27 2023 - 19:26:49 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB Core: 65 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4121 bytes read in 3 ms (1.3 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 184 bytes read in 3 ms (59.6 KiB/s) 15848831 bytes read in 658 ms (23 MiB/s) 8477464 bytes read in 355 ms (22.8 MiB/s) Found mainline kernel configuration 35377 bytes read in 7 ms (4.8 MiB/s) 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 617 bytes read in 6 ms (99.6 KiB/s) Applying kernel provided DT overlay sun8i-h3-tve.dtbo 4185 bytes read in 6 ms (680.7 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0x815b18 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 15848767 Bytes = 15.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 EHCI failed to shut down host controller. Loading Ramdisk to 490e2000, end 49fff53f ... OK Loading Device Tree to 49071000, end 490e1fff ... OK Starting kernel ...

Thought this might be useful: FROM: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2236 01 3.3V 02 5V 03 TWI0-SDA PA12 04 5V 05 TWI0-SCK PA11 06 GND 07 PWM1 PA06 08 UART1_TX PG06 09 GND 10 UART1_RX PG07 11 UART2_RX PA01 12 SIM_CLK/PA_EINT7 PA07 13 UART2_TX PA00 14 GND 15 UART2_CTS PA03 16 TWI1-SDA PA19 17 3.3V 18 TWI1-SCK PA18 19 SPI1_MOSI PA15 20 GND 21 SPI1_MISO PA16 22 UART2_RTS PA02 23 SPI1_CLK PA14 24 SPI1_CS PA13 25 GND 26 SIM_DET/PA_EINT10 PA10 FROM OFFICIAL USER MANUAL: https://drive.google.com/drive/folders/1lrtE6lbpXqxXTMmq7IxROOaZbOQ0U8uP P01 VCC-3V3 P02 VCC-5V P03 TWI0-SDA PA12 P04 VCC-5V P05 TWI0-SCK PA11 P06 GND P07 PWM1 PA6 P08 UART2_TX PA0 P09 GND P10 UART2_RX PA1 P11 S-TWI-SCK PL0 P12 PD11 P13 S-TWI-SDA PL1 P14 GND P15 UART2_CTS PA3 P16 TWI1-SDA PA19 P17 VCC3V3-EXT P18 TWI1-SCK PA18 P19 SPI1_MOSI PA15 P20 GND P21 SPI1_MISO PA16 P22 UART2_RTS PA2 P23 SPI1_CLK PA14 P24 SPI1_CS PA13 P25 GND P26 PD14 So you can make ~/bin/pinout-orange-pi-zero, and ~/bin/pinout containing: #!/bin/bash cat ~/bin/pinout-orange-pi-zero ... or just "~/bin/pinout": #!/bin/bash echo "text text text" ...so you'll have a pinout command like a Raspberry Pi. I have confirmed that pin 10 should be PG07, pin 12 should be PA07 and pin 26 should be PA10 for a DS18B20 temperature sensor with armbianEnv.txt like: $ cat /boot/armbianEnv.txt --- param_w1_pin=PA07 So it looks like the picture from Orange Pi forums is more accurate. Can anyone comment on the differences between the two pinouts eg pin 10, 12, 26, and others? Thanks, and thanks for making Armbian, and firstpost. Also warning, for other noobs (could have saved me several hours): "Armbian 23.5 Jammy" is broken! Click "Archived versions for reference and troubleshooting" on the download page and download "Armbian_23.02.2_Orangepizero_jammy_current_5.15.93.img.xz" instead

Hi Team I have two brand new Orange PI Zero LTS. Is this supported with the normal Zero download? Thanks

ls /sys/class/udc > UDC ls:write error: Device or resource busy I'm trying to get an armbian device (banana pi m2 zero and/or the orange pi zero LTS) to function as a USB client, but I can't seem to get the above step working. Any suggestions? lsof UDC returns nothing. On the RaspberryPI 4 this worked without issue

Well it took me longer than i hoped but i have managed to forward port icenowys code for TVE on the H2+/H3 to mainline armbian. It seems to work totally fine, with a few caveats. First: Sample images of it in action -> https://imgur.com/a/vXQEM Second: the patch itself -> https://github.com/stevenj/h3-tve/tree/v0.0.11 Third a prebuilt image for Orange Pi Zero: -> https://github.com/stevenj/h3-tve/releases/tag/v0.0.11 Howto: just put the patch into userpatches for the sunxi-next kernel, and build. it should apply cleanly. Its for H2+/H3. I have only tried it on a orange pi zero, but it should work on all H2+/H3 boards. You then need to edit /boot/armbianEnv.txt add tve to overlays to enable it. the driver will only run and enable tv out when the tv out devices are specifically enabled, so i created an overlay which does this. If you want to turn TV out off, just remove tve from the overlays line. My armbianEnv.txt overlays looks like this: overlays=usbhost2 usbhost3 tve If you want copious amounts of DRM debug info in your logs, add this as well: extraargs=drm.debug=0xF Its not needed, unless you really want the debug info. Notes: 1. The default mode is PAL, with 720x576 resolution. Thats outside of normal PAL displayable area, and so the screen overscans. I dont know how to correct this, although its mostly just annoying with terminals. I also don't know how to change the video mode to NTSC. 2. The standard font is a bit thin for composite video, and causes slight strobing and color impurity. Its because PAL needs pixels to be a certain MINIMUM width or color information can not be properly encoded. A way to resolve this is use : # apt-get install fbterm ... $ fbterm -s 20 This will run a terminal which is easy to change the font, and pick a bigger one. its much easier to read. Look at the help for fbterm to work out everything it can do. 3. I used the program "fim" to display the test images. there are others for doing stuff on the terminal. 4. I haven't tried X. I am not interested in running an X terminal on a TV, but it should probably work fine. Other than that it all seems good. I originally tested my hardware with the legacy kernel, and the image quality from this patch seems superior to what the legacy kernel produces. (legacy was noisy) The only other thing you need to know is Orange Pi Zero is missing filter circuity from its Composite Output, the most important thing you need to do is put a 50 ohm resistor between the signal and GND. i soldered one inside my RCA connector, it fits fine and isn't too difficult. IF you don't do this the image will bloom and look like total crap, so you have been warned. As this patch allows TVE to be enabled/disabled through use of the Device Tree overlays, i think it should be fine if the Armbian devs want to include it. I am happy to clean out some of the debug messages i added if they are interested in making a standard part of the build. If not, its easy enough to build your own image, just follow the guides on how to rebuild armbian. EDIT: I need to mention, all props go to Icenowy Zheng who wrote the original driver. I just tweaked the device tree stuff and got it in a state where it can apply cleanly to the armbian mainline kernel and build system. Original code is here: https://github.com/Icenowy/linux/tree/tve-v2

Hello. I have a problem with Orange Pi Zero LTS. I also have an expansion board and the required 3.5-jack cable. I have read many different forums and sites where people have described problems with video signal output. Often there are solutions such as: 1. Editing the file /boot/script.bin But this file does not exist. 2. They also talk about the launch of "tv". You need to add an entry to /etc/modules. But that doesn't work either, since ./tvout doesn't exist. As I understand it, in new versions there is no TV support, but there is no way to download old versions either. The latest version that can be downloaded is 5.59, but it also does not support TV. Some people since ~2019-2020 are wondering when this ability will be returned. I have the following questions: 1. Where can I download a version like 5.25 or older? 2. Or is there another way for Armbian to turn on the video signal? 3. Why did the developers remove this function? 4. And why haven't they brought this function back yet? P.S. Sorry for my english