BananaPI M1+ boot loop

[Occhioverde]

Hi there!
I just received three decommissioned BananaPI M1+ from a company and I'm trying to install the latest version of Armbian Buster available on them.
Once I flash the image to the SD card (tested and working fine), however, the board goes into boot loop as per the video.
The only error that seems to be displayed is "EHCI failed to shut down host controller".
If it can be useful to find the cause, I point out that the problem occurs with both Armbian Buster and Armbian Focal regardless of the presence of the "fdtfile=sun7i-a20-bananapi-m1-plus.dtb" line in the /boot/armbianEnv.txt file.
What do you think I could do to solve it?
Thank you all in advance.

[Werner]

Maybe https://armbian.atlassian.net/browse/AR-749

Try building an image from master or wait until 21.08 release.

[dl9sec]

Hi,

 

exact the same boot loop here with my M1 and the latest Armbian Focal.

 

I have a little server running here since years currently with Armbian 21.05.6 Bionic (Linux 5.4.88-sunxi). Only problem with it was, that the GUI freezes after about 15 minutes when HTOP is running in a terminal window of the GUI, but the rest of the system was running further. The system always boots well with a keyboard and a rtl-sdr stick plugged to the USB.

 

Now with the latest Armbian Focal I get this boot loop, when at least one USB device is plugged. Armbian only boots if nothing is plugged to the USB.

 

Is it a bootloader problem?

 

Regards, Thorsten

[Igor]

7 minutes ago, dl9sec said:

Is it a bootloader problem?

Yes. apt update / upgrade + nand-sata-install + update bootloader + reboot .... should do. Or manually.

[dl9sec]

Great stuff, Igor.

 

That did it, thank you very much 

 

Regards, Thorsten

[Rein]

Hi Igor, I seem to have the same problem. Any of the Debian Buster / Focal images refuse to boot up on my banana Pi M1 and go into a loop. Could you please expand on your solution. Apt update won’t work if I can’t boot. I can access the SD with a raspberry Pi . Maybe you can tell me what needs manually be changed to make the SD boot on my banana Pi M1

Regards

rein

[tvs]

