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

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    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. Hello. Can't run x11 on Debian 11. I am using Nano Pi AIR (Allwiner h3). Since the board is not officially supported, I built the image on debian 11 myself. root@nanopiair:/# uname -a Linux nanopiair 5.15.44-sunxi #trunk SMP Wed Jun 8 08:41:04 UTC 2022 armv7l GNU/Linux The LCD is connected via SPI, chip is ili9486. Device tree file has been created, I can see the loading process and the console on the screen. I'm trying to start the X-server by "startx" from ssh session, but for some reason it ends immediately after the start. I tried using fbdev or fbturbo as driver. I also tried to remove the config with the driver in general (section "Device"). Here is the X server log when starting without explicitly specifying a driver: https://pastebin.com/zMXaQngf The only error is: [403138.174] (EE) modeset(0): glamor initialization failed I try to use fbturbo driver. root@nanopiair:# cat /etc/X11/xorg.conf.d/50-fbturbo.conf Section "Device" Identifier "Allwinner A10/A13 FBDEV" Driver "fbturbo" Option "fbdev" "/dev/fb0" Option "SwapbuffersWait" "true" EndSection I get Xorg.log with errors "FBTURBO(0): FBIOPUTCMAP: Invalid argument". Full log - https://pastebin.com/UfgT1K8U I try to use fbdev driver: root@nanopiair:/etc/X11/xorg.conf.d# cat /etc/X11/xorg.conf.d/50-fbdev.conf Section "Device" Identifier "Allwinner A10/A13 FBDEV" Driver "fbdev" Option "fbdev" "/dev/fb0" # Option "SwapbuffersWait" "true" EndSection I get Xorg.log with errors "FBDEV(0): FBIOPUTCMAP: Invalid argument". Full log - https://pastebin.com/EqDCEGLf Why X server terminating after start? I have a second such board, it also has armbian, but on debian 10 and everything works fine without Xorg config.
  2. Hi, I am having an issue with my system running a nanopi Air. After boot, my system won't detect my rtc (i2cdetect doesn't show it) nor my USB device. The problem must come from my SD card or is software related. Indeed, when I am booting from another SDcard, with aembian installed, everything is detected normally. Does anyone has a clue? Thank you, Tibibs
  3. Does anyone know what sort of latency there is using mainline hw accelerated video encoding on Allwinner H3(H.264/265)? How about latency of mjpeg(if it is supported)? I'm trying to build a system with lowest possible latency.
  4. Hi all. I have a board nanopi neo air with armbian linux on it. We with my colleague try to setting up ffmpeg with cedrus264 for hardware accelerated capturing video from ov5640-like camera device. There is my armbianmonitor. There are my v4l2-ctl -d /dev/videox -D out: After some reconfiguration of dts, we can successfully capture video in low fps with ffmpeg -f v4l2 -framerate 25 -video_size 960x720 -i /dev/video1 output.mkv but with ffmpeg -f v4l2 -channel 0 -video_size 960x720 -i /dev/video1 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4 ffmpeg failed: Ffmpeg was buided from FFmpeg-Cedrus, also we try follow this and use this binaries - result haven't changed. After some inspecting sources of ffmpeg-cedrus we found that ffmpeg try to open /dev/cedar_dev device, which don't exists in our system. Ffmpeg fails on opening device. If we replace /dev/cedar_dev by /dev/video0, where is our cedrus driver, ffmpeg fails on ioctl IOCTL_GET_ENV_INFO. In source, it is 99 or 101 line. We check kernel config for configuration, provided by Sunxi-Cedrus and determine that cedrus was configured right. Also we have tried all described actions on official armbian buster image for nanopi neo air and we have got the same result. What we does wrong?
  5. Hi everybody! I am new to this community and I am trying to find out if anyone here with a NanoPi Neo Air board got bluetooth working on Armbian Buster (mainline based kernel 5.10.y). Here is the armbianmonitor -u log http://ix.io/2UKF For about one week I am trying to make bluetooth work and with no result. I tried also Armbian Focal (mainline based kernel 5.10.y) and the results are the same. Bluetooht not working/recognized. I mention that I enabled BT support from armbian-config. dmesg | grep blue empty result rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no The images were compiled on Ubuntu 20.04 with the following command: ./compile.sh BRANCH="current" KERNEL_ONLY="no" KERNEL_CONFIGURE="no" BUILD_DESKTOP="no" RELEASE="buster" BUILD_DESKTOP="no" I am out of ideas. I really appreciate your help and I am willing to pay for some sort of support from your side as I want to make this board fully functional with Armbian. Thank you!
  6. Dear Armbian community, First of all, I am aware of the fact that what I am trying to achieve is not supported, but let me ask anyway. What I am trying to do is to build my custom root filesystem for my specific embedded needs (which is pretty minimal and without systemd) while still using kernel (5.8.16-sunxi) and modules provided by Armbian. It is going great so far, but the first issue I need to figure out is why there are approximately 60 second delays between each brcmf_fw_alloc_request calls (full dmesg available here): [ 40.602927] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 40.620798] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.friendlyarm,nanopi-neo-air.txt failed with error -2 [ 40.620821] brcmfmac mmc2:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.friendlyarm,nanopi-neo-air.txt [ 101.475933] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 162.808829] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-11), device may have limited channels available [ 162.813236] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268 On image provided by Armbian brcmfmac dmesg is exactly the same, but there are no such a long delays between brcmf_fw_alloc_request calls (full dmesg available here): [ 10.540426] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 10.549789] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.friendlyarm,nanopi-neo-air.txt failed with error -2 [ 10.549807] brcmfmac mmc2:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.friendlyarm,nanopi-neo-air.txt [ 11.103778] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 11.106615] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-11), device may have limited channels available [ 11.107934] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268 Here is the list of modules that I'm currently using (from /lib/modules/5.8.16-sunxi): Module Size Used by brcmfmac 180224 0 brcmutil 16384 1 brcmfmac cfg80211 471040 1 brcmfmac rfkill 20480 1 cfg80211 usb_f_acm 20480 1 u_serial 24576 1 usb_f_acm g_serial 16384 0 libcomposite 45056 2 g_serial,usb_f_acm pwrseq_simple 16384 1 sunxi 20480 0 phy_generic 20480 2 sunxi Does anybody know a way to remove these delays without involving systemd at all? Maybe udev would be sufficient? Any opinions are appreciated
  7. Hi, I am fairly new to the SBC board and struggling to begin my setup of the NanoPo NEO Air. This little board is a perfect fit for my project I need to develop. The first problem I encounter is the following: There are no HDMI port. Thus I can't do the basic configuration for my network and allow an SSID access. Does anyone has a solution to preconfigure the WIFI of my Armbian from windows (or Linux if needed)? My second problem will be: I would like to install my system on the EMMC flash to not be dependent of the SD card. Can you confirm I would only need to run the command "nand-sata-install" when I will get access to SSH? Last problem is that I will need to implement a trigger between wifi and AP mode. I have briefly seen some topics about this, some are saying friendly arm have this function natively, others that this function will be develop soon for Armbian and some have some kind of tutorials about it (playing with wpa_supplicant config). What is the state of the art regarding this? Finally but not least, I am trying to get it running with a Bionic image of armbian. If there are some better image to be used, please let me know. I am sorry if those questions seems straightforward but I am not so familiar with Linux and its services nor the SBC world. Thank you for your help and guidance. Tibibs
  8. Hi, I am trying to write my own kernel module/drive for the NanoPi air, running a self-compiled version of armbian 5.83. Actually I only added the PREEMTION option to get real-time behavior when reading/writing from IO pins. I started using the "hello world" template from here. To get the module compiled I had to build the headers for my kernel as well using the option INSTALL_HEADERS in the armbian-build config file. The build debian-package called "linux-headers-next-sunxi_5.83_armhf.deb" was copied and installed on the NanoPi. OK, so now compiling (on the NanoPi - so no cross-compilation) works like a charm: > make make -C /lib/modules/4.19.36-sunxi/build M=/home/gresy/Examples modules make[1]: Entering directory '/usr/src/linux-headers-4.19.36-sunxi' CC [M] /home/gresy/Examples/hello.o Building modules, stage 2. MODPOST 1 modules CC /home/gresy/Examples/hello.mod.o LD [M] /home/gresy/Examples/hello.ko make[1]: Leaving directory '/usr/src/linux-headers-4.19.36-sunxi' But when I try to load the hello-world module it's rejected: > sudo insmod hello.ko insmod: ERROR: could not insert module hello.ko: Invalid module format The following message shows up in the kernel buffer, which implies to me the module is not "preemtion compatible" ... if that's possible at all. Or at least the version magic is wrong. > dmesg ... [ 710.970775] hello: version magic '4.19.36-sunxi SMP mod_unload ARMv7 thumb2 p2v8 ' should be '4.19.36-sunxi SMP preempt mod_unload ARMv7 thumb2 p2v8 ' Here some other information which might be useful: > sudo modinfo hello.ko filename: /home/gresy/Examples/hello.ko version: 0.1 description: A simple Hello world LKM! author: Akshat Sinha license: GPL srcversion: B7B3CF8B5A8284B3911C7AF depends: name: hello vermagic: 4.19.36-sunxi SMP mod_unload ARMv7 thumb2 p2v8 > uname -a Linux nanopiair 4.19.36-sunxi #5.83 SMP PREEMPT Tue Apr 30 11:04:15 CEST 2019 armv7l GNU/Linux So, does anyone know why the module will not get loaded? Thanks for your help, Markus
  9. Hi, I'm want to use my old Nanopi Neo Air with CAM500B as wifi webcam. I flashed the latest armbian bionic image, installed v4l-utils and tried to list the cameras properties with `v4l2-compliance` and `v4l2-ctl --all` but the tools always crash and I can't kill them. `dmesg` shows a NULL pointer exception: [ 56.994526] 8<--- cut here --- [ 56.997657] Unable to handle kernel NULL pointer dereference at virtual address 00000068 [ 57.005825] pgd = c774af94 [ 57.008606] [00000068] *pgd=00000000 [ 57.012243] Internal error: Oops: 5 [#1] SMP THUMB2 [ 57.017122] Modules linked in: brcmfmac brcmutil sun8i_codec_analog sun8i_adda_pr_regmap sun4i_i2s snd_soc_simple_card snd_soc_simple_card_utils snd_soc_core lima snd_pcm_dmaengine gpu_sched sun4i_gpadc_iio snd_pcm cfg80211 snd_timer industrialio snd soundcore rfkill sun8i_thermal zram sunxi_cedrus(C) v4l2_mem2mem uio_pdrv_genirq uio cpufreq_dt sch_fq_codel usb_f_acm u_serial g_serial libcomposite ip_tables x_tables pwrseq_simple [ 57.055242] CPU: 1 PID: 2012 Comm: v4l2-compliance Tainted: G C 5.4.35-sunxi #trunk [ 57.064192] Hardware name: Allwinner sun8i Family [ 57.068916] PC is at v4l2_g_parm_cap+0x3c/0xb4 [ 57.073363] LR is at v4l2_g_parm_cap+0x27/0xb4 [ 57.077808] pc : [<c0796c04>] lr : [<c0796bef>] psr: 00030033 [ 57.084072] sp : d43d1d50 ip : d43d1d84 fp : d4e74840 [ 57.089296] r10: c0ab69f0 r9 : c0aaf59c r8 : d4f9d100 [ 57.094521] r7 : d70fd328 r6 : 00000000 r5 : d4ef6000 r4 : c0f04f48 [ 57.101100] r3 : 00000080 r2 : fffffff0 r1 : 00000000 r0 : d43d1d54 [ 57.107618] Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment none [ 57.114913] Control: 50c5387d Table: 54dbc06a DAC: 00000051 [ 57.120652] Process v4l2-compliance (pid: 2012, stack limit = 0x7ede4d8a) [ 57.127429] Stack: (0xd43d1d50 to 0xd43d2000) [ 57.131780] 1d40: 00000002 00000000 00000000 00000000 [ 57.139945] 1d60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 57.148110] 1d80: 00000000 6a7c03d8 c104e334 c0f04f48 d4ef6000 d4e74840 c0ab69f0 c078a355 [ 57.156274] 1da0: c07b2311 d43d1e54 00000000 6a7c03d8 c0cc5604 d70fd328 c0cc5615 c078a31d [ 57.164440] 1dc0: c0f04f48 d70fd694 c0aaf59c c078af73 d73c0000 00000000 d4f9d100 00000000 [ 57.172605] 1de0: 00000000 d4ef6000 00000000 c0aaf59c c0f04f48 c023f9c5 00080040 c0ec5700 [ 57.180769] 1e00: 1f0be000 6a7c03d8 d7007c18 c0cc5615 c0f04f48 00000004 00000000 00000003 [ 57.188934] 1e20: 000000cc d4ef6000 d4ef6000 c078b41f c0f05400 bef96b8c d4e74840 c078adf5 [ 57.197098] 1e40: 00000000 00000000 00000000 00000000 c9bd4200 00000001 00000000 00000000 [ 57.205262] 1e60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 57.213426] 1e80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 57.221581] 1ea0: 00000000 d69bed78 00000001 00000000 00000001 d43d1ed0 00000004 c0f04f48 [ 57.229746] 1ec0: 60030013 c0150cc7 00000004 d43d1ed0 00000000 6a7c03d8 00000000 6a7c03d8 [ 57.237910] 1ee0: 00000000 c0f04f48 d4e74840 bef96b8c 00000003 bef96b8c d73d0ce8 c0262f41 [ 57.246075] 1f00: d4e2a240 00000002 d08fc7f8 d4e2a248 00000000 c0f04f48 00000000 00000000 [ 57.254239] 1f20: 00000000 00000000 00000000 6a7c03d8 5ac3c35a 00000002 d4e2a240 d08fc7f8 [ 57.262405] 1f40: d4e2a248 00000001 02364058 00000001 bef9705c c0253b5b 00000000 6a7c03d8 [ 57.270569] 1f60: c0f04f48 d4e74840 00000000 d4e74840 c0cc5615 bef96b8c 00000003 00000036 [ 57.278735] 1f80: bef9705c c02635d5 7123fc00 b6f34968 00000001 bef97060 00000036 c0101224 [ 57.286900] 1fa0: d43d0000 c0101001 b6f34968 00000001 00000003 c0cc5615 bef96b8c 7123fc00 [ 57.295064] 1fc0: b6f34968 00000001 bef97060 00000036 bef9a47c bef96a84 004c3e78 bef9705c [ 57.303229] 1fe0: 004c3f00 bef969b4 004845e7 b6d150a8 60030030 00000003 00000000 00000000 [ 57.311407] [<c0796c04>] (v4l2_g_parm_cap) from [<c078a355>] (v4l_g_parm+0x39/0x90) [ 57.319055] [<c078a355>] (v4l_g_parm) from [<c078af73>] (__video_do_ioctl+0x17f/0x314) [ 57.326963] [<c078af73>] (__video_do_ioctl) from [<c078b41f>] (video_usercopy+0x1ff/0x4bc) [ 57.335219] [<c078b41f>] (video_usercopy) from [<c0262f41>] (do_vfs_ioctl+0x8d/0x6e0) [ 57.343042] [<c0262f41>] (do_vfs_ioctl) from [<c02635d5>] (ksys_ioctl+0x41/0x58) [ 57.350431] [<c02635d5>] (ksys_ioctl) from [<c0101001>] (ret_fast_syscall+0x1/0x62) [ 57.358072] Exception stack(0xd43d1fa8 to 0xd43d1ff0) [ 57.363116] 1fa0: b6f34968 00000001 00000003 c0cc5615 bef96b8c 7123fc00 [ 57.371281] 1fc0: b6f34968 00000001 bef97060 00000036 bef9a47c bef96a84 004c3e78 bef9705c [ 57.379443] 1fe0: 004c3f00 bef969b4 004845e7 b6d150a8 [ 57.384491] Code: 01db bf44 2302 61ab (6eb3) 68db [ 57.389321] ---[ end trace b0284d13f94bede6 ]--- Is the camera broken or is this a driver problem?
  10. Hello, I am working on a project in which we need to use a Nanopi Neo Air (based on SoC Allwinner H3). In this project we need to use the USB serial interface to communicate with another part of the project. We need to configure the Nanopi Neo Air USB interface as a peripheral USB . Nanopi Neo Air's USB serial interface is configured by default as a USB host, and in "armbian-config" there is no way to change this configuration. The USB host (which is the other part of the project) will send data to the Nanopi Neo Air whenever there is new data. Is it possible to configure the Nanopi Neo Air as a peripheral USB? How can we do this configuration (if you have documentation please)? Thanks in advance, Best regards, Rami.
  11. I compiled full-armbian image for nanopi air. root@nanopiair:~# uname -a Linux nanopiair 4.19.25-sunxi #5.76 SMP Wed Feb 27 13:46:35 KST 2019 armv7l GNU/Linux and by armbian-config, on armbianEnv.txt overlays=spdif-out root@nanopiair:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: SPDIF [On-board SPDIF], device 0: spdif-dit-hifi dit-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 root@nanopiair:~# speaker-test -tway -c2 -Dhw:0 speaker-test 1.1.3 Playback device is hw:0 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 128 to 131072 Period size range from 64 to 16384 Using max buffer size 131072 Periods = 4 was set period_size = 16384 was set buffer_size = 131072 0 - Front Left 1 - Front Right Time per period = 0.503481 0 - Front Left 1 - Front Right and my dac doesn't detect any signal by coaxial-input. What I can I check?
  12. Nanopi Neo AIr Kernel Module Loading problem when dynamically loading from VirtualBox Built .Ko files.
  13. Hi, I would like to configure my nanopi Air as an AP and facing some issues. I have edit my /etc/network/interfaces as follow to use hostapd # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto wlan0 iface wlan0 inet static hostapd /etc/hostapd.conf address 192.168.1.1 netmask 255.255.255.0 and I have linked the the hostapd.config config file in the /init.d/hostapd. my hostapd.config is as below ssid=AERS interface=wlan0 hw_mode=g channel=5 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_passphrase=aerstest wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 noscan=1 # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 when I power on my board, few things might happen SSID shows up for few seconds and disappear SSID doesn't show up Does anyone has an idea for troubleshooting this? I haven't started to configure the dnsmasq yet. Thank you, Tibibs
  14. Hello, I am working with a Nanopi Neo Air incorporating the System on Chip Allwinner H3. I need to establish a serial communication via the SPI bus, to do this I am looking for some information related to the SPI bus. Can you help me to know the following information please: - What are the min and max SPI bus frequencies that I can use with the Nanopi Neo Air (Allwinner H3)? How can I calculate them? And are there specific frequency values to use (meaning the relationship is not linear, for example: 3.84MHz, 4.34MHz, etc)? - Can the Nanopi Neo Air be configured as an SPI bus master and as a slave (not at the same time) or only as a master? - What is the maximum number of bits that we can send via the SPI bus per second? If there are several, can you please specify them? Thank you very much in advance. Best regards, Rami
  15. I am looking for a working python "wiring library" for the NanoPi Air.... With pyGPIO i have limited success. Only GPIO4 seems to work. Just a quick "use this libray for python..." please. I need 3 GPIO pins (and UART1 which is working well under python...) Thank you!
  16. Hello, I have downloaded and installed Armbian Buster mainline based kernel 4.19.y & Armbian Bionic mainline based kernel 4.19.y from https://www.armbian.com/nanopi-neo-air/ With both versions I have the same problem: WiFi is not working at all ! Before the installation I was running the Friendlyarm factory image and had no problems with WiFi. As I have no internet connection, I can not upload the ArmbianMonitor log. Running this gives no errors. root@nanopiair:~# armbianmonitor -v Starting package integrity check. This might take some time. Be patient please.. . It appears you don't have any corrupt files or packages! Running: root@nanopiair:~# nmcli dummy0: unmanaged "dummy0" dummy, F6:6D:BD:D6:43:A9, sw, mtu 1500 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. shows there is no wlan0 ! also this root@nanopiair:~# ifconfig wlan0 up wlan0: ERROR while getting interface flags: No such device how can I start the device wlan0 ? Thomas
  17. I am trying out the latest Armbian Debian Buster release for a Nanopi Neo Air. It is working fine. I've loaded Armbian into the eMMC and I can boot off of it. I have done `apt update && apt upgrade`. Using armbian-config, I have configured Wi-Fi and can SSH in. However, Bluetooth does not work: # systemctl status ap6212-bluetooth.service * ap6212-bluetooth.service - LSB: Patch firmware for ap6212 adapter Loaded: loaded (/etc/init.d/ap6212-bluetooth; generated) Active: failed (Result: exit-code) since Thu 2019-10-24 04:12:56 UTC; 6min ago Docs: man:systemd-sysv-generator(8) Process: 1928 ExecStart=/etc/init.d/ap6212-bluetooth start (code=exited, status=1/FAILURE) Oct 24 04:12:46 nanopiair systemd[1]: Starting LSB: Patch firmware for ap6212 adapter... Oct 24 04:12:56 nanopiair ap6212-bluetooth[1928]: Initialization timed out. Oct 24 04:12:56 nanopiair ap6212-bluetooth[1928]: bcm43xx_init Oct 24 04:12:56 nanopiair ap6212-bluetooth[1928]: Can't get device info: No such device Oct 24 04:12:56 nanopiair systemd[1]: ap6212-bluetooth.service: Control process exited, code=exited, status=1/FAILURE Oct 24 04:12:56 nanopiair systemd[1]: ap6212-bluetooth.service: Failed with result 'exit-code'. Oct 24 04:12:56 nanopiair systemd[1]: Failed to start LSB: Patch firmware for ap6212 adapter. Prior to installing Armbian, using the stock eMMC distribution from Friendlyarm, Bluetooth did work properly. I was able to use `bluetoothctl` to power on the radio and successfully do scans. I do not think it is a hardware issue. Is Bluetooth expected to work out-of-box for this SBC? If not, what needs to be done?
  18. Is there any working image for Nano Pi Air that supports in same time: - Record in the format of the mpeg4 pipeline, the video codec used is h264. Resolution 1024x768 - Ability to transmit video over WiFi (WiFi AP mode), RTSP protocol. - Ability to connect via USB to transfer recorded files to a PC (USB device mode) - Update firmware via USB (FEL mode for Allwinner SOC)
  19. Hi, I would like to use wiringPi for my NanoPi Neo Air, but after installing wiring P, I only get unable to determine board revision as output from gpio readall. I tried this approaches already: Could someone please explain me how to build wiring P for NanoPi Neo Air so that it is working? On NanoPi Neo Plus 2, I did not have to change anything when installing wiringNP under Armbian.
  20. I have gotten Oops a few times, now this morning I got it again I can see that is says "Segmentation Fault". I could still issue sudo armbianmonitor -u so I included those logs. Since I was also connected to both via SSH, where I was running "armbianmonitor -m" and logged in via serial I include the output of those windows below: SSH output: ... Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 00:56:54: --- 0.00 0% 0% 0% 0% 0% 0% 40.1°C 0/15 00:57:00: --- 0.08 1% 1% 0% 0% 0% 0% 40.1°C 0/15 00:57:05: --- 0.07 1% 0% 0% 0% 0% 0% 40.1°C 0/15 00:57:10: --- 0.06 1% 1% 0% 0% 0% 0% Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 Segmentation fault Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) chip@nanopiair:~$ Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe On the serial console: chip@nanopiair:~$ [ 5328.389678] Unable to handle kernel NULL pointer dereference at virtual address 00000004 [ 5328.486540] pgd = 363f637e [ 5328.518886] [00000004] *pgd=00000000 [ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 [ 5328.619983] Modules linked in: zstd lima gpu_sched sun8i_codec_analog sun4i_i2s snd_soc_simple_card sun8i_adda_pr_regmap ttm snd_soc_simple_card_utils snd_soc_core snd_pcm_dmaengine snd_pcm sun4i_gpadc_iio snd_timer industrialio snd soundcore sun8i_ths cpufreq_dt thermal_sys uio_pdrv_genirq uio zram usb_f_acm u_serial g_serial libcomposite brcmfmac brcmutil cfg80211 ip_tables x_tables pwrseq_simple [ 5329.042410] CPU: 2 PID: 1569 Comm: armbianmonitor Not tainted 4.19.64-sunxi #5.93 [ 5329.131953] Hardware name: Allwinner sun8i Family [ 5329.188229] PC is at __dabt_svc+0x10/0x80 [ 5329.236175] LR is at copy_process.part.5+0x327/0x13e4 [ 5329.296599] pc : [<c0101990>] lr : [<c01193fb>] psr: 200f01b3 [ 5329.371582] sp : ca84beb0 ip : ca853f78 fp : 0000c350 [ 5329.434086] r10: 00000000 r9 : 00000000 r8 : 00000000 [ 5329.496591] r7 : 00000000 r6 : c0e04d48 r5 : 01200011 r4 : ca853a80 [ 5329.574695] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : c0efb38c [ 5329.652801] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment none [ 5329.741303] Control: 50c5387d Table: 4a8e806a DAC: 00000051 [ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) [ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) [ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 [ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 [ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f [ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 [ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 [ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 [ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 [ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 [ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 [ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 [ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 [ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe [ 5331.076160] ---[ end trace 0b97daa0d7e18c3e ]--- Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe I don't know much how to read these log files and outputs so any help in understanding them would be appreciated. /Henrik
  21. Running "sudo armbianmonitor -r" fails with this output: Installing RPi-Monitor. This can take up to 5 minutes. Be patient pleaseE: Unable to locate package rpimonitor /usr/bin/armbianmonitor: line 694: /usr/share/rpimonitor/scripts/updatePackagesStatus.pl: No such file or directory Now patching RPi-Monitor to deal correctly with H3 Now you're able to enjoy RPi-Monitor at http://192.168.11.149:8888 It isn't possible to access RPi-Monitor on http://192.168.11.149:8888. The folder /usr/share/rpimonitor does not exist. This is on a Nano PI Neo Air board with freshly installed "buster". (would have included armbianmonitor -u output but that gives this error since yesterday "(52) Empty reply from server") Any idea or fix to the RPi-Monitor install issue?
  22. first i was able to boot my nanopi from SD card and i was able to access it through SSH. then i was trying to boot my nanopi from EMMC but it was not booting. I already installed a different OS which is specialized for Eflasher (nanopi-neo-core_eflasher_friendlycore-xenial_4.14_armhf_20190522 ) . then i followed the steps carefully: http://wiki.friendlyarm.com/wiki/index. ... i_NEO_Core note : i was using commands since there is no HDMI. I typed : eflasher then i choose 1 and typed yes and waited until the OS was installed successfully and finally i powered off the nanopi, removed the SD card as mentioned, tried to power it on but i could not access it again through SSH anymore. I would if someone could help find the problem. or if someone would post the detailed steps to boot the nanopi NEO CORE from emmc using commands lines not HDMI. thanks in advance
  23. when unpacked to the home directory: user@nanopiair:~/linux-source-5.1.0-sunxi$ find . -xtype l ./debian/hdrtmp/lib/modules/5.1.0-sunxi64/build ./drivers/net/wireless/rtl8812au/include ./drivers/net/wireless/rtl8812au/platform ./drivers/net/wireless/rtl8812au/hal ./drivers/net/wireless/rtl8812au/os_dep ./drivers/net/wireless/rtl8812au/modules.order ./drivers/net/wireless/rtl8812au/core ./net/wireguard/tools/wg-quick/wg Didn't stop me from doing what I needed. All the rtl8812au symlinks point to /home/igorp/samsung/cache/sources/rtl8812au/*
  24. Hi, I am using Linux nanopiair 3.4.113-sun8i distribution on my Nano Pi Neo Air and trying to get the g_ether works. After using modprobe g_ether and set up the network/interfaces auto usb0 iface usb0 inet static address 192.168.0.2 netmask 255.255.255.0 then edit /etc/modprobe.d/g_ether.conf: options g_ether host_addr= 06:7b:95:4c:59:d7 After reboot it shows: [ 6.868451] usb0: MAC 06:7b:95:4c:59:d7 [ 6.868475] usb0: HOST MAC 5e:5b:65:8f:94:85 [ 11.484526] systemd[1]: Found device /sys/subsystem/net/devices/usb0. [ 16.249726] ADDRCONF(NETDEV_UP): usb0: link is not ready in this case my PC can not recognize the usb driver when I plug my nano Pi after I set up the DHCP server on the Nano Pi. I do not know if it relates to [ 16.249726] ADDRCONF(NETDEV_UP): usb0: link is not ready
  25. Try to use a DTS file to add bluetooth reset gpio control to rfkill, but `rfkill list` doesn't show "sunxi-bt". /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { bt_pwr_pin: bt_pwr_pin@0 { pins = "PG13"; function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { rfkill_bt { compatible = "rfkill-gpio"; pinctrl-names = "default"; pinctrl-0 = <&bt_pwr_pin>; reset-gpios = <&pio 6 13 1>; clocks = <&osc32k>; clock-frequency = <32768>; rfkill-name = "sunxi-bt"; rfkill-type = "bluetooth"; }; }; }; }; Background: Try to enable bluetooth on Nanopi Neo Air. After a lot of search, get bluetooth work finally. A few details are: 1. enable UART3 and its CTS & DTS. In /boot/armbianEnv.txt, add something like: param_uart3_rtscts=1 overlays=uart3 2. control bluetooth reset pin PG13 3. enable RTC LOSC output I use a script to test: #!/bin/sh # sudo apt install sunxi-tools devmem2 echo 'Enable 32K RTC LOSC output' devmem2 0x1f00060 b 1 echo 'reset bt' sunxi-pio -m PG13=0 sleep 1 sunxi-pio -m PG13=1 sleep 1 echo 'attach' hciattach /dev/ttyS3 bcm43xx 1500000 flow bdaddr 11:22:33:44:55:66 echo 'config' #hciconfig hci0 up To setup RTC LOSC and PG13, we can also use the above DTS file.
×
×
  • Create New...