Search the Community
Showing results for tags 'bananapi'.
-
Machine model: Banana Pi M2 Berry Linux bpi08 6.2.7-sunxi #3 SMP Fri Mar 17 07:58:04 UTC 2023 armv7l GNU/Linux (armbian@next) Mir ist es nicht möglich eine interne Temperatur auszulesen. Brauche dringend Hilfe! Der Link“/etc/armbianmonitor/datasources/soctemp “ exitiert zwar, nur die Datei / das Verzeichnis existiert nicht: nicht vorhanden → /sys/devices/virtual/thermal/thermal_zone0/temp nicht vorhanden → /sys/class/thermal/thermal_zone1/temp Wo soll diese Dateien überhaupt erstellt werden? Anmerkung Es wäre schön, wenn es für den Banana Pi M2 Berry eigene Tags geben würde. Er unterscheidet sich von dem Banana Pi M2+.
-
Hi, I am looking for an OS for the BPi M2 Berry. Has anyone good experiences to share? Thanks a lot in advance, Friedrich I tried several OS, flashed with rufus.io No satisfying attempt yet. Last try is this: https://forum.banana-pi.org/t/bananapi-bpi-m2-berry-new-image-release-armbian-bullseye/14451
-
On my Banana Pi M5 Armbian Jammy has a strange device name assignment. BPi-M5 has internal 16GB eMMC normally named mmcblk0 and microSD named mmcblk1. Normally it boots from SD and if you install an OS like Raspberry OS for BPi into eMMC, you're still able to boot from SD another OS because RaspiOS maps device correctly. But when Armbian (i.e. Jammy) is installed into eMMC it changes eMMC device to mmcblk1 and SD to mmcblk0, and It prevents SD to boot. And if the eMMC OS corrupts and doesn't boot the SBC bricks and TTL connection is needed to erase boot record. To change OS it's necessary a command to delete boot record and SD on mmblk1 will boot again: dd if=/dev/zero of=/dev/mmcblk1 bs=512 count=1 But the OS on eMMC has to boot and be in good working conditions. Also another guy with Orange Pi has noticd this behaviour: https://forum.armbian.com/topic/9987-sd-card-not-booting-but-works-on-another-emmc-boot-up/ It's important to change this behaviour and do it like RaspiOS.
-
I had successfully installed Armbian_2022.08.8_Bananapi_bullseye_CLI_5.15.74 on my M1 and copied the system to an SSD which I had attached to the SATA port. Then I had updated the UUID in armbianEnv.txt and running the system from SSD was working fine. The system was running headless in my closet for about 2 months, and I even had no problems to remotely restart the device until today, when it did not come back up after a reboot. I took it from the closed and hooked it to a monitor just to see the following error messages: ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 I suspected a broken SD card but a check on my Ubuntu desktop showed no errors on the cards file system. Then I prepared 2 other SD cards, one with Armbian_2022.08.8 as above and the other with Armbian_2023.02.2_Bananapi_bullseye_5.15.93_minimal. Both did show the same problem, though. To me, it looks like a hardware problem with the SD card slot. Is there a way to get the M1 back to work again?
-
armbianmonitor output: http://ix.io/4qwA I assume it's crashing as I have no display connected to it. Every few days I just notice I can no longer reach the network folder, but it works after a power off/power on. Not much running on it, samba for file share and deluge for occasional downloads. I also recently run an update, upgrade and dist-upgrade, but it didn't help. I don't really know what should I look for in the log. OS: Armbian buster (21.02.1) armv7l Host: LeMaker Banana Pi Kernel: 5.15.93-sunxiC CPU: Allwinner sun7i (A20) Family (2) @ 960MHz
-
Hello, im trying to map the i2c-2 to some GPIO ports and have to rewrite the device-tree on armbian 22.04. I'm failing miserably and have no idea how-to do it. I managed to compile the i2c-gpio.ko kernel module as it is not part of the armbian 5.15.89-sunxi kernel. However, here i'm stuck and cant manage to make it happen. On RPi it was simple adding an overlay to config.txt: dtoverlay=i2c-gpio,bus=2,i2c_gpio_sda=27,i2c_gpio_scl=17 /boot/overlays/i2c-gpio.dtbo I'm trying to replicate that for Armbian, here is my dts file: // Overlay for i2c_gpio bitbanging host bus. /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/"; __overlay__ { i2c_gpio: i2c@2 { reg = <0>; compatible = "i2c-gpio"; gpios = <&pio 17 0 /* sda */ &pio 27 0 /* scl */ >; i2c-gpio,delay-us = <2>; #address-cells = <1>; #size-cells = <0>; }; }; }; fragment@1 { target-path = "/aliases"; __overlay__ { i2c_gpio = "/i2c@2"; }; }; fragment@2 { target-path = "/__symbols__"; __overlay__ { i2c_gpio = "/i2c@2"; }; }; __overrides__ { i2c_gpio_sda = <&i2c_gpio>,"gpios:4"; i2c_gpio_scl = <&i2c_gpio>,"gpios:16"; i2c_gpio_delay_us = <&i2c_gpio>,"i2c-gpio,delay-us:0"; bus = <&i2c_gpio>, "reg:0"; }; }; What am I doing wrong?
-
I'm using Banana Pi M2 Zero with Armbian Debian GNU/Linux 10 (Buster). Compiled the image myself with the latest source code using the armbin/build repository. I want to be able to do serial communication on pins 8 and 10. I'm looking for something to appear at /dev/ttyAMA0, so I can communicate with it. I saw some other forum posts which mentioned it'll happen on /dev/ttyS0 , however even that is not happening. The serial communication is working via FTDI (using the USB side connected to the Banana Pi), which indicates there is no problem with the other device. This is what the configuration looks like using "sudo minicom -s". +-----------------------------------------------------------------------+ | A - Serial Device : /dev/ttyS0 | | B - Lockfile Location : /var/lock | | C - Callin Program : | | D - Callout Program : | | E - Bps/Par/Bits : 115200 8N1 | | F - Hardware Flow Control : No | | G - Software Flow Control : No | | | | Change which setting? | +-----------------------------------------------------------------------+ | Screen and keyboard | | Save setup as dfl | | Save setup as.. | | Exit | | Exit from Minicom | +--------------------------+ I have enabled "uart1" using "sudo armbian-config -u" -> System -> Hardware. Connecting Rx, Tx on the pins 8 and 10 also does not show up in "dmesg" How do I go about debugging the issue or finding the root cause of the problem? Many thanks!