Hi,
Same issue than Rein on my BananaPi with Armbian_21.05.1_Bananapi_buster_current_5.10.34_minimal.img.
Thought it might be related to the SDCard health, but F3probe says it's ok.
Some startups achieve to go further on, but ends with a kernel panic, beginning with:
[   12.539309] Internal error: Oops: 805 [#1] SMP THUMB2
The whole start log pasted from minicom can be found here: https://postit.ilinux.fr/?33cebd8991824eed#CvQVEzwarxRShDRzQewGRG8G1Hd4G8LMxYZgPRmLXpmZ (lifetime 1month).
Cheers.

 

[Igor]

Updating u-boot:

https://docs.armbian.com/User-Guide_Recovery/

[Rein]

Hi, I had a look at the updating u-boot info on https://docs.armbian.com/User-Guide_Recovery/

It seems quite involved.

I have just discovered that it is easy to boot up by disconnecting the usb ports and reconnecting mouse and keyboard after the system has booted.

I have replaced my old debian 'stretch' with debian buster-xfce. .

because my banana M1 runs 24/7 rebooting will be quite infrequent.

Maybe this solution is a way out for others until some clever armbian person can come up with a better image file for the M!

Rein

[tvs]

I digged a bit in the forums, and it seems that the loop thing happens to several boards. I saw the commit in August 03 to go back to u-boot tag2020:10 (https://github.com/armbian/build/pull/2963).

This being said, I made a few additionnal tests, since it seems to me that there might be more than u-boot due to OUPS and kernel panics I have been issuing.

Context: BPI is connected via serial but has also a screen, connected to network, nothing plugged in USB.
** Armbian_20.11.6_Bananapi_buster_current_5.10.4_minimal.img + kernel 5.10.55: Pb 'Unable to handle kernel paging request at virtual address 816ba440' at least, startup log is here:

   https://postit.ilinux.fr/?da42320bdeeb734d#FUNpSTD5ogvCc57S84ZfYRLYTUMmXhmSHpxHXhcTNspu (I checked because I didn't read the commit yet)

** Armbian_21.05.1_Bananapi_buster_current_5.10.34_minimal.img
    Here too, startups may be different. Always have a no signal on the screen. Kernel Panic. Log is here: https://postit.ilinux.fr/?52b0500d4a5d0741#BhCykEPZsg9Co9kL84rLJ3hikdtimN1fvedqsLK7iH4B

** Armbian_21.08.0-trunk.110_Bananapi_hirsute_edge_5.13.7.img, checked just in case, but startup ends at 'Starting kernel ...' (nothing happened during at least 5min). Again, no signal on the screen.

** I tried the very last version of u-boot, but like for one week or so, doing so lead me to the following, without anything happening next...
U-Boot SPL 2021.10-rc1-00240-gab97eb341c (Aug 05 2021 - 19:23:48 +0200)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

** Armbian_21.05.1_Bananapi_buster_current_5.10.34_minimal.img + Kernel-5.10.55, the idea here is to check both u-boot and the last kernel. Got some starts ending with 'Starting kernel ...', other with a kernel panic 'not syncing: stack-protector'
   Log is here: https://postit.ilinux.fr/?0ddea25565f1695c#BXCFHWP2W5U3R2A89YsHmJfou8Num5oEgoNibzjD5q6W

** Armbian_21.05.1_Bananapi_buster_current_5.10.34_minimal.img + Kernel-4.19.201
   I made 2 execs, both results in a no signal for the screen.
   The 1st makes a re-mounted-ro of /, and writes Failed to start Armbian-ZRAM config. Log is here: https://postit.ilinux.fr/?7a95b34eb3fd27c6#8wwMV4q1ezMBEisLtJNezBAC6eZQ2p2ukaKHTQZat4tt
  2nd exec went further, I don't know how ARMBian first boot may have impacted this 2nd exec. Still error ans script (ZRAM config and ntp). Exec seems to achieve something, but no login (serial) and no signal on screen either.
  Log is https://postit.ilinux.fr/?ab16234f6bf18104#H6vUrPcuCmsR3ox57SW7ocDgwSBkC4vgNQx925bg8xe5

Note that kernels have been compiled with the sunxi_defconfig configuration.
I had to change a bit what is in /boot to make things work, like adding a script.bin generated from sunxi-tools, and used the boot.cmd taken from ArchLinux https://wiki.archlinux.org/title/Banana_Pi (using ARMbian lead to errors, maybe initram :?

I'm more than willing to help further if instructed what to do...
Cheers.

[klankschap]

With the latest img of the Arbian Buster on an SD, the Olimex board will start, then keeps resetting:

 

 

 

U-Boot SPL 2021.04-armbian (May 06 2021 - 17:21:52 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 17:21:52 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2-eMMC
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:0... In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   eth0: ethernet@1c50000, eth1: usb_ether
230454 bytes read in 17 ms (12.9 MiB/s)
Error: 24 bits/pixel bitmap incompatible with current video mode
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 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
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/boot.scr
3967 bytes read in 3 ms (1.3 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 3 ms (49.8 KiB/s)
9932688 bytes read in 566 ms (16.7 MiB/s)
7973464 bytes read in 455 ms (16.7 MiB/s)
Found mainline kernel configuration
43687 bytes read in 11 ms (3.8 MiB/s)
5532 bytes read in 12 ms (450.2 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9932624 Bytes = 9.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
data abort
pc : [<7ef89db8>]          lr : [<00000011>]
reloc pc : [<4a013db8>]    lr : [<cb08a011>]
sp : 7af4aa18  ip : 00000000     fp : 7efddc78
r10: 00000020  r9 : 7af55ec0     r8 : 7efea98c
r7 : 6c616972  r6 : 00000010     r5 : e7585d3a  r4 : 7af6f3c0
r3 : 7af6f3c8  r2 : 7af6f3b8     r1 : 7afa0458  r0 : 00000019
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: d005 f027 0501 441d (686d) 07ed
Resetting CPU ...

resetting ...

U-Boot SPL 2021.04-armbian (May 06 2021 - 17:21:52 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 17:21:52 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2-eMMC
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:0... In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   eth0: ethernet@1c50000, eth1: usb_ether
230454 bytes read in 17 ms (12.9 MiB/s)
Error: 24 bits/pixel bitmap incompatible with current video mode
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 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
Autoboot in 1 seconds, press <Space> to stop
=>

[Igor]

21 minutes ago, klankschap said:

With the latest img of the Arbian Buster on an SD, the Olimex board will start, then keeps resetting:

All A20 boards have the same problem - check those posts for workaround. 

[Rein]

Thanks for all replies. I am quite happy with the simple solution. I am running my BananaPi 24/7 without display, keyboard, mouse. The only device plugged into one of the usb ports is a wifi dongle. Reboot and cold boot work fine, even after the latest system update. (armbian-buster-xfce). All control is done via ssh / vnc.

At 89 I have to be a bit selective of what I spend my time on. So I leave some of the experimenting to others . Good luck !

Rein.

[klankschap]

With the latest img of the Arbian Buster on an SD, the Olimex board will start, then keeps resetting:

How to get it going ?

.F

 

 

U-Boot SPL 2021.04-armbian (May 06 2021 - 17:21:52 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 17:21:52 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2-eMMC
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:0... In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   eth0: ethernet@1c50000, eth1: usb_ether
230454 bytes read in 17 ms (12.9 MiB/s)
Error: 24 bits/pixel bitmap incompatible with current video mode
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 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
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/boot.scr
3967 bytes read in 3 ms (1.3 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 3 ms (49.8 KiB/s)
9932688 bytes read in 566 ms (16.7 MiB/s)
7973464 bytes read in 455 ms (16.7 MiB/s)
Found mainline kernel configuration
43687 bytes read in 11 ms (3.8 MiB/s)
5532 bytes read in 12 ms (450.2 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9932624 Bytes = 9.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
data abort
pc : [<7ef89db8>]          lr : [<00000011>]
reloc pc : [<4a013db8>]    lr : [<cb08a011>]
sp : 7af4aa18  ip : 00000000     fp : 7efddc78
r10: 00000020  r9 : 7af55ec0     r8 : 7efea98c
r7 : 6c616972  r6 : 00000010     r5 : e7585d3a  r4 : 7af6f3c0
r3 : 7af6f3c8  r2 : 7af6f3b8     r1 : 7afa0458  r0 : 00000019
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: d005 f027 0501 441d (686d) 07ed
Resetting CPU ...

resetting ...

U-Boot SPL 2021.04-armbian (May 06 2021 - 17:21:52 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 17:21:52 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2-eMMC
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:0... In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   eth0: ethernet@1c50000, eth1: usb_ether
230454 bytes read in 17 ms (12.9 MiB/s)
Error: 24 bits/pixel bitmap incompatible with current video mode
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 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
Autoboot in 1 seconds, press <Space> to stop
=>

[Werner]

Known issue (use search next time). Try nightly build (available at download page at very bottom) or wait until 21.08 release which is expected by end of August.

[Igor]

5 hours ago, Rein said:

I am quite happy with the simple solution.

If you can boot the board, you can easily update boot loader and those troubles should be gone. Recovery methods are needed when you can't.

 

1. sudo armbian-config

2. system -> install -> Install / update the bootloader on SD/eMMC

3. reboot

We used to have automated boot loader update, but that brought more problems so we went (years ago) back to manual updating.

[Rein]

Thank you Igor, I’ll give that a go tomorrow. Thanks for your help.

Rein. 👍

[Igor]

7 hours ago, Werner said:

Known issue (use search next time). Try nightly build (available at download page at very bottom) or wait until 21.08 release which is expected by end of August.

This is now the second post that I had to merge with this topic  

[tvs]

I dd Armbian_21.05.1_Bananapi_buster_current_5.10.34_minimal.img then u-boot-sunxi-with-spl.bin (checkout of v2020.10).
BPI boots and things seem to proceed well but then, no signal on the screen -- boot with/without a keyboard is the same.
Since logs are only printed on the screen, I only have the following until 'Starting kernel ...'. Yet, after some time letting the unit proceed, I rebooted and got a OOPS given below.
-- For Werner, as written in my previous post, I tried the Armbian_21.08.0-trunk.110_Bananapi_hirsute_edge_5.13.7.img without result.
Any idea why the screen goes in stanby, printing 'no signal'? (and some configuration modification to have logs printed on serial as well?)

Found U-Boot script /boot/boot.scr
3967 bytes read in 4 ms (967.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 4 ms (37.1 KiB/s)
8968888 bytes read in 592 ms (14.4 MiB/s)
7973464 bytes read in 472 ms (16.1 MiB/s)
Found mainline kernel configuration
43645 bytes read in 15 ms (2.8 MiB/s)
5532 bytes read in 14 ms (385.7 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
  Image Name:   uInitrd
  Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  Data Size:    8968824 Bytes = 8.6 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
  Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
  Loading Ramdisk to 49772000, end 49fffa78 ... OK
  Loading Device Tree to 496fe000, end 49771fff ... OK

[   12.819493] Internal error: Oops: 805 [#1] SMP THUMB2
[   12.866952] Modules linked in: axp20x_adc evdev lima gpu_sched sun4i_gpadc_iio sun4i_ts sunxi_cir sunxi_cedrus(C) v4l2_k
[   12.928746] CPU: 1 PID: 445 Comm: rsync Tainted: G        WC        5.10.34-sunxi #21.05.1
[   12.947387] Hardware name: Allwinner sun7i (A20) Family
[   12.963021] PC is at ext4_llseek+0xa2/0x100
[   12.977450] LR is at sys_llseek+0x69/0xfc
[   12.991520] pc : [<c030682e>]    lr : [<c02739d9>]    psr: 400e0033
[   13.007968] sp : c2ff7f30  ip : 00000000  fp : 000e7bc4
[   13.023397] r10: 00000000  r9 : c9ab5408  r8 : c2d183c0
[   13.038833] r7 : 00000000  r6 : 000e7bc4  r5 : 00000fff  r4 : fffff000
[   13.055621] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : 000e86dc
[   13.072268] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment none
[   13.089691] Control: 50c5387d  Table: 42e3c06a  DAC: 00000051
[   13.105570] Process rsync (pid: 445, stack limit = 0x27f33ead)
[   13.121615] Stack: (0xc2ff7f30 to 0xc2ff8000)
[   13.136208] 7f20:                                     00000000 00000000 00000000 00000000
[   13.154860] 7f40: 00000000 00000000 c0f04fc8 c2d183c0 c030678d c2d183c0 00000000 beb5e5b0
[   13.173580] 7f60: 00000000 c02739d9 00000000 00000035 beb5f1e8 c0274fc9 000e6e91 2a3d352b
[   13.192276] 7f80: b6f69978 00000000 000e7bc4 00000003 0000008c c0100284 c2ff6000 0000008c
[   13.210932] 7fa0: beb5f1e8 c0100061 00000000 000e7bc4 00000003 00000000 000e7bc4 beb5e5b0
[   13.229644] 7fc0: 00000000 000e7bc4 00000003 0000008c 00000003 beb5f1dc 00000000 beb5f1e8
[   13.248346] 7fe0: 0000008c beb5e5a8 b6f51a55 b6f50fc6 400e0030 00000003 00000000 00000000
[   13.267081] [<c030682e>] (ext4_llseek) from [<c02739d9>] (sys_llseek+0x69/0xfc)
[   13.285003] [<c02739d9>] (sys_llseek) from [<c0100061>] (ret_fast_syscall+0x1/0x62)
[   13.303344] Exception stack(0xc2ff7fa8 to 0xc2ff7ff0)
[   13.319145] 7fa0:                   00000000 000e7bc4 00000003 00000000 000e7bc4 beb5e5b0
[   13.338220] 7fc0: 00000000 000e7bc4 00000003 0000008c 00000003 beb5f1dc 00000000 beb5f1e8
[   13.357216] 7fe0: 0000008c beb5e5a8 b6f51a55 b6f50fc6
[   13.373046] Code: f3bf 8f5b f8d9 2080 (429a) d1f1  
[   13.388839] ---[ end trace d728074366bef4bf ]---
[   13.845445] systemd[1]: Started Armbian memory supported logging.
[   13.882704] systemd[1]: Starting Journal Service...
[   14.223207] systemd[1]: Started Journal Service.
[   14.356481] systemd-journald[470]: Received request to flush runtime journal from PID 1
 

[Igor]

1 hour ago, tvs said:

Any idea why the screen goes in stanby, printing 'no signal'?

 

Since you are obviously new, welcome to check FAQ: https://docs.armbian.com/User-Guide_FAQ/ and a support contract you have: https://github.com/armbian/build#support It doesn't give you any power to change project R&D focus which is needed to be changed to diagnose such issues. Remember - you have as much developers you support.

 

Problem was recognised and it seems fixed from engineering perspective. We will (double) check when time permits. Perhaps soon, perhaps next year. Its irrelevant since we are totally overloaded and you don't seems to notice. In the mean time check if you can help - where you can.

 

1 hour ago, tvs said:

For Werner, as written in my previous post, I tried the Armbian_21.08.0-trunk.110_Bananapi_hirsute_edge_5.13.7.img without result.

U-boot version on those builds?

[tvs]

4 hours ago, Igor said:

 

Since you are obviously new, welcome to check FAQ: https://docs.armbian.com/User-Guide_FAQ/ and a support contract you have: https://github.com/armbian/build#support It doesn't give you any power to change project R&D focus which is needed to be changed to diagnose such issues. Remember - you have as much developers you support.

 

Problem was recognised and it seems fixed from engineering perspective. We will (double) check when time permits. Perhaps soon, perhaps next year. Its irrelevant since we are totally overloaded and you don't seems to notice. In the mean time check if you can help - where you can.

I'll have a look. As written previously, I would gladly help if I can.
You're saying that the problem was recognized. Is there some doc somewhere?

4 hours ago, Igor said:

U-boot version on those builds?

U-Boot 2020.10-armbian (Jul 17 2021 - 06:11:38 +0000) Allwinner Technology
Yet, runs I made ended at "Starting kernel ..." and the current start went further, but "Oops - undefined instruction: 0 [#1] SMP THUMB2"
Thus my previous questions: if it's related to a branch of the kernel, I can try others -- I tried with linux-4.19.201 in previous tests of which I posted the logs..
Cheers.

 

[Igor]

11 hours ago, tvs said:

You're saying that the problem was recognized. Is there some doc somewhere?

Problem recognised = we believe it is real. Not something that is affected by one users wrong powering or similar hw problem. When a problem gets a chance that it will be recorded into our internal to do list.

 

11 hours ago, tvs said:

I would gladly help if I can.

Help on areas you are good at. There are plenty ideas what kind of help we need, https://armbian.atlassian.net/jira/projects is full of recognised but unsolved problems. 

 

11 hours ago, tvs said:

if it's related to a branch of the kernel, I can try others

 

To my understanding its something related with u-boot, but knowing more could easily cost week(s) of dedication and investigation. I have already asked a skilled person in this area to investigate deeper. But he is also doing something else and can only look when his personal time permits. Not right now. With a few thousands which we receive from you, we can't have specialist standing by waiting for problem to happen. We only cover electricity.

 

According to your questions - I think you can't help here. Putting a pressure - asking questions without adding value - is pointless. This is forum, not a support you have paid for.