Search the Community

Dear Community, I'll build a Developer Team specially for Banana Pi Boards!" GPIO Libarys I started updating/modifing the old GPIO-Libarys, so they can be used on the latest builds! I want to build a Team, for GPIO-Libary Development, for porting these Libarys: WiringPi-Node WiringPi-PHP WiringPi-Perl WirinigPi-Ruby gpiozero rpi-gpio Updating and modifying these: RPi.GPIO BPI-WiringPi2-Python BPI-WiringPi2 At the end, all currently working GPIO Libarys are: luma.oled RPi.GPIO BPI-WiringPi BPI-WiringPi2 BPI-WiringPi2-Python Armbian Build System for Banana Pi I started building the build-system for full banana pi support! Anyone who would like to join the developer-team, just pn me, post in this thread, or contact me on github or discord!" I created a GIthub-Organisation for this project and a Discord Server. A Domain & VPS Server is commin Monday!" Goals: Support ONLY for Banana Pi Boards Board Determiner Script which exports Board-Infos, required by gpio-libs (usual located at: /var/lib/bananapi) APT-Mirror Archive Hosted by our project-teams vps-server! ( Mirror stores all latest gpio-libarys we specially build for using on latest builds and other packages we'll develope in future) Added APPGROUPS: Pentesting, TV-Box, Server-Side, Game Desk & Development Revised menu for selecting extensions and other additional items Revised config menu Adding additional build options A Web-Based Project-Server Hosted Build-System will be build and available on the project-page, where you can build images remotely, according to you settings made in the WebInterface, with live progress & build-log + downloading compressed own image-release. A publish option will be added to, where you can upload your builded image to any Cloud/Storage we provide. Revised device trees According to APPGROUPS and Enabled Extensions: I2C, SPI, UART are enabled in the gpio_develope extension, and all requirements for gpio-programming are pre-installed, the gpio libs are pre-installed too. If you have some Ideas, what we could add or which wishes we can make true, just reply in this post, or contact us. Github Organisation Discord greetz, hexzhen3x7

This is what the network status looks like immediately after turning on the power: $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether d6:e3:db:f5:f2:24 brd ff:ff:ff:ff:ff:ff inet 192.168.100.124/24 metric 100 brd 192.168.100.255 scope global dynamic end0 valid_lft 259179sec preferred_lft 259179sec inet6 fe80::d4e3:dbff:fef5:f224/64 scope link valid_lft forever preferred_lft forever 4: wlx60fb005126f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 60:fb:00:51:26:f0 brd ff:ff:ff:ff:ff:ff This is what the network status looks like after a reboot: $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether d6:e3:db:f5:f2:24 brd ff:ff:ff:ff:ff:ff inet 192.168.100.124/24 metric 100 brd 192.168.100.255 scope global dynamic end0 valid_lft 258362sec preferred_lft 258362sec inet6 fe80::d4e3:dbff:fef5:f224/64 scope link valid_lft forever preferred_lft forever Nothing helps other than unplugging the power cable and plugging it back in. Tried the following images: Armbian_24.8.1_Bananapim2pro_bookworm_current_6.6.47_minimal.img.xz Armbian_24.5.3_Bananapim2pro_bookworm_current_6.6.36_minimal.img.xz Armbian_24.2.1_Bananapim2pro_bookworm_current_6.6.16.img.xz Outputs of armbianmonitor -U are in attachment. wifi_ok.txt wifi_no.txt

Whatever I plug into the usb otg port, it doesn't get recognised. I think the port got disabled. What happened? I connected a new harddrive via usb3 but the machine wouldn't boot because of some "Unexpected XHCI event". I had to add a usbstoragequirks to u-boot env. (via armbian-config) to solve that, but now the usb otg port is no longer working. Googled a lot and found one possible solution but it did not work for me ( https://forum.banana-pi.org/t/topic/5485/13 ). https://paste.armbian.com/aqowuxukev

I can't upgrade armbian focal to bullseye.

Sorry about off-topic, just got forum giveaway Banana Pi M2 Pro and got confused - manufacturer doesn't care to reveal power jack size and all my 5V power adapter plugins are too small or too large. Can some happy owner of this SBC share plugin dimensions?

I have recently acquired a BPI-M2 Pro with what is supposed to be USB WiFi (Realtek RTL8821CU). I am running Armbian 22.08.7 Bullseye. armbian-config does not recognize any WiFi. The output from lsusb -t also does not show the presence of USB WiFi as expected. root@bananapi-m2p:~# lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M Do I have a defective device, or is the WiFi not actually a USB module? Is there something else I need to try to enable WiFi? Thanks, Ray