Search the Community

The problem seems to be kernel version 6.1.30; Just writing image file 'Armbian_23.5.1_Nanopineo_bookworm_current_6.1.30_minimal.img' to SD-card gives the following output via serial console: U-Boot SPL 2022.04-armbian (May 27 2023 - 19:27:28 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.04-armbian (May 27 2023 - 19:27:28 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 33 devices, 12 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface0 Error: ethernet@1c30000 address not set. No ethernet found. starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: 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@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 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 182 bytes read in 2 ms (88.9 KiB/s) 10963883 bytes read in 456 ms (22.9 MiB/s) 8477464 bytes read in 354 ms (22.8 MiB/s) Found mainline kernel configuration 35417 bytes read in 7 ms (4.8 MiB/s) 504 bytes read in 5 ms (97.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 4185 bytes read in 5 ms (817.4 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: 10963819 Bytes = 10.5 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 4958b000, end 49fffb6b ... OK Loading Device Tree to 4951a000, end 4958afff ... OK Starting kernel ... From here on it hangs. The board runs fine with kernel 5.15.93 and Bookworm userspace from its usual SD-card that I manually upgraded to Bookworm (edit sources lists and added armbian.gpg key). That dist-upgrade did not upgrade the kernel, still kept at 5.15.93. Also I saw no change in U-boot. As a trial, switched to nightly in armbian-config, that installed kernel 6.1.30, but also same hang as the official image. So I rolled-back that trial, and now the question is, why does this kernel 6.1.30 hang?

Hello! Brand new user here to the NanoPi Neo and even the forum. I'm planning to use a NanoPi Neo as hardware "interactor", the main idea is to connect a NanoPi Neo to a smartphone (Android or iOS), power the board from the USB cable and work in Host Mode to interact with de smartphone with libimobiledevice or adb. OTG does not support charging + data at the same time without a "special" OTG adapter. What I want to do is power the NanoPi by using the smartphone and even interact with it in host mode, like a regular computer will do, in simple terms, using a single cable, but getting power from it. Is this possible using NanoPi microUSB+OTG port? Can this be archieved in "gadget mode"? (Tutorial) I'm new to this OTG, USB dual-role thing and I can't fully understand it. Do I need a hardware mod? Is the only way to archieve this feature to usea an adapter with external power-in ?? Very many thanks for your help.

Neo has one SPI port and I need two, so would like to add another spi using spi-gpio, but no success (I think). I am using Armbian 23.02.2 Bullseye, default kernel does not enable it, recompiled using linux-source-5.15.93-sunxi.tar.xz, enabled spi-gpio as module. Digged around forum, prepared below dts and armbian-add-overlay succeeded. But there is no message arrived when loading (dmesg shows nothing about spi) and no /dev/spi* created. Is it OK or there must be something? Please advise.... / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/"; __overlay__ { softspi: spi_gpio { compatible = "spi-gpio"; #address-cells = <1>; #size-cells = <0>; ranges; sck-gpios = <&pio 0 15 0>; /* PG6 */ mosi-gpios = <&pio 0 16 0>; /* PG7 */ miso-gpios = <&pio 0 1 0>; /* PA6 */ num-chipselects = <0>; status = "okay"; spidev { compatible = "linux,spidev"; reg = <0>; spi-max-frequency = <10000000>; status = "okay"; }; }; }; }; };

I am trying to get NanoPi Neo to work with a Murata 2AE module Over USB. The Murata module uses the Infineon CYW4373 chipset. So far I have: Rebuilt the kernel with CONFIG_BRCMFMAC_USB=y. This allowed the device to be recognized, but unable to load a driver Installed linux-firmware. Now the devices loads and even shows up as a wireless interface in ifconfig (wlan0 on bleeding edge, wlx..... on current) However, configuring the interface or scanning does not work. root@nanopineo:~# iwlist wlan0 scan wlan0 Interface doesn't support scanning : Invalid argument and I can find the following errors in dmesg: [ 21.187787] brcmfmac: brcmf_usb_dl_cmd: usb_submit_urb failed -19 [ 21.635746] ieee80211 phy0: brcmf_fws_attach: failed to set bdcv2 tlv signaling [ 30.228992] ieee80211 phy0: brcmf_cfg80211_add_iface: iface validation failed: err=-16 If anyone has has worked gotten this chipset to work or has any general guidance on where to go next, I would appreciate it.

Hi. Please help me to understand how hardware encoding works in nanopi with H3 chipset. I have newest version of armbianos: cedrus and related modules is loaded by kernel There are following hardware acceleration methods and encoders Please explain me what i am doing wrong here : and here: Thanks a lot.

Good morning, I'm trying to activate PWM by hardware to use wiringpi. I activate the PWM option from Armbian config hardware, but it doesn't seem to have any effect, and UART0 doesn't seem to be deactivated. I'm not sure if there's any issue or if I'm doing something else wrong. The build is Armbian 22.11.1 Jammy with Linux 5.15.80-sunxi. Thanks for the help!

Hello after some search i successfull attack Ibutton on 1 wire, using ibutton probe my problem is that by default kernel scan for slaves every 10 seconds. Want to change it to 1 second or less if possible. Searching a bit, on some linux distributions this solves the problem: modprobe wire timeout=1 slave_ttl=5 modprobe w1-gpio but since in arbian /arbianEnv.txt take care of modules loaded, it do not work, My current file is: verbosity=1 bootlogo=false console=serial disp_mode=1920x10[D80p60 overlay_prefix=sun8i-h3 overlays=i2c0 pps-gpio uart1 uart2 uart3 usbhost1 usbhost2 w1-gpio param_pps_pin=PA6 param_w1_pin=PC3 rootdev=UUID=6dee376a-a115-473b-939b-b91774c75fa8 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I have tried to add: param_w1_timeout=1 param_wire_timeout=1 and some other - unsuccessfull I need some help, thanks in advance

Hi, i need to download version Armbian 21.05.6 Buster with Linux 5.10.43-sunxi , is it possible to do it now and how? thank you

I am creating a script that can backup sd-cards running on the system, resizing it with desired value or via resize2fs calculated. I learn a lot but there are a few things I don't fully understand. When I create a backup I dd what I understand is the bootsector, ie I grab the "start" position of the partition I am backing up with fidisk and use that value and a blocksize of 512. I then add another 10mb (in bytes) just to be sure. Usually the bootsector is 8192 big, but not always (IIRC nanopi neo3;s is WAY bigger). dd bs=512 count=$DDBOOTSECTOR if=/dev/mmcblk0 of=$IMG_FILE conv=noerror,sync status=progress I then truncate the file, calculated either by resize2fs minimum calculation or via an input + file usage in df (depending of what flag I start the script with) + bootsector + yadayadayda. (if someone want me to post the script I will, but the script and calculations work, although I "force" some commands) I then loop the created img file and delete the partition on the /dev/loop0 and recreates it to cover 100%. Then format it with mkfs.ext4 copying the name and uuid from wherever I backup from. I mount the loop and rsync / rsync -ahvD --exclude={/lost+found,/proc/*,/sys/*,/dev/*,/tmp,/run/*,/mnt/*,/media/*,/var/log.hdd,/var/swap,/etc/udev/rules.d/70-persistent-net.rules,/var/lib/asterisk/astdb.sqlite3-journal} --info=progress2 --stats --delete --force --partial / $tmp_dir This seems to work, but there are probably some things that are just "accepted" not really "perfect". So questions: 1. Should I only dd the EXACT bootsector and not add the extra 10mb? The reason I ask is because if I try to delete the partition with parted, I have to do a hack in the scrip where I simulate button presses, it warns me that "the partition cant be outside of the disk" when I try to REMOVE it. Solution, I use sfdisk to remove the partition, but it prompts me to think there is something wrong going on here. If the size I create is ABOVE the resize2fs reported minimum i don't get this warning. sfdisk was the solution in this case, but still curious on this behavior. If I try to only dd the small part, it sometimes works, sometimes doesn't so I come here asking. (I might be able to do some further research but since I have other questions, why not ask) 2. Does armbian ever update the u-boot via apt? I do my next update with rscync by looping the file and mounting it. But that wont EVER cover the bootsector. 2b. If yes, do I solve this by again dd:ing ONLY the bootsector? 3. I have noticed that sudo apt update on armbian includes armhf even though running arm64. This makes the update process VERY long. dpkg --print-foreign-architectures shows armhf so i remove it with dpkg --remove-architecture armhf and then find /var/lib/apt/lists/ -type f -exec rm {} -v \; Seems to fix this but is this a bad idea? Why is the armhf even being fetched to begin with? To my memory I have not added arhmf architecture... Thanks in advance!

Hello, it is been awhile since I used armbian with Orange PI, now I took one orange PI NEO on it's connector is UART0, UART1 and UART2. My goal is to use all UARTS available on board. Googling a little I found the part where I should use BIX2FEX to convert script.bin and insert port definitions there, bot looks like that way is obsolete. looks by default only one uart is initialized: root@nanopineo:/boot# cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:16550A mmio:0x01C28000 irq:49 tx:11630 rx:0 RTS|DTR 1: uart:unknown port:00000000 irq:0 2: uart:unknown port:00000000 irq:0 3: uart:unknown port:00000000 irq:0 4: uart:unknown port:00000000 irq:0 5: uart:unknown port:00000000 irq:0 6: uart:unknown port:00000000 irq:0 7: uart:unknown port:00000000 irq:0 I'm not sure that only available serial is not the MicroUSB one. Can someone point me in direction where UARTS are defined now?

Has anyone managed to get video encoder working with the latest mainline kernel? I'm getting stuck trying to compile the cedar_ve kernel driver from https://github.com/uboborov/sunxi-cedar-mainline I have downloaded the kernel source using armbian-config and then built the sunxi-cedar-mainline kernel driver. However, I fail to load the driver due to version magic: When trying to force the load: But no dmesg message about magic check failure.

I have a 8811CU WiFi dongle that failed to work on my Nanopi Neo. When connecting using nmcli, I get this error "Error: Connection activation failed: (7) Secrets were required, but not provided." The device is correctly recognized and I can perform iw scan without issue. I tried with 6.1.7(edge) and 5.15.89(current) kernel, and install the driver from https://github.com/morrownr/8821cu-20210916, all end up with the exact same error. Here's the journal log where "nl80211: kernel reports: Authentication algorithm number required" error stands out. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4565] audit: op="connection-update" uuid="5723cd52-fc51-48bf-ab79-33a902d143b6" name="MySSID" args="802-11-wireless-security.psk" pid=5230 uid=1000 result="success" Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4781] device (wlx90deadbeef85): Activation: starting connection 'MySSID' (5723cd52-fc51-48bf-ab79-33a902d143b6) Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4795] audit: op="connection-activate" uuid="5723cd52-fc51-48bf-ab79-33a902d143b6" name="MySSID" pid=5230 uid=1000 result="success" Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4810] device (wlx90deadbeef85): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4871] device (wlx90deadbeef85): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4910] device (wlx90deadbeef85): Activation: (wifi) access point 'MySSID' has security, but secrets are required. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4913] device (wlx90deadbeef85): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5164] device (wlx90deadbeef85): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5201] device (wlx90deadbeef85): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5232] device (wlx90deadbeef85): Activation: (wifi) connection 'MySSID' has security, and secrets exist. No new secrets needed. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5236] Config: added 'ssid' value 'MySSID' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5237] Config: added 'scan_ssid' value '1' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5238] Config: added 'bgscan' value 'simple:30:-70:86400' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5241] Config: added 'key_mgmt' value 'SAE FT-SAE' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5243] Config: added 'auth_alg' value 'OPEN' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5244] Config: added 'psk' value '<hidden>' Feb 14 13:51:55 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Trying to associate with e8:9f:ff:00:ff:00 (SSID='MySSID' freq=2452 MHz) Feb 14 13:51:55 nanopi-neo wpa_supplicant[540]: nl80211: kernel reports: Authentication algorithm number required Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2452 ht_enabled=1 ch_offset=0 ch_width=20 MHz cf1=2452 cf2=0 Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.6389] device (wlx90deadbeef85): supplicant interface state: inactive -> associating Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.6391] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: inactive -> associating Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-ASSOC-REJECT status_code=53 Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=1 duration=10 reason=CONN_FAILED Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.8990] device (wlx90deadbeef85): supplicant interface state: associating -> disconnected Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.8993] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: associating -> disconnected Feb 14 13:52:07 nanopi-neo NetworkManager[513]: <info> [1676400727.9463] device (wlx90deadbeef85): supplicant interface state: disconnected -> scanning Feb 14 13:52:07 nanopi-neo NetworkManager[513]: <info> [1676400727.9467] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: disconnected -> scanning Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID" Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Trying to associate with ea:9f:ff:00:ff:00 (SSID='MySSID' freq=5220 MHz) Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: nl80211: kernel reports: Authentication algorithm number required Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5220 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5210 cf2=0 Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.5834] device (wlx90deadbeef85): supplicant interface state: scanning -> associating Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.5837] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: scanning -> associating Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-ASSOC-REJECT status_code=53 Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=2 duration=20 reason=CONN_FAILED Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.6529] device (wlx90deadbeef85): supplicant interface state: associating -> disconnected Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.6532] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: associating -> disconnected Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3324] device (wlx90deadbeef85): Activation: (wifi) association took too long Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3328] device (wlx90deadbeef85): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3516] device (wlx90deadbeef85): Activation: (wifi) asking for new secrets Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3633] device (wlx90deadbeef85): no secrets: No agents were available for this request. Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3636] device (wlx90deadbeef85): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3755] device (wlx90deadbeef85): Activation: failed for connection 'MySSID' Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3788] device (wlx90deadbeef85): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 14 13:52:30 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Reject scan trigger since one is already pending Feb 14 13:52:32 nanopi-neo NetworkManager[513]: <info> [1676400752.3693] device (wlx90deadbeef85): supplicant interface state: disconnected -> inactive Feb 14 13:52:32 nanopi-neo NetworkManager[513]: <info> [1676400752.3697] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: disconnected -> inactive

Hi all, I am new to armbian, it is a wonderful project. I just have a nanopi neo core board, fellow the guide doc, it can be boot from the SD card, but the board has internal 8GB emmc. how can I install the armbian into it, so it can boot from emmc without using SD card? Thanks!

Hello. I have several new NanoPi-NEO Core devices. OS FriendlyELEC (Ubuntu 16.04.2) was already installed on them, and it does not allow me to boot from the SD card. There is an image created by a script emmc-backup.sh How do I deploy this image?

On my NanoPi Neo Core, the flash has the following partitions: Most of the drives I've encountered have the starting sector set as 2048, while this one has 49152. I'm assuming that U-Boot reside before the 49152th sector. How can I see what is below 49152th sector in the partition table?

Hi! I need to use the UART1 port on my NanoPi NEO. This usually means just adding "uart1" to the `overlays` in `/boot/armbianEnv.txt`. What I would like to do is build a custom image that already has the overlay activated by default. I read the following documentations: - https://docs.armbian.com/User-Guide_Armbian_overlays/ - https://docs.armbian.com/Developer-Guide_User-Configurations/ But couldn't find anything about it. At first I tried to define the `DEFAULT_OVERLAYS` env var in `userpatches/config-example.conf` since I noticed it was defined in the configuration for the board, but it didn't work. I manage to make it work by modifying the `armbianEnv.txt` file within the `customize-image.sh` script, using some sed magic. For exemple: RELEASE=$1 LINUXFAMILY=$2 BOARD=$3 BUILD_DESKTOP=$4 Main() { echo "Release: $RELEASE" case $RELEASE in jammy) DisplayArmbianBootConf ;; esac } # Main DisplayArmbianBootConf() { echo "Adding UART1 overlay" sed -i '/overlays/s/$/ uart1/' /boot/armbianEnv.txt echo "armbianEnv.txt: " cat /boot/armbianEnv.txt echo "UART1 added." } Now this works fine, but it feels a bit "hackish". So I was wondering, is there a better way to achieve this ? This I miss an env var, conf file or specific configuration which would allow me to append overlays to the default overlay of the board ? Thanks,