Jump to content

Search the Community

Showing results for tags 'nanopineo3'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
    • Orange Pi 5
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 21 results

  1. Hi! Have limited knowledge in linux, all self learned so bear with me if I sometimes sound like an i**ot in my wording. I have used lots of different Raspberry pi's but since they are near to impossible to get your hands on I figured I'd try out some of the alternate boards. Got myself a nanoPiNeo2, orangePiZero2 and an orangePiPC2 just for the fun of it. I have tried this on the nanoPi and the opiZero2 and run into the same problems, havent even opened the opiPC2 yet but I suspect it will be the same problem on that board. Downloaded armbian for each separate board (instead of debian) because I want to use the same system on all my devices so its easier for me to learn. Got everything working as I wanted (just making a simple pihole to give away as xmas presents) but when it came to backing up, I ran into a wall. With the raspberries I use a script called image-backup located on the raspberrypi forums (awesome script made by RonR) but that obv wont work here since the rpi uses a fat32 as a boot partition. There is a flag you can run when using the script called "ubuntu", but it didn't work. Ok then, lets use win32 imager instead to just rip the card, its only 8gb, not a huge deal, I can probably even shrink the size with e2fsck and parted (as I understand it armbian autoexpands the card on mount anyway?) but I get an i/o error in win32 after a few seconds, this might actually be my computer, going to try it on another computer in a day or two, (I only have one). I tried other programs too, but none seems to work so I decided to try to dd from the mounted card. The backup directory is on a mounted cif on a windows computer if that has to do with anything? sudo dd if=/dev/mmcblk0 of=/path/to/backup/ddbackup.img bs=4M conv=sync status=progress That didn't work, I get (the numbers are bigger I just randomly took a number, the important thing is the +1 that gets added to the "normal" number in "records out", I suspect that is the boot sector?) 15874+1 records in 15875+0 records out I figured it had to do with the card being mounted so I made ANOTHER identical install on another sdcard and inserted the original sd in the usb with a card reader and doing the dd from /dev/sda instead (without it being mounted), but I get the exact same thing and when trying to flash the image and use that card, the board just never comes to life. Network port keeps flashing but nothing else. My plan was to make a backup.img file, mount that with a loop and shrink the "partition" with shrink2fs and parted. But even trying to mount the created image files gives me errors about bad superblocks etc, probably because of what I described above. Running e2fsck also gives me a TON of errors. I have tried for DAYS, searching all over the internet (figuring things out for myself is the best way to learn) but I get nowhere. Is there a simple solution to this? The only time I actually got a working .img file is if I dd a blank img file first from /dev/zero and set the file to become a size (with bs and count) where all data can fit and then rsync / into it. I can mount it with a loop (losetup) and access the files, but naturally it wont boot on the board (if I flash it to an sd card) since I read that the boot sector is "out of bonds" or whatever its called. Same error, just flashing network port. I'm at a complete loss here, I REALLY want to have an img file that the xmas gift holders get that they can just flash onto an sdcard in case of a breakdown of the software somehow. Please have pity on my soul!
  2. hi everyone How can I activate the SPI in the nanopi neo3 board?
  3. Lets say I wish to creat three kernels with different timer settings like 100Hz/250Hz/1000Hz. The name of the generated SDcatd image is always the same which is not helpful. When I want to use them later as well for a multiboot scenario, so swtchable kernels, I need as well different names, so it is not only to rename the image files. USing Menuconfig, I could normally put a localization extension to it...when I do this, the image creation process fails as the system looking into wrong folder names. So, is there an alrernative path ? Or is this a bug ?
  4. Sorry to ask such a beginner question, but I am still learning about Armbian... When I install debian Kernels from Kernel.org myself, I find this in my source-folder of the distro which I created when unzip/tar the Kernel. But as Armbian does this in the backround for me...where is this folder ? RTLA is a new tool to use osnoise tracer and needs to be compiled from source. https://lwn.net/Articles/869563/ THX
  5. Hi all, For the past few days, I've been trying to SSH into my NanoPi Neo3, but I keep getting the "Incorrect password" error. My set up: Load a supported Armbian image onto a 16GB, class 10 micro SD card using balenaEtcher. https://armbian.hosthatch.com/archive/nanopineo3/archive/Armbian_21.08.1_Nanopineo3_focal_current_5.10.60.img.xz Connect the NanoPi to my laptop, with a shared internet connection (Please note: It connects just fine. I've tried with a manual and automatic DHCP connection, and in both cases, been able to obtain the IP address). Insert the micro SD card. Plug in the power cord, and wait for the blinking yellow light. SSH into the root user, using "ssh root@XXX.XXX.XXX.XXX" (I've also tried using PuTTY). After all that, I get prompted for a password. I enter in the password, but then I get the "Incorrect password" error. I've tried "1234", "fa", "NULL", and a range of other passwords. Also note, I've tried this process on a Windows, Mac, and Linux computer. I really appreciate any help or ideas! Thanks, Chandler
  6. Dear maintainers, Guess some device tree issues with neo3 got me into this mess, since rk3328-nanopi-neo3-rev02.dtb is missnig. Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 7 ms (444.3 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 428 bytes read in 6 ms (69.3 KiB/s) 12514638 bytes read in 556 ms (21.5 MiB/s) 30083584 bytes read in 1326 ms (21.6 MiB/s) Failed to load '/boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kind regards, Dennis
  7. Dear all, I occasionally have a full /var/log at startup on various boards, probably because the logs are not rotated /vaccuumd at boot (we had a thread about this in the old opi1 forum). The rotating /vaccuum is currently done every 15 minutes, so I figured why not do it directly at boot as well? For this purpose I updated /etc/cron.d/armbian-truncate-logs with an extra @reboot line: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */15 * * * * root /usr/lib/armbian/armbian-truncate-logs @reboot root /usr/lib/armbian/armbian-truncate-logs I rebooted several times, and didn't get a full /var/log anymore. All subsequent problems like failing networking when filesystem full also vanished;-) Kind regards, Dennis
  8. Hello People. First of all, thank you to all the people that puts work and time into this project. It's my first time posting here. I've been trying to solve this problem by myself since this board it's unsupported now, but I had no luck. The thing it's, I can't get the linux to recognize properly the PlutoSDR, I get this errors in dmesg. [ 19.885514] usb 4-1: new high-speed USB device number 6 using xhci-hcd [ 20.035134] usb 4-1: Dual-Role OTG device on non-HNP port [ 20.035310] usb 4-1: set a_alt_hnp_support failed: -32 [ 20.161463] usb 4-1: new high-speed USB device number 7 using xhci-hcd [ 20.311139] usb 4-1: Dual-Role OTG device on non-HNP port [ 20.311316] usb 4-1: set a_alt_hnp_support failed: -32 [ 20.312182] usb usb4-port1: attempt power cycle [ 20.721465] usb 4-1: new high-speed USB device number 8 using xhci-hcd [ 20.743390] usb 4-1: Dual-Role OTG device on non-HNP port [ 20.743570] usb 4-1: set a_alt_hnp_support failed: -32 [ 20.869463] usb 4-1: new high-speed USB device number 9 using xhci-hcd [ 20.891387] usb 4-1: Dual-Role OTG device on non-HNP port [ 20.891565] usb 4-1: set a_alt_hnp_support failed: -32 [ 20.892491] usb usb4-port1: unable to enumerate USB device This only happens with pluto, the board recognize properly other USB devices. I've try compiling other kernel, forcing DWC3 driver to be HOST only, but didn't change anything (and broke the LAN port 😧 ). The pluto has an OTG port but, for my understanding, should be in device mode because I'm using an standard micro USB cable. I haven't try modifying the device tree since I don't understand really well all the options (I've used rk3328-nanopi-neo3-rev02.dtb and rk3328-nanopi-r2-rev20.dtb with same results) I tested the compiled versions 20.05.9 - Linux 5.4.51, 20.08 - Linux 5.7.15 and 21.08.1 - Linux 5.13.12. Also tried upgrading (and fixing the dtb problem when upgrading) but also didn't help. Hope someone can help me, I can provide more information if needed. Thank you!
  9. Dear community, dear @Igor (as maintainer of NEO3 CSC), thanks a lot for the NEO3 support. This board ran rock solid for me approx. two years straight – much more stable than my other SBCs running Armbian (due to various reasons, no offense :)). However, the board failed to boot with "ERROR: Did not find a cmdline Flattened Device Tree". It appears that ``rk3328-nanopi-neo3-rev02.dtb`` went missing. This must have happened when upgrading the package ``linux-dtb-current-rockchip64`` from 21.08.2 to 22.02.1. As a workaround, it helps to (download the CSC image for the board again, get the file out of the image,) place the file in ``/boot`` and set ``fdtfile=../rk3328-nanopi-neo3-rev02.dtb`` in ``/boot/armbianEnv.txt`` I think it's a pity that support for this board broke, which works so well with Armbian. Any chance we can get the dtb back into the package? Cheers, Lukas
  10. Hi Armbians :) Armbian's discontinued support of the NanoPi Neo3 board, hit me very hard. I have operated multiple of these SBCs with Armbian very stable, in different DCs for a long time. Because of the defunctional kernel under Armbian, I was forced to look around for alternatives and only came across Manjaro, DietPi and Friendlyarm published by FriendlyElec themself. Unfortunately I was not happy with Manjaro and Friendlyarm. Dietpi, on the other hand, seems to be doing quite well till now. And most importantly, it doesn't seem to have the kernel/ reboot problem that affected Armbian. But how can that be if it's based on Armbian? Can someone explain that to me?
  11. Because I have updated to Armbian 22.02 with the linux 5.15.25 kernel and I am using the rk3328-nanopi-r2-rev00 device tree, I thought I should share what I have discovered. 1/ I had trouble setting up a one-wire device (ds18b20 temperature sensor). I think the w1-gpio pin assigned in the supplied overlay is messing up access of the SD card. I found some helpful information from this post: https://forum.pine64.org/showthread.php ... #pid100639 I copied the overlay code, modified it to use GPIO2_A2 (pin 7 on the 26pin header), compiled it and copied the new dtbo file to "/boot/overlay-user/" . Added the "user_overlays=rockchip-w1-gpio" line to "/boot/armbianEnv.txt" and rebooted. Success. I was able to read the ds18b20. (I have since discovered the utility "armbian-add-overlay" would have done the compile, copy and edit steps all at once.) The steps I took: Overlay filename: rockchip-w1-gpio.dts /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/"; __overlay__ { w1: onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; gpios = <&gpio2 2 0>; status = "okay"; }; }; }; }; You will probably need to install the device-tree-compiler. sudo apt install device-tree-compiler Compile the overlay: dtc -I dts -O dtb -o rockchip-w1-gpio.dtbo rockchip-w1-gpio.dts Copy the compiled overlay: sudo cp rockchip-w1-gpio.dtbo /boot/overlay-user/ Add the "user_overlays=rockchip-w1-gpio" line (without quotes) to "/boot/armbianEnv.txt" and reboot. I have learnt a bit more about "Device Trees" and "dt overlays" (I still don't understand how it all works), it turns out overlays can be used to change (somewhat) what has been configured in the Device Tree being used. So here are some more overlays that I have come up with after grabbing snippets from here and there. 2/ I have read of people editing and recompiling the device tree dtb file to enable the USB-OTG to be used as a "normal" USB port. I have created an overlay that changes the dr_mode of the USB-OTG from "otg" to "host". Overlay filename: rockchip-usb-otg.dts /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328-usb\0rockchip,rk3066-usb\0snps,dwc2"; fragment@0 { target-path = "/usb@ff580000"; __overlay__ { dr_mode = "host"; }; }; }; Compile: dtc -@ -I dts -O dtb -o rockchip-usb-otg.dtbo rockchip-usb-otg.dts Copy the compiled overlay to /boot/overlay-user/ and add "rockchip-usb-otg" (without quotes) to /boot/armbianEnv.txt on the "user_overlays=" line. After a reboot, check by plugging a "9-hole To Dual USB2.0 Female Header Adapter Cable" (or similar) onto the USB header and plug a couple of flash drives in to the USB sockets. Type lsblk and the resulting output should show /dev/sda and /dev/sdb. 3/ The rk3328-nanopi-r2.dtb doesn't enable "pwm". PWM is handy for controlling the speed of a cooling fan. There is a header on the board for just a thing. (2Pin JST ZH 1.5mm Connector for 5V Fan) Overlay filename: rockchip-pwm-gpio.dts /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/pwm@ff1b0020"; __overlay__ { status = "okay"; }; }; }; Compile, copy and edit as above and reboot. ls /sys/class/pwm/ This should show "pwmchip0" is available. To be able to control "PWM" from userspace, a couple of other things need to be in place. The user needs to be a member of the "gpio" group and some udev rules need to be in place. filename: 50-pwm.rules SUBSYSTEM=="pwm*", PROGRAM="/bin/sh -c '\ chown -R root:gpio /sys/class/pwm && chmod -R 770 /sys/class/pwm;\ chown -R root:gpio /sys/devices/platform/*.pwm/pwm/pwmchip* && chmod -R 770 /sys/devices/platform/*.pwm/pwm/pwmchip*\ '" Copy the 50-pwm.rules file to:- "/etc/udev/rules.d/" (without the quotes) Reload the udev rules. udevadm control --reload-rules ; udevadm trigger Here is a shell script to setup the PWM. Values for period and duty-cycle width may be changed as required. filename: setpwm.sh #! /usr/bin/bash # activate the PWM. echo 0 > /sys/class/pwm/pwmchip0/export #Wait for export to settle sleep 2 # set period to 10ms echo 10000000 > /sys/class/pwm/pwmchip0/pwm0/period # set normal polarity. needs to be reset explicitly. Bug? echo "inversed" > /sys/class/pwm/pwmchip0/pwm0/polarity echo "normal" > /sys/class/pwm/pwmchip0/pwm0/polarity # enable the PWM echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable # set duty cycle to 1ms echo 1000000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle 4/ The NanoPi NEO3 has a push button. From documentation I have found, indicates that it is supposedly a reset button, but it seems to have no effect. This overlay renames the button and sets the function to "Power Off" (or "Reset"). I wanted it to shutdown the NEO3, so I have configured it as "KEY_POWER" (0x74). Change line 15 to "linux,code = <0x198>;" for a Reset button. Overlay filename: rockchip-power-button.dts /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/"; __overlay__ { gpio-keys { button@0 { label = "k1_button"; linux,code = <0x74>; //0x198 = KEY_RESTART, 0x74 = KEY_POWER }; }; }; }; }; Compile, copy and edit as above and reboot. Press the button and the NEO3 should shutdown (or restart). 5/ Apparently the NanoPi R2 has two additional LEDS, ("lan-led" and "wan-led") that the NEO3 does not. The rk3328-nanopi-r2.dtb assigns these LEDS to GPIO pins that are on the 26pin header that would be used as normal GPIO or used by I2S and SPI on the NEO3. To make these pins available for use, I have made an overlay that re-assigns the "lan-led" and "wan-led" to gpios that (according to the NEO3 schematic) are not used on the NEO3. Overlay filename: rockchip-leds.dts /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/"; __overlay__ { gpio-leds { led@2 { gpios = <&gpio0 5 0>; }; led@3 { gpios = <&gpio0 6 0>; }; }; }; }; }; Compile, copy and edit as above and reboot. Check by using "gpioinfo" gpioinfo gpiochip0 The output will show that the "lan-led" and "wan-led" are now assigned to gpiochip0, lines 5 and 6 respectively. I believe that using these simple Device Tree Overlays, has made my NanoPi NEO3 perform as it was intended. I have found one flaw. After upgrading to the latest armbian kernel, 20.02, two GPIO pins will not change state. They are GPIO2_B7/I2S1_MCLK (gpiochip2, 15) and GPIO3_B0/SPI_CSN0 (gpiochip3, 8). Something is loaded during boot that sets them both High (I have LEDs connected and can see when they go High). Using the commands "gpioset gpiochip2 15=0" and "gpioset gpiochip3 8=0" does not turn the LEDs off. There are no errors or warnings when using the commands and "gpioinfo" shows that the pins are "input active-high". This effect did not happen using the previous kernel and happens late in the boot process. I am ruling out any Device Tree problems as the Green Status LED is flashing happily well before either pin goes high. Regards, John
  12. I manged to get the USB OTG headers working on the NEO3 by modifying the NanoPi R2S DTB that it is currently using. 2 changes were needed: - Replaced all usb2 references to usb0 - Changed dr_mode for usb@ff580000 from otg to peripheral Modified DTB file attached if anyone else wants to give this a try or has a need for OTG on the NEO3 rk3328-nanopi-neo3-rev00.dtb
  13. Hello, When I comment device via USB 3.0 I see it: ender3@ender3:~$ lsusb Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 1d50:614e OpenMoko, Inc. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub However with pins GND, DP1, DM1, +5V Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub See Layout / USB2.0 - https://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO3 Any ideas how I should activate these pins? Want to connect 3d printer and endoscope OTG camera that works with RPi, so should be matter of drivers. Testing on printer now. Also, if it is not supported, may I use simple USB 2.0 hub to connect to USB 3.0 port WiFI card, 3d printer and OTG endoscope camera? Prefer to activate these pins if I may to choose : )
  14. Hi Armbians I have a problem with one of my NanoPi Neo 3 boards and dropped RX packages on eth0. From multiple Neo 3`s I have running, this is the only one having this issue. But its also the only one with 1GB of RAM. All other boards have 2GB of RAM. But this should not matter I think. Output ifconfig: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet XXXXXXXXXX netmask 255.XXXXXXX broadcast XXXXXXXXXX ether XXXXXXXXXXX txqueuelen 20000 (Ethernet) RX packets 140166777 bytes 110091299296 (102.5 GiB) RX errors 0 dropped 3686 overruns 0 frame 0 TX packets 127249076 bytes 110451144546 (102.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 39 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 20000 (Lokale Schleife) RX packets 96 bytes 7103 (6.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 96 bytes 7103 (6.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Output "ethtool -S eth0": Any secure way to fix this issue?
  15. I have a nanopi neo3 rk3328. I would like to modify the i2s(1) at start. I tried to modify /boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb but nothing change. Which is the right dtb file its load at start? Thank you.
  16. I got the following error message when I try to install firmware-misc-nonfree_20190114-2_all.deb from the upstream debian repository. ... Get:1 http://deb.debian.org/debian buster/non-free arm64 firmware-misc-nonfree all 20190114-2 [3,338 kB] Fetched 3,338 kB in 1s (4,022 kB/s) Selecting previously unselected package firmware-misc-nonfree. (Reading database ... 77206 files and directories currently installed.) Preparing to unpack .../firmware-misc-nonfree_20190114-2_all.deb ... Unpacking firmware-misc-nonfree (20190114-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-misc-nonfree_20190114-2_all.deb (--unpack): trying to overwrite '/lib/firmware/dvb-fe-xc5000-1.6.114.fw', which is also in package armbian-firmware 21.02.2 d ... So it seems, there is the same firmware package in different packages...but idea, because armbian-firmware 21.02.2 miss the mt7* firmware, which is required to use the wifi expansion module of the nanopi neo3. So, I think the pakcage mantainer should resolve this issue.
  17. Hi I try ro install and use Armbian on my NanoPi NEO 3. But when I do a first boot, I stuck at Generate Locale step. How can I fix it? Thank you very much. .
  18. hi, I am running newest armbian for NEO3. I've noticed that when I issue poweroff command armbian shuts down correctly, but the CPU (with heatsink) remains hot. I left my board for 2 days in poweroff state and it remained 'warm' all the time. Is there something that can be done to put CPU to sleep before shutting down system (or some low power state) ?
  19. HI I just bought 2 neo3 and started with Armbian and the MAC address is the same. But using the official image is a different MAC address.How can I use Armbian so that neo3 has the correct unique MAC address? I use cmd xxd / sys / bus / nvmem / devices / rockchip-efuse0 / nvmem I get the same value.
  20. I'm trying to make boot a NanoPi Neo3 from SSD connected through USB. - I installed armbian Buster 5.8.6 downloaded from armbian.com - Next, I tried with and without apt update - connected an external SSD through the USB port and and a USB 3.0->SATA box - Executed nand-sata-install and selected the option to boot from external SSD - The system prepared the SSD, copied filesystem, modified boot (and I verified that in armbianExt.txt it set the UUID of the external disk) - rebooted ... And nothing I've observed that the system not always detects the external SSD. I must unplug and plug it to be recognized (as /dev/sda btw). Perhaps this is part of the problem. Does anyone have any idea on what happens and how can I solve it?
  21. /usr/bin/brcm_patchram_plus/rk3399 hogs 100% CPU until rk3399-bluetooth.service is stopped and disabled. The NanoPi Neo3 does not have bluetooth.
×
×
  • Create New...