Search the Community

Hi, I'm using Nanopi DUO2 for few IoT projects. Using the microUSB serial console connection is very convenient and fast method to manage this SBC. Unfortunately with latest version of Armbian (tested with v24.11.0) it not working any more. Version 23.11.1 works fine out from the box, but after sudo apt update && sudo apt full-upgrade the microUSB serial console is not available. Any suggestion how to switch it back will be very appreciated. Slawek

We have a project based on FriendlArm's NanoPi Neo Air board. Currently the devices are running Armbian 18.04 LTS loaded from emmc. We are looking for a way to update the devices "offline" / with no user interaction. We can upload data to the devices via FTP and also can execute shell scripts. We can not easily access the on-board micro SD slot but have an external SD-Slot / USB-A Port with lots of free memory on each device. Any hints or explanations are very welcome!

Hi all! I may need some pointers. I'm using a 2.4" LCD at spi1 which works as /dev/fb0 on armbian bookworm (6.1.63) Meanwhile I've learned frambuffer is deprecated and to be replaced by drm., but ... - I could not find enough details to understand the drm architecture in general - there is a linux/drivers/gpu/drm/tiny/ili9341.c how is that used at all? - How to use drm in armbian? For my case any acceleration is not necessary (and likely not possible even if the H3 has Mali Hardware) but I want to avoid further changes if /fbX is really gone. btw. I want to add touch with shared SPI soon, work in progress. Of course that should also work then later on with drm - I'm thinking of any possible conflicts inside the Device Tree which then may need further tweaking. It's all nice but sooooooo time consuming... T.

Hi, I am working on enabling crust support in Armbian. A draft version of pull request is here. I have made the changes for the same. With my changes, crust compiles as part of building the image and gets bundled in u-boot. I can also see the following message from U-boot U-Boot 2022.10-armbian (Jun 14 2023 - 13:49:59 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 61 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Starting SCP... Net: SCP/INF: Crust v0.5.10000 eth0: ethernet@1c30000 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 and the following message is present in dmesg output [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.0 So I know that crust is getting loaded. I am not sure how I can test if its working as its supposed to be. I can use some guidance for the same. Thanks in advanced

Hi there! I've recently configured the ov5640 camera overlay and was able to capture videos either with mjpg-streamer of ffmpeg. Now on 6.1.34 both causes now a kernel oops. From the stack trace it looks like it happens inside v4l2 "media_pad_remote_pad_first" Unable to handle kernel NULL pointer dereference at virtual address 00000030 ... ... PC is at media_pad_remote_pad_first+0xa/0x58 I don't think v4l2 is the root cause because this may mean it fails alle the time which is unlikely. Looks like a null ptr gets passed in into media_pad_remote_pad_first ffmpeg used like this, but other parameters all resulting in the kernel oops at the same location. sudo media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:UYVY8_2X8/1280x720@1/15]' ffmpeg -hwaccel_device 0 -framerate 15 -f v4l2 -video_size 1280x720 -i /dev/video1 -r 15 -pix_fmt yuv420p -b:v 1280k test1280-15.mp4 WORKS on 4.14.x (was video0 and media0 here) mjpeg streamer testing ./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1920x1080 -f 5 -q 30 -n " -o "./output_http.so -w ./www" Possible root causes: 1) Something is now wrong inside my DT overlay due to kernel changes? I'm thinking about the i2c and spi relationships 2) Something is broken inside ov5640 driver 3) Something is broken inside v4l Maybe someone can provide some hints to point me in the right direction for further investigation? Attached are the dmesg output and overlay source. Thilo mjpg-streamer with camera overlay oops 06.08.2023 output.txt sun8i-h3-ov5640.dts

Hi there 👋 I've tried the CSC edge images Armbian_23.02.0-trunk_Nanopiduo2_lunar_edge_6.1.8.img and Armbian_23.02.0-trunk_Nanopiduo2_sid_edge_6.1.8.img and the machine does not want to boot. Is there a more stable image somewhere? FriendlyCore boots on this board. Thanks. U-Boot SPL 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 60 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 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@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 4077 bytes read in 2 ms (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 234 bytes read in 2 ms (114.3 KiB/s) 18804544 bytes read in 780 ms (23 MiB/s) 8706400 bytes read in 363 ms (22.9 MiB/s) Found mainline kernel configuration Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' Kernel image @ 0x42000000 [ 0x000000 - 0x84d960 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 18804480 Bytes = 17.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device sun8i_emac_eth_start: Timeout missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-81-e1-0b-9c-e0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default sun8i_emac_eth_start: Timeout Config file not found sun8i_emac_eth_start: Timeout sun8i_emac_eth_start: Timeout

Hi there 👋 I'm using a NanoPi Duo2 with Armbian 21.08.1 Bullseye and Linux jenkins-agent-arm32 5.15.93-sunxi #23.02.2 SMP Fri Feb 17 23:49:46 UTC 2023 armv7l GNU/Linux I want to use an SPI screen on it, but I don't know which library to use to handle the GPIO... I've tested quite a few and none of them seem to work. I have enabled SPI and I2C in `armbian-config` and `sudo i2cdetect -y 0` works (even if nothing is found), but what is the next step? sudo i2cdetect -y 0 [sudo] password for poddingue: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- poddingue@jenkins-agent-arm32:~$ ls /dev/i2c* /dev/i2c-0 What library/tool should I install to get the `gpio` command for example? Thanks.

Hello all. I have a Nanopi due2 with Armbian. I've enabled my SPI in armbianEnv.txt file and with: overlays=spi-add-cs1 spi-spidev usbhost0 usbhost2 usbhost3 param_spidev_spi_bus=1 param_spidev_spi_cs=1 but when I try to use "/dev/spidev1.1", CS pin is active high by default not active low. how can I change it to active low.