Banana Pi M2 Zero (Allwinner H2+)

CityAceE · Apr 17, 2024

Banana Pi M2 is one of the most inexpensive boards based on the H3/H2+ chip. I have one. This is one of the first models on H2+. I load Armbian fine, but I can't load Basic Engine.

I soldered the UART and saw the following:

U-Boot SPL 2021.10 (Apr 16 2024 - 05:13:32 +0000) DRAM: 512 MiB Trying to boot from MMC1 MMC: no card present spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ERROR ### Please RESET the board ###

I also tried to use ready-made U-Boot from Armbian. Loading reaches the kernel, but in the end the error still appears:

`U-Boot SPL 2024.01-armbian (Mar 14 2024 - 00:35:37 +0000)
DRAM: 512 MiB
Trying to boot from MMC1
ns16550_serial serial @1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19

U-Boot 2024.01-armbian (Mar 14 2024 - 00:35:37 +0000) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Banana Pi BPI-M2-Zero
DRAM: 512 MiB
Core: 63 devices, 16 uclasses, devicetree: separate
WDT: Not starting watchdog @1c20ca0
MMC: mmc @1c0f000: 0, mmc @1c10000: 1
Loading Environment from FAT... OK
In: serial @1c28000
Out: serial @1c28000
Err: serial @1c28000
Net: No ethernet found.
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2239 bytes read in 2 ms (1.1 MiB/s)
Executing script at 43100000
4097968 bytes read in 172 ms (22.7 MiB/s)
** No boot file defined **
Unknown command 'usb' - try 'help'
Unknown command 'bootmenu' - try 'help'
Saving Environment to FAT... OK
** No boot file defined **
Kernel image @ 0x42000000 [ 0x000000 - 0x3e87b0 ]
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
Card did not respond to voltage select! : -110
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
=>`
Is it possible to add support for Banana Pi M2 Zero? Device Tree is available in Armbian.

Uuli · Apr 18, 2024

CityAceE Banana Pi M2 is one of the most inexpensive boards based on the H3/H2+ chip. I have one. This is one of the first models on H2+. I load Armbian fine, but I can't load Basic Engine.

I soldered the UART and saw the following:

U-Boot SPL 2021.10 (Apr 16 2024 - 05:13:32 +0000)
DRAM: 512 MiB
Trying to boot from MMC1
MMC: no card present
spl: mmc init failed with error: -123
SPL: failed to boot from all boot devices
ERROR ### Please RESET the board ###

