I am trying to connect a ds3231 module to get time during boot (dns does'nt like 1970) and without internet connexion. I load a recent build UBUNTU 26.2.1 on the M5 but unfortunatly after 2 days of research with chatgpt , I ask to knowledge experience people if they know if it's possible and which kind of dts can make this module up and running. I did'nt identify a dtbo on the distribution , a made a lot of investigation , pin 3 and 5 og the 40pins connector is connect to the cpu with pullup resistor , i try a lot dts conf and nothing gave result. If some one did this kind of connexion thanks in advance.

Gérard

Needing a backup system, I was enamored of the low power requirements to run the bpi-m5.  But they have no sata ports to drive bigger SSD's. But I bought a 5 stack of 4Tb TMSC built SSD drives at $200/copy, figuring on using a USB3.2 hub and startech's usb3.2 to sata adaptors, a big drive cage and a 50 watt 5 volt psu. More than 3 drives plugged in was too much current for the hub, itgot hot & shut down, so I bought another hub & glued it to the otherside of the drive cage. Problem solved. Printed the shelves to hold the drives and a BPI-m5.  I configured the 5 SSD's into a software raid6 of 11TB. A friend that is really good at shell scripts knocked up an rsync based thing that could go thru the user trees of all my machines, currently itself, this box, and all my cnc stuff in the garage, several 3d printers, a total of 8 machines, soon to be 9, making a backup of /home/gene or /home/cnc since cnc is first user on the pi running my big but old Sheldon lathe. This draws around 15 watts idling, up to 19 watts running, and does it all in 28 or 29 minutes.  So that is something else these pi clones can do, and do very well.

I've run it 7 or 8 times in two weeks, adding another 3d printer to the $systems list each time. Its used 4% of the 11TB so far.  Using rsync the only expansion in storage is the backup copy of any file thats been changed since the last run.

I love doing odd stuff  like this just to see if it can be done. And it has succeeded beyond my expectations. That rpi4b running that lathe was another such "project".  Started with an rpi3b which wasn't quite fast enough but its been running for over a decade, almost a decade since I switched it to a rpi4b.  There, when the lathe is off, linuxcnc controls that too, the pi and monitor show as a 23 watt load.  Whats not to like?

The pager requires 10 or more mouse clicks, starting with the _ . . . .  . at the upper left corner of what I think is the default xfce4 screen. All the eye candy and mouse clicks to actually switch workspaces are very distracting when one is trying to configure klipper. Can all this be reduced to a single click on the dot representing that workspace in the micro-pager? 

The eye candy is impressive to visiting frogs, until its a PITA when actually doing work. We buy these things in 6 pack qty's to do work, and give you a small monthly support, but impressing the frogs is maybe .0000002% of the time spent as I don't invite the frogs in to see my printer farm very often.

i have a screen thats bigger than what I could see (frame).

on a raspberry, i change the config with overlay adjustment. But i dont know how to do this for the banana pi..

Someone Here could redirect me the rijgt pad where to fix it?

I want to replace these OS with armbian server. I tried  armbian v6.12 (Ubuntu KDE 24.04, Ubuntu Server 24.04 and Minimal IOT). None of them boot from SD card.

The Ubuntu 20.4 image downloaded from BPI site boot well from SD card.

I have restored the original Android image with Amlogic burnin tool on one M5 and Armbian don't boot from SD but the ubuntu 20.4 from BPI site works well.

I don't known what to do ?

Thank's in advance

After doing the magic combination CTRL+ALT+F1/F2 and login in console mode,

this will fix the issue and open the gates of cinnamon
 

sudo apt install xinit

Enjoy ,

       SoSie

Also I ordered 2 more of the keyboard/mouse combo''s which are the same as I'm using with a similar install for klipper running a 3d printer, but the dongle doesn't init when plugged in ack dmesg output, refusing its on discovery assigned address.  So no keyboard/mouse is locally possible. I'll unpack the 2nd identical copy and see if its also broken. Switching back to an ultra- micro sized keyboard with a touchpad mouse works fine. And the second keyboard/mouse works as expected. The pw gizmo ask's for amandabackup's pw, I gave it my first user pw which it accepted logging me in normally. So I typed whoami and it responded gene.  So wth is confusing the login requester?????????

Many Thanks for any assistance. And why do I have  to say solved in order to post when its not solved?? Counter productive to other readers.

I'm trying to control an 5v PWM Fan using hardware PWM pins of Banana Pi M5.
I'm not able to output any pwm signal on any pin.

It looks like there is an pwm controller visible at `/proc/device-tree/soc/bus@ffd00000/pwm@19000`.
File `/proc/device-tree/soc/bus@ffd00000/pwm@19000/status` has content `okay` and file `/proc/device-tree/soc/bus@ffd00000/pwm@19000/pinctrl-0` has content `&`.

When i run script:
 

echo 0 | tee /sys/class/pwm/pwmchip0/export
echo 40000 | tee /sys/class/pwm/pwmchip0/pwm0/period
echo 20000 | tee /sys/class/pwm/pwmchip0/pwm0/duty_cycle
echo 1 | tee /sys/class/pwm/pwmchip0/pwm0/enable

echo 1 | tee /sys/class/pwm/pwmchip1/export
echo 40000 | tee /sys/class/pwm/pwmchip1/pwm1/period
echo 20000 | tee /sys/class/pwm/pwmchip1/pwm1/duty_cycle
echo 1 | tee /sys/class/pwm/pwmchip1/pwm1/enable

(only those 2 pins of PWMs are free, script runs without any errors)

i cannot detect any pwm signals on any of 40-pin connector.

Additionally after that :
 

#: cat /sys/kernel/debug/pinctrl/*/pinmux-pins | grep pwm
pin 81 (GPIOX_16): ffd19000.pwm (GPIO UNCLAIMED) function pwm_e group pwm_e
pin 13 (GPIOE_1): ff802000.pwm (GPIO UNCLAIMED) function pwm_ao_d group pwm_ao_d_e

#: cat /sys/kernel/debug/pwm
0: platform/ff802000.pwm, 2 PWM devices
 pwm-0   (sysfs               ): requested enabled period: 100000 ns duty: 50000 ns polarity: normal
 pwm-1   (regulator-vddcpu    ): requested enabled period: 1250 ns duty: 100 ns polarity: normal

1: platform/ffd19000.pwm, 2 PWM devices
 pwm-0   (wifi32k             ): requested period: 30518 ns duty: 15259 ns polarity: normal
 pwm-1   (sysfs               ): requested enabled period: 100000 ns duty: 50000 ns polarity: normal

So looks like pwm signals are not routed to IO pins.

I tried to add overlay :

/dts-v1/;
/plugin/;

/ {
    compatible = "bananapi,m5", "amlogic,meson-sm1";

    fragment@0 {
        target-path = <&pwm_ef>;
        _overlay__ {
            status = "okay";
            pinctrl-0 = <&pwm_e_pins>;
            pinctrl-names = "default";
        };
    };

    fragment@1 {
        target-path = "/";
        __overlay__ {
            pwm_e_pins: pwm_e_pins {
                compatible = "pwm-gpio";
                pinctrl-names = "default";
                pinctrl-0 = <&pwm_e>;
            };
        };
    };
};

which i compiled with dtc and added to  `/boot/overlay-user`, after that i added a line

user_overlays=meson-m5-custom-pwm

to `/boot/armbianEnv.txt`

But it didn't worked. I'm not surprised because it was generated by AI, and i don't now anything about overlays.

Is there anybody that can help me with writing this overlay ? Or maybe there is simpler solution ?

I'm experiencing a severe boot delay on my Banana Pi M5 running Server Armbian Image (v25.2.2 - Banana Pi M5 - Armbian Linux 6.12.21-current-meson64) when no HDMI monitor is connected. The board itself is working fine, but without an HDMI connection, the system takes several long minutes to complete the boot process.

Details
The system boots normally and quickly when an HDMI monitor is attached. However, without a monitor, in headless mode , the boot process is significantly delayed several minutes (approx. 4 minutes). Blue led blinking normaly.

I've Tried modified /boot/armbianEnv.txt by setting:

• display_autodetect=false
• disablehpd=true
• hdmi_force_hotplug=1

Unfortunately, these changes did not resolve the boot delay issue.

Do you please have any suggestions or insights on how to modify the boot process to fix this problem?
Thank you in advance.

I had trouble with the wifi dongle which is TP-Link (RTL8188 skew) product.

The system detects no wifi adapter after booting or reboot, 

however, it can be detected after a hot-plug (remove then plug) action.

How can I solve the problem?

Thank you all.

I am able to boot properly in this mode and "help" properly lists all the commands available in this mode.

On my board Armbian is running in EMMC.

When I invoke "mmc" or the "mmcinfo" commands the system replies with the following error:

Card did not respond to voltage select

If I insert an Sdcard in the slot these two commands do respond properly which implies that uboot is seeing the Sdcard as default.

Is there a way to redirect these commands to the EMMC?

Regards

Hello everyone and thanks for accepting me in the forum. I recently bought a banana pi M5, intalled armbian but i can't use i2c, I tried to enable i2cA and i2cB from armbian-config without success. I have also tested numerous dts files with no success. Can anyone help me with this?
Thank you.

As subtitler guy, I experienced many troubles making aegisub work. ,

I finally made the subtitle editor, working with hardware under armbian jammy but having still annoyances. I want to share my thought and my discoveries on it.
First I would like to thanks all who post on this already, including alternative ways such as schroot and of course the armbian team for the improvements
of the boot .. schroot allow to run an linux in a linux. According to what I experienced, meson driver development is leaded by oibaf and in advance in ubuntu
but here aegisub does exists only on debian.

The idea was thus to boot on debian jammy and chroot in debian buster armhf at least or better bookworm arm64.
By doing so, I crashed many time aegisub 3.2.2 due to lua badly supported.  schrooting and debian bookworm gives many warning messages (see the pict below, I washed the lua script directory too) but
goes further if we dare to skip assert warnings.  Moreover, at this point, we are no more dealing with Llvm (software accel using 100% of CPUs) but meson-drm and panfrost (harware accel, using 20% of CPUs).
aegisub still remains very fragile but very responsive. So today I decided to switch and to boot into bookworm directly.

After launching aegisub 3.20.3 on arm64 with panfrost enabled (you can check this with glxinfo -B, or inxi -Gs), I discovered it is very stable but suffered of responsivity due to a flood in the logs Hewitt has just given... a patch yesterday against  "panfrost ffe40000.gpu: l2 power transition timeout" log flood here: https://lkml.org/lkml/2024/3/22/977
You will also  be unable to set brightness by software (too bright for my eyes) at least on xfce4, trying my luck with all
techniques https://askubuntu.com/questions/894465/changing-the-screen-brightness-of-the-external-screen
that did not succeed except that ddcci-dkms gave me a clue during install : BACKLIGHT_CLASS_DEVICE disabled in this kernel

I suggest enabling dkms and this for future kernel and taking Hewitt patch into account.

With these findings, did someone has noticed the same and manage to make sound and videos responsive without unsync?

PS/ For now, the armbian is on a sdcard, the log flood may be the cause of the unsync. I have to test further. Trying with latest jammy and schrooting under bookworm.

I've recently started migrating a project for Banana Pi M5 from Debian 10 Buster to Armbian, because I've found that the latest versions of it now support the GPU, Mali G31, and come with Panfrost OpenGL driver, which is crucial for this project.

Everything was perfect until I had to implement two features: operating with TV via CEC and showing boot logo. Quickly about the last one - as I've understood, we have to use Plymouth, but I didn't really get how to do it, I've tried to activate it but had no success (how exactly see under paragraph). However, it doesn't work on Server Images (even on those that were compiled with build tools and activated option BOOT_LOGO in kernel conf), but in GUI Images everything is fine with it. Also I've tried using uBoot logo (boot-logo.bmp.gz), but also no success.

# Adding "splash quiet loglevel=0 logo.nologo" to extraargs in "/boot/armbianEnv.txt"
# Activating bootlogo in "/boot/boot.cmd" (am I even supposed to edit this file?)

sudo plymouth-set-default-theme -R customtheme # It contains our logo
# sudo update-initramfs -c -u # In fact, it runs automatically
sudo reboot
# ...
sudo plymouthd
sudo plymouth --show-splash

Now about CEC. I've made some observations:

CEC Under Debian

# Sorry, there is no support for Shell syntax highlighting apparently.

pi@TEST:~$ uname -a
Linux TEST 4.9.312-BPI-M5 #1 SMP PREEMPT Wed Mar 1 01:44:35 UTC 2023 aarch64 GNU/Linux
pi@TEST:~$ cec-client -l
libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC
Found devices: 1

device:              1
com port:            AOCEC
vendor id:           0000
product id:          0000
firmware version:    5
type:                unknown

pi@TEST:~$ ls -l /dev/*cec*
crw-rw-rw- 1 root root 503, 0 Feb 14  2019 /dev/aocec
pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1
opening a connection to the CEC adapter...
pi@TEST:~$ # Works fine.
pi@TEST:~$ echo 'on 0' | cec-client -s -d 1
opening a connection to the CEC adapter...
pi@TEST:~$ # Works fine.
pi@TEST:~$ sudo lsmod | grep cec
pi@TEST:~$ sudo find /lib/modules/ -name "*cec*"
pi@TEST:~$ # No CEC module in lsmod or modules overall, but works fine.
pi@TEST:~$

It uses AOCEC on 4.9 Linux kernel. Works flawlessly.

All the parts in "/boot/boot.ini" concerning CEC:

...

### voutmode : hdmi or dvi
setenv voutmode "hdmi"
# setenv voutmode "dvi"

# HPD enable/disable option
setenv disablehpd "false"

# Enable/Disable CEC
setenv cec "true"

...

### Normal HDMI Monitors
if test "${display_autodetect}" = "true"; then hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi

...

# Boot Args
setenv bootargs "...${cec_enable} sdrmode=${sdrmode}"

...

If I set cec "false" this happens:

pi@TEST:~$ cec-client -l
libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC
Found devices: 1

device:              1
com port:            AOCEC
vendor id:           0000
product id:          0000
firmware version:    5
type:                unknown

pi@TEST:~$ ls -l /dev/*cec*
crw-rw-rw- 1 root root 503, 0 Feb 14  2019 /dev/aocec
pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1
opening a connection to the CEC adapter...
unable to open the device on port AOCEC
ERROR:   [            2233]     AllocateLogicalAddresses - failed to allocate device '0', type 'recording device'
ERROR:   [            2233]     failed to find a free logical address for the client
ERROR:   [            2233]     failed to register the new CEC client - cannot allocate the requested device types
ERROR:   [            2233]     failed to register a CEC client
pi@TEST:~$ # Doesn't work
pi@TEST:~$

Here, "/dev/aocec" doesn't sweep away when setting CEC to false. It just becomes unaccesible.

CEC Under Armbian

pi@TEST:~$ uname -a
Linux TEST 6.6.8-edge-meson64 #1 SMP PREEMPT Wed Dec 20 16:02:07 UTC 2023 aarch64 GNU/Linux
pi@TEST:~$ cec-client -l
libCEC version: 6.0.2, compiled on Linux ... , features: P8_USB, DRM, P8_detect, randr, Exynos, Linux, AOCEC
Found devices: NONE
pi@TEST:~$ ls -l /dev/*cec*
ls: cannot access '/dev/*cec*': No such file or directory
pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1
autodetect FAILED
pi@TEST:~$ echo 'on 0' | cec-client -s -d 1
autodetect FAILED
pi@TEST:~$ sudo lsmod | grep cec
pi@TEST:~$ sudo find /lib/modules/ -name "*cec*"
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/pulse8/pulse8-cec.ko
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/rainshadow/rainshadow-cec.ko
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio/cec-gpio.ko
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec.ko
/lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec-g12a.ko
/lib/modules/6.6.8-edge-meson64/kernel/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.ko
pi@TEST:~$ sudo modprobe cec
pi@TEST:~$ sudo modprobe cec-gpio
pi@TEST:~$ sudo modprobe ao-cec
pi@TEST:~$ sudo modprobe ao-cec-g12a
pi@TEST:~$ sudo modprobe dw-hdmi-cec
pi@TEST:~$ sudo modprobe pulse8-cec
pi@TEST:~$ sudo modprobe rainshadow-cec
pi@TEST:~$ sudo lsmod | grep cec
rainshadow_cec         16384  0
pulse8_cec             24576  0
dw_hdmi_cec            12288  0
ao_cec_g12a            12288  0
ao_cec                 16384  0
cec_gpio               12288  0
pi@TEST:~$ # cec.ko isn't in libs so in lsmod there is no such module, but why "modprobe cec" gives no error?
pi@TEST:~$ ls -l /dev/*cec*
ls: cannot access '/dev/*cec*': No such file or directory
pi@TEST:~$ # And activating modules just doesn't help, there is still no any "/dev/*cec*" device
pi@TEST:~$

It doesn't use any of CEC on 6.6.8 Bleeding Edge Linux kernel (I've tested it before on stable 6.1 kernel, but it didn't work as well, I've activated some modules concerning CEC in kernel config and built using the latest possible kernel, thinking it will change something). Just doesn't work. AOCEC module is compiled and launched though, but it doesn't use it at all since there is no "/dev/*cec*" device.

All the parts in "/boot/boot.cmd" concerning CEC:

...

setenv sdrmode "auto"
setenv voutmode "hdmi"
setenv disablehpd "false"
setenv cec "false"

...

if test -e ${devtype} ${devnum} ${prefix}zImage; then
    ...
    setenv bootargs "...${cec_enable} sdrmode=${sdrmode}"

...

Somehow, it misses the part where we should set "cec_enable" variable. What if I restore it and set to true? But I don't really think it will change something, as "/dev/aocec" existed on Debian even when CEC was disabled.

That didn't work, as well as adding "hdmitx=cec3f" to extraargs in "/boot/armbianEnv.txt". There is just no CEC device in "/dev/", I don't know which type of problem is that - module, overlay, kernel??

Yes, I've used v4l, and it also fails because it doesn't find any "/dev/*cec*".

Anyway, I hope this problem can be resolved and thanks to everyone for attention, have a happy new 2024 year!

I tried to build myself one from master (current and edge  - bullseye/desktop/xfce), same outcome: it shows the Splashscreen and then stops here:

I don't have a USB-to-TTL adapter, so I can't provide more debug informations.

The only images that still boot (reliably!) from the SD card are the ones archived here https://imola.armbian.com/archive/bananapim5/archive/ that still used the Kernel 5.19.16.

The switch to 6.0.x occurred two weeks ago: https://github.com/armbian/build/commit/ce61bd7827d42c63bc1f763dad5c7e4717e1f75b

I tried to checkout the previous commit (20d388b) and to build an image from it, but it failed:

So I can't confirm, but I'm under the impression that all the images since the switch to Kernel 6.0.x don't boot anymore from the SD card.

Hi,

I've been looking to run the desktop version of Armbian on the M5 however it will not start (blank screen, no signal). I can see the Debian Icon at startup, and the Armbian Icon at shutdown.

startx does not bring it up, however sudo startx will but I'm not sure if this is the best way.

I have tested:

Armbian_22.11.3_Bananapim5_bullseye_current_6.1.4_gnome_desktop.img

Armbian_22.11.3_Bananapim5_bullseye_current_6.1.4_cinnamon_desktop.img

and both are the same.

Any ideas are appreciated!

Thanks.

I have tried Bullseye CLI image 30nov from  https://www.armbian.com/bananapi-m5/

flashed with etcher to ensure integrity on sdcard sandisk A1 64G
It appears that it loops in /scripts/local-block giving up to mount armbian root

even with correct UUID
why does it loop like this?

I spent mainly a week figuring out why it was a nightmare with cinnamon on debian
I thought it was a matter of cinnamon version and/or mesa version of panfrost
but it was a modeline detection problem from xorg.

After trying my luck I finally discover where the bad duck resided on debian versions :

-  bullseye who was lagging , managing to use mali accel but overflowded with log errors

- bookworm was loosing HDMI signal just after login in..

I will only talk about bookworm 
In fact, cinnamon internal xrandr, tool who detect the screen modelines, fails to access and to grab screen EDID modelines like xrandr did.
it results it acts like it was in headless mode. Taking this into account I reinstalled the xorg-dummy-video pacakge and my /etc/X11/xorg.conf.d/01-armbian_defaults.conf
l provided in

then it succeed to login in low res. 720x480 declared in /boot/armbianEnv.txt. Fromcinnamon it is impossible to change the resolution display,
the display tool did not react in cinnamon-settings, it crashes. I have to use the alternate arandr. to change the screen resolution on each reboot

Boot loop looking for system into USB.

I have to disconnect USB then it boots up from SD.

Any help?

I have connected an LCD touch display via HDMI and USB to the M5.

The display shows messages during booting or shutdown but then "freezes" leaving the last few lines of the boot process displayed but does not show the console or anything else.

What am I missing?

I have read some things about it but I'm not even sure if they apply to this board or they are updated, about acpi events, logind and AR100, and I've read the official schematics of the board. It seems the button is connected to ADC pins.

I installed acpid but acpi_listen reports nothing.

But evtest does!

root@bananapim5:~# evtest /dev/input/by-path/platform-adc_keys-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "adc_keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 259 (BTN_3)
Properties:
Testing ... (interrupt to exit)


Event: time 1687334663.436476, type 1 (EV_KEY), code 259 (BTN_3), value 1
Event: time 1687334663.436476, -------------- SYN_REPORT ------------
Event: time 1687334663.948482, type 1 (EV_KEY), code 259 (BTN_3), value 0
Event: time 1687334663.948482, -------------- SYN_REPORT ------------

Is there a way to tell the system that this is event is an acpi event or a driver would be needed?

I don't think I can make a real driver but I think I could get read the event from /dev/input/by-path/platform-adc_keys-event with python or something. If I can't I could always wrap evtest and make it do the reading.

Thanks!

This is the whole error: https://paste.debian.net/1283664

And this is the armbianmonitor -U log: https://paste.debian.net/1283662/

The board runs fine with debian with 4.9.x kernel supplied by manufacturer. Armbian is the second image I try because I need a newer kernel. I'll try to find one that is less new.

Thank you for your support!

EDIT: I tried again without wifi and it worked flawlessly. I can't make it crash with a wired connection. I used the same wifi plug with Debian and I never had an error but maybe there's a bug in the driver in this image or something...

Oh! it's there in the kernel panic.

[  555.599414] Call trace:
[  555.601829]  ODM_RA_TxRPT2Handle_8188E+0x110/0x390 [r8188eu]
[  555.607435]  rtl8188eu_recv_tasklet+0x364/0x3a0 [r8188eu]
[  555.612782]  tasklet_action_common.constprop.0+0x13c/0x150
 

It's indeed something with the wifi plug. It's a TP-LINK WN725N

I replaced it with u-boot from Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16.img and that one works fine.

U-Boot 2022.10-armbian (Feb 12 2023 - 17:20:43 +0000)bpi-m5

Model: Banana Pi BPI-M5
SoC:   Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2)
DRAM:  3.8 GiB
Core:  384 devices, 27 uclasses, devicetree: separate
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@ff3f0000
Autoboot in 2 seconds
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10 
scanning bus usb@ff500000 for devices... error in inquiry

If I unplug the USB hard disk then also the newer u-boot works fine:

scanning bus usb@ff500000 for devices... 4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Banana Pi M5 here.

Really thanks so much by your generous work with Armbian software.

I did a try with:

Armbian 23.02.2 Jammy XFCE

Armbian 23.02.2 Bullseye XFCE

Armbian 22.11.3 Jammy XFCE

Armbian 22.08.7 Jammy XFCE

But only 22.08.7 loads desktop. The others versions does not load desktop after Armbian logo load screen, but I can login through SSH.

I'm not proficiency with computers, I used Linux from many years ago but as an entry user, it's only a hobby, so excuse me if this problem is solved, but I don't find a solution in forum neither the Internet and I'm with these problems for months.

Does anyone know how to solve the issue with screens?

Other details:

Power sources used with BPI-M5:

- AC/DC Adaptor Model DSM-0530 (5V 3A) supplied with BPI-M5.

- Original raspberry foundation AC adapter Model KSA-15E-051300HE (5.1V 3.0A) supplied with RPI-4B.

SD cards:

-  SanDisk Ultra 64GB (never issues with RPI-4B neither Windows)

- Kingston Canvas Select Plus 32GB (never issues with RPI-4B neither Windows)

I'm trying Linux flavors because I like Ubuntu a lot for different applications, and I would like to use Kodi too. In Armbian 22.08.7 I thought that Kodi did not have GPU acceleration because options menus were really slow at 1080, but then I saw in the changelog that I was wrong trying v22.08.1 because Armbian included BPI-M5 support on Armbian 22.11.1, so I would like to give it a try.

Thanks so much

Using the vanilla ARMBIAN image 23.02.2_Bananapim5_bullseye_current_6.1.11_minimal

Enabling the provided uartA and uartC dtbos fails.

Here is the output from the boot process, as captured via the Serial Debug interface:

 

238 bytes read in 3 ms (77.1 KiB/s)
Applying kernel provided DT overlay meson-uartA.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
238 bytes read in 3 ms (77.1 KiB/s)
Applying kernel provided DT overlay meson-uartC.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC

It seems that this image provides invalid dtbos, likely not properly built alongside the same kernel image.

I'm happy to help debug this as I have a system at the ready.

I know this is a forbidden question, I will adress specially to @chewitt and @Igor.

Why I dare to do this?  Because today, it is the fist time I managed to run Libreelec (LE) nighly https://test.libreelec.tv/11.0/Amlogic/bananapi-m5/
and have the somehow the same suffering with boot and so on and as I did not give up,

I shot the last bug preventing LE to boot. I don't want to register in every forum for each pack , christian forgive me I will put the explanation here.
The last image suffer from a missing link..in /flash as it is all momified in squashfs , this need extra skills.

wget https://ftp.halifax.rwth-aachen.de/libreelec/LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img.gz
gunzip LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img
partx -a LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img
losetup -a /dev/loop0
mount /dev/loop0p1 /media/LIBREELEC
cp /media/LIBREELEC/SYSTEM .
unsquashfs SYSTEM 
cd squashfs-root/flash
#here is the missing killing link
ln -s .. SYSTEM
cd -
mksquashfs squashfs-root/    -noappend  -comp zstd -Xcompression-level 15
cp SYSTEM /media/LIBREELEC/
umount /dev/loop0p1

Then use gparted to wipe out the sdcard, and use dd
 

dd if=LibreELEC-AMLGX.arm-11.0.1-bananapi-m5.img of=/dev/mmcblck1 bs=1M

Boot and ENJOY!

Hello,

I'm trying to rotate the desktop from landscape to portrait. Trying to do this in the display settings in the desktop does not work correctly as it only uses the top half of the screen.

What does work is to rotate using xrandr:

xrandr -o right

I'm trying to do this automatically on start up so I have written a script to call from lightdm.conf

The script:

#!/bin/sh
xrandr -o right
exit 0

The parts in lightdm.conf [Seat:*] that I've edited:

display-setup-script=/home/badger/screen.sh
session-setup-script=/home/badger/screen.sh

This works for the login screen, however it does not rotate the display.

Any ideas how to do this?

Thanks.

And I'm using 3.5" display with HDMI interface. The screen has a native 480x320 resolution, but accept a range from 640x480 to 1920x1080.

On resolutions over 800x480 is not readable, so I'm able to change resolution with the following line in /boot/armbianEnv.txt 

extraargs=video=HDMI-A-1:800x480M@87 fbcon=rotate:0

with lower resolutions 800x480 to 640x480 (60 to 87hz) the screen has an offset down of one character line so ther's a blank line up and I don't see login and shell input command down. 

Looking at 16:9 resolutions I see all the text with the minimum of 896x504

I don't know how to set overscan and screen offset up 1 character line with 800x480 o 720x480. Every help will be appreciated.

The mission:  to change display resolution for "None-1" ('unknown display') - when no physical screen/display/monitor is attached.

Machine: Banana Pi M5 (Bpi M5).

I use it as a headless machine (without any monitor connected) and access it via a remote control/share screen application (such as: Teamviewer).

The problem: the display is very small as the resolution is set to 720 X 576.

I couldn't find any way or method to define/change the resolution in such a case. How can this be done?

I'll appreciate any assistance you can provide.

Thanks in advance!

This is the information of the machine and Armbian version installed:

BOARD=bananapim5
BOARD_NAME="Banana Pi M5/M2P"
BOARDFAMILY=meson-sm1
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=b475b12
VERSION=22.11.4
LINUXFAMILY=meson64
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=current

I got a BPIM5 with rtl8822cs board and a BPIM2+ with internal wifi chip for home automation.

I started my project (vpn gateway) with the ubuntu server distribution on BPIM5. I had a lot of instability of the wifi driver (lost of station in AP mode) and and the board crashed every two, three days.

I switches to ARMBIAN with the last Armbian 22.11.3 Bullseye with Linux 6.1.4-meson64.  This software seems to work fine on M2+ and wifi is fine and stable. So I tried to move my M5 to the same level.

The M5 boot on sd card, I move it on MMC memory and the board boot . Unfortunatly the wifi board (rtl8822cs sdio) is not recognized at boot .

Does the driver and overlays file available somewhere for the M5 board and the WIFI sdio board ?

Thanks for your help

Gerard

I am new to Armbian and I am working with the Jammy Minimal CLI image (9 Jan 2023) in a Banana Pi M5.

I need to configure the w1 to the pin GPIOA_14 and I have tried adding the following to /boot/armbianEnv.txt:

overlays=w1-gpio

param_w1_pin=GPIOA_14

But it does not work. How should I configure it?


Thanks

I've tried to install the newest Armbian image "Armbian_22.08.7_Bananapim5_jammy_edge_5.19.16_cinnamon_desktop.img.xz"

Copied with Balena Etcher to SDcard. Attached a serial tty cable and started with card in SD-Slot.

Unfortunately it stops while booting. Please can anybody help me ?

Zitat

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

no sdio debug board detected
L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 277370

BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
board id: 1
Load FIP HDR DDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
PIEI prepare done
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
DDR4 probe

LPDDR4_PHY_V_0_1_21-Built : 15:37:51, Mar 26 2020. g12a gf098346 - gongwei.chen@droid11-sz
ddr clk to 1320MHz

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 12, cur: 2. Board id: 255. Force loop cfg
LPDDR4 probe
ddr clk to 1392MHz

dmc_version 0001
Check phy result
INFO : End of CA training
INFO : End of initialization
INFO : Training has run successfully!
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of Write leveling coarse delay
INFO : Training has run successfully!
Check phy result
INFO : End of initialization
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

soc_vref_reg_value 0x 00000014 00000017 00000015 00000015 00000016 00000016 00000016 00000016 00000014 00000015 00000013 00000014 00000014 00000014 00000015 00000013 00000016 00000013 00000016 00000015 00000016
 dram_vref_reg_value 0x 00000060
2D training succeed
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00e00024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass

non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 378
result report
boot times 0Enable ddr reg access
Load FIP HDR from SD, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from SD, src: 0x00078200, des: 0x01768000, size: 0x0009a600, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0
MVN_1=0x00000000
MVN_2=0x00000000
[Image: g12a_v1.1.3386-3b31431 2019-05-21 10:41:54 luan.yuan@droid15-sz]
OPS=0x10
ring efuse init
2b 0c 10 00 01 32 0e 00 00 13 32 31 36 58 4b 50
[0.017319 Inits done]
secure task start!
high task start!
low task start!
boot bl31
NOTICE:  BL31: v1.3(release):4fc40b1
NOTICE:  BL31: Built : 15:57:33, May 22 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast

<debug_uart>

U-Boot 2022.07-armbian (Oct 18 2022 - 07:30:35 +0000)bpi-m5

Model: Banana Pi BPI-M5
SoC:   Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2)
DRAM:  3.8 GiB
Core:  385 devices, 27 uclasses, devicetree: separate
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@ff3f0000
Autoboot in 2 seconds
 ** fs_devread read error - block
Failed to mount ext2 filesystem...
switch to partitions #0, OK
mmc0 is current device
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
switch to partitions #0, OK
mmc1(part 0) is current device
** Invalid partition 1 **
Couldn't find partition mmc 1:1
MMC Device 2 not found
no mmc device at slot 2
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.129 (5 ms)
*** Warning: no boot file name; using 'C0A80181.img'
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'C0A80181.img'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-f2-2e-26-1f-a3-6c
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/01-f2-2e-26-1f-a3-6c'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A80181
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A80181'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A8018
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A8018'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A801
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A801'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A80
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A80'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A8
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A8'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0A'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C0'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/C'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/default-arm-meson-u200
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/default-arm-meson-u200'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/default-arm-meson
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/default-arm-meson'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/default-arm
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/default
Speed: 1000, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'pxelinux.cfg/default'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Config file not found
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.129 (4 ms)
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'boot.scr.uimg'.
Load address: 0x8000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.129 (5 ms)
Using ethernet@ff3f0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.129
Filename 'boot.scr.uimg'.
Load address: 0x8080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
=>

Here is the serial log:

U-Boot 2022.07-armbian (Oct 18 2022 - 07:30:35 +0000)bpi-m5

Model: Banana Pi BPI-M5
SoC:   Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2)
DRAM:  3.8 GiB
Core:  385 devices, 27 uclasses, devicetree: separate
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@ff3f0000
Autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
8147 bytes read in 3 ms (2.6 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-sm1-bananapi-m5.dtb
Current variant:
161 bytes read in 2 ms (78.1 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-sm1-bananapi-m5.dtb
Mainline bootargs: root=UUID=d0c122f6-b8a9-4650-94c2-77c85521b2d8 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=79a75e49-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u    cgroup_enable=memory swapaccount=1
19116246 bytes read in 838 ms (21.8 MiB/s)
mmc fail to send stop cmd
 ** fs_devread read error - block
Failed to load '/boot/Image'
 ** fs_devread read error - block
Failed to mount ext2 filesystem...
Can't set block device
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
 ** fs_devread read error - block
Failed to mount ext2 filesystem...
Can't set block device
 ** fs_devread read error - block
Failed to mount ext2 filesystem...
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    19116182 Bytes = 18.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
switch to partitions #0, OK
mmc1(part 0) is current device
** No partition table - mmc 1 **
Couldn't find partition mmc 1:1
MMC Device 2 not found
no mmc device at slot 2
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.156 (12 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-ba-df-83-51-8d-a0
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8009C
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8009
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A800
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A80
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-meson-u200
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-meson
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
Speed: 100, full duplex
*** ERROR: `serverip' not set
Config file not found
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.156 (2 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.156 (2 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET