Jump to content

Search the Community

Showing results for tags 'nanopifire3'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • 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


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 8 results

  1. I am trying to compile the full OS image (incl. kernel and u-boot) for nanopifire3 target but fail every time. I am following the provided build instructions. I have tried compiling on multiple machines, but the one I am using has 8 cores and 12gb RAM. I have tried in an Ubuntu 22.04 LXC container, Ubuntu 22.04 in a VM, and the the docker container provided by Armbian. My kernel has the binfmt_misc module loaded (verified with lsmod), no spaces are present in build path, and I have tried both root user and sudo as a regular user. I have also checked the similar issues on the armbian forum Please forgive me if anything is incorrectly formatted or so, I have tried to provide as much detail as I can. If I didn't provide something, please tell me and I will do my best to resolve the issue. Additionally, I know this board is CSC status and not supported. I am not asking for support with anything in the OS, I am simply trying to build a new kernel for the device. Here are the exact steps required to produce the issue. 1. Install Ubuntu 22.04 on bare metal/VM and install git from apt 2. Run git clone --depth 1 https://github.com/armbian/build; cd build; ./compile.sh 3. Select "Full OS build for flashing" 4. Select "Show a kernel configuration menu before compiling" (but I never got this far so it probably doesn't matter) 5. Show CSC and pick nanopifire3 from list 6. Pick bullseye (I believe all of them error the same but my target is bullseye) 7. Pick image with server interface and standard/minimal image (both error same) 8. The error shown below will be produced when compiling u-boot. Error log from console [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-s5p6818 ] [ o.k. ] * [l][c] script-loading.patch [ o.k. ] * [l][c] update-nanopi-fire3-support.patch HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf # # configuration written to .config # scripts/kconfig/conf --silentoldconfig Kconfig # # configuration written to .config # CHK include/config.h UPD include/config.h GEN include/autoconf.mk GEN include/autoconf.mk.dep CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h UPD include/generated/timestamp_autogenerated.h UPD include/config/uboot.release CFG u-boot.cfg CHK include/generated/version_autogenerated.h UPD include/generated/version_autogenerated.h CC lib/asm-offsets.s CC arch/arm/lib/asm-offsets.s CHK include/generated/generic-asm-offsets.h CHK include/generated/asm-offsets.h UPD include/generated/generic-asm-offsets.h UPD include/generated/asm-offsets.h HOSTCC tools/bmp_logo HOSTCC tools/img2srec HOSTCC tools/mkenvimage.o HOSTCC tools/os_support.o WRAP tools/lib/crc32.c HOSTCC tools/aisimage.o HOSTCC tools/atmelimage.o HOSTCC tools/fip_create/fip_create.o HOSTCC tools/nexell/SECURE_BINGEN.o HOSTCC tools/default_image.o WRAP tools/common/bootm.c WRAP tools/lib/fdtdec_common.c WRAP tools/lib/fdtdec.c HOSTCC tools/nexell/BOOT_BINGEN.o HOSTCC tools/fit_common.o HOSTCC tools/fit_image.o HOSTLD tools/nexell/SECURE_BINGEN HOSTLD tools/nexell/BOOT_BINGEN HOSTLD tools/fip_create/fip_create HOSTCC tools/gpimage.o HOSTCC tools/gpimage-common.o WRAP tools/common/image-fit.c HOSTCC tools/image-host.o WRAP tools/common/image.c LDS u-boot.lds HOSTCC tools/imagetool.o [ error ] ERROR in function compile_uboot [ main.sh:595 -> main.sh:481 -> compilation.sh:241 -> general.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated Full output log (/build/output/debug/output.log) here https://files.electrohaxz.host/file/d240f5c497e8db0f53dbf940329fb4f6/output.log
  2. Hello everone. I'm new to embedded linux. To start with, I have nanopi fire 3 and smart 6818 cards, but I cannot access gpio pins with any gpio library. Why doesn't the NPi-GPIO library work with these cards? At first I was using the lubuntu version, I tried a lot there, but I couldn't. Now I'm trying to do something using armbian version 21.04. I'll post the problem I'm facing below. Thank you in advance for your help. Traceback (most recent call last): File "npigpio.py", line 1, in import NPi.GPIO as GPIO File "/usr/local/lib/python3.7/dist-packages/NPi.GPIO-", line 1, in from NPi._GPIO import * RuntimeError: Is not NanoPi based board.
  3. Hi! For some reason my nanopi fire 3's gigabit ethernet is very unstable. When connected to my local machine directly, the ping latency is insanely high and irregular: PING ( 56(84) bytes of data. 64 bytes from icmp_seq=1 ttl=64 time=112 ms 64 bytes from icmp_seq=2 ttl=64 time=333 ms 64 bytes from icmp_seq=3 ttl=64 time=350 ms 64 bytes from icmp_seq=4 ttl=64 time=203 ms 64 bytes from icmp_seq=5 ttl=64 time=1014 ms 64 bytes from icmp_seq=6 ttl=64 time=423 ms 64 bytes from icmp_seq=7 ttl=64 time=93.4 ms 64 bytes from icmp_seq=8 ttl=64 time=345 ms 64 bytes from icmp_seq=9 ttl=64 time=358 ms 64 bytes from icmp_seq=10 ttl=64 time=49.6 ms 64 bytes from icmp_seq=11 ttl=64 time=1021 ms 64 bytes from icmp_seq=12 ttl=64 time=299 ms 64 bytes from icmp_seq=13 ttl=64 time=305 ms 64 bytes from icmp_seq=14 ttl=64 time=318 ms 64 bytes from icmp_seq=15 ttl=64 time=300 ms 64 bytes from icmp_seq=16 ttl=64 time=1008 ms 64 bytes from icmp_seq=17 ttl=64 time=290 ms 64 bytes from icmp_seq=18 ttl=64 time=306 ms 64 bytes from icmp_seq=19 ttl=64 time=211 ms 64 bytes from icmp_seq=20 ttl=64 time=1023 ms ^C --- ping statistics --- 21 packets transmitted, 20 received, 4.7619% packet loss, time 20085ms rtt min/avg/max/mdev = 49.608/418.113/1022.521/312.908 ms, pipe 2 The nanopi fire 3 is directly connected to my desktop computer via a CAT6 cable, and the desktop computer's network adapter supports gigabit ethernet. Note that it is a direct cable connection and I am getting <1ms with my other boards such as the odroid xu4. I have also tried connecting the nanopi fire 3 directly to a netgear switch behind a router. Still terrible ping. Surprisingly if I force nanopi fire 3 to use 100Mbps ethernet connection, the ping latency is suddenly normal. I've tested the ethernet cable and it is working fine. And the nanopi fire 3 has a stable PSU(5.1V with no load and 5.05V under load). To investigate further, I tested Friendlyarm's friendlycore (seems to be ubuntu 18.04, kernel 4.4, aarch64) on the fire 3. And the gigabit ethernet is working with full speed. I also tested all history versions of armbian on the nanopi fire 3, and NONE OF THEM HAVE WORKING STABLE GIGABIT ETHERNET. This makes me think that there is something wrong in the gigabit ethernet code with armbian's s5p6818 4.14 kernel, since friendlyarm's 4.4 kernel does not have that issue. Also something worth noticing: nanopi fire 3 running armbian has less power draw(0.5 W) than friendlyarm's kernel, so it is possible that its network adapter attempted but cannot draw enough power to enable gigabit ethernet, thus the random and irregular ping. Tl;dr: There are some bugs in Armbian's 4.14 kernel for Nanopi Fire 3 that prevents gigabit ethernet from working properly.
  4. Hello, I'm trying to get working my NanoPi Fire3 with HD702 screen and I found out some issues. I'm running Armbian_20.02.7_Nanopifire3_bionic_legacy_4.14.174 image on it. -- First and most significant is that the ethernet port isn't working properly. I cannot ping anything and if I try to deactivate and activate ethernet connection in Network Manager it says: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.) Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn> [1585663445.9567] dhcp4 (eth0): request timed out Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info> [1585663445.9569] dhcp4 (eth0): state changed unknown -> timeout Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info> [1585663445.9738] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 4459 Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info> [1585663445.9739] dhcp4 (eth0): state changed timeout -> done Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info> [1585663445.9761] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn> [1585663445.9800] device (eth0): Activation: failed for connection 'Wired connection 1' Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info> [1585663445.9845] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0045] policy: auto-activating connection 'Wired connection 1' Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0147] device (eth0): Activation: starting connection 'Wired connection 1' (cf44b283-2a76-371d-9d8a-84fccecce8ea) Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0166] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0202] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0241] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info> [1585663446.0268] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) After reboot, it's connected via eth, but if I try to ping something is also fails root@nanopifire3:~# ping PING 8.8.88 ( 56(84) bytes of data. From icmp_seq=1 Destination Host Unreachable From icmp_seq=2 Destination Host Unreachable From icmp_seq=3 Destination Host Unreachable From icmp_seq=4 Destination Host Unreachable From icmp_seq=5 Destination Host Unreachable From icmp_seq=6 Destination Host Unreachable From icmp_seq=7 Destination Host Unreachable From icmp_seq=8 Destination Host Unreachable From icmp_seq=9 Destination Host Unreachable From icmp_seq=10 Destination Host Unreachable From icmp_seq=11 Destination Host Unreachable From icmp_seq=12 Destination Host Unreachable From icmp_seq=13 Destination Host Unreachable From icmp_seq=14 Destination Host Unreachable From icmp_seq=15 Destination Host Unreachable From icmp_seq=16 Destination Host Unreachable From icmp_seq=17 Destination Host Unreachable From icmp_seq=18 Destination Host Unreachable From icmp_seq=19 Destination Host Unreachable From icmp_seq=20 Destination Host Unreachable From icmp_seq=21 Destination Host Unreachable From icmp_seq=22 Destination Host Unreachable From icmp_seq=23 Destination Host Unreachable From icmp_seq=24 Destination Host Unreachable ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available -- I connected my HD702 screen to board and if I install xubuntu-core/desktop... it works, but It's running via fb, thus it's slow and FriendlyArm OneWire touchscreen isn't working. I wasn't able to find information if is OneWire touchscreen supported in your kernel, or how to get it working. I wasn't able to find any information if is GPU in S5P6818 supported or if it's possible to have accelerated desktop environment on it. -- My last question is if SPI on this board works. Thanks in advance.
  5. Here's what I get when trying to boot (data is from my serial adapter): I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error Wakeup Sub CPU 1234567 CPU Wakeup done! WFI is expected. CPU0 is Master! U-Boot 2016.01-armbian (Sep 02 2019 - 08:57:37 +0200) DRAM: 1 GiB MMC: NEXELL DWMMC: 0, NEXELL DWMMC: 1 loaded from SD, getting env from MMC 1 *** Warning - bad CRC, using default environment MIPI: display.0 HDMI: display.0, preset 0 (1280 * 720) HDMI: phy ready... LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000 In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ** File not found /boot.scr ** ## Executing script at 40000000 Wrong image format for "source" command 1277 bytes read in 31 ms (40 KiB/s) ## Executing script at 40000000 Wrong image format for "source" command Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 40000000 Wrong image format for "source" command ** Bad device mmc 0 ** ## Executing script at 40000000 Wrong image format for "source" command nanoPi# Here's what gpg and sha256sum output: % gpg --verify Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.asc gpg: assuming signed data in 'Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img' gpg: Signature made Mon Jan 20 00:04:11 2020 EST gpg: using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 gpg: Good signature from "Igor Pecovnik <igor@armbian.com>" [unknown] gpg: aka "Igor Pecovnik (Ljubljana, Slovenia) <igor.pecovnik@gmail.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: DF00 FAF1 C577 104B 50BF 1D00 93D6 889F 9F0E 78D5 % sha256sum -c Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.sha Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: OK Output of mount: # mount --ro Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img /mnt/usb mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. dmesg doesn't mention anything about the mounting problems. Gdisk outputs: # gdisk -l Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img GPT fdisk (gdisk) version 1.0.1 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: 2957312 sectors, 1.4 GiB Logical sector size: 512 bytes Disk identifier (GUID): 9FF78C6C-5C9B-4B4D-A4F3-B0B52827C119 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 2957278 Partitions will be aligned on 2048-sector boundaries Total free space is 8158 sectors (4.0 MiB) Number Start (sector) End (sector) Size Code Name 1 8192 2957311 1.4 GiB 8300 Linux filesystem The board I'm using is the Nano PI Fire3 LTS. It has worked before, although with a different Micro SD card. I accidentally erased it's SD card and I'm trying to reinstall. My current Micro SD card is a SanDisk Ultra 32GB rated USH-I, (10), U with a 1 inside, and A1. I used dd if=IMG of=DEV BS=8192 status=progress to place the image onto the Micro SD card. I also tried with my original SP Micro SD card without success. If you need anything else, just yell. Thanks!
  6. Hello, Recently I bought a nanopi fire 3 and installed armbian without any issue (Armbian_5.91_Nanopifire3_Debian_buster_next_4.14.133). The first thing I did was to connect the nanopi to my ADSL router in order to complete the basic configuration. Everything worked fine. Then I connected the nanopi to an Edimax gigabit ethernet switch and here is where the network problems appeared. The ethernet connection was too slow, with ping times of more than 1000ms, and an unstable behavior that made it almost impossible to connect via ssh. 64 bytes from icmp_seq=1 ttl=64 time=1004 ms 64 bytes from icmp_seq=2 ttl=64 time=1025 ms 64 bytes from icmp_seq=3 ttl=64 time=1001 ms 64 bytes from icmp_seq=4 ttl=64 time=1002 ms After many reconfigurations and reinstalls, I tried forcing the ethernet interface to work at 100Mbps, and it solved the network slugginess and unstability. ethtool -s eth0 speed 100 autoneg off Other devices connected to the same switch work fine at 1Gbps. Although with this workaround I can work for now, I still want to use my nanopi at full speed if possible. Anybody has any idea of how can I solve it?
  7. Hi there! I recently installed Armbian (Stretch: Armbian_5.83_Nanopifire3_Debian_stretch_next_4.14.115) on my new NanoPi Fire3. I was able to boot, but it responds so slow, that it is unusable! For example, when I SSH into it, it takes a log time to show me the login prompt. When I enter the username and press enter, it takes about 5 seconds to ask me for password. When I enter password, it takes about 10 seconds to show me the Armbian banner. I wasn't even able to go past the changing of unix password on first login, because it just "froze". I have installed the image twice on my SD card, just to make sure it isn't a corrupted install. I'm using a good PSU, and a good quality Samsung EVO 32GB sd card. I have tried installing DietPi, and FriendlyElec's 64 bit xenial image, without problems! This behavior happens only with Armbian. I want to use Armbian because I understood that it supports Docker on the Fire3 (is this true?) I haven't tried the Ubuntu version of Armbian, since it has Desktop, and I'm looking for a headless OS. BTW, is the Armbian Stretch image for the NanoPi 64 bit? Thank you guys for the excellent work!
  8. Hi all, In the review of the Fire3 at least one person mentions powering this board via something other than the MicroUSB. This would allow me to use the serial console that's supposedly exposed over that port instead of wiring up yet another USB to serial converter. What I can't work out is a) which pin/s are used to power it, and b) what kind of power supply is used. I'd rather not fry the board (it'll do that itself under load) so can someone point me in the right direction? Thanks in advance.
  • Create New...