Jump to content

Search the Community

Showing results for tags 'nanopiair'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

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. Hi, I was looking the wiki, but I didn't find if is it possible to connect a RJ45 jacket to Nano PI NEO Air. If yes, what are the pins? Best regards, Marcos Sousa
  2. Guest

    lirc_gpio

    Why not to add lirc_gpio support to NanoPiNeo Air ? Even if it is not planned, I try to use this patch : https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sun7i-default/0050-lircgpio_and_raw.patch Kernel compilation is ok for me : apt-get -y install git git clone https://github.com/igorpecovnik/lib --depth 1 cp lib/compile.sh . ./compile.sh I try to apply this patch now : ~/crosscompile/lib/patch/kernel/sun7i-default/0050-lircgpio_and_raw.patch I expected to have a lircgpio.ko somewhere, but nothing. Is there a procedure or a tutorial or some help to build a driver ?
  3. Guest

    insmod gpio-ir-recv.ko

    Hello All, I am on NanoPiAir, I really want to use my home made ir receiver with this board haha So I try : insmod /lib/modules/3.4.113-sun8i/kernel/drivers/media/rc/gpio-ir-recv.ko and I have : insmod: ERROR: could not insert module gpio-ir-recv.ko: Unknown symbol in module In another side I tried to build a lircgpio.ko with a patch but I can't find the .ko generated despite kernel compilation succeed. If someone can help, this should be great
  4. Hi, I am using ARMBIAN 5.25 stable Ubuntu 16.04.2 LTS 3.4.113-sun8i on my Nanopi neo air. uname -a says Linux nanopiair 3.4.113-sun8i #10 SMP PREEMPT Thu Feb 23 19:55:00 CET 2017 armv7l armv7l armv7l GNU/Linux I think, since I made the last apt-get upgrade and rebooted, my bluetooth stopped working. lsmod gives: lsmod Module Size Used by bmp085 3487 0 pcf8591 3363 0 snd_usb_audio 80352 0 snd_hwdep 5562 1 snd_usb_audio snd_usbmidi_lib 17545 1 snd_usb_audio snd_rawmidi 17134 1 snd_usbmidi_lib gspca_ov534 9254 0 gspca_main 19688 1 gspca_ov534 g_serial 27617 2 dhd 666855 0 hidp 12949 0 rfcomm 32879 0 hci_uart 20384 0 bluetooth 174097 5 hidp,hci_uart,rfcomm btrfs 712409 0 on another neo air with older system Linux nanopiair 3.4.113-sun8i #28 SMP PREEMPT Thu Feb 2 02:01:28 CET 2017 armv7l armv7l armv7l GNU/Linux lsmode it said: Module Size Used by bnep 9617 2 bmp085 3487 0 pcf8591 3363 0 g_serial 27617 2 dhd 666855 0 hidp 12949 0 rfcomm 32879 0 hci_uart 20384 1 bluetooth 174097 25 bnep,hidp,hci_uart,rfcomm btrfs 712409 0 I also tried to install a nightly build Armbian_5.26.170227_Nanopiair_Ubuntu_xenial_dev_4.10.0 but there was no bluetooth on this build as well. Any Ideas, what I can do to get my hci0 device back? Thank you very much and best regards, David
  5. Hi All, I'm trying to use mic and line-out on nano pi neo air. I did this regarding to topics I found : apt-get install pulse-audio pulseaudio -D I tried some modifications in this file without succeed for the moment : /etc/pulse/daemon.conf I use alsamixer to check volume control but I have no sound when I do : speaker-test -c4 -l1 -twav Does analog audio or mic input are avaliable on nano pi neo air ? http://nanopi.io/nanopi-neo-air.html Best Regards
  6. I received NanoPi NEO and NEO Air boards along with the NanoHat PCM5102a that FriendlyArm is selling: http://www.friendlyarm.com/index.php?route=product/product&product_id=169 It's a good quality audio stereo out addon board compatible with NEO and NEO Air. I got it working with Armbian on NEO Air! I adapted commits from FA's repo to match Armbian's tree and get that DAC working, (original commits here: https://github.com/friendlyarm/h3_lichee/search?utf8=%E2%9C%93&q=pcm5102a+&type=Commits). Add these to 'userpatches/kernel/sun8i-default`: https://gist.github.com/Simon-L/c8c119c86d7d3fe4316387c3ae818379 Add this config to 'userpatches' to have the driver built-in: https://gist.github.com/Simon-L/56bf6a3ec423e37973ee0da0bc16979f Then run './compile.sh' The fex file also needs to be modified, you can use this one: https://gist.github.com/Simon-L/f0c88190814f0f482773e81512e56553 This should be all that's needed! Test it with 'aplay /usr/share/sounds/alsa/Noise.wav' and install madplay if you want to try with mp3 files. Can I safely share the content of the /boot folder and expect it to work for user copy-pasting it to the /boot folder on their sdcard? It has the kernel and the fex which are the only files the process has modified. Obviously you'd still have to trust me I'm trying to turn this into a more straightforward way. Do I need to commit to modify defconfig and .fex file or is it supported in userpatches/ folder as well? There is one issue reported in syslog that doesn't seem to prevent it from working, here's the relevant part of the log: [ 1.598532] pcm5102a_probe [ 1.607823] asoc: snddaudio <-> pri_dai mapping ok [ 1.610531] ------------[ cut here ]------------ [ 1.610583] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x8c/0xac() [ 1.610604] sysfs: cannot create duplicate filename '/devices/platform/snddaudio' [ 1.610625] Modules linked in: [ 1.610694] [<c0016a20>] (unwind_backtrace+0x0/0xe8) from [<c0617cc0>] (dump_stack+0x20/0x24) [ 1.610742] [<c0617cc0>] (dump_stack+0x20/0x24) from [<c0029750>] (warn_slowpath_common+0x5c/0x74) [ 1.610788] [<c0029750>] (warn_slowpath_common+0x5c/0x74) from [<c00297a8>] (warn_slowpath_fmt+0x40/0x48) [ 1.610833] [<c00297a8>] (warn_slowpath_fmt+0x40/0x48) from [<c017aab8>] (sysfs_add_one+0x8c/0xac) [ 1.610877] [<c017aab8>] (sysfs_add_one+0x8c/0xac) from [<c017acb8>] (create_dir+0x70/0xc4) [ 1.610917] [<c017acb8>] (create_dir+0x70/0xc4) from [<c017b0bc>] (sysfs_create_dir+0xc4/0xe4) [ 1.610965] [<c017b0bc>] (sysfs_create_dir+0xc4/0xe4) from [<c0306bf0>] (kobject_add_internal+0xdc/0x1d0) [ 1.611013] [<c0306bf0>] (kobject_add_internal+0xdc/0x1d0) from [<c0306ef8>] (kobject_add+0x78/0x90) [ 1.611064] [<c0306ef8>] (kobject_add+0x78/0x90) from [<c03b0078>] (device_add+0xf8/0x578) [ 1.611114] [<c03b0078>] (device_add+0xf8/0x578) from [<c03b4208>] (platform_device_add+0x110/0x16c) [ 1.611161] [<c03b4208>] (platform_device_add+0x110/0x16c) from [<c03b47a4>] (platform_device_register+0x30/0x34) [ 1.611214] [<c03b47a4>] (platform_device_register+0x30/0x34) from [<c08f6f94>] (sunxi_snddaudio0_init+0x54/0xa4) [ 1.611263] [<c08f6f94>] (sunxi_snddaudio0_init+0x54/0xa4) from [<c000867c>] (do_one_initcall+0xa8/0x164) [ 1.611313] [<c000867c>] (do_one_initcall+0xa8/0x164) from [<c08d1a74>] (kernel_init+0x168/0x254) [ 1.611364] [<c08d1a74>] (kernel_init+0x168/0x254) from [<c000f1b0>] (kernel_thread_exit+0x0/0x8) [ 1.611455] ---[ end trace bd16a9742f20e8dd ]--- [ 1.611481] ------------[ cut here ]------------ [ 1.611509] WARNING: at lib/kobject.c:198 kobject_add_internal+0x180/0x1d0() [ 1.611533] kobject_add_internal failed for snddaudio with -EEXIST, don't try to register things with the same name in the same directory. [ 1.611560] Modules linked in: [ 1.611601] [<c0016a20>] (unwind_backtrace+0x0/0xe8) from [<c0617cc0>] (dump_stack+0x20/0x24) [ 1.611644] [<c0617cc0>] (dump_stack+0x20/0x24) from [<c0029750>] (warn_slowpath_common+0x5c/0x74) [ 1.611686] [<c0029750>] (warn_slowpath_common+0x5c/0x74) from [<c00297a8>] (warn_slowpath_fmt+0x40/0x48) [ 1.611732] [<c00297a8>] (warn_slowpath_fmt+0x40/0x48) from [<c0306c94>] (kobject_add_internal+0x180/0x1d0) [ 1.611778] [<c0306c94>] (kobject_add_internal+0x180/0x1d0) from [<c0306ef8>] (kobject_add+0x78/0x90) [ 1.611825] [<c0306ef8>] (kobject_add+0x78/0x90) from [<c03b0078>] (device_add+0xf8/0x578) [ 1.611870] [<c03b0078>] (device_add+0xf8/0x578) from [<c03b4208>] (platform_device_add+0x110/0x16c) [ 1.611915] [<c03b4208>] (platform_device_add+0x110/0x16c) from [<c03b47a4>] (platform_device_register+0x30/0x34) [ 1.611962] [<c03b47a4>] (platform_device_register+0x30/0x34) from [<c08f6f94>] (sunxi_snddaudio0_init+0x54/0xa4) [ 1.612007] [<c08f6f94>] (sunxi_snddaudio0_init+0x54/0xa4) from [<c000867c>] (do_one_initcall+0xa8/0x164) [ 1.612052] [<c000867c>] (do_one_initcall+0xa8/0x164) from [<c08d1a74>] (kernel_init+0x168/0x254) [ 1.612098] [<c08d1a74>] (kernel_init+0x168/0x254) from [<c000f1b0>] (kernel_thread_exit+0x0/0x8) [ 1.612125] ---[ end trace bd16a9742f20e8de ]--- Any hint? The codec still works fine. There is no control in alsamixer. Thanks to @tkaiser and @Igor for their help on IRC.
  7. Guest

    Lirc Reconfigure

    Hi All, I use ARMBIAN 5.25 stable Ubuntu 16.04.2 LTS 3.4.113-sun8i on Nano Pi Neo Air and I try : dpkg-reconfigure lirc I select my remote and then my transmitter nicely After configure, I have this error: ls: cannot access '/lib/modules/3.4.113-sun8i/kernel/drivers/staging/media/lirc': No such file or directory I tried : apt-get install lirc-modules-source But It has no installation candidate... Do someone know how can I do ? Best Regards
  8. Hello everybody! How can I create access point with nmtui ? I spent some time playing with nmtui, and finally my nanopi got address something like 10.42.0.1. But it doesn't look normal, I can't create default gateway like 192.168.0.1 So, I couldn't see my hotspot from another device( android phone or other pc ) Maybe somebody resolved this problem?
  9. Hello all, I'm working on a project where I need at least 460800 baud on a UART on the NanoPi Neo Air. Works great at lower baud rates but can't seem to get it much faster than 115200. Any thoughts on clock adjustment or CPU speed? I'm using Armbian 5.24 with the 3.X kernel
  10. Hi, I have nanopi neo air and want to use Ethernet over USB (micro USB on the board). I configured CDC_Ethernet and RNDIS on kernel's(Debian Jessie) USB gadget section. With ifconfig, usb0 is in the list and with dmesg, it seems g_ether has been configured and it is ready but noting happens on windows nor Linux to show any active network connection or even usb connection on device manager... Please help how can i use usb to have ethernet ... BR, Masoud
  11. Hello, Is it possible to get a WiFi Direct connection from Nanopi Neo Air to for example smartphone and send a file to it? I mean with not using router. Thanks in advance for every answer!
  12. Guest

    Lirc Input GPIO

    Hello, I have a special Ir Receiver which works on a raspberry but not on nano pi neo air... input levels are different ? I can receive signal (I have pulses and spaces) but datas are corrupted and I must transmit longer to have a proper result... Is it possible to change Lirc input pin ?
  13. Hello, I am going to buy this unit, becuase I am lookig for a cheap board with bluetooth and camera input included. NanoPi Neo Air seems to be the best choice (and the only - talking about cheap board). Anyway, did someone play with its bluetooth interface programming? I mean sending (mainly, but also recieving files) from NanoPi by bluetoot. Are there any working tools (C, python)? Thanks for any post in advance!
  14. Hello, I try to get WiFi P2P working on the Nano Pi Neo Air with a 4.x mainline kernel and so I tried the latest available nightly build "Armbian_5.24.170118_Nanopiair_Ubuntu_xenial_4.9.4.img" but I have problems to establish a connection. Does anybody have WiFi P2P working on the Nano PI Neo Air? The problem seems be a problem with the P2P_CLIENT interface creation at the brcmfmac driver. My P2P test peer is a Nexus 5 phone and I'am able to see the peer device using wpa_cli p2p_peers. But when I try to connect I get following driver error messages at the Kernel Log. [ 8.085540] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Jun 6 2014 14:50:39 version 7.10.226.49 ® FWID 01-8962686a [ 83.057486] brcmfmac: brcmf_do_escan: error (-110) [ 83.062334] brcmfmac: brcmf_cfg80211_scan: scan error (-110) [ 85.611612] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 85.617463] brcmfmac: brcmf_p2p_tx_action_frame: sending action frame has failed [ 85.625002] brcmfmac: brcmf_p2p_send_action_frame: Failed to send Action Frame(retry 1) [ 88.171615] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout wpa_supplicant log: p2p-dev-wlan0: Control interface command 'P2P_CONNECT 36:fc:ef:a4:be:2c pbc' p2p-dev-wlan0: Determining shared radio frequencies (max len 1) p2p-dev-wlan0: Shared frequencies (len=0): completed iteration p2p-dev-wlan0: Shared frequencies (len=0): valid for P2P p2p-dev-wlan0: Determining shared radio frequencies (max len 1) p2p-dev-wlan0: Shared frequencies (len=0): completed iteration p2p-dev-wlan0: P2P: num_unused_channels: 1 P2P: Setup freqs: freq=0 num_MCC=1 shared_freqs=0 num_unused=1 P2P: Current operating channels are not available for P2P. Try to use another channel P2P: Own frequency preference: 0 MHz P2P: Create a new interface p2p-wlan0-0 for the group nl80211: Create interface iftype 8 (P2P_CLIENT) Failed to create interface p2p-wlan0-0: -110 (Connection timed out) P2P: Failed to create new group interface P2P: Failed to allocate a new interface for the group wpa_supplicant is started as following: wpa_supplicant -B -iwlan0 -c/etc/p2p_supplicant.conf -f /var/log/wpa_supplicant.log -dd p2p_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant update_config=1 device_name=NANO-P2P device_type=1-0050F204-1 config_methods=virtual_push_button physical_display keypad p2p_go_intent=1 country=US p2p_no_group_iface=1 Thank you, Steve
  15. Hi guys, first I want to thank you for your marvelous work. I've learned much... I've ordered a Nano Pi Neo Air and two Nano Pi Neo from Friendly Arm which arrived last week to build some squeezelite clients and drop them around the house. At the moment I'm just using some cheap USB-C-Media Soundcards but plan to invest in better ones, if the multi-room solution I have in mind is used enough. The Nano Pi Neo (not Air) does exactly what it should using the Ubnuntu Xenial Image from the download page. Cheers! For the Air's I've used the Debian release, don't know really why ;-) At first I've bootet it from a SD-Card after a direct eMMC-Flash using https://github.com/ThomasKaiser/sunxi-armbian-flasher-osxfailed. Etcher always mouns about not finding diskutil (tried 1.0.0beta15 and 1.0.0beta17 - OSx 10.12.2) on the first run. After restarting Etcher it shows the "drive" and I can flash, but after that mmc1 could not be found as stated on the serial console - that seems like another problem and I did not copy the message, sorry. I've installed Debian from the SD-Card to the eMMC with /usr/lib/nand-sata-install/nand-sata-install.sh which worked fine. Cheers again! After that I've configured Wifi by editing /etc/network/interfaces and adding an auto wlan0. After restarting networking - online! Everything seems to work fine, installing Squeezelite, configuring it and listening to music from the Logitech-Media-Server in sync with the other Nano Pi's. WOW! I'm using a dedicated power supply (5V, 2A) and attached the usb-sound-dongle via an OTG-Y-Cable together with the 5V. http://imgur.com/a/Ta3iB But something seems quirky. I can't get a stable ssh connection via Wi-Fi - Serial works fine meanwhile. After some time listening to music from the device, it drops from the player list in the media server and won't come back again while it is still pingable. The load of the board is somewhere around 0.02-0.16 the whole time. This is a ping to the device: PING nanopiair.fritz.box (192.168.42.165): 56 data bytes 64 bytes from 192.168.42.165: icmp_seq=0 ttl=64 time=149.826 ms 64 bytes from 192.168.42.165: icmp_seq=1 ttl=64 time=64.753 ms 64 bytes from 192.168.42.165: icmp_seq=2 ttl=64 time=85.062 ms 64 bytes from 192.168.42.165: icmp_seq=3 ttl=64 time=104.953 ms 64 bytes from 192.168.42.165: icmp_seq=4 ttl=64 time=27.079 ms 64 bytes from 192.168.42.165: icmp_seq=5 ttl=64 time=4.260 ms 64 bytes from 192.168.42.165: icmp_seq=6 ttl=64 time=4.676 ms 64 bytes from 192.168.42.165: icmp_seq=7 ttl=64 time=3.576 ms 64 bytes from 192.168.42.165: icmp_seq=8 ttl=64 time=5.415 ms 64 bytes from 192.168.42.165: icmp_seq=9 ttl=64 time=4.240 ms 64 bytes from 192.168.42.165: icmp_seq=10 ttl=64 time=4.242 ms [...] 64 bytes from 192.168.42.165: icmp_seq=1990 ttl=64 time=4.391 ms 64 bytes from 192.168.42.165: icmp_seq=1991 ttl=64 time=4.363 ms 64 bytes from 192.168.42.165: icmp_seq=1992 ttl=64 time=4.313 ms 64 bytes from 192.168.42.165: icmp_seq=1993 ttl=64 time=31.534 ms 64 bytes from 192.168.42.165: icmp_seq=1994 ttl=64 time=52.714 ms 64 bytes from 192.168.42.165: icmp_seq=1995 ttl=64 time=72.956 ms 64 bytes from 192.168.42.165: icmp_seq=1996 ttl=64 time=94.694 ms 64 bytes from 192.168.42.165: icmp_seq=1997 ttl=64 time=13.832 ms 64 bytes from 192.168.42.165: icmp_seq=1998 ttl=64 time=37.470 ms 64 bytes from 192.168.42.165: icmp_seq=1999 ttl=64 time=60.732 ms 64 bytes from 192.168.42.165: icmp_seq=2000 ttl=64 time=80.521 ms 64 bytes from 192.168.42.165: icmp_seq=2001 ttl=64 time=100.608 ms 64 bytes from 192.168.42.165: icmp_seq=2002 ttl=64 time=18.236 ms 64 bytes from 192.168.42.165: icmp_seq=2003 ttl=64 time=38.494 ms 64 bytes from 192.168.42.165: icmp_seq=2004 ttl=64 time=57.605 ms 64 bytes from 192.168.42.165: icmp_seq=2005 ttl=64 time=77.558 ms 64 bytes from 192.168.42.165: icmp_seq=2006 ttl=64 time=97.405 ms 64 bytes from 192.168.42.165: icmp_seq=2007 ttl=64 time=14.296 ms 64 bytes from 192.168.42.165: icmp_seq=2008 ttl=64 time=37.039 ms 64 bytes from 192.168.42.165: icmp_seq=2009 ttl=64 time=61.979 ms 64 bytes from 192.168.42.165: icmp_seq=2010 ttl=64 time=79.827 ms 64 bytes from 192.168.42.165: icmp_seq=2011 ttl=64 time=104.190 ms 64 bytes from 192.168.42.165: icmp_seq=2012 ttl=64 time=5.220 ms 64 bytes from 192.168.42.165: icmp_seq=2013 ttl=64 time=8.095 ms 64 bytes from 192.168.42.165: icmp_seq=2014 ttl=64 time=6.569 ms 64 bytes from 192.168.42.165: icmp_seq=2015 ttl=64 time=5.788 ms 64 bytes from 192.168.42.165: icmp_seq=2016 ttl=64 time=6.476 ms So, no packet drops - only very varying packet round trip times. Here's my iwconfig (WPA2): wlan0 IEEE 802.11 ESSID:"myssid" Mode:Managed Frequency:2.462 GHz Access Point: XX:XX:XX:XX:XX:XX Bit Rate=72 Mb/s Tx-Power:32 dBm Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Managementmode:All packets received Link Quality=5/5 Signal level=-34 dBm Noise level=-91 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:77 Invalid misc:0 Missed beacon:0 Maybe the excessive retries are a hint? On the shell I have to wait for 10 or more seconds to type in another command or character. Serial, as already said, responds quick as usual. Maybe I've choosed the wrong antenna? But then the iwconfig should tell other values. I bought these: https://www.amazon.de/gp/product/B01FZ47URG/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 Hopefully you can point me out what I could do to have reliable Wi-Fi on the otherweise fine Nano Pi Neo Air board. Though I'm not using them to do heavy lifting. Regards, Patrik
  16. Hi, I am using Armbian for NanoPI NEO AIR + CAM500B. I am unable to see any /dev/video0. I am able to get the camera working with FA default image. Here is my dmeg output. I really appreciate any help to get this working. I would like to use OV5640 with https://github.com/avafinger/ov5640driversto control frame rate. Thanks
  17. Hi all, I build Armbian for my NanoPi Air with both Linux 3.4 and Linux 4.X, and config usb to be an USB Ethernet Gadget but it does not work with Linux 4.X. There is nothing showing when "dmesg | grep gadget" on Linux 4.x But in Linux 3.4 I got following messages: root@nanopiair:/# dmesg | grep gadget [ 2.559263] g_ether gadget: using random self ethernet address [ 2.565929] g_ether gadget: using random host ethernet address [ 2.582905] gadget_is_softwinner_otg is not -int [ 2.582923] gadget_is_softwinner_otg is not -int [ 2.583012] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [ 2.590546] g_ether gadget: g_ether ready [ 13.898453] g_ether gadget: high-speed config #2: RNDIS root@nanopiair:/# root@nanopiair:/# Do you know how enable the Ethernet Gadget for Linux 4.x? Thanks in advance,
  18. Is there any way to change brightness settings on CAM500B? I can't get clear images fswebcam. Using nanopi neo air with CAM500B and Ubuntu core. :~# v4l2-ctl -l error 25 getting ctrl White Balance, Automatic error 25 getting ctrl Exposure error 25 getting ctrl Horizontal Flip error 25 getting ctrl Vertical Flip error 25 getting ctrl Color Effects Thanks
  19. Hi, Messages flooded with the i2c0 messages after the NeoAir boots as showing below: [ 10.234498] dhd_module_init: Exit err=0 [ 10.240493] systemd[1]: Listening on Syslog Socket. [ 10.246332] systemd[1]: Starting Journal Service... [ 10.360420] systemd[1]: Started Journal Service. [ 10.813583] systemd-udevd[179]: starting version 215 [ 11.191615] twi_start()434 - [i2c0] START can't sendout! [ 11.197938] twi_start()434 - [i2c0] START can't sendout! [ 11.204329] twi_start()434 - [i2c0] START can't sendout! [ 11.210906] twi_start()434 - [i2c0] START can't sendout! [ 11.221376] twi_start()434 - [i2c0] START can't sendout! [ 11.228399] twi_start()434 - [i2c0] START can't sendout! [ 11.237229] twi_start()434 - [i2c0] START can't sendout! [ 11.243890] twi_start()434 - [i2c0] START can't sendout! [ 11.250510] twi_start()434 - [i2c0] START can't sendout! and so on every ms or so. Do you know how to fix it? Thanks in advance
  20. First sorry for starting a similar thread here and in [1]. I try to read a DS18B20, which does not work with Armbian, DietPi, and Friendlyarm's Ubuntu. This morning, my idea was to slow down the CPU - and it worked. In detail: By running some useless cpu consuming python scripts, reading the DS18B20 works fine. As soon as i stop them, reading the sensor immediately fails. So there might be some timing issues in the implementations of w1-gpio and w1-gpio-board. Are there any hints how i can get these issues fixed? Thanks! Thomas [1] http://www.friendlyarm.com/Forum/viewtopic.php?f=47&t=393
  21. Hello is there any way to stream rtsp on H3 devices? With this i can record video ffmpeg -t 30 -f v4l2 -channel 0 -video_size 1280x720 -i /dev/video0 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4 My hardware is NanoPI neo air + CAM500B. Using friendlyARM's image at the moment because camera don't work on Armbian. (/dev/video0 is there but mjpg-streamer end with errors for example)
  22. So I have installed Armbian on a number of boards in the past without real issue. I'm currently installing the latest version (not nightly build or anything) on my new NanoPi NEO AIR. A couple of points. Firstly - WIFI seems weak on the internal aerial - I set everything up on the serial port but once I used WINSCP - I note the terminal is slow - despite apt-get-update and other installs seeming to run pretty well. Secondly (and this has never happened before) it is now 7th of November early in the morning and my script for installing programs seemed to be running into issues until I realised the board time was set 6 days in the past (I only installed Armbian last night) - never had that happen. I changed the date mid-stream and all seems to be installing ok... it will be some time before the script is complete but looking ok up to now.
  23. Edit: Price seems to be $17.99 Just FYI: FriendlyARM is preparing another H3 board: NanoPi Air somehow related to NanoPI NEO (same low default DRAM clockspeed let me believe this). What we already know (by looking at Github commits): onboard eMMC (no idea about the size) no HDMI no Ethernet AP6212 based WiFi+BT (connected through SDIO and UART) Personal assumptions: most probably also just a single bank DRAM configuration most probably also a SD card slot maybe eMMC only an option and a basic version without eMMC available same 40 x 40 mm dimensions as NEO, eMMC on the lower PCB side next to H3, AP6212 on the upper (where the Ethernet Jack is located on the NEO -- assumption based on heatsink design for NEO) Therefore adding Armbian support for this board is pretty easy as soon as we're done with NanoPi NEO since it's then just combining settings for NanoPi NEO with Banana Pi M2+ (WiFi/BT). No official announcement available yet and no traces in FA's wiki. But since the FriendlyARM folks follow the 'release often, release early' principle most information can be gathered from Github sources
  24. This is a rather interesting board isn't it? H3, GPIO, 0.5GB memory. http://www.cnx-software.com/2016/07/07/smaller-than-raspberry-pi-zero-meet-nanopi-neo-arm-linux-development-board/ Would it be possible to run this on Armbian?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines