Search the Community
Showing results for tags 'nanopineo'.
-
hi guys, using Armbian 23.02.2 Buster with Linux 5.15.93-sunxi on a NanoPi Neo Core LTS. I configured cron to do a daily reboot at 00:30. Every 10-20 days the system is becoming unresponsive unless I do a power cycle. Where should I begin to investigate this issue? Thank you
-
Hi all I have a project need high uart baudrate, > 2Mbit/S, how can I get this work, seems the stty not work correctly
-
I have a NanoPi Neo V1.4 running Armbian 23.8.1 bullseye with kernel nanopineo 6.1.63-current-sunxi. Now, that I got my micro-USB port working for a SD card holder, I want to programmatically backup my boot SD on a regular base to another SD. Yes, it works by a full dd-copy. but this is quite time consuming and I want to skip some directories while backup, which does not work with dd. The idea: Take a new SD (same model as source SD) Create a new partition table and a primary partition 1 with fully equal parameters as my source SD Format partition 1 with ext4 and mount to /mnt rsync all files (exclude some directories as e.g. /var/log) from source / to target / (which is /mnt/) Use this SD in case of a problem with the source SD as new boot SD In /boot/armbianEnv.txt i have rootdev=/dev/mmcblk0p1. No UUID used. But, it just does not boot. The LED's of my NanoPi stay on with no blinking at all. Nothing is written to /var/log. Unfortunately I cannot connect a console to the NanoPi to see the boot messages. Only SSH at this time. What is missing on the new SD? I assume something with the U-Boot bootloader? Can anybody help me? What is missing and needs to be copied to the SD? I assume to the bytes 512-8192 just in front of partition 1 and after the partition table. Even that a full dd works, I'd like to know how to do that manually. Thanks a lot for help 🙂
-
I'm powering my NanoPi Neo V1.4 1801 through the USB type A port beside the Ethernet RJ45. I'm using Armbian 23.11.1 bookworm with kernel Linux nanopineo 6.1.63-current-sunxi. Now I want to enable the Micro-USB port (usually used for powering) to act as an USB host so that I can plugin an USB-stick. I found very few instructions for e.g. Orange Pi. There the device tree needs to be changed for usb@1c19000 and usb0-vbus. Also in armbianEnv.txt the line param_usb0_mode=0 should be added. But none of the instructions work for my NanoPi Neo. In the schematics, a SY6280 is connected via GPIOL2/USB0-DRVVBUS to the H3 cpu. This should theoretically allow the NanoPi Neo to apply the 5V internally to the Micro-USB port. But how? Can please anybody post complete instructions how to enable the Micro-USB Port as an fully working USB host port? PS: The tag for this post is wrong, but I could not add another one...
-
Hello wonderful people! I am having trouble getting my SSD1351 1.5" RGB SPI OLED working with my NanoPi Neo v1.4 running armbian 23.11.1 with kernel 6.1.63.. Since the removal of fbtft_device from the linux kernel I have had a really hard time getting any screen to work with any of my SBC's (except RaspberryPi using the fbcp_ili9341 library) I have tried converting fbcp_ili9341 for use with the NanoPi but I keep getting "Failed to load VideoCore kernel Mailbox"... so I gave up on that lol.. Then I learned dtoverlay was a thing and after days of searching around I eventually found a .dts file for the SSD1351 here (https://github.com/raspberrypi/linux/blob/rpi-6.1.y/arch/arm/boot/dts/overlays/ssd1351-spi-overlay.dts) but it is designed for the RaspberryPi! and i have no idea how to modify it for use with the NanoPi Neo.. Any modifications I make to the file do nothing helpful! The pins I'm using are as follows: VCC----------3.3V------17 GND--------GND------20 CS------------24--------24 (PC3) RESET------12---------12 (PA6) DC/RS------18---------18 (PG9) MOSI-------19---------19 (PC0) SCK---------23---------23 (PC2) Is anyone able to help me get this screen working? Thank you so much EDIT: fixed typo
-
(sorry for my english) hello!! My problem: can't compile image. I follow step-to-step in official documentation, but it failed in result. And I don't understand why, please help. I do it in Virtual box; Linux version 6.2.0-33-generic (buildd@lcy02-amd64-073) (x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 10:33:52 UTC 2 Device: nanopi neo air https://pastebin.com/xBrAv8AL - i put here my logs
-
The 1-bay NAS kit v1.2 has an RTC with option to add CR2032 button cell to keep HW time when system is shut down. But running `timedatectl` when device is booted in offline mode shows RTC is set to 1970-01-01 00:00:00 which defeats the purpose of having the option of CR2032. And yes, the button cell have juice; I've bought it a week ago and tested it before putting it in the kit.
-
I have board which has 2 slaves on the SPI bus, requiring ce0 and ce1. My system: Armbian 23.8.1 Bookworm with Linux 6.1.47-current-sunxi I applied overlays: spi-add-cs1 and spi-spidev, there's an spi in the system. As soon as I apply spi-double-spidev-bus.dts, the spi disappears. How to make two cs? As soon as I apply spi-double-spidev-bus.dts, the spi disappears. Also, as I assume there is a problem with CS1, I reassign it with my overlay: CS is reassigned in the system, but the spi device polls once. When polling again, errors occur. When I manually set the cs there are no re-polling errors. I use "spi-device" - accessing the SPI serial bus using Node.js on Linux boards https://github.com/fivdi/spi-device On another board, the author's "spi-device" SPI polling works without problems https://github.com/fivdi/spi-device/issues/27 Please help to make sense of these two issues.
-
Hi all, I have a Nano Pi Neo Core board with Armbian 5.15.93, and I want to upgrade it to 6.1. I ran the "armbian-config", and selected the new version linux-image-edge-sunxi=23.02.2 based on kernel 6.1.11-sunxi. After the update the board does not boot anymore. Further investigation shows that the original "/boot" folder was looking like this: And after the upgrade, I get this: A "uInitrd" symlink is broken, the "uInitrd-6.1.11-sunxi" file is missing, and obviously, the board cannot boot. Question N1: where can I get the proper "uInitrd-6.1.11-sunxi" file? I cannot find it online, and I think, it can only be built from a source? As a temporary workaround, I installed the image from https://www.armbian.com/nanopi-neo/ into another board, and copied the "uInitrd-6.1.30-sunxi" file from that board manually to the first one. A sort of hacky way, but the board was able to boot. But I have another remote board, which I have no physical access to, so I cannot boot it from SD card and do the same trick. Question N2: after the kernel upgrade and fixing a missing file, the board can boot. But there are some issues: - "/etc/os-release" shows "Ubuntu 20.04.6 Focal fossa". I suppose, only the kernel was updated but other files were intact? Commands "apt update" and "apt upgrade" did not help. - "/etc/armbian-release" is now missing. - "/etc/apt/sources.list" and "/etc/apt/sources.list.d/armbian.list" are still pointing to "focal" (is it enough just to change to "jammy"?) - "armbian-config" does not show any kernels anymore and does not allow upgrades or downgrades What is the right way to update Ubuntu to the latest one as well? Thanks and best regards
