kris777
-
Posts
78 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by kris777
-
-
What should the correctly enabled I2C service (for a 40x2 LCD) look like on Bananapim2pro? Should I edit the armbianEnv.txt file and add, for example, the following entry: overlays=i2c0 i2c1?
The armbian-config service is a bit confusing, and after editing it, I get this:........................
verbosity=1
console=both
overlay_prefix=meson
fdtfile=amlogic/meson-sm1-bananapi-m2-pro.dtb
rootdev=UUID=a4fb8074-c453-45da-ab31-4d61dca46cfa
rootfstype=ext4
overlays=i2cA i2cB
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u..................
There are other options, but they probably don't apply to bananapim2pro. :
sm1-odroid-c4-i2c0
g12b-bananapi-cm4-i2c2
g12a-radxa-zero-i2c-ao....
-
After the update/upgrade, all CPUs are now installed
nproc 4
This didn't fix my Bluetooth (maybe it's some individual bug in my system?) but since Bluetooth works correctly in the new images for OrangePi 3 LTS, I'm marking this thread as resolved... I'll probably install the latest image soon, although it will be time-consuming............................
orangepi3-lts:~# dmesg | grep "CPU"
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.005157] smp: Bringing up secondary CPUs ...
[ 0.007070] Detected VIPT I-cache on CPU1
[ 0.007260] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.009368] Detected VIPT I-cache on CPU2
[ 0.009541] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.011117] Detected VIPT I-cache on CPU3
[ 0.011261] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.011373] smp: Brought up 1 node, 4 CPUs
[ 0.011398] CPU: All CPU(s) started at EL2
[ 0.011443] CPU features: detected: 32-bit EL0 Support
[ 0.011449] CPU features: detected: 32-bit EL1 Support
[ 0.011458] CPU features: detected: CRC32 instructions
[ 0.011470] CPU features: detected: PMUv3
[ 0.260754] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.414642] sun50i_cpufreq_nvmem: Using CPU speed bin speed0
[ 0.457342] WARNING: CPU: 3 PID: 71 at drivers/iommu/iommu.c:612 __iommu_probe_device+0x1a8/0x4a0
[ 0.457375] CPU: 3 UID: 0 PID: 71 Comm: kworker/u16:4 Not tainted 6.18.19-current-sunxi64 #2 PREEMPTPs. I don't know if I announced the CPU solution too early? Maybe there's a problem with the processor clock speed?
..............
cat /etc/default/cpufrequtils
ENABLE=false
MIN_SPEED=480000
MAX_SPEED=1810000
GOVERNOR=performance
root@orangepi3-lts:~# cpu
Temperature: 40 °C
CPU-0 Frequency: 1608 Mhz
CPU-1 Frequency: 1608 Mhz
CPU-2 Frequency: 1608 Mhz
CPU-3 Frequency: 1608 Mhz
root@orangepi3-lts:~# cat /etc/default/cpufrequtils
ENABLE=false
MIN_SPEED=480000
MAX_SPEED=1810000
GOVERNOR=performance
root@orangepi3-lts:~# cat /etc/default/cpufrequtils
ENABLE=false
MIN_SPEED=480000
MAX_SPEED=1810000
GOVERNOR=performance
root@orangepi3-lts:~#root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
1608000
root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
performance
performance
performance
performance
...............shouldn't it be : 1810000 ... ?
-
I tested the new version (Armbian_26.2.0-trunk.591_Orangepi3-lts_forky_current_6.18.18_minimal) in terms of bloototh and it's OK... but there are errors that rule out this image. Namely, the system lacks 4 working processor cores 🙂 ... only one. Something is wrong at startup because the green LED is on and the red LED is constantly flashing/pulsing.
Bringing up secondary CPUs ... [ 5.092655] CPU1: failed to come online [ 5.092666] CPU1: failed in unknown state : 0x0 [ 10.217311] CPU2: failed to come online [ 10.217324] CPU2: failed in unknown state : 0x0 [ 15.341948] CPU3: failed to come online [ 15.341961] CPU3: failed in unknown state : 0x0 [ 15.342047] smp: Brought up 1 node, 1 CPU [ 15.342057] SMP: Total of 1 processors activated. [ 15.342063] CPU: All CPU(s) started at EL2 [ 15.342112] CPU features: detected: 32-bit EL0 Support [ 15.342119] CPU features: detected: 32-bit EL1 Support [ 15.342129] CPU features: detected: CRC32 instructions [ 15.342146] CPU features: detected: PMUv3 [ 15.342193] alternatives: applying system-wide alternativesIt's some kind of incompatibility: U-Boot / TF-A / kernel ....
Similar errors are found in the version uploaded by: armbian imager (minimal / cli / debian - trixie) more information: https://paste.armbian.com/afokonucej
command "poweroff" not working ! ?
On version: Ubuntu / minimal (cli) there are the same errors regarding CPU...etc
.....................................
dmesg | grep "CPU"
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: kernel page table isolation forced ON by KASLR
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.006129] smp: Bringing up secondary CPUs ...
[ 5.092344] CPU1: failed to come online
[ 5.092356] CPU1: failed in unknown state : 0x0
[ 10.216761] CPU2: failed to come online
[ 10.216771] CPU2: failed in unknown state : 0x0
[ 15.341165] CPU3: failed to come online
[ 15.341176] CPU3: failed in unknown state : 0x0
[ 15.341242] smp: Brought up 1 node, 1 CPU
[ 15.341258] CPU: All CPU(s) started at EL2
[ 15.341291] CPU features: detected: 32-bit EL0 Support
[ 15.341297] CPU features: detected: 32-bit EL1 Support
[ 15.341309] CPU features: detected: CRC32 instructions
[ 16.273971] ledtrig-cpu: registered to indicate activity on CPUs
[ 17.351303] sun50i_cpufreq_nvmem: Using CPU speed bin speed0
......................... -
That's strange 🙂 ...we have the same kernel. Maybe something's broken in the system? But I haven't messed with Bluetooth in the system. I've only updated the system: apt update /apt upgrade /reboot 🙂
root@orangepi3-lts:~# rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bluetooth unblocked unblocked 1 wlan phy0 unblocked unblocked .............................. bluetoothctl Waiting to connect to bluetoothd... it keeps reading but shows nothing? ................... bt-device -l ** ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Aborted .............Something must have broken in the system, but what and where?
Can you give me the exact: Armbian image + version ...
Contents of ..../lib/firmware/uwe5622/
also: armbianEnv.txt
Output dmesg | grep -i uart i dmesg | grep -i bluetooth
Maybe that will help me figure out where the errors are in my system? Or maybe I have Debian and you have Ubuntu?
Ps. or, more simply, information from the file: diagnostics.txt
command in terminal:
.................
(
uname -a
cat /etc/os-release
ls -lh /lib/firmware/uwe5622/
lsmod | grep -iE "bt|sprd|uwe"
dmesg | grep -i uart
ls /dev/tty* | grep -i "ttyS\|ttyAMA\|ttyBT"
cat /boot/armbianEnv.txt
rfkill list
hciconfig -a
bluetoothctl list
hcitool dev
bt-device -l
dmesg | grep -iE "bluetooth|uwe|sprd|hci"
) > diagnostics.txt.....................
-
armbianmonitor -u in the link it shows : https://paste.armbian.com/uzudezufit
Linux version 6.12.74-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #6 SMP Thu Feb 19 15:29:56 UTC 2026
-
Wi-Fi works → so the problem is only in GPIO / DTB initialization for Bluetooth
It worked on the older kernel, but now it doesn't 😞....
Supposedly this is the cause, but is it really?
QuoteDTB (device tree) does not configure GPIO reset/power for the UWE5622.
hci_uart cannot initialize the controller → hci0 is not created.
The overlay for BT in mainline 6.x does not yet exist in Trixie.
❌ Result: hciconfig -a and bluetoothctl list show nothing.
armbianmonitor -u
-
On my Orange Pi 3 LTS I don't use ethernet, only wifi and it works OK... maybe that's why I didn't notice the problem... but here is some information about ethernet on Pi 3 LTS
https://forum.armbian.com/topic/19846-orange-pi3-lts/page/11/#comment-226536
-
I switched to the Armbian version of Debian Trixie and now it's OK
-
I gave some information ..... Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease ? 🙂
If this is a bug, meaning the repositories are in beta, then OK... but I don't know if I installed them? Or are they standard in the images/firmware installations, e.g., for the Opi3LTS version?
Ps. Has support for my OrangePi3LTS model been completely abandoned? ...because now I don't have the option to install the system to the emmc memory in the :armbian-config options? / nand-sata-install / armbian-install 😞
I think the easiest way would be to switch to the Debian/Triexie version from bookworm because unfortunately bookworm has only bugs and no support for the wifi card now 🙂
-
Quote
It is likely that the team (or person) responsible for preparing the armbian-bsp-cli-orangepi3-lts-current package for version $25.8.2$ uploaded it to the repository before or without making sure that the required version of base-files ($25.8.2$) was already available there. This is why none of the standard commands (upgrade, full-upgrade, install) worked until we forced the installation with dpkg --ignore-depends.
This is the hint I got from AI 🙂
I changed the repositories from beta to stable and installed:
sudo sed -i 's|beta.armbian.com|apt.armbian.com|g' /etc/apt/sources.list.d/armbian.list
and
sudo apt download armbian-bsp-cli-orangepi3-lts-current
sudo dpkg --install --ignore-depends=base-files armbian-bsp-cli-orangepi3-lts-current_25.8.2_arm64.debNow it's OK....but is this the right approach?
-
LC_ALL=C apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://download.docker.com/linux/debian bookworm InRelease Hit:5 http://deb.debian.org/debian bookworm-backports InRelease Hit:6 https://github.armbian.com/configng stable InRelease Hit:7 https://dtcooper.github.io/raspotify raspotify InRelease Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.439 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it -
I think I messed something up in the system, maybe with the repositories, but I get this message when updating...
apt update Stary:1 http://deb.debian.org/debian bookworm InRelease Stary:2 http://security.debian.org bookworm-security InRelease Stary:3 https://download.docker.com/linux/debian bookworm InRelease Stary:4 http://deb.debian.org/debian bookworm-updates InRelease Stary:5 http://deb.debian.org/debian bookworm-backports InRelease Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease Stary:7 https://github.armbian.com/configng stable InRelease Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease Czytanie list pakietów... Gotowe Budowanie drzewa zależności... Gotowe Odczyt informacji o stanie... Gotowe 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it root@orangepi3-lts:~# apt list --upgradable -a Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401]maybe someone has already dealt with this message and error?
-
I have a question regarding the configuration of the /etc/asound.conf file... are there any changes in the new kernel that prevent this from happening? I've noticed that my USB audio card no longer loses its settings and its position doesn't change. However, to be sure, I tried editing the /etc/asound.conf file... but it turns out to be impossible 🙂 That is, after saving the settings in /etc/asound.conf... ALSA doesn't work! 🙂
Moreover, the blocking for certain selected devices doesn't work either. In my case, the blocking is: HDMI Audio... in the file: /etc/modprobe.d/blacklist.conf
blacklist sun9i_hdmi_audio blacklist snd_soc_simple_cardAre these changes related to the detection/blocking, etc., of block devices in Linux?
-
OK...I think it worked in OrangePi3 LTS 🙂 ...first, clean up the remnants:
.................................................................
sudo apt purge v4l2loopback-dkms
sudo apt autoremove
...............................................................
armbian-config
then I had to switch to a different kernel: edge:6.15.4-edge-sunxi64 ....then update the system: apt update / upgrade / reboot ! install from GitHub: v4l2loopback and then:
cd ~/v4l2loopback
....................................................................
VERSION=$(grep -oP 'PACKAGE_VERSION="\K[^"]+' dkms.conf)sudo cp -r . /usr/src/v4l2loopback-$VERSION
sudo dkms add -m v4l2loopback -v $VERSION
sudo dkms build -m v4l2loopback -v $VERSION
sudo dkms install -m v4l2loopback -v $VERSIONdkms status
sudo modprobe v4l2loopback
ls /dev/video*...................................................................
I guess it's OK now:................................................................
Quotels /dev/video*
/dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4
root@orangepi3-lts:~/v4l2loopback# lsmod
Module Size Used by
v4l2loopback 45056 0
uinput 16384 1
bnep 16384 2
hci_uart 106496 1
btqca 16384 1 hci_uart
btrtl 20480 1 hci_uart
btintel 36864 1 hci_uart
btbcm 20480 1 hci_uartBut in my opinion the module is not working properly 😞
I'll be more precise, it works OK... but OrangePi3LTS is a weak device and the option/module: v4l2loopback and the ffmpeg program that transmits/splits the image to two programs (motion/ustreamer) causes high CPU usage... but it works OK, so my problem is solved
-
I can't build it from GitHub, or rather I've built it but it doesn't work because the kernel headers don't seem to match and it can't be loaded. I guess you have to compile the entire kernel with this module 🙂 ..uppss
Quotemodinfo /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko | grep vermagic
vermagic: 6.12.35-current-sunxi64 SMP mod_unload aarch64
modinfo /lib/modules/$(uname -r)/updates/v4l2loopback.ko
filename: /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko
alias: char-major-10-255
license: GPL
version: 0.15.1
author: Vasily Levin, IOhannes m zmoelnig <zmoelnig@iem.at>,Stefan Diewald,Anton Novikovet al.
description: V4L2 loopback video device
srcversion: 45D4A1AED5D88ED1EEB4704
depends: videodev
name: v4l2loopback
vermagic: 6.12.35-current-sunxi64 SMP mod_unload aarch64
parm: debug:debugging level (higher values == more verbose) (int)
parm: max_buffers:how many buffers should be allocated [DEFAULT: 2] (int)
parm: max_openers:how many users can open the loopback device [DEFAULT: 10] (int)
parm: devices:how many devices should be created (int)
parm: video_nr:video device numbers (-1=auto, 0=/dev/video0, etc.) (array of int)
parm: card_label:card labels for each device (array of charp)
parm: exclusive_caps:whether to announce OUTPUT/CAPTURE capabilities exclusively or not [DEFAULT: 0] (array of bool)
parm: max_width:maximum allowed frame width [DEFAULT: 8192] (int)
parm: max_height:maximum allowed frame height [DEFAULT: 8192] (int)sudo modprobe v4l2loopback
insmod /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko
insmod: ERROR: could not insert module /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko: Invalid module format -
sudo apt install v4l2loopback-dkms Czytanie list pakietów... Gotowe Budowanie drzewa zależności... Gotowe Odczyt informacji o stanie... Gotowe v4l2loopback-dkms is already the newest version (0.12.7-2). 0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 8 nieaktualizowanych. root@orangepi3-lts:~# sudo modprobe v4l2loopback modprobe: FATAL: Module v4l2loopback not found in directory /lib/modules/6.12.35-current-sunxi64
-
Can we count on adding a module to the future kernel... I mean: v4l2loopback 🙂
-
Remote backup maybe only as data ... e.g. restic / rsync programs
In my opinion it is best to make a backup of the SD cardin linux connect miniSD card and make a backup in terminal:
fdisk -l
if your SD card is: sda / sda1.... then choose sda !
and then make a backup:
dd if=/dev/sda of=/path_to_backup.img status=progressRestoring the image to the SD card with the same size:
dd bs=4M if=/path_to_copy.img of=/dev/sdb status=progressIf you want to burn the image to a smaller capacity SD card because, for example, the system is only 30% occupied, use the program:PiShrink
https://github.com/Drewsif/PiShrink
it works great for me for Armbian 🙂sudo pishrink.sh /path_to_backup.img / /new_backup-Pishrink.img
-
I tried to set the I2C interface with the armbian-config option but it doesn't work because it writes to the file: armbianEnv.txt ....
overlays=sun50i-h6-i2c0 sun50i-h6-i2c1 sun50i-h6-i2c2
and it didn't work on my OrangePi3LTS and it doesn't start the i2C service on startup? but when I enter it manually:
overlays=i2c0 i2c1 i2c2
then the i2c service works with my 40x2 LCD 🙂 ...is this a bug and if so can it be fixed?
is the option: armbian-config still compatible with my OrangePi3 LTS? -
maybe add manually in the file /boot/armbianEnv.txt the entry:
overlays=i2c0 i2c1 i2c2 -
I have a question, does anyone know a method to start
in the Opi Lite system the I2S audio interface and in particular I mean the module: PCM5102 / PCM5102a
On my old OrangePi Lite board, sound and audio in the configuration as mentioned above really work great ... but unfortunately the Armbian system that I use is no longer supported. This is the Ubuntu version (xenial) and kernel: 3.4.113-sun8i, I managed to update some programs important to me, e.g. mpd / mpc but not to the latest versions. I also have another version of OrangePI 3 LTS and I know that on this model it is rather impossible to start I2S + PCM5102 so I used a good sound card under USB and it is OK. However, I think that it should be possible on the Pi Lite? so far I have tried such a howto ... but without success.
armbian-add-overlay sun8i-h3-I2S-out.dtsentry in the file sun8i-h3-I2S-out.dts :
/dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/"; __overlay__ { pcm5102a: pcm5102a { #sound-dai-cells = <0>; compatible = "ti,pcm5102a"; pcm510x,format = "i2s"; }; }; }; fragment@1 { target = <&i2s0>; __overlay__ { status = "okay"; pinctrl-0 = <&i2s0_pins>; sound-dai = <&pcm5102a>; pinctrl-names = "default"; }; }; fragment@2 { target-path = "/"; __overlay__ { sound_i2s { compatible = "simple-audio-card"; simple-audio-card,name = "I2S-master"; simple-audio-card,mclk-fs = <256>; simple-audio-card,format = "i2s"; status = "okay"; simple-audio-card,cpu { sound-dai = <&i2s0>; }; simple-audio-card,codec { sound-dai = <&pcm5102a>; }; }; }; }; };and an additional entry in the armbianEnv.txt file :
user_overlays=sun8i-h3-I2S-outI once did it according to another tutorial but it was on the old Ubuntu Xenial system
https://www.dimdim.gr/2016/12/orange-pi-one-lite-as-music-streamers-part-2/
It would be useful to update the system and kernel after a dozen or so years 🙂
-
i2s doesn't work on my OrangePi lite either...oops
-
I checked again and the latest stable version works correctly with OrangePi3 -LTS also the I2C interface for my 40x2 LCD is version: Armbian_23.11.1_Orangepi3-lts_bookworm_current_6.1.63.
https://k-space.ee.armbian.com/archive/orangepi3-lts/archive/
regards
-
Every rational user knows exactly what it's about... after all, no one will spend their time updating and improving the firmware for every piece of equipment, even if it's only from OrangePi.
Unless you're a retiree and have a lot of time and willingness and a sharp mind... oopsss
🙂
Or maybe some other form of help could be used instead of the so-called help from the community (which probably means no one) from the forum? For example, a form of payment for a specialist, developer to adjust or update a specific piece of equipment/model, e.g. OrangePi3-LTS in the form of a progress bar of payments for a given model? ... I wonder if there are people willing to use this form of help...
So a proverbial fundraiser for a specific model?Ps. I found a version for OrangePi3-lts with an old, properly working kernel: 15.16.17.7 ... but Debian is already a bookworm
I2C service ?
in Banana Pi M2 Pro
Posted · Edited by kris777
Thanks for the info to try other options 🙂
Thanks for the tip, I'll try other options 🙂 It worked for: odroid-c4 ... basically, the settings are the same as for the OrangePI3LTS, I'm talking about connecting cables to a 40x2 / 20x2 LCD.
The diagram for the BananapiM2pro is as follows:
My Winstar 40x2 OLED LCD compatible with drivers: hd44780 / driver: WS0010 is detected in the system as: 3f
..................................
sudo i2cdetect -y 0
[sudo] kris:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 3f
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
..................................
You can also enter the appropriate values yourself in the file:
sudo nano /boot/armbianEnv.txt
verbosity=1
console=both
overlay_prefix=meson
fdtfile=amlogic/meson-sm1-bananapi-m2-pro.dtb
rootdev=UUID=a4fb8074-c453-45da-ab31-4d61dca46cfa
rootfstype=ext4
overlays=sm1-odroid-c4-i2c0 sm1-odroid-c4-i2c1
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
regards