Jump to content

Search the Community

Showing results for tags 'nanopiduo'.

  • 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
  • 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

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Giveaway

Categories

  • Members

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

  1. How is i2c1 and i2c2 mapped on Nanopi Duo? I can configure in armbian-config, but all the Duo pin diagrams only show i2c0.
  2. Hello First of all, thank you for the great effort of the Armbian project. In second place: I have a NanoPi Duo device, which has been working fine with an old version of Armbian. But when trying to use the latest version, it happens that the serial port console continuously gives the following message and does not allow login ... ... [ OK ] Started Update UTMP about System Runlevel Changes. [ OK ] Started Network Manager Script Dispatcher Service. nanopiduo login: root (automatic login) Authentication failure nanopiduo login: root (automatic login) Authentication failure nanopiduo login: root (automatic login) Authentication failure ... The nanopi duo only gives the possibility of access by UART, since in practice, the analog video output does not work. Does anyone have a solution for this problem? Thanks!
  3. An interesting fact (at least from what I can tell), the NanoPi Duo (v1.0 and v 1.1) has no builtin PUDs. Checking http://wiki.friendlyarm.com/wiki/images/8/8a/Schematic_NanoPi_Duo-v1.1.pdf and I see no PUDs on the GPIO schematic. Is this true? Is the Orange Pi Zero the same way?
  4. Hi there, i need some help with using the UART1 pins 8 & 9. I own a Duo with Ubuntu 16.04.6 I've installed a software that is able to send codes over the UART1 pins to my smart home system. The software is 'active (running)' but has no connection via UART1. UART1 is enabled(npi-config) but i does not work. WiringNP is required for my software and installed. Is there any point i've missed? Did i have to switch UART1 pins to in- and output? One error i get: Service Control Manager on computer xx.x.x.xx cannot be opened. You may not have permission to do this. PS: These pins must work, i rebuild another thing that's works fine! Software configs are the same, that is not the problem.
  5. I'm looking for udev rules or some other way to read system LEDs without sudo. I tried https://github.com/todbot/blink1/blob/master/linux/51-blink1.rules, but I suspect it's not 100% what I need for the Duo.
  6. I noticed with the latest bionic image on the Duo it does a soft shutdown when you use the built in button. The problem is I use this button for my own uses. Can this feature be disabled and relinquish control of the button? gpioinfo | grep k1 line 3: unnamed "k1" input active-low [used]
  7. Hi guys, I've been having problems on my NanoPi Duo implementing a music streaming service using Alsa PCM to output the audio. When calling snd_pcm_open with the nonblock flag set, I had snd_pcm_writei returning a broken pipe error several times per day (when continuously playing). I noticed not setting this flag and, thus, allowing snd_pcm_writei to block until there was enough room in the Alsa PCM buffer, did not show this problem. This was however unusable because the blocking behaviour slowed down the rest of the software enough to be annoying. I think I solved it now by checking with snd_pcm_avail_update if there's enough room available, otherwise I would not call snd_pcm_writei. Just wanted to put htis out there for anyone's future reference because I could not find any known issues with setting this flag + I don't understand what's causing this.. If anyone has experienced this as well, or might have a clue what's going on, please let me know 4.19.25-sunxi #5.78 SMP Mon Apr 8 07:46:22 CEST 2019 armv7l GNU/Linux
  8. This has been replaced by: User Space IO get more details on this thread. Well, it's time to say goodbye to sysfs and hello to libgpiod! @zador.blood.stained pointed me in the right direction, but you need to do one little hack I'll explain below involving compiler_types.h. I tested this on a NanoPi Duo, but it should work on any mainline Armbian release (and other distros as well) as long as the kernel is >= 4.8. Try ls /dev/gpiochip* and see if anything is listed. If so, then proceed. I'm continuing work on my Github site https://github.com/sgjava/libgpiod-extra, so please report any issues there. There is an Armbian install script that automates the steps below I generated the Python wrapper, but there's a lot of functions to test, so I'm not sure of the quality. I'm working on some simple Python tests. sudo armbian-config, Software, Headers sudo apt-get install libtool pkg-config git clone https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git cd libgpiod mkdir -p include/linux cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler_types.h include/linux/. ./autogen.sh --enable-tools=yes --prefix=/usr/local CFLAGS="-I/usr/src/linux-headers-$(uname -r)/include/uapi -Iinclude" make sudo make install sudo ldconfig Let's try some commands: sudo gpiodetect gpiochip0 [1c20800.pinctrl] (224 lines) gpiochip1 [1f02c00.pinctrl] (32 lines) sudo gpioinfo | grep "\[used\]" line 10: unnamed "nanopi:blue:status" output active-high [used] line 166: unnamed "cd" input active-high [used] line 202: unnamed "interrupt" input active-high [used] line 205: unnamed "reset" output active-low [used] line 6: unnamed "?" output active-high [used] line 7: unnamed "vcc-wifi" output active-high [used] line 10: unnamed "nanopi:green:pwr" output active-high [used] Notice how it found the Duo's built in LEDs Now let's test the Duo's built in button (press and release 3 times): sudo gpiomon --num-events=3 --rising-edge gpiochip1 3 event: RISING EDGE offset: 3 timestamp: [1516774143.944174870] event: RISING EDGE offset: 3 timestamp: [1516774145.123474395] event: RISING EDGE offset: 3 timestamp: [1516774145.987531088] Wire up LED (the normal way) and use Duo's IOG11 then to turn on and off: sudo gpioset gpiochip0 203=0 sudo gpioset gpiochip0 203=1 Python code import time from libgpiod.libgpiod import * chip = gpiod_chip_open("/dev/gpiochip0") line = gpiod_chip_get_line(chip, 203) # The will set line for output and set initial value (LED on) if gpiod_line_request_output(line, "test", 0) == 0: time.sleep(3) # LED off gpiod_line_set_value(line, 1) gpiod_line_release(line) gpiod_chip_close(chip) More reading at https://www.cnx-software.com/2017/11/03/learn-more-about-linuxs-new-gpio-user-space-subsystem-libgpiod and https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/README. Maybe @Larry Bank will work on ArmbianIO II It looks like in the old Github site there was a milestone to create Python and C++ wrappers https://github.com/brgl/libgpiod/milestone/3. Once I learn more about libgpiod I may just generate them like I did for ArmbianIO.
  9. Hello everyone, Around July 2018 I was able to successfully build an Armbian image for NanoPi Duo using provided documentation: https://docs.armbian.com/Developer-Guide_Build-Preparation/ The reason I decided to build the image was that I needed it with legacy kernel 3.4.113. For some reason there were significant problems with using the mainline kernel with direwolf application which is an amateur radio APRS modem. The device hanged with mainline kernel after few hours of operation without any reason and this was not an overheat problem (temperatures below 50 degrees and a huge heatsink). I believe that it is some problem with audio driver for H2 which seems to be rewriten in mainline kernel, I don't see any other possibility as direwolf doesn't use any other peripherals and when it is not running or even running without soundcard, the device does not hang. Anyway, on July 2018 I was able to build it with kernel 3.4.113. I had to make a proper fex file for nanopiduo, because it is not available in sources. The resulting image file worked flawlessly for many months (Armbian_5.55_Nanopiduo_Ubuntu_xenial_default_3.4.113.img). Today I wanted to make the build again using the Ubuntu Bionic which seems to be now the only supported environment. I believe that I made everything like before, added the same fex file for nanopiduo and got a proper img file (Armbian_5.74_Nanopiduo_Ubuntu_xenial_default_3.4.113.img). But... the device does not even boot. Looks like something must have changed in the software, maybe U-boot version, maybe some configuration. Do you have any clue what may be wrong? Is the legacy kernel going to be no longer supported? On Monday I'm going to check via serial console, maybe it will give some output helping to understand what's going on. But it looks like I have a problem.
  10. Hi Guys, today I've Updated from "Armbian_5.67_Nanopiduo_Debian_stretch_next_4.14.90" to Armbian_5.69_Nanopiduo_Debian_stretch_next_4.19.13" now I've the follwing problem on my nanopi duo. It has Wifi onboard (XR819), but after an Update to Kernel 4.19.13-sunxi. my wifi device was lost. Before the Update the wifi device was listet as wlan0. to avoid configuration errors i also reinstalled the system. It does not work with debian or ubuntu. If i roleback to an older kernel everything works great. uname -a Linux nanopiduo 4.19.13-sunxi #5.69 SMP Wed Jan 9 16:26:48 CET 2019 armv7l armv7l armv7l GNU/Linux ifconfig -a dummy0: flags=130<BROADCAST,NOARP> mtu 1500 ether fa:76:fc:15:3e:84 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 02:42:0f:94:b1:fc txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 37 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled Module Size Used by zstd 16384 4 evdev 20480 1 sun8i_codec_analog 24576 0 sun8i_adda_pr_regmap 16384 1 sun8i_codec_analog snd_soc_simple_card 16384 0 snd_soc_simple_card_utils 16384 1 snd_soc_simple_card sun4i_i2s 20480 0 snd_soc_core 106496 4 sun4i_i2s,sun8i_codec_analog,snd_soc_simple_card_utils,snd_soc_simple_card snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core sun4i_gpadc_iio 16384 0 snd_timer 24576 1 snd_pcm industrialio 49152 1 sun4i_gpadc_iio snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun8i_ths 16384 0 zram 20480 5 cpufreq_dt 16384 0 uio_pdrv_genirq 16384 0 gpio_keys 20480 0 thermal_sys 57344 3 cpufreq_dt,sun8i_ths,sun4i_gpadc_iio uio 16384 1 uio_pdrv_genirq sch_fq_codel 20480 2 usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1 lima 40960 0 gpu_sched 20480 1 lima ttm 57344 1 lima dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.19.13-sunxi (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.69 SMP Wed Jan 9 16:26:48 CET 2019 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: FriendlyARM NanoPi DUO [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0x57c00000 [ 0.000000] On node 0 totalpages: 131072 [ 0.000000] Normal zone: 1152 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 131072 pages, LIFO batch:31 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: Using PSCI v0.1 Function IDs from DT [ 0.000000] random: get_random_bytes called from start_kernel+0x8d/0x3c2 with crng_init=0 [ 0.000000] percpu: Embedded 18 pages/cpu @(ptrval) s41484 r8192 d24052 u73728 [ 0.000000] pcpu-alloc: s41484 r8192 d24052 u73728 alloc=18*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129920 [ 0.000000] Kernel command line: root=UUID=4184603d-f069-41c2-95e2-68f03fbdbdcc rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ab235005-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] allocated 524288 bytes of page_ext [ 0.000000] Memory: 365120K/524288K available (8192K kernel code, 896K rwdata, 2420K rodata, 1024K init, 316K bss, 28096K reserved, 131072K cma-reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xe0800000 - 0xff800000 ( 496 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf800000 - 0xbfe00000 ( 6 MB) .text : 0x(ptrval) - 0x(ptrval) (9184 kB) .init : 0x(ptrval) - 0x(ptrval) (1024 kB) .data : 0x(ptrval) - 0x(ptrval) ( 897 kB) .bss : 0x(ptrval) - 0x(ptrval) ( 317 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 36585 entries in 72 pages [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000011] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000026] Switching to timer-based delay loop, resolution 41ns [ 0.000347] Console: colour dummy device 80x30 [ 0.000434] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.000455] pid_max: default: 32768 minimum: 301 [ 0.000919] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000935] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.002452] CPU: Testing write buffer coherency: ok [ 0.003214] CPU0: update cpu_capacity 1024 [ 0.003227] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.004266] Setting up static identity map for 0x40100000 - 0x40100054 [ 0.004548] rcu: Hierarchical SRCU implementation. [ 0.005946] smp: Bringing up secondary CPUs ... [ 0.017179] CPU1: update cpu_capacity 1024 [ 0.017192] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.028574] CPU2: update cpu_capacity 1024 [ 0.028585] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.039866] CPU3: update cpu_capacity 1024 [ 0.039877] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.040049] smp: Brought up 1 node, 4 CPUs [ 0.040063] SMP: Total of 4 processors activated (192.00 BogoMIPS). [ 0.040071] CPU: All CPU(s) started in HYP mode. [ 0.040076] CPU: Virtualization extensions available. [ 0.042073] devtmpfs: initialized [ 0.054859] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 [ 0.055247] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.055276] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.064378] xor: measuring software checksum speed [ 0.103945] arm4regs : 598.000 MB/sec [ 0.144054] 8regs : 356.000 MB/sec [ 0.184188] 32regs : 365.000 MB/sec [ 0.224308] neon : 605.000 MB/sec [ 0.224316] xor: using function: neon (605.000 MB/sec) [ 0.224430] pinctrl core: initialized pinctrl subsystem [ 0.226227] NET: Registered protocol family 16 [ 0.230623] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.231531] audit: initializing netlink subsys (disabled) [ 0.231895] audit: type=2000 audit(0.204:1): state=initialized audit_enabled=0 res=1 [ 0.232704] cpuidle: using governor ladder [ 0.232763] cpuidle: using governor menu [ 0.233766] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.233776] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.328896] raid6: int32x1 gen() 89 MB/s [ 0.397151] raid6: int32x1 xor() 76 MB/s [ 0.465276] raid6: int32x2 gen() 122 MB/s [ 0.533403] raid6: int32x2 xor() 94 MB/s [ 0.601559] raid6: int32x4 gen() 123 MB/s [ 0.670046] raid6: int32x4 xor() 92 MB/s [ 0.738275] raid6: int32x8 gen() 118 MB/s [ 0.806317] raid6: int32x8 xor() 82 MB/s [ 0.874403] raid6: neonx1 gen() 235 MB/s [ 0.942731] raid6: neonx1 xor() 219 MB/s [ 1.010959] raid6: neonx2 gen() 316 MB/s [ 1.079151] raid6: neonx2 xor() 283 MB/s [ 1.147283] raid6: neonx4 gen() 379 MB/s [ 1.215543] raid6: neonx4 xor() 318 MB/s [ 1.283811] raid6: neonx8 gen() 341 MB/s [ 1.351973] raid6: neonx8 xor() 288 MB/s [ 1.351981] raid6: using algorithm neonx4 gen() 379 MB/s [ 1.351987] raid6: .... xor() 318 MB/s, rmw enabled [ 1.351994] raid6: using neon recovery algorithm [ 1.354701] SCSI subsystem initialized [ 1.355059] libata version 3.00 loaded. [ 1.355427] usbcore: registered new interface driver usbfs [ 1.355505] usbcore: registered new interface driver hub [ 1.355622] usbcore: registered new device driver usb [ 1.355930] media: Linux media interface: v0.10 [ 1.356000] videodev: Linux video capture interface: v2.00 [ 1.356282] pps_core: LinuxPPS API ver. 1 registered [ 1.356291] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.356336] PTP clock support registered [ 1.358912] clocksource: Switched to clocksource arch_sys_counter [ 1.530605] VFS: Disk quotas dquot_6.6.0 [ 1.530771] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.546050] NET: Registered protocol family 2 [ 1.547394] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes) [ 1.547445] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 1.547542] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 1.547663] TCP: Hash tables configured (established 4096 bind 4096) [ 1.547852] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 1.547912] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 1.548244] NET: Registered protocol family 1 [ 1.549147] RPC: Registered named UNIX socket transport module. [ 1.549155] RPC: Registered udp transport module. [ 1.549162] RPC: Registered tcp transport module. [ 1.549169] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.549600] Trying to unpack rootfs image as initramfs... [ 2.486968] Freeing initrd memory: 7936K [ 2.490248] Initialise system trusted keyrings [ 2.490659] workingset: timestamp_bits=14 max_order=17 bucket_order=3 [ 2.502065] zbud: loaded [ 2.506251] NFS: Registering the id_resolver key type [ 2.506300] Key type id_resolver registered [ 2.506309] Key type id_legacy registered [ 2.506332] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.506340] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 2.508527] JFS: nTxBlock = 3938, nTxLock = 31508 [ 2.529389] Key type asymmetric registered [ 2.529406] Asymmetric key parser 'x509' registered [ 2.529551] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 2.529821] io scheduler noop registered [ 2.529830] io scheduler deadline registered [ 2.530169] io scheduler cfq registered (default) [ 2.530179] io scheduler mq-deadline registered [ 2.530187] io scheduler kyber registered [ 2.530448] io scheduler bfq registered [ 2.532647] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO [ 2.540272] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver [ 2.543274] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [ 2.640693] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [ 2.645020] console [ttyS0] disabled [ 2.665272] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 40, base_baud = 1500000) is a U6_16550A [ 2.665368] console [ttyS0] enabled [ 2.675671] brd: module loaded [ 2.686214] loop: module loaded [ 2.690382] libphy: Fixed MDIO Bus: probed [ 2.691425] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 2.691495] dwmac-sun8i 1c30000.ethernet: No regulator found [ 2.692119] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 2.692133] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 2.692146] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 2.692157] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 2.692169] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 2.692181] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 2.692434] libphy: stmmac: probed [ 2.693278] dwmac-sun8i 1c30000.ethernet: Found internal PHY node [ 2.693450] libphy: mdio_mux: probed [ 2.693486] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY [ 2.693501] dwmac-sun8i 1c30000.ethernet: Powering internal PHY [ 2.703199] libphy: mdio_mux: probed [ 2.704792] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.704802] ehci-platform: EHCI generic platform driver [ 2.705129] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.705180] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.706648] ehci-platform 1c1a000.usb: irq 27, io mem 0x01c1a000 [ 2.718931] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.719433] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.719449] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.719461] usb usb1: Product: EHCI Host Controller [ 2.719472] usb usb1: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.719483] usb usb1: SerialNumber: 1c1a000.usb [ 2.720468] hub 1-0:1.0: USB hub found [ 2.720554] hub 1-0:1.0: 1 port detected [ 2.721962] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.722003] ohci-platform: OHCI generic platform driver [ 2.722294] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.722349] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.722767] ohci-platform 1c1a400.usb: irq 28, io mem 0x01c1a400 [ 2.783385] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 2.783400] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.783412] usb usb2: Product: Generic Platform OHCI controller [ 2.783423] usb usb2: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 2.783434] usb usb2: SerialNumber: 1c1a400.usb [ 2.784329] hub 2-0:1.0: USB hub found [ 2.784416] hub 2-0:1.0: 1 port detected [ 2.786447] usbcore: registered new interface driver usb-storage [ 2.787803] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0 [ 2.787816] sun6i-rtc 1f00000.rtc: RTC enabled [ 2.788172] i2c /dev entries driver [ 2.790642] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0) [ 2.792091] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2 [ 2.793084] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.793531] ledtrig-cpu: registered to indicate activity on CPUs [ 2.793659] hidraw: raw HID events driver (C) Jiri Kosina [ 2.793865] usbcore: registered new interface driver usbhid [ 2.793871] usbhid: USB HID core driver [ 2.801500] Initializing XFRM netlink socket [ 2.802745] NET: Registered protocol family 10 [ 2.818694] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB [ 2.819496] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 2.819627] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 2.837401] Segment Routing with IPv6 [ 2.837586] NET: Registered protocol family 17 [ 2.837629] NET: Registered protocol family 15 [ 2.837729] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 2.837814] 8021q: 802.1Q VLAN Support v1.8 [ 2.837905] Key type dns_resolver registered [ 2.838710] Registering SWP/SWPB emulation handler [ 2.839859] registered taskstats version 1 [ 2.839868] Loading compiled-in X.509 certificates [ 2.840009] zswap: loaded using pool lzo/zbud [ 2.843651] Btrfs loaded, crc32c=crc32c-generic [ 2.855309] mmc0: host does not support reading read-only switch, assuming write-enable [ 2.858476] mmc0: new high speed SDHC card at address aaaa [ 2.859539] Key type encrypted registered [ 2.860784] mmcblk0: mmc0:aaaa SB32G 29.7 GiB [ 2.864517] mmcblk0: p1 [ 2.878655] ehci-platform 1c1c000.usb: EHCI Host Controller [ 2.878710] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 3 [ 2.879720] ehci-platform 1c1c000.usb: irq 29, io mem 0x01c1c000 [ 2.894919] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00 [ 2.895298] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.895313] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.895324] usb usb3: Product: EHCI Host Controller [ 2.895335] usb usb3: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.895346] usb usb3: SerialNumber: 1c1c000.usb [ 2.896329] hub 3-0:1.0: USB hub found [ 2.896406] hub 3-0:1.0: 1 port detected [ 2.897870] ehci-platform 1c1d000.usb: EHCI Host Controller [ 2.897917] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 4 [ 2.898375] ehci-platform 1c1d000.usb: irq 31, io mem 0x01c1d000 [ 2.910946] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00 [ 2.911294] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.911309] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.911320] usb usb4: Product: EHCI Host Controller [ 2.911332] usb usb4: Manufacturer: Linux 4.19.13-sunxi ehci_hcd [ 2.911343] usb usb4: SerialNumber: 1c1d000.usb [ 2.912218] hub 4-0:1.0: USB hub found [ 2.912285] hub 4-0:1.0: 1 port detected [ 2.913620] ohci-platform 1c1c400.usb: Generic Platform OHCI controller [ 2.913676] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 5 [ 2.914052] ohci-platform 1c1c400.usb: irq 30, io mem 0x01c1c400 [ 2.975278] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 2.975293] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.975305] usb usb5: Product: Generic Platform OHCI controller [ 2.975316] usb usb5: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 2.975327] usb usb5: SerialNumber: 1c1c400.usb [ 2.976157] hub 5-0:1.0: USB hub found [ 2.976224] hub 5-0:1.0: 1 port detected [ 2.977540] ohci-platform 1c1d400.usb: Generic Platform OHCI controller [ 2.977582] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 6 [ 2.977963] ohci-platform 1c1d400.usb: irq 32, io mem 0x01c1d400 [ 3.039259] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 3.039274] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.039286] usb usb6: Product: Generic Platform OHCI controller [ 3.039297] usb usb6: Manufacturer: Linux 4.19.13-sunxi ohci_hcd [ 3.039308] usb usb6: SerialNumber: 1c1d400.usb [ 3.040168] hub 6-0:1.0: USB hub found [ 3.040259] hub 6-0:1.0: 1 port detected [ 3.041681] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 3.041816] usb_phy_generic usb_phy_generic.0.auto: Linked as a consumer to regulator.0 [ 3.044310] of_cfs_init [ 3.044466] of_cfs_init: OK [ 3.044576] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 3.044677] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 3.044734] vcc3v0: disabling [ 3.044745] vcc5v0: disabling [ 3.044752] vcc-wifi: disabling [ 3.046216] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.4 [ 3.046327] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 3.055199] Freeing unused kernel memory: 1024K [ 3.067304] Run /init as init process [ 4.284456] lima 1c40000.gpu: bus rate = 200000000 [ 4.284475] lima 1c40000.gpu: mod rate = 384000000 [ 4.284965] [TTM] Zone kernel: Available graphics memory: 252576 kiB [ 4.284973] [TTM] Initializing pool allocator [ 4.286577] lima 1c40000.gpu: gp - mali400 version major 1 minor 1 [ 4.286705] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1 [ 4.286809] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1 [ 4.287015] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus [ 4.289174] [drm] Initialized lima 1.0.0 20170325 for 1c40000.gpu on minor 0 [ 4.292444] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 4.292654] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 4.295874] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.4 [ 4.296016] sunxi-mmc 1c10000.mmc: Dropping the link to regulator.2 [ 4.300760] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.2 [ 4.300881] sunxi-mmc 1c10000.mmc: Linked as a consumer to regulator.4 [ 4.306747] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 4.471019] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB [ 4.484820] sunxi-mmc 1c10000.mmc: no support for card's volts [ 4.484839] mmc1: error -22 whilst initialising SDIO card [ 4.486595] sunxi-mmc 1c10000.mmc: no support for card's volts [ 4.486608] mmc1: error -22 whilst initialising MMC card [ 5.242439] random: fast init done [ 5.273173] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 5.945405] systemd[1]: System time before build time, advancing clock. [ 5.997248] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 5.998075] systemd[1]: Detected architecture arm. [ 6.038122] systemd[1]: Set hostname to <nanopiduo>. [ 6.734729] random: systemd: uninitialized urandom read (16 bytes read) [ 6.735374] systemd[1]: Started ntp-systemd-netif.path. [ 6.747246] random: systemd: uninitialized urandom read (16 bytes read) [ 6.747686] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 6.767131] random: systemd: uninitialized urandom read (16 bytes read) [ 6.768868] systemd[1]: Created slice User and Session Slice. [ 6.784709] systemd[1]: Created slice System Slice. [ 6.800025] systemd[1]: Listening on Journal Socket (/dev/log). [ 6.811597] systemd[1]: Listening on Syslog Socket. [ 6.823672] systemd[1]: Listening on udev Control Socket. [ 7.020660] g_serial gadget: Gadget Serial v2.4 [ 7.020679] g_serial gadget: g_serial ready [ 7.030098] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 7.717854] systemd-journald[247]: Received request to flush runtime journal from PID 1 [ 8.532121] zram: Added device: zram0 [ 8.536882] zram: Added device: zram1 [ 8.541498] zram: Added device: zram2 [ 8.542765] zram: Added device: zram3 [ 8.547628] zram: Added device: zram4 [ 8.551948] zram: Added device: zram5 [ 8.591819] cpu cpu0: Linked as a consumer to regulator.5 [ 8.591980] cpu cpu0: Dropping the link to regulator.5 [ 8.592404] cpu cpu0: Linked as a consumer to regulator.5 [ 8.594027] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594053] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000) [ 8.594221] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594235] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 8.594440] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594455] cpu cpu0: _opp_add: OPP not supported by regulators (1152000000) [ 8.594638] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.594653] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 8.594801] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.594816] cpu cpu0: _opp_add: OPP not supported by regulators (1224000000) [ 8.595133] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.595152] cpu cpu0: _opp_add: OPP not supported by regulators (1248000000) [ 8.595310] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.595323] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 8.595519] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.595533] cpu cpu0: _opp_add: OPP not supported by regulators (1344000000) [ 8.595715] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.595728] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 8.660881] input: r_gpio_keys as /devices/platform/r_gpio_keys/input/input0 [ 8.686443] zram1: detected capacity change from 0 to 64659456 [ 8.893417] sun8i_ths 1c25000.thermal-sensor: no memory resources defined [ 8.893462] sun8i_ths: probe of 1c25000.thermal-sensor failed with error -22 [ 8.944511] thermal thermal_zone0: failed to read out thermal zone (-110) [ 9.795151] Adding 63140k swap on /dev/zram1. Priority:5 extents:1 across:63140k SSFS [ 9.809915] zram2: detected capacity change from 0 to 64659456 [ 10.853228] Adding 63140k swap on /dev/zram2. Priority:5 extents:1 across:63140k SSFS [ 10.856888] zram3: detected capacity change from 0 to 64659456 [ 11.153417] random: crng init done [ 11.153437] random: 7 urandom warning(s) missed due to ratelimiting [ 11.262534] Adding 63140k swap on /dev/zram3. Priority:5 extents:1 across:63140k SSFS [ 11.266098] zram4: detected capacity change from 0 to 64659456 [ 11.296137] Adding 63140k swap on /dev/zram4. Priority:5 extents:1 across:63140k SSFS [ 11.421362] zram0: detected capacity change from 0 to 52428800 [ 11.795961] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [ 14.546107] EXT4-fs (mmcblk0p1): resizing filesystem from 226304 to 7712800 blocks [ 26.674028] EXT4-fs (mmcblk0p1): resized to 3145728 blocks [ 37.360914] EXT4-fs (mmcblk0p1): resized to 5767168 blocks [ 45.342118] EXT4-fs (mmcblk0p1): resized filesystem to 7712800 [ 49.293013] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 49.297171] Generic PHY 0.1:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0.1:01, irq=POLL) [ 49.303114] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 49.303138] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 49.303151] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 49.304029] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  11. The latest img for the nanopi-duo the h2+ overlays for i2c, spi,1wire are missing . seems the build has some issues.... I cant load up the parts I need for testing.
  12. terminal command to connect 1)wifi (using username and password). 2)hotspot os i am using is Armbian_5.65_Nanopiduo_Debian_stretch_next_4.14.78.
  13. I connected FA-CAM202 ( 2M USB cam provided by FriendlyArm) to USB2 pins on Nanopi Duo, The OS is Armbian Bionic mainline kernel 4.14.y The V4l applications output error as Unable to start capture: Input/output error i: Error grabbing frames The dmesg shows uvcvideo: Failed to query (GET_CUR) UVC control 3 on unit 1: -32 uvcvideo: Failed to set UVC commit control : -32 (exp. 26) This Cam FA-CAM202 is worked on PC while other USB CAM such as Logitech works on the same configuration of Nanopi Duo, on USB2. It is more like a driver compatibility issues, do we have parameters to try or something else we can let the UVC CAM which worked on PC run on Armbian ? Tks
  14. Hi, how you decode video on Nanopi Duo with hardware acceleration? Have you any images or instruction how i could test hardware acceleration by using Nanopi duo? Mainline kernel doesn't support hardware acselleration, right? I tried build image with legacy kernal (3.4.x), but it doesn't run. Any ideas?
  15. I just flashed https://dl.armbian.com/nanopiduo/Ubuntu_bionic_next.7z and it doesn't appear to detect the onboard wifi. ip a only shows lo and eth0. I'm going to try the expansion board with Ethernet onboard and see what shows up. OK, just tried this on a adapter board with Ethernet and now there's an eth0 and Wired Connection 1. It appears the eth0 is really the wifi adapter, but nmtui treats it like an Ethernet connection. Same issue with https://dl.armbian.com/nanopiduo/Debian_stretch_next.7z Wifi not detected, but eth0 is detected instead of wlan0.
  16. Hi, I'm trying to use the popular LTE USB modem Huawei E3372s (Stick mode) with NanoPi Duo. Modem is in Network card mode - USB_Modeswitch was installed and started root@nanopiduo:~# lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0525:a4a7 Netchip Technology, Inc. Linux-USB Serial Gadget (CDC ACM mode) Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub WVDial is installed and configured: /etc/wvdial.conf [Dialer Orange] Modem = /dev/ttyUSB1 Init3 = AT+CGDCONT=1,"IP","internet" Username = "internet" Password = "internet" Phone = "*99#" Dial Command = ATDTW Stupid Mode = yes Dial Attempts = 0 the connection to my provider is going fine: root@nanopiduo:~# wvdial orange& [1] 2752 root@nanopiduo:~# --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 ATQ0 V1 E1 S0=0 OK --> Sending: AT+CGDCONT=1,"IP","internet" AT+CGDCONT=1,"IP","internet" OK --> Modem initialized. --> Sending: ATDTW*99# --> Waiting for carrier. ATDTW*99# CONNECT --> Carrier detected. Starting PPP immediately. --> Starting pppd at Mon Jan 29 06:38:27 2018 --> Pid of pppd: 2753 --> Using interface ppp0 --> local IP address 10.89.114.208 --> remote IP address 10.64.64.64 --> primary DNS address 194.204.159.1 --> secondary DNS address 194.204.152.34 root@nanopiduo:~# ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b2:9b:24:4e:11:e2 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 35 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 64 bytes 5184 (5.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 64 bytes 5184 (5.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.93.28.221 netmask 255.255.255.255 destination 10.64.64.64 ppp txqueuelen 3 (Point-to-Point Protocol) RX packets 7 bytes 106 (106.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 157 (157.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 12:42:33:5d:22:81 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 but I can't ping nothing on the Internet: root@nanopiduo:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ^C --- 8.8.8.8 ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7254ms The modem (E3372s) with RPi 3 and latest Raspbian works perfectly. Also plugged into my Windows 10 PC works OK. Nano Pi Duo is powered from good 3A 5V power source and USB socket for Huawei 3371s is separately powered from this same source (not via pins on Nano Pi Duo). checked with: Armbian_5.38_Nanopiduo_Debian_stretch_next_4.14.15, Armbian_5.38_Nanopiduo_Ubuntu_xenial_next_4.14.15.img and also with nanopi-duo_friendlycore-xenial_4.14.52_20180628.img. If you have any idea what should I check any suggestions will be very appreciated. Slawek
  17. OK, folks, I have I2C working for Luma.OLED, but now I'm trying an SPI display (SSD1331) and having some issues. I modified OPi.GPIO pin mappings as follows (see below), but I'm wondering if my SPI configuration is correct. I'm using overlays=spi-spidev and param_spidev_spi_bus=1, but I'm wondering if I should also be using CS1 configuration as well since I'm using SPI bus 1 (bus 0 is reserved for flash). i.e. param_spidev_spi_cs=1 and overlays=spi-add-cs1. I only ask this because the Luma.OLED instructions say "Because CS is connected to CE0, the display is available on SPI port 0. You can connect it to CE1 to have it available on port 1. If so, pass port=1 in your serial interface create call." I tried it without the CS settings and nothing happens on the display. # NanoPi Duo physical pin to actual GPIO pin BOARD: { 3: 12, # I2C0_SDA/GPIOA12 5: 11, # I2C0_SCL/GPIOA11 7: 203, # GPIOG11 8: 198, # UART1_TX/GPIOG6 10: 199, # UART1_RX/GPIOG7 11: 5, # DEBUG_RX(UART_RXD0)/GPIOA5/PWM0 12: 363, # GPIOL11/IR-RX 13: 4, # DEBUG_TX(UART_TXD0)/GPIOA4 19: 15, # UART3_RTS/SPI1_MOSI/GPIOA15 21: 16, # UART3_CTS/SPI1_MISO/GPIOA16 23: 14, # UART3_RX/SPI1_CLK/GPIOA14 24: 13 # UART3_TX/SPI1_CS/GPIOA13 }, # NanoPi Duo BCM pin to actual GPIO pin BCM: { 2: 12, # I2C0_SDA/GPIOA12 3: 11, # I2C0_SCL/GPIOA11 4: 203, # GPIOG11 8: 13, # UART3_TX/SPI1_CS/GPIOA13 9: 16, # UART3_CTS/SPI1_MISO/GPIOA16 10: 15, # UART3_RTS/SPI1_MOSI/GPIOA15 11: 14, # UART3_RX/SPI1_CLK/GPIOA14 14: 198, # UART1_TX/GPIOG6 15: 199, # UART1_RX/GPIOG7 17: 5, # DEBUG_RX(UART_RXD0)/GPIOA5/PWM0 18: 363, # GPIOL11/IR-RX 27: 4 # DEBUG_TX(UART_TXD0)/GPIOA4 },
  18. I cannot get SPI working on my Nanopi Duo or rather there is no /dev/spi*. I build a custom Kernel with the build process and Network and other stuff works. Loading the spi-spidev overlay in various ways did not help. (Loading via U-Boot, during runtime, combine the overlay and devicetree and compile it as whole) By the way, the Images from https://www.armbian.com/nanopi-duo/ are not even booting through U-Boot for me. Some Infos:
  19. @Igor at the /etc/update-motd.d/30-sysinfo on my armbian debian stretch it didnt show the cpu-temp line after the login I did take a look at the file /etc/update-motd.d/30-sysinfo and didnt under stand the actual funtion getboardtemp: function getboardtemp() { if [ -f /etc/armbianmonitor/datasources/soctemp ]; then read raw_temp </etc/armbianmonitor/datasources/soctemp 2>/dev/null if [ ! -z $(echo "$raw_temp" | grep -o "^[1-9][0-9]*\.\?[0-9]*$") ] && (( $(echo "${raw_temp} < 200" |bc -l) $ # Allwinner legacy kernels output degree C board_temp=${raw_temp} else # Marvell gets special treatment for whatever reasons grep -qi Marvell /proc/cpuinfo && \ board_temp=$(( $(awk '{printf("%d",$1/1000)}' <<<${raw_temp}) - 20 )) || \ board_temp=$(awk '{printf("%d",$1/1000)}' <<<${raw_temp}) fi elif [ -f /etc/armbianmonitor/datasources/pmictemp ]; then # fallback to PMIC temperature board_temp=$(awk '{printf("%d",$1/1000)}' </etc/armbianmonitor/datasources/pmictemp) fi } # getboardtemp BUT if I did do it cut down to: function getboardtemp() { if [ -f /etc/armbianmonitor/datasources/soctemp ]; then # Allwinner legacy kernels output degree C board_temp=$(awk '{printf("%.2f",$1/1000)}' </etc/armbianmonitor/datasources/s$ elif [ -f /etc/armbianmonitor/datasources/pmictemp ]; then # fallback to PMIC temperature board_temp=$(awk '{printf("%d",$1/1000)}' </etc/armbianmonitor/datasources/pmi$ fi } # getboardtemp I do get a CPU-temp line at the Welcome-Message after the login-screen. For me it looks like that the mainline-kernel also output degree C (not only legacy like in the commecnt-line). My NanoPi Duo as Information: System diagnosis information will now be uploaded to http://ix.io/15r6
  20. I just got 4 NanoPi Duos v1.1 and the OTG port functions (unlike v1.0)! This is with the FriendlyElec image. I was wondering should I compare the FriendlyElec's sun8i-h2-plus-nanopi-duo.dtb to the one on Armbian? I already tried messing with Armbian's sun8i-h2-plus-nanopi-duo.dtb by changing usb@01c19000 status = "okay" and adding dr_mode = "host". I'm not sure I can just drop in the dtb? Any way, I'll see what I can figure out. I'm excited the OTG port works now for more than just power since that saves you from buying the Mini Shield if you have a simple project that just needs a USB drive or camera.
  21. dear all , thank you for the armbian os which is work more than great with me , I already bought DLINK DWM-157 and follow the installation steps , and as i see all going fine with me , but when i connect the modem i receive this output , [ 64.089219] usb 2-1: device descriptor read/64, error -71 [ 64.579198] usb 2-1: device descriptor read/64, error -71 [ 65.209195] usb 2-1: device descriptor read/64, error -71 [ 66.659297] scsi 0:0:0:0: rejecting I/O to offline device [ 69.969188] scsi 0:0:0:0: rejecting I/O to offline device [ 72.924173] usbserial_generic 2-1:1.0: device has no bulk endpoints [ 72.949655] usbserial_generic 2-1:1.1: device has no bulk endpoints [ 74.052684] sd 0:0:0:0: [sda] Asking for cache data failed [ 74.058213] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 89.047207] usbserial_generic 2-1:1.0: device has no bulk endpoints [ 158.137210] usbserial_generic 2-1:1.0: device has no bulk endpoints [ 195.367217] usbserial_generic 2-1:1.0: device has no bulk endpoints this is link for the steps http://ftp.dlink.ru/pub/usb/DWM-157/Description/D-Link DWM-157 Linux guide.pdf please any advice will be appreciated, as also , i connect the modem to windows 10 , and work fine without any issue ... wait for you all regards
  22. I'm wanting to connect a Raspberry Pi Zero to my NanoPi Duo via USB Ethernet OTG. Has anyone gotten this to work? I've been following instructions posted at different sites (here's one - https://dev.webonomic.nl/connecting-to-a-raspberry-pi-zero-with-just-an-usb-cable-i) and I can get it to work via my desktop (with Debian) and a Raspberry Pi Zero and between RPI3 and RPI0, but can't seem to get it to work between NanoPi Duo and RPI0. Of course, I don't have a desktop on the NanoPi Duo, so everything has to be done via command line.
  23. I've been trying to change the I2C clock frequency on a NanoPi Duo doing the following: cd /boot/dtb sudo cp sun8i-h2-plus-nanopi-duo.dtb sun8i-h2-plus-nanopi-duo.dtb.old sudo dtc -I dtb -O dts -o sun8i-h2-plus-nanopi-duo.dts sun8i-h2-plus-nanopi-duo.dtb sudo nano sun8i-h2-plus-nanopi-duo.dts in i2c@01f02400 section change clock-frequency = <0x186a0> to clock-frequency = <0x30d40> (200 KHz) sudo dtc -I dts -O dtb -o sun8i-h2-plus-nanopi-duo.dtb sun8i-h2-plus-nanopi-duo.dts reboot Looking in armbianEnv.txt I have overlay_prefix=sun8i-h3 and cat /proc/device-tree/model shows FriendlyARM NanoPi DUO. The issue is that no matter what I change clock-frequency to it stays the same i.e. 100 KHz. Either I'm changing the wrong value or I have the wrong template?
  24. The Luma library allows you to display text, graphics, animation, etc. on multiple display types. Here I will describe the easiest one to configure which is Luma.OLED and the I2C version of the SSD1306. You can find these displays on EBay and Amazon for less than $10 US each (you can get them for less than $3 US if you order from China, but it might not show up). I've configured Luma on many SBCs and it's my go to library if I need a small display for projects. Requirements NanoPi Duo (I used V1.0 board with 512 MB RAM) flashed with Armbian image. This will work with or without the mini shield. Small nylon nuts, bolts and standoffs if you want to mount display I2C OLED display (check http://luma-oled.readthedocs.io/en/latest/hardware.html) 4 female to female jumper wires If you want to configure wifi the easy way just edit the following file on the SD sudo nano /media/username/43296f0d-fc9e-4cec-b3bf-f335fc72f371/etc/network/interfaces and add: allow-hotplug wlan0 iface wlan0 inet static address 192.168.1.69 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 wpa-ssid your_ssid wpa-psk your_password Comment out the eth0 stuff. You can do it the hard way with the debug serial interface though if you want When I ordered my Duos I forgot to order the USB dongle, so I would have been out of luck otherwise. Boot up and configure the Duo the way you like, power off and wire up the display as follows: VCC to either 5Vin or 3V3 GND to GND SCL to SCL SDA to SDA Power up Duo and configure I2C: sudo nano /boot/armbianEnv.txt and add i2c0 to overlays= sudo apt-get install i2c-tools sudo usermod -a -G i2c username (non-root user you created) sudo 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- If you see the 3c on i2c0 then you are in business. Let's install Luma.OLED: sudo apt-get install python-dev python-pip libfreetype6-dev libjpeg-dev sudo -H pip install --upgrade pip sudo apt-get purge python-pip sudo -H pip install --upgrade pip setuptools sudo -H pip install --upgrade luma.oled sudo -H pip uninstall RPi.GPIO (this will not work on Duo and is not needed for I2C) OK, let's create a simple demo program to make sure things are working nano i2chello.py: import time from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306 serial = i2c(port=0, address=0x3C) device = ssd1306(serial) with canvas(device) as draw: draw.rectangle(device.bounding_box, outline="white") draw.text((3, 3), "Hello", fill="white") time.sleep(10) And you should see (screen shot from the Luma emulator): Now we can install the Luma examples: sudo apt-get install git-core libsdl-dev libportmidi-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-image1.2-dev git clone https://github.com/rm-hull/luma.examples.git cd luma.examples sudo -H pip install -e . Let's run an example: sudo python examples/invaders.py -d ssd1306 --i2c-port 0 --i2c-address 0x3c
  25. I've built https://github.com/auto3000/RPi.GPIO_NP for the Duo running Armbian Ubuntu test image: cd /sys/class/gpio for i in gpiochip* ; do echo `cat $i/label`: `cat $i/base` ; done 1c20800.pinctrl: 0 1f02c00.pinctrl: 352 Has anyone actually got RPi.GPIO working on Duo? I'm trying to get luma.oled cranking and have SPI working fine, but need GPIO working as well.
×
×
  • Create New...