Jump to content

Search the Community

Showing results for tags 'nanopineo2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Discord


Location


Interests

  1. Hi, I owe a fritzbox 5530 which is configured for both IPv6 and IPv4. My armbian ( debian 11 ) SBC ( neo2 running kernel 5.19.1 ) shows: root@armbian:~# ip a |grep inet6 inet6 ::1/128 scope host inet6 2a02:a45f:b977:1:3383:1a4e:38e2:733f/128 scope global dynamic noprefixroute inet6 2a02:a45f:b977:1:a05d:7fc7:a5d0:d647/64 scope global dynamic noprefixroute inet6 fe80::3383:1a4e:38e2:733f/64 scope link noprefixroute However I am unable to resolve the IPv6 address while for another debian box it is working fine: root@armbian:~# ping debian.fritz.box PING debian.fritz.box(debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0)) 56 data bytes 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=1 ttl=255 time=4.12 ms 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=2 ttl=255 time=3.34 ms ^C root@armbian:~# ping armbian.fritz.box PING armbian.fritz.box (192.168.10.6) 56(84) bytes of data. 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=1 ttl=64 time=0.999 ms 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=2 ttl=64 time=2.51 ms ^C Any thoughts please?
  2. 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
  3. Today I swapped my old Neo2 against a Neo2 LTS 1GB in my NAS case - so I had a old Neo2 512MB free for the black Aluminum-OLED-case which I got in a drawer. Now I did try to activate the OLED in ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi64 Linux npi-neo2-27 4.19.4-sunxi64 #6 SMP Fri Nov 30 14:02:43 +03 2018 aarch64 GNU/Linux First (like on a i2c-clock" I activated i2c0 in armbian-config: root@npi-neo2-27(192.168.6.27):~# armbian-config System --> Hardware --> [*] i2c0 After the reboot I checked for the i2c-OLED-device and got: root@npi-neo2-27(192.168.6.27):~# apt install i2c-tools root@npi-neo2-27(192.168.6.27):~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- After some trial and error(-messages) I did found the following dependencies for compiling/installing the software for the OLED-Board: apt-get install python-setuptools libjpeg-dev After that I did the normal "5 Enable NanoHat-OLED manually" from http://wiki.friendlyarm.com/wiki/index.php/NanoHat_OLED with root@npi-neo2-27(192.168.6.27):~# cd /home/guido root@npi-neo2-27(192.168.6.27):~# git clone https://github.com/friendlyarm/NanoHatOLED.git root@npi-neo2-27(192.168.6.27):~# cd NanoHatOLED root@npi-neo2-27(192.168.6.27):~# ./install.sh And after the next reboot the OLED-Display did work
  4. Sorry for my stupid question. If I connect by TTL to USB adapter, after setting up login/password, terminal is freezing. Board is Nanopi NOE2. I think this is due to the fact that my adapter is warm or not of poor quality. While I order a new one, is there a way to enable ssh access over the lan network?
  5. Hi all. I'm new, so don't hit too hard. I'm interested in how the NAS Dock for NanoPi Neo2 is defined in the system. I want to install OpenWRT, because I need a NanoPi based router. Armbian seems to me too complicated for such tasks. If you put OpenWRT on NEO2, then NAS Dock is not detected in the system. At that time Armbian determines, I can easily open the HDD or connect devices to the dock's USB port. Please tell me. Which module or driver is responsible for the dock to be defined in the system? The Openwrt forum has not yet been able to help me, so I'm writing here. Help as you can.
  6. I am building kernel 5.10.4 sources on NanoPi Neo 2 with Armbian 20.11.10 Focal and get following error: nanopineo2:~:% cd /usr/src/linux-headers-5.10.4-sunxi64 nanopineo2:linux-headers-5.10.4-sunxi64:% sudo make headers_check nanopineo2:linux-headers-5.10.4-sunxi64:% sudo make scripts nanopineo2:linux-headers-5.10.4-sunxi64:% sudo make prepare scripts/Makefile.build:414: warning: overriding recipe for target 'modules.order' Makefile:1407: warning: ignoring old recipe for target 'modules.order' make[1]: *** No rule to make target 'arch/arm64/kernel/vdso/vdso.lds', needed by 'arch/arm64/kernel/vdso/vdso.so.dbg'. Stop. make: *** [arch/arm64/Makefile:182: vdso_prepare] Error 2 Do I miss something? Could someone confirm the error I see?
  7. DTS overlay to activate I2S DAC 5102a on Armbian Buster 5.4.43 armbian-add-overlay sun50i-h5-i2s0-out.dts If you don't have headers armbian-config (software->headers) Manual install whithout headers mkdir /boot/overlay-user/ dtc -I dts -O dtb sun50i-h5-i2s0-out-no-header.dts -o /boot/overlay-user/sun50i-h5-i2s0-out.dtbo add user_overlays=sun50i-h5-i2s0-out to /boot/armbianEnv.txt sun50i-h5-i2s0-out.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target-path = "/"; __overlay__ { pcm5102a: pcm5102a { #sound-dai-cells = < 0x00 >; compatible = "ti,pcm5102a"; status = "okay"; linux,phandle = < 0x26 >; phandle = < 0x26 >; pcm510x,format = "i2s"; }; }; }; fragment@1 { target-path = "/aliases"; __overlay__ { i2s0 = "/soc/i2s@1c22000"; }; }; fragment@2 { target = <&i2s0>; __overlay__ { status = "okay"; pinctrl-0 = <&i2s0_pins>; sound-dai = <&pcm5102a>; pinctrl-names = "default"; }; }; fragment@3 { target-path = "/"; __overlay__ { sound_i2s { compatible = "simple-audio-card"; simple-audio-card,name = "I2S-master"; simple-audio-card,mclk-fs = <256>; simple-audio-card,format = "i2s"; status = "okay"; simple-audio-card,cpu { sound-dai = <&i2s0>; }; simple-audio-card,codec { sound-dai = <&pcm5102a>; }; }; }; }; }; sun50i-h5-i2s0-out-no-header.dts /dts-v1/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target-path = [ 2f 00 ]; __overlay__ { pcm5102a { #sound-dai-cells = < 0x00 >; compatible = "ti,pcm5102a"; status = "okay"; linux,phandle = < 0x26 >; phandle = < 0x26 >; pcm510x,format = "i2s"; }; }; }; fragment@1 { target-path = "/aliases"; __overlay__ { i2s0 = "/soc/i2s@1c22000"; }; }; fragment@2 { target = < 0xffffffff >; __overlay__ { status = "okay"; pinctrl-0 = < 0xffffffff >; sound-dai = < 0x26 >; pinctrl-names = "default"; }; }; fragment@3 { target-path = [ 2f 00 ]; __overlay__ { sound_i2s { compatible = "simple-audio-card"; simple-audio-card,name = "I2S-master"; simple-audio-card,mclk-fs = < 0x100 >; simple-audio-card,format = "i2s"; status = "okay"; simple-audio-card,cpu { sound-dai = < 0xffffffff >; }; simple-audio-card,codec { sound-dai = < 0x26 >; }; }; }; }; __symbols__ { pcm5102a = "/fragment@0/__overlay__/pcm5102a"; }; __fixups__ { i2s0 = "/fragment@2:target:0\0/fragment@3/__overlay__/sound_i2s/simple-audio-card,cpu:sound-dai:0"; i2s0_pins = "/fragment@2/__overlay__:pinctrl-0:0"; }; __local_fixups__ { fragment@2 { __overlay__ { sound-dai = < 0x00 >; }; }; fragment@3 { __overlay__ { sound_i2s { simple-audio-card,codec { sound-dai = < 0x00 >; }; }; }; }; }; };
  8. Just flashed Armbian 20.11.9 for NanoPi Neo 2 with kernel 5.10.4. I have run armbian-config to install kernel 5.10.4 source, but there is no any option for 5.10.x kernel sources, I see only options for 5.8.x and 5.9.x.
  9. I'm trying to disable IPv6 on my NanoPi Neo2. Initially I used the option in armbian-config -> Network -> IPv6 (toggle). I can confirm that IPv6 is disabled by running 'ip a' and no longer seeing any IPv6 addresses. And I can also confirm that the following config is changed in /etc/sysctl.conf: net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 However after a reboot I see the IPv6 addresses back. I found a guide (itsfoss) that suggest the same changes to sysctl.conf and if the changes do not persist ander a startup I should make edit /etc/rc.local : #!/bin/bash # /etc/rc.local /etc/sysctl.d /etc/init.d/procps restart exit 0 However that didn't seem to help. Looking in the forums I came across one topic which is marked solved however I think the author might have had the same issue (how-can-i-disable-ipv6-or-use-temporary-addresses-regular-methods-dont-work-solved) Does anyone else have this issue and know how to solve it? Thanks and happy new year!
  10. Hi, I am trying to interface I/O expander MCP23017 to Nano Pi Neo2(Hardware specs:1 GB RAM, Gigabit Ethernet . Software specs: Debian Buster with Armbian Linux 4.19.59-sunxi64 ) . The issue I am having is I am not able to see the device when I run sudo i2cdetect -y 0 . I have enabled i2c overlays in /boot/armbian.txt . I am using 10 K Ohm pull-ups on SDA and SCK . I get no activity while running i2cdetect on the oscilloscope on SCK and SDA lines . Is this an issue with the kernel ?
  11. During first boot and following first login as root got this error message: New to Armbian? Documentation: https://docs.armbian.com Support: https://forum.armbian.com New root password: ************ Repeat password: ************ Detected timezone: America/Mexico_City (CST, -0600) Generating locales: es_MX.UTF-8 Adding console keyboard layout: mx /usr/bin/ckbcomp: Can not find file "symbols/mx" in any known directory I am not sure that console keyborad layout "mx" exists.
  12. Good evening, I ran into some problems with sbc-bench on a couple of Allwinner boards Orange Pi Zero, Orange Pi Zero+, Orange Pi One and Nanopi Neo 2 spcifically. The 7 Zip benchmark causes the following error: ./sbc-bench.sh: Zeile 611: 4206 Bus-Zugriffsfehler "${SevenZip}" b >> ${TempLog} Most likely due to a problem with the ZRam: zram: Decompression failed! err=-22 This happens on all boards under Debian and focal with different SD cards and power supplies. The benchmark ran previously on this setups without any issues – unfortunately I don’t know when it stopped working and hence cannot narrow down the change that caused the problem. The benchmark results and armbianmonitor output from the Orange Pi one as an example: http://ix.io/2EPZ http://ix.io/2ES2 Is this a known issue? Is there a solution? Daniel
  13. I have a problem with NEO2 and EDIMAX EW 7822ULC. I can't see none of my 5GHz network SSID, but I can connect to 2.4 GHz. I am using Buster minimal image. It is something I should do to solve this problem? Thank you.
  14. Hi, Is the first time that I will post on the forum. I don't know if it is the right place for it. Sorry if my question doesn't belong here. I want to install that program (USB Network Gate Linux) on the lastest version of Armbian Debian based (No Ubuntu) on my board, which is NanoPi NEO 2 1GB. After plugged into the board, I entered via SSH, change psswd and I did: sudo apt-get update sudo apt-get upgrade Downloaded the file with wget https://cdn.electronic.us/products/usb-over-ethernet/linux/download/eveusb_armv7l.deb I tried to install it with dpkg -i eveusb_armv7l.deb But I get missing dependencies so... sudo apt-get -f install Tried again but now I have the error which is in the picture below I tried to do this https://www.tecmint.com/install-kernel-headers-in-ubuntu-and-debian/ But there isn't any kernel header available for linux kernel 5.4.20 Could you please help me? Thank u for ur time
  15. Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?
  16. update works on 5.4.28-sunxi64, so for sure kernel issue... I fail to start the nfs-kernel-server on my neo2: ● nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-06-19 22:50:35 CEST; 57s ago Main PID: 28168 (code=exited, status=1/FAILURE) Jun 19 22:50:35 neo2 systemd[1]: Starting NFS server and services... Jun 19 22:50:35 neo2 rpc.nfsd[28168]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused) Jun 19 22:50:35 neo2 rpc.nfsd[28168]: rpc.nfsd: unable to set any sockets for nfsd Jun 19 22:50:35 neo2 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Jun 19 22:50:35 neo2 systemd[1]: nfs-server.service: Failed with result 'exit-code'. Jun 19 22:50:35 neo2 systemd[1]: Stopped NFS server and services. and from dmesg: [621412.035437] rpc.nfsd: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 [621412.035472] CPU: 2 PID: 25458 Comm: rpc.nfsd Not tainted 5.4.43-sunxi64 #20.05.2 [621412.035476] Hardware name: FriendlyARM NanoPi NEO 2 (DT) [621412.035481] Call trace: [621412.035498] dump_backtrace+0x0/0x180 [621412.035505] show_stack+0x14/0x20 [621412.035516] dump_stack+0xb0/0xd8 [621412.035528] warn_alloc+0xfc/0x168 [621412.035535] __alloc_pages_slowpath+0x9c4/0x9f0 [621412.035543] __alloc_pages_nodemask+0x214/0x298 [621412.035551] alloc_pages_current+0x80/0xf0 [621412.035561] kmalloc_order+0x1c/0x88 [621412.035624] nfsd_file_cache_init+0x64/0x248 [nfsd] [621412.035660] nfsd_svc+0x198/0x288 [nfsd] [621412.035695] write_threads+0x94/0x110 [nfsd] [621412.035729] nfsctl_transaction_write+0x54/0x98 [nfsd] [621412.035739] __vfs_write+0x18/0x40 [621412.035745] vfs_write+0xb0/0x1d0 [621412.035752] ksys_write+0x64/0xe8 [621412.035759] __arm64_sys_write+0x18/0x20 [621412.035770] el0_svc_common.constprop.2+0x88/0x150 [621412.035777] el0_svc_handler+0x20/0x80 [621412.035785] el0_svc+0x8/0xc [621412.035789] Mem-Info: [621412.035810] active_anon:14680 inactive_anon:13376 isolated_anon:0 active_file:3920 inactive_file:3223 isolated_file:0 unevictable:0 dirty:8 writeback:0 unstable:0 slab_reclaimable:13144 slab_unreclaimable:17259 mapped:4842 shmem:176 pagetables:1074 bounce:0 free:29614 free_pcp:0 free_cma:26079 [621412.035827] Node 0 active_anon:58720kB inactive_anon:53504kB active_file:15680kB inactive_file:12892kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:19368kB dirty:32kB writeback:0kB shmem:704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [621412.035831] Node 0 DMA32 free:118456kB min:4396kB low:4980kB high:5564kB active_anon:58768kB inactive_anon:53512kB active_file:15644kB inactive_file:13036kB unevictable:0kB writepending:32kB present:524288kB managed:489208kB mlocked:0kB kernel_stack:3632kB pagetables:4296kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:104316kB [621412.035852] lowmem_reserve[]: 0 0 0 [621412.035861] Node 0 DMA32: 2311*4kB (UMEHC) 571*8kB (UMEHC) 1032*16kB (UMEHC) 740*32kB (HC) 434*64kB (HC) 184*128kB (C) 40*256kB (C) 6*512kB (C) 0*1024kB 0*2048kB 0*4096kB = 118644kB [621412.035910] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [621412.035917] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB [621412.035923] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [621412.035929] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB [621412.035932] 7530 total pagecache pages [621412.035939] 194 pages in swap cache [621412.035945] Swap cache stats: add 24936974, delete 24936777, find 248269/24985229 [621412.035949] Free swap = 48244kB [621412.035952] Total swap = 244600kB [621412.035955] 131072 pages RAM [621412.035958] 0 pages HighMem/MovableOnly [621412.035962] 8770 pages reserved [621412.035965] 32768 pages cma reserved [621412.035972] nfsd: unable to allocate nfsd_file_hashtbl I will try to downgrade kernel and see if this solves the issue Regards Termo
  17. Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... https://github.com/sfx2000/byte-unixbench more to follow...
  18. (Edit: it's a red herring for me to worry about swap. Please see a few posts down...) Hello. My NanoPi Neo 2 only has 512MB RAM. I'm using it for OpenMediaVault. It starts swapping very badly (totally paralysing it) when I FTP 60GB worth of tiny files into an attached 500GB SSD SATA drive (attached with the NAS kit). Yes, ProFTPd is RAM-hungry! I know how to create and work with traditional linux swap files. I'm a noob to this whole zram thing, which I suspect is more trouble than it's worth. I would prefer to not use zram, and use a traditional swap file on an attached 6TB 3.5" SATA drive (attached over USB 2.0 with UAS). It's a backup drive that sits there all day long doing nothing, in fact it goes to sleep all day (and only wakes up in the middle of the night to do a backup). zramctl shows: NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram1 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram2 lzo 60.3M 4K 78B 12K 4 [SWAP] /dev/zram3 lzo 60.3M 4K 78B 12K 4 [SWAP] Those zram device files are on my Sandisk Ultra MicroSD card (which is "A1"), where Armbian runs from. My lightly-used SATA drive would be better for me, for running a traditional swap file from (due to its just sleeping all day otherwise). Is there some way to tell my Armbian "quit with zram, and just use a traditional swap file, as per my /etc/fstab"? BTW: I've set my "vm.swappiness" to 5 in /etc/sysctl.conf
  19. I'm trying to use a c270 webcam, but it is not listed on USB devices. Can someone help me?
  20. I've got a Sony RX100VA camera that I want to connect to the NanoPi Neo2 running Armbian Buster. On the Camera I can select the type of USB connection: -Auto -Mass Storage -MTP -PC Remote My intention is to use the PC Remote connection for use with gphoto2, this works fine on a PC with Ubuntu 18.04, but when I connect the camera to the Nano Pi Neo2 with Armbian, the camera display shows connecting (but doesn't connect). I suspect a bug in the OS, but I am unsure how to find it. lsusb gives the following report with an error: can't get debug descriptor: Resource temporarily unavailable root@nanopineo2:~# lsusb -d 054c:0cb2 -v Bus 003 Device 019: ID 054c:0cb2 Sony Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x054c Sony Corp. idProduct 0x0cb2 bcdDevice 2.00 iManufacturer 1 Sony iProduct 2 DSC-RX100M5A iSerial 3 C7A5602C40B2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0027 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 7 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered) Mounting as a mass storage device works fine, but then I can't use it with gphoto2. How do I find the bug?
  21. Good evening, In your opinion, what is the best alternative to the NanoPi NEO2? I don't need wifi or sata. I'm looking for a stable and qualitative armbian with a gigabit and usb port. Is there a better performing armbian that the NEO2 has for less than 40$? Thanks
  22. Hi all, Running Armbian Ubuntu 18.04 with stock neo2 4.19.20 kernel I tried installing https://github.com/friendlyarm/WiringNP but after installation `gpio readall` says : "This NanoPi model is currently not supported." However all the wiki's and the Github page says it's supported.......? I can see GPIO in the sys fs at /sys/class/gpio/ but I was hoping to have an easier time with it than manually exporting each pin and calculating offsets for pins with scraps of info online etc. Objective 1: Read a high/low 3.3v/0v status from a GPIO Objective 2: Read an analog voltage, using an ADC. Does the H5 include an ADC? When I look in http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Page 13 says 2.1.4.9.KEYADC * Analog to digital converter with 6-bit resolution for key application * Maximum sampling frequency up to 250 Hz * Supports general key, hold key and already hold key * Supports single , normal and continuous work mode I don't need high speed sampling, don't need interrupts, the simpler and easier the implementation the better. Any help will be much appreciated PS: How to fix friendlyarm/WiringNP friendlyarm/WiringNP is not accepting issues on their github repo, but it seems to be the best fork out there. How can we get them to accept issues and how can we fix the issue? http://forked.yannick.io/friendlyarm/WiringNP
  23. Hi, there are invalid references inside sun50i-h5-fixup.scr, I think. I use NANOPINEO2, myself compiled linux-*-current-sunxi64_20.05.0-trunk_arm64.deb, kernel 5.4.28-sunxi64 #trunk SMP PREEMPT. amrbianEnv.txt (reduced): overlay_prefix=sun50i-h5 overlays=i2c0 uart1 uart2 usbhost1 usbhost2 usbhost3 param_uart1_rtscts=1 param_uart2_rtscts=1 For example, the row param_uart2_rtscts=1 leads to use following rows of sun50i-h5-fixup.scr: fdt get value tmp_phandle1 /soc/pinctrl@1c20800/uart2 phandle fdt get value tmp_phandle2 /soc/pinctrl@1c20800/uart2_rts_cts phandle fdt set /soc/serial@1c28800 pinctrl-names "default" "default" fdt set /soc/serial@1c28800 pinctrl-0 "<${tmp_phandle1}>" fdt set /soc/serial@1c28800 pinctrl-1 "<${tmp_phandle2}>" env delete tmp_phandle1 tmp_phandle2 There are some error messages during boot: Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 tmp_bank=A tmp_pin=21 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND 10046717 bytes read in 505 ms (19 MiB/s) As a result, the RTS/CTS handshaking for UART2 is unfunctional. May be for UART1 and UART3 is the same? I think the reason is that there are no paths /soc/pinctrl@1c20800/uart2 and /soc/pinctrl@1c20800/uart2_rts_cts inside the device tree specified by sun50i-h5-nanopi-neo2-v1.1.dtb file. The right paths are /soc/pinctrl@1c20800/uart2-pins and /soc/pinctrl@1c20800/uart2-rts-cts-pins, I think. Am I right? I've tried easy modification of SCR script - handshaking is now functional, but CRC is bad. If I am right, what is the right way to correct this? Script change (how properly?), DTB change, DTBO creation, ...? Moreover, look at this reduced listing of /sys/firmware/devicetree/base/soc/pinctrl@1c20800: csi-pins emac-rgmii-pins i2c0-pins i2c1-pins i2c2-pins i2s0-pins i2s1-pins mmc0-pins mmc1-pins mmc2-8bit-pins spi0-pins spi1-pins uart0-pa-pins uart1-pins uart1-rts-cts-pins uart2-pins uart2_rts_cts uart2-rts-cts-pins uart3-pins uart3-rts-cts-pins w1_pins Why are somewhere dashes "-" and somewhere underscores "_" ? Thank you.
  24. Hi, I want to expand my NanoPi-NEO2 more uart ports through I2C, so I make a choice to use a sc16is750 module( just like sparkfun sc16is750 ). Below is all of my system information: pi@nanopineo2:~$ uname -a Linux nanopineo2 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux First step ,I edit a device tree overlay for the sc16is750 named sc16is750-i2c.dts as below: pi@nanopineo2:/boot/overlay-user$ sudo nano sc16is750-i2c.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { /* This fragment is required only if using interrupts */ target = <&pio>; __overlay__ { sc16is750_pin_irq: sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; }; }; }; fragment@1 { target = <&i2c1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; sc16is750: sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x4d>; status = "okay"; clocks = <&sc16is750_clk>; gpio-controller; #gpio-cells = <3>; /* Below are optional properties for supporting interrupts */ interrupt-controller; #interrupt-cells = <3>; interrupt-parent = <&pio>; interrupts = <0 17 2>; /* PG11 IRQ_TYPE_EDGE_FALLING */ pinctrl-names = "default"; pinctrl-0 = <&sc16is750_pin_irq>; sc16is750_clk: sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <14745600>; }; }; }; }; __overrides__ { int_pin = <&sc16is750>,"interrupts:0"; addr = <&sc16is750>,"reg:0"; }; }; Second step, I add the sc16is750-i2c.dts to my /boot/overlay-usr as below: pi@nanopineo2:/boot/overlay-user$ sudo armbian-add-overlay sc16is750-i2c.dts Compiling the overlay Copying the compiled overlay file to /boot/overlay-user/ Reboot is required to apply the changes Afterthen, I checked sc16is750-i2c.dtbo as below: pi@nanopineo2:/boot/overlay-user$ fdtdump sc16is750-i2c.dtbo **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> /dts-v1/; // magic: 0xd00dfeed // totalsize: 0x5f8 (1528) // off_dt_struct: 0x38 // off_dt_strings: 0x4d0 // off_mem_rsvmap: 0x28 // version: 17 // last_comp_version: 16 // boot_cpuid_phys: 0x0 // size_dt_strings: 0x128 // size_dt_struct: 0x498 / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overlay__ { sc16is750_pin_irq { pins = "PA17"; function = "irq"; bias-pull-up; phandle = <0x00000002>; }; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { #address-cells = <0x00000001>; #size-cells = <0x00000000>; sc16is750@4d { compatible = "nxp,sc16is750"; reg = <0x0000004d>; status = "okay"; clocks = <0x00000001>; gpio-controller; #gpio-cells = <0x00000003>; interrupt-controller; #interrupt-cells = <0x00000003>; interrupt-parent = <0xffffffff>; interrupts = <0x00000000 0x00000011 0x00000002>; pinctrl-names = "default"; pinctrl-0 = <0x00000002>; phandle = <0x00000003>; sc16is750_clk { compatible = "fixed-clock"; #clock-cells = <0x00000000>; clock-frequency = <0x00e10000>; phandle = <0x00000001>; }; }; }; }; __symbols__ { sc16is750_pin_irq = "/fragment@0/__overlay__/sc16is750_pin_irq"; sc16is750 = "/fragment@1/__overlay__/sc16is750@4d"; sc16is750_clk = "/fragment@1/__overlay__/sc16is750@4d/sc16is750_clk"; }; __fixups__ { pio = "/fragment@0:target:0", "/fragment@1/__overlay__/sc16is750@4d:interrupt-parent:0"; i2c1 = "/fragment@1:target:0"; }; __local_fixups__ { fragment@1 { __overlay__ { sc16is750@4d { clocks = <0x00000000>; pinctrl-0 = <0x00000000>; }; }; }; }; }; After reboot, I check the tty devices: pi@nanopineo2:~$ dmesg | grep tty [ 2.056137] printk: console [ttyS0] disabled [ 2.076722] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 26, base_baud = 1500000) is a U6_16550A [ 2.076773] printk: console [ttyS0] enabled [ 2.098045] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 27, base_baud = 1500000) is a U6_16550A [ 2.119044] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 28, base_baud = 1500000) is a U6_16550A [ 2.142198] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 29, base_baud = 1500000) is a U6_16550A [ 5.873610] serial serial0: tty port ttySC0 registered Also, I have check the i2c: pi@nanopineo2:~$ sudo i2cdetect -y 1 [sudo] password for pi: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- my sc16is750 address:0x4d Finally, I check the tty devices: pi@nanopineo2:~$ ls -l /dev/ttyS* crw------- 1 pi tty 4, 64 Mar 23 03:21 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Mar 23 03:16 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Mar 23 03:16 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Mar 23 03:16 /dev/ttyS3 pi@nanopineo2:~$ cat /proc/tty/drivers /dev/tty /dev/tty 5 0 system:/dev/tty /dev/console /dev/console 5 1 system:console /dev/ptmx /dev/ptmx 5 2 system /dev/vc/0 /dev/vc/0 4 0 system:vtmaster unknown /dev/ttySC 242 0-7 serial g_serial /dev/ttyGS 245 0-3 serial serial /dev/ttyS 4 64-67 serial pty_slave /dev/pts 136 0-1048575 pty:slave pty_master /dev/ptm 128 0-1048575 pty:master unknown /dev/tty 4 1-63 console So, My question is why I cannot find the /dev/ttySC0? Anyone can give me some advice to resolve the problem. Thanks.
  25. Dears, We have 4 boards Nanopi Neo2, but when we connect to energy, they don't boot, leds of net port (green and yellow ones) and internal led (red) are on all time. We tried to access via serial port (using an usb-serial adapter), but they not show any boot process. We tried some different boot images on sd card. Nothing works. All four devices are in this situation (and they are new!). There is any thing we can do?
×
×
  • Create New...