Jump to content

Search the Community

Showing results for tags 'nanopiduo2'.

  • 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
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • 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
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Location


Interests

Found 13 results

  1. Hello all. I have a Nanopi due2 with Armbian. I've enabled my SPI in armbianEnv.txt file and with: overlays=spi-add-cs1 spi-spidev usbhost0 usbhost2 usbhost3 param_spidev_spi_bus=1 param_spidev_spi_cs=1 but when I try to use "/dev/spidev1.1", CS pin is active high by default not active low. how can I change it to active low.
  2. Hi folks! So first here is the key question: Did anyone get exactly this combination NanoPi Duo2, ov5640 camera, armbian focal running? If YES, HOW … ? 😊 Details below. btw. buster would be also fine... uname -a output is Linux nanopiduo2 5.10.34-sunxi #21.05.1 SMP Thu May 6 20:13:21 UTC 2021 armv7l armv7l armv7l GNU/Linux I’m quite new to Linux and Armbian and have a slight problem using an Nanopi Duo2 and an ov5640 camera. It works pretty well using the image from FriendlyElec. This has been tested using the mjpg-streamer. Due to this success I’m sure the entire hardware setup is correct. Unfortunately the ov5640 camera does not work using mjpg-streamer as before with the armbian focal image. Also some testing with ffmpeg did not work. I can explain in more detail what β€œdoes not work” means. Ideally I’d like to have the mjpg-streamer (or the later experimental) in a working shape for testing purposes. THEN I can decide how to proceed with my own development. ffmpeg would be also okay for testing. For me it looks like ffmpeg fails for other reasons. I did dig through several newsgroups but could not identify the root cause. Here is what I verified or tested: 1) i2cdetect 2 output is correct. It shows the device on address 0x3c I’m not sure if that worked from the beginning after several changes but this didn’t impact at all the failing camera. 2) v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/video0 /dev/media0 3) v4l2-ctl --list-formats ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'ST12' (Sunxi Tiled NV12 Format, compressed) [1]: 'NV12' (Y/CbCr 4:2:0) 4) modprobe ov5640 does not show any errors inside the dmesg output. Interestingly after rmmod and modprobe frame_rate=2 there IS an error β€œunknown parameter”. This means THIS current module as part of the kernel doesn’t have that parameter as specified elsewhere. 5) I also played a little with dtb overlays but still no success. The last β€œhardcore test” 😊 was putting in the friendlyArm dtb into the armbian image but that caused other errors. Thanks in advance!
  3. Hi, I am looking to Secure Boot Allwinner H3. We use Nano Pi Duo2 with latest Armbian OS. End goal is to have all the OS / Data on the SD Card Encrypted. Can anybody help ?
  4. Hi, Nano pi duo 2 module I2C is not working in kernal Armbian Focal 5.10.21. I have camera OV5640 attached to Nano PI duo 2 via I2C 2 I found my I2C2 is disable how can I enable? root@nanopiduo2:~# fdtget /boot/dtb/sun8i-h3-nanopi-duo2.dtb /soc/i2c@1c2b400 status disabled I found I2C 2 which is connect to camera is not working root@nanopiduo2:~# ls -l /sys/class/i2c-adapter/ total 0 the I2C detect command and sometimes armbianmonitor does not genetrate the link, root@nanopiduo2:~# i2cdetect -y 0 Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory root@nanopiduo2:~# i2cdetect -y 1 Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory root@nanopiduo2:~# i2cdetect -y 2 Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or directory root@nanopiduo2:~# sudo armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the Please find the image the boot Environment is changes in the device (reffer attachment) but the link file its not changed which is real? System diagnosis information will now be uploaded to http://ix.io/2Tb2 Please post the URL in the forum where you've been asked for.
  5. Hi, I have a problem with usbhost on a NanoPi Duo2 with Armbian Bionic: Linux nanopiduo2 4.19.36-sunxi #5.82 SMP Mon Apr 22 19:12:08 CEST 2019 armv7l armv7l armv7l GNU/Linux Everything works fine so far except for USB hosts. None of the connected USB devices is detected. I am quite sure that the voltage supply is stable. I tried to power the board in two ways: From an USB powerbank (2A) with a short USB cable From a laboratory power supply (1.5A) directly connected to the 5V and GND power pins In both cases, the board works ablsolutely stable, no reboots, no SD card issues, even with some I2C devices and a GPS receiver connected to UART and Wifi networking. However, no USB host. I am using a USB connector breakout board with very short connections to the NanoPi (everything mounted on a breadboard). VUSB and GND are connected to 5V/GND with ~2 cm wires. I have tried USB2 and USB3, and I have tried to swap D+ and D- on both ports. USBHOST0, 2, and 3 are enabled in armbian-config and the overlays are loaded at boot: ... 374 bytes read in 9 ms (40 KiB/s) Applying kernel provided DT overlay sun8i-h3-i2c0.dtbo 502 bytes read in 9 ms (53.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-uart1.dtbo 504 bytes read in 9 ms (54.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4155 bytes read in 9 ms (450.2 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ... lsusb reports always the following, no matter if there is any USB device connected: :~$ lsusb 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 and :~$ dmesg |grep usb [ 0.000000] Kernel command line: root=UUID=82ac9789-2ef5-473c-81a2-1c4d59545882 rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=5065b6de-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 1.360294] usbcore: registered new interface driver usbfs [ 1.360374] usbcore: registered new interface driver hub [ 1.360504] usbcore: registered new device driver usb [ 2.567569] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO [ 2.788367] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.788422] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.789881] ehci-platform 1c1a000.usb: irq 27, io mem 0x01c1a000 [ 2.804274] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.804769] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.804784] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.804796] usb usb1: Product: EHCI Host Controller [ 2.804807] usb usb1: Manufacturer: Linux 4.19.36-sunxi ehci_hcd [ 2.804818] usb usb1: SerialNumber: 1c1a000.usb [ 2.807807] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.807874] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.808350] ohci-platform 1c1a400.usb: irq 28, io mem 0x01c1a400 [ 2.872742] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 [ 2.872758] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.872770] usb usb2: Product: Generic Platform OHCI controller [ 2.872781] usb usb2: Manufacturer: Linux 4.19.36-sunxi ohci_hcd [ 2.872792] usb usb2: SerialNumber: 1c1a400.usb [ 2.876097] usbcore: registered new interface driver usb-storage [ 2.884958] usbcore: registered new interface driver usbhid [ 2.884964] usbhid: USB HID core driver [ 2.969162] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 2.976654] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 2.982968] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 2.991897] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 4.236043] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 4.480475] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 8.757860] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 8.798639] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.048938] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.078126] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.155500] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.176147] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.211080] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.269968] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 9.299488] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 14.705827] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe I can not interpret the 'Couldn't get regulator' message... perhaps this is the problem? Possibly something wrong with the device tree? There is no further output in demsg when dis/connecting a USB device. I have tried several USB sticks: memory, RTL-SDR, Bluetooth, IR, but no success. Interestingly, the lsusb and dmesg outputs are exactly the same as shown above if USBHOST2 and 3 are disabled in armbian-config. I am running out of ideas, so any suggestions are welcome, Thanks.
  6. When installing snaps I get the following error: error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-910419852: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. It worked about a mouth ago but now whenever I build the images and try to install a snap I get that error. Steps to reproduce: 1. Build Nanopi Duo2 image with kvm and squashfs 2. Connect to device and install snapd 'sudo apt install snapd' 3. Install snap to test it 'sudo snap install hello-world' Expectation: Snaps work as this is the same process that I did before to use snaps on armbian image for this device Result: Getting the error I have tried multiple sd cards, multiple nanopi duo2 devices and both 18.04 and 20.04 images.
  7. I am not sure if this is intended or bug, When building the image for Nanopi duo2 I cannot add kvm. This worked before so I guess that this is regression. I get this search result for kvm in the build process: β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ Search Results ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ β”‚ Symbol: KVM [=KVM] β”‚ β”‚ Type : unknown β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ Symbol: DRM_I915_GVT_KVMGT [=n] β”‚ β”‚ Type : tristate β”‚ β”‚ Defined at drivers/gpu/drm/i915/Kconfig:122 β”‚ β”‚ Prompt: Enable KVM/VFIO support for Intel GVT-g β”‚ β”‚ Depends on: HAS_IOMEM [=y] && DRM_I915_GVT [=n] && KVM && VFIO_MDEV [=n] && VFIO_MDEV_DEVICE [=n] β”‚ β”‚ Location: β”‚ β”‚ -> Device Drivers β”‚ β”‚ (1) -> Graphics support β”‚ β”‚ -> Intel 8xx/9xx/G3x/G4x/HD Graphics (DRM_I915 [=n]) β”‚ β”‚ -> Enable Intel GVT-g graphics virtualization host support (DRM_I915_GVT [=n]) β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ Symbol: KVM_GUEST [=KVM_GUEST] β”‚ β”‚ Type : unknown β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ Symbol: PTP_1588_CLOCK_KVM [=n] β”‚ β”‚ Type : tristate β”‚ β”‚ Defined at drivers/ptp/Kconfig:106 β”‚ β”‚ Prompt: KVM virtual PTP clock β”‚ β”‚ Depends on: PTP_1588_CLOCK [=y] && KVM_GUEST && X86 β”‚ β”‚ Location: β”‚ β”‚ -> Device Drivers β”‚ β”‚ (2) -> PTP clock support
  8. I started compiling some project (snowboy ) on the nanopiDuo2 like I am doing on the FriendlyCore 16.04 and suddenly the board stop working/booting. The red led is blinking fast, the same sd card is working on different boards, FriendlyCore does not boot on this board. "provide a log from serial console" I don't have serial cable yet. This happened to me twice, on Armbian 18.04 and on 20.04. First it destroyed the "IoT-2G Application Carrier Board for NanoPi Duo2" that it was on without the board, and the carrier had burnt smell, internet cable and power were connected. For one of them the red led is blinking fast, for the other the led does not blink at all (I can upload video of the red led if it helps). Just the last time it was compiling snowboy, the others I don't remember. I am uploading the Armbianmonitor of the last sd card but using different board.
  9. Hi all, Firstly, I want to say that I'm new to Armbian and embedded Linux. I have tried searching the solution for my problem on various sites but I haven't had any luck. I am using a Nano Pi Duo 2 (H3) board with Armbian Buster to communicate with another device through UART1 (TX1, RX1). I am able to communicate at 115200 bps with no problem. However, I need the baud rate to be at least 230400 bps (ideally 921600) for my application. I'm using WiringNP library. When I changed to those baud rates and performed a simple feedback test (shorting TX/RX), I can receive the data. But when I connect it to another device, the communication does not function correctly. I read from this thread that the UART baud depends on the UART clock frequency because of <2.5% error. I believe that the current UART clock is 24 MHz. After checking this table out, I think I need my UART clock to be at least 30 MHz to get the baud rates above. I successfully change the I2C clock from 100 kHz to 400 kHz by following this thread. Can I do the same thing for my UART clock? Could anyone please help me with this problem? Thank you so much in advance. I've been struggling with this problem.
  10. WiringNP does not work on NanopiDuo2, both in 18.04 and Ubuntu 20.04 Error piBoardRev: Unable to determine board revision from /proc/cpuinfo -> Is not NanoPi based board. -> You may want to check: -> http://www.lemaker.org/ open /sys/class/su Armbian /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Allwinner sun8i Family Revision : 0000 Serial : 02c00181e49e909a vs friendlyarm OS /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : sun8i Revision : 0000 Serial : 02c00081af9196e6 Armbian /sys/class/sunxi_info/sys_info file does not exist. vs friendlyarm /sys/class/sunxi_info/sys_info file content: sunxi_platform : sun8iw7p1 sunxi_secure : normal sunxi_chipid : unsupported sunxi_chiptype : unsupported sunxi_batchno : unsupported sunxi_board_id : 8(0) board_manufacturer: FriendlyElec board_name : FriendlyElec NanoPi-Duo2
  11. Not sure if this is the right forum, or it should be under board bringup.... I have a few Duo2 boards running with the FriendlyElec image, but my OrangePi boards all run Armbian... I do prefer Armbian :-) . Playing around a little I can get the Nanopi Neo Air image running, but not with the wired ethernet. (My boards reside on my own design with a ethernet jack, which works perfect with the FE/FA image) I have the Armbian build environment running in a VM, and can compile my own kernel etc. ButI need a few pointers how to get the right board config in the image/kernel.... Or... Does someone already have a build setup running for the Duo2, who is willing to share it? Thanks in advance for your time..! Paul
  12. Is there a plan for supporting the "NanoPi Duo2" from"friendlyarm" in the future? http://wiki.friendlyarm.com/wiki/index.php/NanoPi_Duo2
  13. I'm working on a Duo project that needs SPI and this is how I configured and tested it without the mini shield. Requirements: NanoPi Duo with test Armbian image 1 female to female jumper wire Enable SPI on boot: sudo nano /boot/armbianEnv.txt Add spi-spidev to overlays= Add line param_spidev_spi_bus=1 sudo reboot If everything worked you should have /dev/spidev1.0. Check with ls /dev/spi*. Now we can test with a C program: cd wget http://www.raspibo.org/renzo/spidev_test.c gcc -o spidev_test spidev_test.c sudo ./spidev_test -D /dev/spidev1.0 spi device: /dev/spidev1.0 spi mode: 0 bits per word: 8 max speed: 500000 Hz (500 KHz) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 shutdown now -h then wire up MO and MI pins with jumper to create loop back and power up sudo ./spidev_test -D /dev/spidev1.0 spi device: /dev/spidev32766.0 spi mode: 0 bits per word: 8 max speed: 500000 Hz (500 KHz) FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF DE AD BE EF BA AD F0 0D OK, let's try some Python now: sudo apt-get update sudo apt-get install python-dev sudo apt-get install python-pip sudo -H pip install --upgrade pip setuptools sudo -H pip install --upgrade spidev nano spitest.py import spidev input = [1 ,2 ,3, 4, 5] print "input: %s" % input spi = spidev.SpiDev() spi.open(1,0) output = spi.xfer2(input) print "output: %s" % output Save code and run program: sudo python spitest.py input: [1, 2, 3, 4, 5] output: [1, 2, 3, 4, 5]
Γ—
Γ—
  • Create New...