Could you please try the LT build (https://basicengine.org/git_builds/h3_lt/basicengine-h3-lt-2024-04-16.7z)?
I only recently reactivated that because I finally managed to reduce the display latency to an acceptable point, and while it is severely untested, it has both a more recent bootloader and a more recent kernel.

CityAceE · Apr 19, 2024

uli Thank you for your answer!
I'm currently working on adding support for Banana Pi M2 Zero to the latest version of Basic Engine RX. I've made some progress so far and if I am successful, I will share the final results with others.

CityAceE · Apr 20, 2024

Unfortunately, I have not yet been able to achieve a successful result. I have confirmed that the device boots and starts Uboot, which then loads and starts the kernel. The kernel goes through all of the boot steps successfully and displays the login prompt. However, unfortunately, the screen does not initialize. Can you please advise me on how to proceed?

Out: vidconsole Err: vidconsole

`U-Boot SPL 2020.10 (Apr 20 2024 - 09:20:44 +0300)
DRAM: 512 MiB
Trying to boot from MMC1

U-Boot 2020.10 (Apr 20 2024 - 09:20:44 +0300) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Banana Pi BPI-M2-Zero
DRAM: 512 MiB
MMC: mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
No working controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
294 bytes read in 2 ms (143.6 KiB/s)

Executing script at 43100000

switch to partitions #0, OK
mmc0 is current device
4097312 bytes read in 192 ms (20.4 MiB/s)
29610 bytes read in 4 ms (7.1 MiB/s)

Flattened Device Tree blob at 43000000

Booting using the fdt blob at 0x43000000
Loading Device Tree to 49ff5000, end 49fff3a9 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.10.31 (cityacee@builder) (arm-buildroot-linux-gnueabihf-gcc.br_real (Buildroot -g646ae94dca-dirty) 11.3.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Sat Apr 20 08:52:24 MSK 2024
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d`
...

`[ 2.356200] [cedar]: memory allocated at address 45900000
[ 2.361647] [cedar]: install end!!!
done
ROOT DEV /dev/mmcblk0
DATA PART /dev/mmcblk0p3
DATA PART NO 3
Mounting data partition:
Starting network: OK
Starting dropbear sshd: OK
Sun Apr 17 06:35:26 UTC 2022

Welcome to Buildroot for the Orange Pi Lite
OrangePi_Lite login: [ 31.844182] vcc3v0: disabling
[ 31.847183] vcc5v0: disabling
[ 190.564281] random: crng init done
[ 190.567715] random: 2 urandom warning(s) missed due to ratelimiting

Welcome to Buildroot for the Orange Pi Lite
OrangePi_Lite login:`

Uuli · Apr 21, 2024

CityAceE Can you please advise me on how to proceed?

As I have said before:

uli Could you please try the LT build (https://basicengine.org/git_builds/h3_lt/basicengine-h3-lt-2024-04-16.7z)?

because

uli it has both a more recent bootloader and a more recent kernel.

I can get me one of these boards, but the time I am able and willing to invest in this project varies, so it would probably lie around for quite a while until I get around to do something with it. I think we might be able to get you up and running faster by trying the LT version and seeing if that works.

CityAceE · Apr 22, 2024

Yes, of course, I tested the LT version, but unfortunately, the result is also disappointing.

U-Boot SPL 2024.01 (Apr 16 2024 - 07:27:07 +0000)
DRAM: 512 MiB
Trying to boot from MMC1

U-Boot 2024.01 (Apr 16 2024 - 07:27:07 +0000) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Lite
DRAM: 512 MiB
Core: 66 devices, 19 uclasses, devicetree: separate
WDT: Not starting watchdog@1c20ca0
MMC: mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... MMC: no card present
** Bad device specification mmc 0 **
In: serial,usbkbd
Out: serial,vidconsole
Err: serial,vidconsole
Net: No ethernet found.
Hit any key to stop autoboot: 0
MMC: no card present
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
=>

Uuli · Apr 22, 2024

CityAceE Yes, of course, I tested the LT version, but unfortunately, the result is also disappointing.

Thanks for testing. I suppose that's another shortcut coming to bite me...

On H616, every board needs its own image, but I assumed that all H3/H2+ boards are similar enough that one bootloader will fit them all. It looks like that isn't the case after all...

I'll see if I can get around to figure this out. If you want to try it yourself, you can clone the basicengine-buildroot and do a make basicengine_h3_defconfig and then change BR2_TARGET_UBOOT_BOARD_DEFCONFIG in .config to bananapi_m2_zero and make and see if that works (image will be in output/images/sdcard.img).

(Looking at my shell history, building basicengine-buildroot needs the following non-obvious packages in addition to all the usual stuff buildroot needs: p7zip ninja-build gettext python3 python3-polib asciidoctor libsdl2-dev libgpiod-dev texi2html texinfo libncurses-dev help2man)

If that works, I'll have to fix the git build script to create multiple H3 images (just like the H616), and we'll have to read through the device trees to see which board has which MMC config...

Either way, thanks for your help.

CityAceE · Apr 23, 2024

uli I'll see if I can get around to figure this out. If you want to try it yourself, you can clone the basicengine-buildroot and do a make basicengine_h3_defconfig and then change BR2_TARGET_UBOOT_BOARD_DEFCONFIG in .config to bananapi_m2_zero and make and see if that works (image will be in output/images/sdcard.img).

You won't believe it, but I've already done this and many other experiments. Unfortunately, it has not yet been possible to achieve the necessary result.

What you are offering will not be enough. At least in the basicengine_h3_defconfig file (and probably in orangepi_lite_defconfig) in the BR2_LINUX_KERNEL_INTREE_DTS_NAME section, add a link to the sun8i-h2-plus-bananapi-m2-zero tree. And also sun8i-h2-plus-bananapi-m2-zero.dtb to the list in the file board/basicengine/h3/genimage.cfg. You also need to edit the start menu boot.scr and add Banana Pi M2 Zero to it.

Only in this case, the project will compile successfully and all the necessary files will be in their places. However, all this will not allow you to run this build on Banana Pi.

The maximum result will be achieved if the path to boot.scr from Banana Pi is replaced in the basicengine_h3_defconfig file in the BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOLS_SCRIPT_SOURCE section.

By experimentation, I found out that Banana Pi halts if there is a string setenv fdt_high ffffffff in boot.scr. Also, the string mmc dev 0 is missing to successfully load Banana Pi. So the ideal option is to use boot.scr from Banana Pi.

If you do all this and successfully compile the project, then Banana Pi will boot. We will see the boot log in the console and on the monitor for a short time. Then the monitor will turn off and boot log will continue only to the UART console. The necessary partitions will be created on the SD. However, the BASIC section will not be filled with the necessary data. It all ends with a command line prompt. And you can even log in as root without a password.

That's all I've been able to achieve so far. But I don't have any more ideas. My knowledge is not enough.

Uuli · Apr 23, 2024

CityAceE At least in the basicengine_h3_defconfig file (and probably in orangepi_lite_defconfig) in the BR2_LINUX_KERNEL_INTREE_DTS_NAME section, add a link to the sun8i-h2-plus-bananapi-m2-zero tree. And also sun8i-h2-plus-bananapi-m2-zero.dtb to the list in the file board/basicengine/h3/genimage.cfg. You also need to edit the start menu boot.scr and add Banana Pi M2 Zero to it.

I simply assumed I had dumped all the H2+/H3 device trees into the image already. Must have missed that one.
That said, I just checked linux-sunxi.org, and what they say is this:

Despite its name the M2 Zero is totally incompatible to Banana Pi/M1/M1+/Pro/M2/M2U/M3/M64 due to a different SoC - requiring different boot loaders and drivers. It's another attempt to cash-in on the Banana Pi's popularity with a SBC sharing only Brand-name, form factor and GPIO header.

(Thanks to libv for not mincing words here. )

So I don't think I will be engaging with this thing any further when it comes to a bare-metal (RX) implementation.

With LT that is another matter, though. If you are willing to take on the job of bending the basicengine_h3_lt_defconfig into something that works on the BPi M2 Zero, I'd be more than happy to include the result in the repo and the git builds.

CityAceE If you do all this and successfully compile the project, then Banana Pi will boot. We will see the boot log in the console and on the monitor for a short time. Then the monitor will turn off and boot log will continue only to the UART console. The necessary partitions will be created on the SD. However, the BASIC section will not be filled with the necessary data. It all ends with a command line prompt. And you can even log in as root without a password.

That is a bit strange. There is nothing that in any way depends on the flavor (RX or LT), board, CPU or anything hardware-related when it comes to partitioning. Could you perhaps go and edit /etc/init.d/S30part and add set -x in the second line? Then we would be able to see what's going on in that script.

Maybe it's simply the reboot that fails. The sequence is:

create partition
create a file named /make_vfat file in the root directory
reboot
create FAT32 file system
remove /make_vfat
mount FAT32 file system
extract data

If the reboot fails, you will end up with an SD card with the right partitions, but no file system on the BASIC partition and a /make_vfat file on the root partition. In that case, simply power cycling the board should do the trick.

CityAceE · Apr 23, 2024

uli Despite its name the M2 Zero is totally incompatible to Banana Pi/M1/M1+/Pro/M2/M2U/M3/M64 due to a different SoC - requiring different boot loaders and drivers.

I have realized that it would be impossible to add M2 Zero as an additional device. Therefore, I am now focusing on building a system for only one device.

uli So I don't think I will be engaging with this thing any further when it comes to a bare-metal (RX) implementation.

I'm sorry to hear that, but I understand your situation.

uli If you are willing to take on the job of bending the basicengine_h3_lt_defconfig into something that works on the BPi M2 Zero, I'd be more than happy to include the result in the repo and the git builds.

I will try my best to do everything within the limits of my knowledge and experience.

uli extract data

It seems to me that the problem is somewhere in this place. But it needs to be checked.

I'm experimenting with the same SD cards. Interestingly, after recreating the file system, the same files that I recorded earlier remain on the BASIC section, for example, video recording files of the process. I have not studied why this happens, but I have noticed this behavior.

uli Could you perhaps go and edit /etc/init.d/S30part and add set -x in the second line? Then we would be able to see what's going on in that script.

I will conduct such an experiment at a later date. I will also record a video of the boot process for you to watch.

Uuli · Apr 23, 2024

CityAceE I'm experimenting with the same SD cards. Interestingly, after recreating the file system, the same files that I recorded earlier remain on the BASIC section, for example, video recording files of the process. I have not studied why this happens, but I have noticed this behavior.

That is intentional so you can update to a later version without losing your files. The setup code will only create a new file system if there isn't one already, and it will only unpack the system files if there is no sys directory.

CityAceE · Apr 23, 2024

uli

I've made the final build. I also formatted the BASIC partition in NTFS just in case and changed its name. Next, I deployed sdcard.img to this SD. After launching on Banana Pi M2 Zero, everything went down, the FAT32 partition was created with the correct name and content. There are no errors at any stage. I filmed the download process for you. And as I understand it, this is the finish line. Basic Engine RX will not work on Banana PiM 2 Zero due to differences in hardware from other computers with H2+/H3, which is programmed in the Bare Metal style.

https://youtu.be/XiUCXH_gCfM?si=0hcMAeNmB9Yh7-mB

CityAceE · Apr 23, 2024

uli

I'm trying to build H3_LT so far just by default, without any changes. I get an error. What could be wrong?

generate_png_fonts.c:25:10: fatal error: png.h: No such file or directory 25 | #include <png.h>

UPD:
Fixed by installation of libpng-dev package.

CityAceE · Apr 24, 2024

Now Banana Pi M2 Zero boots Basic Engine LT:

https://youtu.be/A3X0KttUWfw

Sometimes, during kernel boot, the computer freezes and you have to press reset.

Uuli · Apr 24, 2024

Excellent. Please post the config here so I can add it.

Also, please try to reproduce the hangs without "quiet" in the bootargs so we can see where it happens. (I added that to silence the boot messages because the serial port is slow enough to slow down the boot process noticeably.)

CityAceE · Apr 24, 2024

uli Please post the config here so I can add it.

Here is.

basicengine-buildroot-banana-pi-m2-zero.zip

3kB

Also here is a link to the compiled disk image for Banana Pi M2 Zero:
https://disk.yandex.ru/d/OZtEt75p5Hh-DA

uli Also, please try to reproduce the hangs without "quiet" in the bootargs so we can see where it happens. (I added that to silence the boot messages because the serial port is slow enough to slow down the boot process noticeably.)

1.

[ 3.065243] mmc0: new high speed SDIO card at address 0001 [ 3.074368] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.06 [ 3.082761] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.090058] usb usb3: Product: Generic Platform OHCI controller [ 3.096019] usb usb3: Manufacturer: Linux 6.6.21 ohci_hcd [ 3.101461] usb usb3: SerialNumber: 1c1a400.usb [ 3.106771] hub 3-0:1.0: USB hub found [ 3.110614] hub 3-0:1.0: 1 port detected [ 3.115294] Waiting for root device /dev/mmcblk0p2... [ 3.584204] usb 3-1: new low-speed USB device number 2 using ohci-platform [ 3.821233] usb 3-1: New USB device found, idVendor=1a81, idProduct=1004, bcdDevice= 0.01 [ 3.829491] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.836654] usb 3-1: Product: Wireless Dongle [ 3.841029] usb 3-1: Manufacturer: G-Tech [ 3.853718] input: G-Tech Wireless Dongle as /devices/platform/soc/1c1a400.usb/usb3/3-1/3-1:1.0/0003:1A81:1004.0001/input/input1 [ 3.924983] hid-generic 0003:1A81:1004.0001: input,hidraw0: USB HID v1.11 Keyboard [G-Tech Wireless Dongle] on usb-1c1a400.usb-1/input0 [ 3.950206] input: G-Tech Wireless Dongle Mouse as /devices/platform/soc/1c1a400.usb/usb3/3-1/3-1:1.1/0003:1A81:1004.0002/input/input2 [ 3.962528] input: G-Tech Wireless Dongle as /devices/platform/soc/1c1a400.usb/usb3/3-1/3-1:1.1/0003:1A81:1004.0002/input/input3 [ 3.974338] input: G-Tech Wireless Dongle Consumer Control as /devices/platform/soc/1c1a400.usb/usb3/3-1/3-1:1.1/0003:1A81:1004.0002/input/input4 [ 4.044361] input: G-Tech Wireless Dongle System Control as /devices/platform/soc/1c1a400.usb/usb3/3-1/3-1:1.1/0003:1A81:1004.0002/input/input5 [ 4.057762] hid-generic 0003:1A81:1004.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [G-Tech Wireless Dongle] on usb-1c1a400.usb-1/input1

Then I turned off the USB dongle and restart Banana Pi:

[ 3.167428] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.06 [ 3.175742] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.182990] usb usb3: Product: Generic Platform OHCI controller [ 3.188939] usb usb3: Manufacturer: Linux 6.6.21 ohci_hcd [ 3.194362] usb usb3: SerialNumber: 1c1a400.usb [ 3.199684] hub 3-0:1.0: USB hub found [ 3.203541] hub 3-0:1.0: 1 port detected [ 3.208257] Waiting for root device /dev/mmcblk0p2...

Next, the computer cannot be loaded, it freezes every time after clicking on the reset. But if you turn off the computer and then turn it on, then the kernel can boot. If you insert a USB dongle during "freezing", then information will be recorded in the log, and it will also be recorded if you remove the dongle. However, there is still no further loading of the kernel. I've tried recording to different SD cards, but the behavior is always the same. This is repeated whenever there is no "quiet" option. When there is a "quiet", then freezes are not so frequent and halt can be defeated by pressing reset.

Uuli · Apr 24, 2024

CityAceE Next, the computer cannot be loaded, it freezes every time after clicking on the reset. But if you turn off the computer and then turn it on, then the kernel can boot. If you insert a USB dongle during "freezing", then information will be recorded in the log, and it will also be recorded if you remove the dongle. However, there is still no further loading of the kernel. I've tried recording to different SD cards, but the behavior is always the same. This is repeated whenever there is no "quiet" option. When there is a "quiet", then freezes are not so frequent and halt can be defeated by pressing reset.

If found this post on the Banana Pi forum:
https://forum.banana-pi.org/t/waiting-for-root-mmc-device/16676

So adding

               mmc0 = &mmc0;
               mmc1 = &mmc1;
               mmc2 = &mmc2;

to the aliases block in the device tree is supposed to fix this. And I actually think it would. In the boot log you posted there is this line:

CityAceE [ 3.065243] mmc0: new high speed SDIO card at address 0001

So the MMC controller that the WiFi chip is connected to is suddenly mmc0, not the one with the SD card slot. Looks like the order is random and probably depends on how fast the MMC controllers are responding. That explains why seemingly random changes to the system cause boot failures.

If you could try adding these statements to the aliases block dts file and check if it work then, I can just add another patch (probably best to do it for all Allwinner boards) and we're good. (Apparently the "correct" way to handle this is using UUIDs to mount file systems, I might have to look into that as well.)

CityAceE · Apr 24, 2024

uli If you could try adding these statements to the aliases block dts file and check if it work

I have not come up with another way to convert DTS to DTS in the copiled image, make changes there and convert back DTS to DTB.

I received errors during the reverse conversion process.

root@builder:/mnt/cityacee/1# dtc -I dts -O dtb -f sun8i-h2-plus-bananapi-m2-zero.dts -o sun8i-h2-plus-bananapi-m2-zero.dtb
sun8i-h2-plus-bananapi-m2-zero.dts:1465.10-1471.4: ERROR (path_references): /aliases: Reference to non-existent node or label "mmc0"

sun8i-h2-plus-bananapi-m2-zero.dts:1465.10-1471.4: ERROR (path_references): /aliases: Reference to non-existent node or label "mmc1"

sun8i-h2-plus-bananapi-m2-zero.dts:1465.10-1471.4: ERROR (path_references): /aliases: Reference to non-existent node or label "mmc2"

Warning: Input tree has errors, output forced

Unfortunately, it didn't help. The computer boots up every other time.

But these changes probably need to be made during the image build process. But I do not know how to do it.

CityAceE · Apr 25, 2024

I think I figured out how to do it. I'll come back with the result later.

Uuli · Apr 25, 2024

CityAceE But these changes probably need to be made during the image build process. But I do not know how to do it.

If you have compiled an image already, the easiest way is probably to edit the dts file, then delete output/build/linux-6.6.21/.stamp_built and run make again.