Jump to content

Search the Community

Showing results for tags 'bananapim2ultra'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 13 results

  1. Hi everyone I have a litlle problem with my customize-image.sh, in my previous version builded last year everything go ok, but currently I cannot copy my scripts from tmp/overlay to /home/$user. When I am looking into the logs everything looks properly, few moments ago I tried copy these files into root folder and everything is ok but I still cannot copy anything to my home folder... I also try check proper adduser command logging into the system during build and I also find my home/$user catalogs but on the built image home folder is empty. Have you any suggestion or solution to fix that issue ?
  2. Hi I have here Banana Pi M2 Berry and I want to use it now as web server, plus few more things, ftp, plex, pi-hole and later also for use some sensors on it. What the best the best OS for it? Armbian is always made for Ultra not Berry and most versions make problems 🙄😒😉 The GUI itself is so !SLOW!, maybe the driver for video are also not right? Can someone give me a link to a proper Armbian for Banana Pi M2 Berry ??? Or advice what for alternative OS?
  3. Dear Community, I want to build a custom FirmWare for Banana Pi M2 Berry, im currently using the BPI-M2-Ultra Firmware, cuz no BPI-M2-Berry FirmWare exist. What do I need for building for my SBC(BPI-M2-Berry) ? I want to use my SBC as a LTE-Router/ Mesh-Repeater and want to pre-install some necessary packages, the device need. I want to build a Dashboard for Administrate the Device. Maybe I'll use electron + reactjs, or would it be better to use php for it? Greetz BlackLeakz
  4. The long explanation is here Before: # dmesg ...... [ 9.606887] thermal_sys: Failed to find 'trips' node [ 9.606902] thermal_sys: Failed to find trip points for thermal-sensor id=1 [ 9.606923] sun8i-thermal 1c24c00.thermal-sensor: Failed to register sensor 1 (-EINVAL) [ 9.606938] sun8i-thermal: probe of 1c24c00.thermal-sensor failed with error -22 ...... My patch for sun8i-r40.dtsi. Yes, it's copy-paste with changing names of a cpu thermal trip point for a gpu thermal trip point. Now it's ok # ls /sys/devices/virtual/thermal/ cooling_device0 thermal_zone0 thermal_zone1 fix_gpu_thermal_zone_sun8i-r40_bananapi-m2u.patch
  5. Hi everyone! To cut long story short I have to make a microUSB port work as USB Host. I found out that there is a patch that will bring the port up. Last year I managed to build a full custom image for my board using armbian documentation. I've already successfully upgraded software upto Armbian 23.8.1 Bullseye with Linux 6.1.53-current-sunxi So I'm going to build custom kernel with the patch applied to arch/arm/boot/dts/sun8i-r40.dtsi https://github.com/Vutlan/linux-sunxi/commit/e0b16f86b91b5b03c4acd041aa2d45eb688378b2#diff-fb8cf9a1a0b868557516caf54f4e966b ehci0: usb@1c14000 { compatible = "allwinner,sun8i-r40-ehci", "generic-ehci"; reg = <0x01c14000 0x100>; interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_EHCI0>; resets = <&ccu RST_BUS_EHCI0>; phys = <&usbphy 0>; phy-names = "usb"; status = "disabled"; }; ohci0: usb@1c14400 { compatible = "allwinner,sun8i-r40-ohci", "generic-ohci"; reg = <0x01c14400 0x100>; interrupts = <GIC_SPI 40 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_OHCI0>, <&ccu CLK_USB_OHCI0>; phys = <&usbphy 0>; phy-names = "usb"; status = "disabled"; }; The main question : Am I going to move in a right direction ? What I've already done: - "git pull" in armbian/build directory. Now I'm trying to build a kernel from the edge branch (because 6.1.y kernel is in the edge branch) for BananaPi M2 Ultra. During the compilation the script is trying to add RTL8811CU and ask for someone's github credentials. When I've feed it with my credentials it is answered that "remote: Support for password authentication was removed on August 13, 2021." So it's been failed. Mayby I should remove old clonned local repository and re-clone it from github again ? Although u-boot has been built successfully. But it's an earlier branch than installed - 23.02.0-trunk. What should I build at all to make microUSB port work as USB Host ? Or maybe it's possible to make necessary changes in my current configuration, isn't it ? Any suggestions are welcome P.S. I've already removed an old armbian/build folder and clonned again. Script compile.sh works well, there's no question about github credentials.
  6. Is there a way to skip this phase? Is it possible to force board to boot from SD card again? I have BananaPI M2 Ultra v1.1 board and my goal is to get this little device boot Linux OS from its eMMC storage. So I entered URL https://www.armbian.com/bananapi-m2u/, connected board with keyboard, display and ethernet switch and downloaded image (Bookworm CLI). Then I followed document at https://docs.armbian.com/User-Guide_Getting-Started/ and was able to get my board boot from SD card. Then I made configurations as guided and lastly proceeded installation to eMMC. Then I made poweroff, took SD card out and started board. Boot started nicely but sadly stuck at stage "Scanning for Btrfs filesystems". I read also document at https://docs.armbian.com/User-Guide_Recovery/ but it didn't help. EDIT: I forgot to mention that I chose ext4 filesystem when doing installed into eMMC. EDIT: And booting from this same SD card fails if I flash it again.
  7. Hi, Just started playing with BananaPi (I have M2Berry model) and installed Armbian from Armbian download page: Armbian_23.5.2_Bananapim2ultra_bookworm_current_6.1.30_minimal (connecting with board over UART/SSH - no need for desktop at this moment). Wanted to use GPIO, however using sysfs do not work as expected: root@bananapim2ultra:~# echo "24" > /sys/class/gpio/export -bash: echo: write error: Unknown error 517 root@bananapim2ultra:~# echo "24" > /sys/class/gpio/export -bash: echo: write error: Device or resource busy Went with lsmod to check modules but having only: root@bananapim2ultra:~# lsmod | grep gp gpu_sched 28672 1 lima Same for modprobe: root@bananapim2ultra:~# modprobe gpio modprobe: FATAL: Module gpio not found in directory /lib/modules/6.1.30-sunxi It looks like the kernel do not have gpio module, which is really strange since the GPIO is main feature for such boards. Running armbian-config - maybe I will find something. Can somebody help me out a little with it?
  8. I've been trying to bring up Armbian on my Banana Pi M2 Ultra (with A40i SoC). First I tried using the community rolling release, and then building it myself from source code. In every case, it was failing to boot; on the HDMI console it was hanging at the stage where the initrd was attempting to scan for the root partition. ("Scanning for btrfs filesystems") Taking a closer look at the verbose output of the UART console during a boot attempt, I saw that there was an error message about the sunxi-mmc device driver experiencing a failure while it was enumerating the EMMC chip: [ 4.136553] mmcblk2: mmc2:0001 8GTF4R 7.28 GiB [ 4.144362] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 4.150727] sunxi-mmc 1c11000.mmc: send stop command failed On a hunch, I patched the device tree to disable that interface. After compiling that change and installing a new image on a microSD card, the board booted flawlessly, and I am now in a working desktop environment. This leads me to a question: How likely is it that there's just some damaged/defect on my particular board which makes its EMMC unusable? (In which case I might stop here, and be satisfied with the result: Because, I'm not particularly interested in working with the EMMC chip anyway.) Or, it is possible that there's a systemic problem with the Banana Pi M2 Ultra device tree which would be equally impacting everyone's ability to boot? (In which case it might be worthwhile to dig a little deeper, try to figure out why the kernel is hanging when it attempts to enumerate the EMMC chip, and perhaps submit a patch to fix the problem.) Has anyone else experienced this? Or, in case this is a systemic problem, does anyone have some advice about the most appropriate next steps to contribute a fix back to the community?
  9. Is there any way to get interrupts working on BPI M2 Berry/Ultra? I tried with raspbian and wiringPI/RPi.GPIO but there is a wait for support() “bug” which has been reported a while ago but no updates have been made in the thread. Currently Im running Armbian 22.11.00. If anyone has some experience or suggestion for a library/smth and is willing to share it that would be great. Thank you for your time.
  10. Hello, In a GOLANG based, RPi 3B+ project I am using the https://github.com/stianeikeland/go-rpio package to read the state of the GPIO-s. I am planning to set up some Banana Pi M2 Berries with the same software. The package - as it was expected - doesn't work with the M2 Berry. I could adapt the package for the Berry, but I don't know which peripheral chip is used in it. Does anyone know which peripheral chip is used in the Berry? (The schematic diagram on BPI's page is useless). Thanks, G.
  11. Hello! I met next problem: I need configure UART communication with baud rate 1 Mb/s (or 2 or 3). But internal clock of the bus is 1.5 MHz, and if i try to communicate with 1 Mb/s, error is too big. Is it possible somehow change internal clock of the uart? Or maybe any other possibilities how to configure such communication ? Or maybe you know any models with higher internal clock of the bus (Like on 6.5 MHz on raspberry pi 4, for example) ? Now one section is equal to 1.333 microseconds, but it should be 1.0 mcs. I found same topic at this forum, but it's no solution there: Thank you and have a good day
  12. Hi all. Firstly, sorry I had posted this query in the wrong forum. I´m trying to add support for a raw SPI comunication through SPI0, as it´s a custom comunication with a little auxiliary board, I think best option is to have a spidev device. My scenario is: Banana pi m2 ultra Armbian 5.4.35-sunxi, server (No gui). I have been modifying .dts and .dtsi files, here are parts of the files that I modified: sun8i-r40.dtsi spi0_pins: spi0-pins { pins = "PC0", "PC1", "PC2"; function = "spi0"; }; spi0: spi@1c05000 { compatible = "allwinner,sun8i-spi"; device_type = "spidev"; reg = <0x01c05000 0x1000>; interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>; clock-names = "ahb", "mod"; pinctrl-names = "default"; pinctrl-0 = <&spi0_pins>; resets = <&ccu RST_BUS_SPI0>; status = "disabled"; #address-cells = <1>; #size-cells = <0>; }; sun8i-r40-bananapi-m2-ultra.dts &spi0 { status = "okay"; num-chipselects = <1>; cs-gpios = <&pio 2 23 GPIO_ACTIVE_LOW>; // CS = PC23 spidev@0 { reg = <0>; compatible = "spidev"; status = "okay"; spi-max-frequency = <1000000>; }; }; I created a script to compile these files !/bin/bash sudo cpp -nostdinc -I include -I arch -undef -x assembler-with-cpp arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts preproc.dts dtc -I dts -O dtb -o sun8i-bananapi-m2-ultra.dtb preproc.dtc And I get my new dts. As a comment, the compilation of the device tree throws me this warning: sun8i-r40-bananapi-m2-ultra.dtb: Warning (unit_address_vs_reg): Node /clocks/clk@1 has a unit name, but no reg propert However, I think it is prior to my modifications, because if I delete all my changes the warning is already there. So, next step, I procede to replace original dtb in Banana pi with the one that I just generated, under /boot/dtb-5.4.35-sunxi/ And then, reboot. I expected to get spix.y device under /dev but there is no change here. If i decompile my new dtb, I can see spi spi0-pins { pins = "PC0", "PC1", "PC2"; function = "spi0"; phandle = <0x20>; }; spi@1c05000 { compatible = "allwinner,sun8i-spi"; reg = <0x1c05000 0x1000>; interrupts = <0x0 0xa 0x4>; clocks = <0x7 0x29 0x7 0x71>; clock-names = "ahb", "mod"; pinctrl-names = "default"; pinctrl-0 = <0x20>; resets = <0x7 0x11>; status = "okay"; #address-cells = <0x1>; #size-cells = <0x0>; num-chipselects = <0x1>; cs-gpios = <0xd 0x2 0x17 0x1>; So, Could somebody please tell me what thing (or probably things) I am doing wrong, or if there are any steps I am forgetting? Just in case, I modified the armbianEnv.txt that way overlay=spi-spidev param_spidev_spi_bus=0 to add the spidev overlays (although if I'm not wrong this shouldn't be necessary, since I already enabled spi from the dts, is that correct?) Thanks in advance to anyone who takes the time to read my issue, and if you have any suggestions, they will be more than welcome. Regards. mhc
  13. I put the log of the console... I can compile a linux 4.11 and ubuntu 16.04.3 server with the packet from ARMBIAN... thats greats... but i had to correct some files to compile OK!!! Ubuntu 16.04.3 LTS bananapim2ultra ttyS0 bananapim2ultra login: root Password: Last login: Mon Nov 13 20:47:13 UTC 2017 on ttyS0 ____ ____ _ __ __ ____ _ _ _ _ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | \/ |___ \ | | | | | |_ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |\/| | __) | | | | | | __| | |_) | (_| | | | | (_| | | | | (_| | | __/| | | | | |/ __/ | |_| | | |_ |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_|_____| \___/|_|\__| _ __ __ _ | '__/ _` | | | | (_| | |_| \__,_| Welcome to ARMBIAN 5.34 user-built Ubuntu 16.04.3 LTS 4.11.0-rc8-next-20170427-sunxi System load: 0.18 0.18 0.09 Up time: 3 min Memory usage: 1 % of 2017MB IP: Usage of /: 63% of 1.6G root@bananapim2ultra:~#
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines