Search the Community

Showing results for tags 'mainline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Marker Groups

  • Members

Product Groups

  • Misc

Categories

  • Armbian

Categories

  • Giveaways

Categories

  • Applications

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 842 results

  1. Hi All, Just wanted to share a good story using armbian. I have used in the past 1-wire probes for temperature, and the process included decompiling, editing and recompiling dtb for my Banana Pi M1, which was not easy at all. Every firmware update deleted by changes and had to redo de recompilation. With latest kernels and armbian version, the process is now extremely easy, just edit: /boot/armbianEnv.txt Adding this lines: overlays=w1-gpio param_w1_pin=PI3 # desired pin(7th pin (GCLK) or number 4 on first column where number 1 is +3V) param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off I just struggled a little bit to find the GPIO code (decompiled dtb and checked possible candidates). Information about temperature is here: cat /sys/bus/w1/devices/XX-YYYYYYY[this is your probe serial, if you have more they will be in /sys/bus/w1/devices/] /w1_slave You have plenty of information here, but don't need to do all they explain, just my edition has been enough: http://linux-sunxi.org/1-Wire
  2. Hi! New to the forums, this is my first post. I've been trying out some of the pre-built Armbian images on my Orange Pi Zero to get a taste for the OS and it's perfect for my purposes, however I've noticed something odd about the current mainline images that's possibly a small oversight. I browsed the forums before posting and noticed that TV Out functionality has been disabled by default on H3-based boards due to an interference with HDMI output on mainline, which is naturally understandable. There's only one small problem - the same patch has been applied to H2+ boards which lack an HDMI Out altogether. I've explored the image currently provided (the latest Buster/mainline download) and noticed that it too is set to output to HDMI which isn't on the board and isn't supported by the SoC. As such, the board can only operate as headless when those pre-built images are used, which is naturally less than ideal. There *was* a patch available that solved this issue on mainline, however it's rather old, no longer maintained and doesn't work on the latest builds. I'm currently compiling my own image based on the legacy kernel which apparently still supports TV Out by default, but I wanted to ask if it'd be possible for me to adjust the configuration of the current images to simply enable it on what's readily available. I did check /boot/ in search of Script.bin, but the file was not available and armbianEnv.txt doesn't seem to give me the option to change modes, and even if it did, it probably wouldn't change things if the output is disabled altogether. Do you have any advice? I'd very much like to use the latest kernel rather than the legacy one, if possible.
  3. Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at http://linux-sunxi.org/Linux_mainlining_effort still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if a working mainline kernel with DSI for the Pine 64 is starting to look like a possibility and if it might be possible to include in an armbian build. I might be able to do some testing of anyone can guide me in making a build with the necessary patches.
  4. I have read two old threads in this forum: I have been running this (will post more details if needed) for a few days: VERSION=5.90 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" Kernel is 4.19.62-sunxi The BPi would hang/freeze, seemingly randomly within a day or two. When it does that, there is no HDMI video or response to ping. After reading the first thread, I did stress test on the BPi for more than 2 days. The BPi actually hold up. So, next I ran "ping -i 30 -D 192.168.8.1" -- pinging my home gateway every 30 seconds. The BPi has also been up while that is going on. Now its uptime is more than 5 days. I have no problem keeping this going as a workaround -- just thought it may also be of interest to some one.
  5. Hello,Respected Developers: I'm an Orange Pi user.In the process of using the armbian, I encountered serious problems. My Control Board is Orange Pi PC Plus.Armbian is "ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi" I installed jdk and mysql.And run a JAVA program.I set a time zone for Asia-Chongqing,The system language is Chinese,I use three serial ports. When running for a period of time,There will be bugs.About one to three days. The specific phenomena are as follows: 1.Run "date",the time is 1978. 2.Mysql occupy cpu 195%, occupy mem 27%,systemd occupy cpu 34%,Another systemd occupy cpu 14% ,systemd-jo+ occupy cpu 39%. 3.eth0‘s ip disappear,Unable to connect remotely from the network for ssh.I only use serial port to connect. 4.I can't use the reboot command to restart,I input "reboot",It didn't respond. Time automatically changed to 1978. I hope you can help me solve this problem,Thanks very much.
  6. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.
  7. The problem I have an USB endoscope camera that works fine with my Orange Pi lite's normal USB port. However I need both USB port for other devices, so I want to connect this same USB camera, which was orginally marketed as USB otg camera for android phones, using Opi lite's micro usb otg connector. What have I tried - In armbian-config menu, I have enabled usbhost0. I believe this overlay is for the usb otg port, but just to be sure I also enabled usbhost1, usbhost2 and usbhost3. - Using dtc I decompiled sun8i-h3-orangepi-lite.dtb into sun8i-h3-orangepi-lite.dtc. - In this dtc file, I looked up musb, and changed status = "disabled" to "okay", and added dr_mode = "host", like this usb@01c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x6 0x20>; resets = <0x6 0x11>; interrupts = <0x0 0x47 0x4>; interrupt-names = "mc"; phys = <0x18 0x0>; phy-names = "usb"; extcon = <0x18 0x0>; status = "okay"; linux,phandle = <0x47>; phandle = <0x47>; dr_mode = "host" }; - Again with dtc, I compiled the dts to dtb file which replaced the old one (I've made backup). - After reboot, this seemed to have done something root@orangepilite:~$ dmesg |grep musb [ 4.086014] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 4.086025] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 9 [ 4.086290] usb usb9: Manufacturer: Linux 4.14.78-sunxi musb-hcd [ 4.086295] usb usb9: SerialNumber: musb-hdrc.1.auto However, when I connect the camera to the usb otg port, it doesn't work. The LED's on the camera doesn't turn on (so there is probably no power coming from the port, also there are no video devices on /dev/. How do I connect my camera to the micro usb port on Orange pi lite?
  8. My BPi M1 board is working fine, but the old bananalinux is no longer updating. So I downloaded Armbian Bionic mainline image as it is supported. However, after I boot it up, I get no HDMI video signal. I know that the BPi is working as I can see its IP address on my router and ping it. Any suggestions? Try a different image? Build my own? Thank you in advance for helping.
  9. In the FriendlyARM thread http://www.friendlyarm.com/Forum/viewtopic.php?f=53&amp;t=1427&amp;p=5685#p5685 we did try to use A64 images from the Pine64 or the BananaPi M64 with the NanoPi A64. The last times we did that with less success - OK Sytem is running but Network/Sound has to added via USB. No suppport for the onboard devices But today a user did wrote that - with the actual stable Pine64-image ( Armbian_5.69_Pine64_Debian_stretch_next_4.19.13 ) WiFi is useable. So I flasded the Pine64-image to a MicroSDCard and did boot. Additiionally I did see with "aplay -l" the HDMI and the analog Sound-device. But ethernet isnt "connected" right via the .dtb armbian inside can see the ethernet-part of the SoC (set IP and see MAC) and the external RTL8122E Phy blinks the Link and Transfered-Packets via LED.... My first idea was to edit the Pine64 DTB to match the NanoPI A64 DTB in the ethernet-part - but with these Pins & PHandle's I did get stuck BUT my second idea did work much better, because in the armbian-build-system I also did see the sun50i-a64-nanopi-a64.dtb So I checked the board-config-file for the pine64.conf ( under ./build/config/boards/ ) - there is an entry for a defconfig file and the armbin-build-system has also a defonfig file for the nanopi-a64 ./build/cache/sources/u-boot/v2018.11/configs/nanopi_a64_defconfig while the NanoPi A64 isnt (official) supported by the Meneu-System of the armbian-build-system. So I copied ./build/config/boards/pine64.conf to ./build/config/boards/nanopia64.conf and did edit it like in the following way: # A64 quad core 512MB-2GB SoC GBE BOARD_NAME="NanoPiA64" BOARDFAMILY="sun50iw1" BOOTCONFIG_DEFAULT="sun50iw1p1_config" BOOTCONFIG="nanopi_a64_defconfig" # MODULES="sunxi_codec sunxi_i2s sunxi_sndcodec 8723bs" MODULES_NEXT="" # KERNEL_TARGET="default,next,dev" CLI_TARGET="bionic,stretch:next" DESKTOP_TARGET="xenial:default" # CLI_BETA_TARGET="" DESKTOP_BETA_TARGET="" and did compile for the NanoPi A64 with ./compile.sh EXPERT="yes" in ./build/ Now I could select the NanoPi A64 (falsely) as supported board and did select DEV (armbian 5.71 with Kernel 4.20) I did build the console and the Desktop-version. In the console-version I was happy to see eth0 & wlan0 working, but the HDMI and analog soundsystem is missing (which was visible in Pine64 next 4.19.13) So there was no need for a RTL8211E-driver (because its only a PHY) like I did read before at http://linux-sunxi.org/Ethernet#Realtek_RTL8211E In the Desktop-version the GUI did start without problems (not fast, but useable) - like on a older pinebook (a64) build Maybe DEV was "too much"? I will try the NEXT for my NanoPi A64 File Or maybe the nanopi A64 dtb isnt correct on the "sound-part"?
  10. I tested the recently added sunxi-dev patch to improve the SATA write speed. Here are the results: Board: Cubietruck OS: Ubuntu Bionic (18.04.2), Armbian 5.86 Kernel: 5.1.0 with and without RFC-drivers-ata-ahci_sunxi-Increased-SATA-AHCI-DMA-TX-RX-FIFOs.patch SATA-device: SAMSUNG SSD 830 Series, 256GB Measurement method: dd if=/dev/zero of=/tesfile bs=? count=? oflag=direct bs: measured 4k, 64k and 1M block sizes count: adjusted to ensure that data written is ~500MB Measurements below are made with kernel 5.1.0 without (before) and with the mentioned patch: dd bs Before MB/s After MB/s Increase 4k 13.3 19.0 43% 64k 35.9 82.0 128% 1M 42.5 112.0 164% As you can see, the SATA write speed improved, especially when using larger block sizes. Up to now, no negative side-effects encountered.
  11. Hello all, I used using opi one with (Armbian_5.90_Ubuntu_bionic_4.19.57) image. and used the uart0 pins for hardware pwm but the output was around 330mv pwm not 3.3v as i want. my initial thoughts was either the uart0 isn't disabled or there are no pull ups activated, although i tryed using this: https://github.com/iboguslavsky/pwm-sunxi-opi0 Remap pins in FEX: ; Disable debug UART0 [uart_para] uart_debug_port = 0 uart_debug_tx = port:PA04<2><1> uart_debug_rx = port:PA05<2><1> ; Enable PWM0 on PA05 [pwm0_para] pwm_used = 1 pwm_positive = port:PA05<3><0> but there is no FEX but DTB files and i didn't know how to disable uart0 and activate pwm in DTB/DTS files. so how can i get a 3.3v pwm on uart0 (hardware pwm) ?
  12. 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.
  13. Hello, I have installed Armbian Debian Stretch Next (mainline kernel) on my Odroid C2 and updated to newest version(apt update & apt upgrade). Everything works fine except USB ports. I have USB LTE modem which is not recognized. I have tried "lsusb -v" but with this modem not works. But when I connect USB keyboard first then "lsusb -v" and next I connect LTE modem and type "lsusb -v" then it's works. I also tried connecting USB LTE modem before Odroid C2 boot but this workaround not working. Is there any workaround which not involving connecting more than one USB device? Maybe usb kernel modules (usbcore, ehci_hcd, ...) compiled as external modules will help find workaround?
  14. Hi, I have two OrangePi Lite running side by side. After working fine for about 8 months both started to experience same issue with wireless: The board works randomly for few hours or few days and then looses wireless connection. When this happens reboot does not help as then issue occurs immediately after the boot. Unplugging and replugging power source resolves that for a while and then happens again I suspect it may not be related to a hardware issue or wireless hotspot, as I have at least 3 other clients that continue to work fine. Searching for it on the internet brought this issue with Raspberry Pi: https://github.com/raspberrypi/linux/issues/1988. Raspberry uses different wireless chipset either. All that makes me think this may be an issue in the kernel itself Any ideas or thoughts? Workaround also appreciated Thanks
  15. Hi Guys, After a long time after the release Linux kernel 4.x I want use the I2S on Lime2 (Armbian Stretch kernel 4.14.14), but I2S interface did not work. I was add activation of overlays i2s0 and i2s1 into/boot/armbianEnv.txt root@lime2:~# cat /boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=dcf7af80-8026-4e99-870f-f0d35f926063 rootfstype=ext4 overlays=i2s0 i2s1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u After reboot I can't see I2S interfaces... root@lime2:~# aplay -l aplay: device_list:270: no soundcards found... root@lime2:~# lsmod | grep snd snd_soc_core 118784 1 sun4i_i2s snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd I2S really supported in Mainline on A20?
  16. Greetings, After setting my tinkerboard pins 22 and 24 as an Inputs, they reverts to being an output pin on HIgh after around 30 seconds. What is the cause of this? Is this some kind of feature. I don't have this happen on any other pin other than these 2. iomari
  17. Hello, I have Banana Pi R2 with armbian bionic. Have two wlan cards both USB, both works. But earlier when I used openwrt on x86 my both wlan and lan were bridged and had one IP - which was router IP. Here with armbian wlan hotspot get other IP than armbian itself. Is there any way to change it to bridge? Or best practices is to leave it as is? regards, Maciek
  18. Hardware setup :: Olimex Lime 2 Rev.k + 7" LCD + 5V power supply through the power jack. No battery is connected to the lime 2 board. Problem :: when the board boots up, the xfce power manager shows that the Battery is connected and it's in charging mode. The current charge value of the battery changes randomly like 92%, 56% and etc. When it reaches 0% the board will shut down. It completes the shut down procedure. The following is the terminal output, to find the battery status. Even though the battery is not connected you can observe that it returns the Voltage and reports that the battery is present root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/voltage_now 2865000 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/present 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/online 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/capacity 0 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/capacity 0 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/online 1 root@olinuxino:~# cat /sys/class/power_supply/axp20x-battery/voltage_now 2879000 root@olinuxino:~# [ OK ] Stopped Unattended Upgrades Shutdown. [ OK ] Stopped target Timers. [ OK ] Stopped target Sound Card. ..... ..... ..... The board shut down as soon as the capacity reached 0%. I have three Lime 2 Rev.K boards, the behaviour is seen in all. What could be the reason for this behavior? Should I disable xfce power manager? What are the other problems with disabling xfce power manager? Can you please tell me the steps to disable the xfce4-power-manager. Note : I am using the Armbian_Ubuntu_bionic_5.1.12 OS with Lime 2 rev.K. It doesn't happen with Armbian_5.72.1 Debian_stretch. Attachments:: AXP209 Charging LED is ON - Even though the battery is not connected to the board, the charging LED is ON. The LED is not continuously ON, it blinks in random order. xfce4 Power manger - Image of xfce4 Power manger which shows that battery is connected even though its not physically connected.
  19. I want to use my GPIO pins on my OPi lite. After much research and testing, I have done the following - Add user pi to group gpio - Changed /etc/udev/rules.d/99-gpio.rules to SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\ chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\ chown -R root:gpio /sys/devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio && chmod -R 770 /sys/devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio;?\ '"???? Now, accessing GPIO pins is working fine via bash: (env) pi@orangepilite:~$ echo 65 > /sys/class/gpio/export (env) pi@orangepilite:~$ echo out > /sys/class/gpio/gpio65/direction (env) pi@orangepilite:~$ echo 1 > /sys/class/gpio/gpio65/value The LED connected to the corresponding pin lights up nicely. The problem is using Python to control the pin. I'm using the python module OrangePi.GPIO (env) pi@orangepilite:~$ python >>> import OPi.GPIO as GPIO >>> GPIO.setboard (GPIO.PCPCPLUS) >>> GPIO.setmode (GPIO.BOARD) >>> GPIO.setup (21, GPIO.OUT) Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: No access to /dev/mem. Try running as root! This error is only there when trying to run the script from user pi. On root it's working fine. How do I access gpio pins on a non root user in python?
  20. I've tried to compile libgpiod (my assumption is this is a user space lib) and it depends on gpio.h which is used by the kernel. According to https://github.com/brgl/libgpiod/issues/22 gpio.h should be installed with linux-libc-dev which is already installed and gpio.h is missing. I installed the kernel headers and tried (it ends up with typedef conflicts): ./autogen.sh --enable-tools=yes --prefix=/usr/local CFLAGS="-I/usr/src/linux-headers-4.14.14-sunxi/arch/arm/include -I/usr/src/linux-headers-4.14.14-sunxi/include" configure: error: linux/gpio.h header not found (needed to build the library) I've attached the config.log. Maybe I'm totally missing the boat, but there's not a lot of info out there build this for ARM and there are no deb packages for ARM I can find. config.log
  21. Greetings. I'm running a headless cluster of Odroid C2's (eMMC) using the latest Armbian buster minimal image with kernel 4.19.69-meson64. I'm encountering an issue where it takes a long time for SSH connection to be accepted (initially up to 30 min consistently). I get a connection refused. The issue seems to be due to the entropy pool becoming depleted during the early boot process which blocks SSH from starting while it refills the pool. The problem seems to be known and documented well here: https://daniel-lange.com/archives/152-Openssh-taking-minutes-to-become-available,-booting-takes-half-an-hour-...-because-your-server-waits-for-a-few-bytes-of-randomness.html As suggested I have installed installed haveged which brings the SSH startup from 30 mins to 10 mins after boot, which is an improvement, but still not good. Has anyone else experienced this issue? Any ideas?
  22. Yesterday my 14" Pinebook arrived so I thought I'll collect some already available information. A lot of work still has to be done to get a decent laptop experience with this hardware so this is neither a review nor a stupid Un-Review but just a preview instead. To get the idea about dimensions I added a 13" and a 15" laptop to the picture. Pinebook is wedge-shaped and thickness matches both the 2011 15" MacBook Pro and the 13" from 2015: Display size closely matches the 13" MacBook Pro (but of course pixel density / resolution don't match as well as quality: TN vs. IPS and coating -- it should be obvious if you've the 'you get what you pay for' principle in mind but I'm sure we'll see reviews somewhere else where people are comparing Pinebook with Chrome/MacBooks and think they would get the same display quality for a fraction of costs) Last hardware detail: heat dissipation. I've been curious how well the Pinebook's thermal design is and it looks pretty good. This is the moronic sysbench pseudo benchmark calculating prime numbers endlessly and the Pinebook sitting on a pillow to prevent airflow below the case bottom. Throttling settings are rather conservative with 65°C defined as first trip point and only after a couple of minutes the internal A64 SoC temperature reached this value and slight throttling occured (1.15 GHz down to 1.1 GHz, that's a 'difference' you won't be able to notice). So it seems the combination of a thermal pad with a large metal plate inside the case is rather sufficient: What you see here is a graph drawn by RPi-Monitor, one of my favourite tools to get a clue what's going on with ARM devices (since it's not a heavy monitoring tool that changes the way the OS behaves but it's pretty lightweight sp you can run it in the background and let it monitor/record stuff like cpufreq scaling, consumption and so on). Pinebook currently ships with a rather clean Ubuntu Xenial on the eMMC with Mate desktop environment based on latest BSP u-boot and kernel. To get RPi-Monitor installed on this Ubuntu @pfeerickprovides a script (please follow progress over there). When I played around with Wi-Fi I noticed that Wi-Fi powermanagement seems to be enabled (makes working via SSH close to impossible) and that MAC address changes on every reboot. To disable Wi-Fi powermanagement I simply used the Armbian way: root@pinebook:~# cat /etc/NetworkManager/dispatcher.d/99disable-power-management #!/bin/sh case "$2" in up) /sbin/iwconfig $1 power off || true ;; down) /sbin/iwconfig $1 power on || true ;; esac Unless Wi-Fi driver gets a fix to use a MAC address based on the SoC's individual so called SID one way to assign a fixed MAC address for the Wi-Fi is to add a wifi.cloned-mac-address property to all NetworkManager profiles after establishing a Wi-Fi connection first: nmcli con show | grep wlan | while read ; do set ${REPLY}; nmcli con modify "$1" wifi.cloned-mac-address $(cat /sys/class/net/$4/address); done (I'm pretty sure some masochistic people prefer fiddling around in /etc/network/interfaces instead so if you're not using your laptop as a laptop being carried around and seeing a lot of Wi-Fis you can also use the usual tweaks for the interfaces file. Please also note that using a random MAC address can be considered a privacy feature on laptops since it makes tracking of you in public environments harder). While watching the Pinebook's charging/discharging behaviour I noticed that consumption drawn from wall while charging oscillates between 9W and 15W while being used and display active so it's really great that Pine Inc fixed Pine64's design flaw N° 1: Pinebook is NOT equipped with shitty Micro USB for DC-IN leading to all sorts of trouble but just like SoPine baseboard now uses a 3.5mm/1.35mm barrel jack combined with a 5V/3A PSU (for other hardware details please refer to linux-sunxi wiki page). Battery status (health, capacity, voltage and so on) is already available through sysfs but some values are wrong or need calibration. This needs to be fixed with further upgrades. Also interesting: charging seems to be under control of the ARISC core inside A64 SoC and works together with Pinebook's AXP803 PMIC (powermanagement IC) even when there's no OS running. This will be somewhat challenging to implement later with mainline I would believe... I'll stop here for now since Pinebook is still stuff for developers and not end users. Just some resources for interested parties: https://github.com/ayufan-pine64/boot-tools (Kamil implemented an u-boot based approach to flash directly to eMMC and there you find the necessary BLOBs to convert other BSP based Pine64 images for Pinebook since different DRAM and other settings require different SPL+u-boot) https://github.com/ayufan-pine64/linux-pine64 (based on longsleep's BSP kernel but with more fixes currently for Pinebook) $mainline resources (I lost track where to find most recent stuff but will add this later) Wrt Armbian running on Pinebook we could now simply exchange u-boot+SPL+DT of our Xenial Desktop image... but I hope we won't do that but wait until dust has settled while helping with development efforts in the meantime. In other words: no Armbian on Pinebook (right) now
  23. I am using Olimex Lime 2 Emmc Rev.k for a project. One of the Boards shuts down randomly. Its not a freeze or a sudden power down of the board. The board undergoes a complete shut down procedure. I checked the log entries in /var/log/syslog log file. There is a entry of board going to shut down but I couldn't find the reason for shut down. Is there a way to find out if the board got shut down because of the Power-button press, shutdown command from a SSH client, shutdown because of temperature or shutdown because of under voltage ? Is there a log file i can check to find the reason for shutdown?
  24. Hi, I know it's a waste of time to play with an old bananapi pro but I think I could do it so I want to do it ! I can't make working PCM5102a DAC. I read a lot of things through different website but noway ! I tried https://forum.armbian.com/topic/9009-info-friendlyarm-pcm5102a-hat-with-nanopi-neo-under-mainline-4xx/ . I've only obtain this next to the step "armbian-add-overlay ./sun8i-h3-I2S-out.dts": $lsmod|grep i2s sun4i_i2s 20480 0 snd_soc_core 114688 2 sun4i_codec,sun4i_i2s snd_pcm 69632 4 sun4i_codec,sun4i_i2s,snd_pcm_dmaengine,snd_soc_core I tried the next step but nothing more: dmesg|grep -i pcm keep empty. I tried to make a module with this tuto https://hackaday.io/project/162373/instructions with the make command and his model of pcm5102a.c file, nothing more. I tried too with https://github.com/torvalds/linux/blob/master/sound/soc/codecs/pcm5102a.c failed ! aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun4icodec [sun4i-codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 Anyway ! Where I am wrong ? Is there a step that I do well ?
  25. Hello, I am trying to communicate with a mcp2515 breakout (8Mhz oscillator) on an Orange Pi Pc+ I have modified the breakout following info on Raspberry Pi: HowTo/Quickstart MCP2515 to keep logic level @3v I have two other nodes composed by two Arduinos, with same (not modified) breakout, one that transmits the other receives. I have successfully tested the first breakout (used on OPi) with an Arduino (powered by 3.3v and 5v on TJA1050). It lets me think that hardware is OK. Below photos of wiring (nb: orange wire becomes red, is wired near TJA1050 = 5v): It seems I have the same results with (edited) user_overlay and the compiled one provided in zador.blood.stained's post dmesg| grep 'can\|mcp\|spi' [ 6.701431] mcp251x spi0.0 can0: MCP2515 successfully initialized. [ 28.455699] can: controller area network core (rev 20170425 abi 9) [ 28.471752] can: raw protocol (rev 20170425) The controller seems well seen, I can bring up the can0 interface: sudo ip link set can0 type can bitrate 125000 triple-sampling on sudo ifconfig can0 up ifconfig can0 can0: flags=193<UP,RUNNING,NOARP> mtu 16 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC) 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 candump is mute although the Arduino receiver displays messages from Arduino transmitter. And cansend do not give error but I could not see this messages on Arduino receiver. Does someone would have an idea of what I am missing ?