Hello,

I have a problem with uboot, during its scan of USB buses, it blocks for several tens of seconds, displays an error, then boots. Sometimes it blocks completely and it takes several ON/OFF attempts to get it started.

I'm using Nano Pi Core LTS with the mini-shield, I have over 20 and it's happening on all of them. This is what is displayed when it finally starts :

U-Boot SPL 2020.10-armbian (Aug 08 2021 - 15:18:24 +0200)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Aug 08 2021 - 15:18:24 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0

Error: ethernet@1c30000 address not set.
No ethernet found.

starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... Device NOT ready
   Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3964 bytes read in 6 ms (644.5 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc [...]

 

 

And when it completely blocks:

 

U-Boot SPL 2020.10-armbian (Aug 08 2021 - 15:18:24 +0200)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Aug 08 2021 - 15:18:24 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0

Error: ethernet@1c30000 address not set.
No ethernet found.

starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0xd8d80
Device NOT ready
   Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds

The problem does not occur with FriendlyARM's operating system. So it seems to me that the hardware is not at fault ?

Have you ever encountered this problem and do you have a solution ?

 

Thanks

5 minutes ago, epsilonrt said:

do you have a solution ?

 

Are you trying this with a latest software from the download section?

Yes, this happens on all versions of Armbian that I have tested.

On the other hand, I just did a test, because I read a comment that you had posted on another post which incriminated the hardware.

I isolated the Nano Pi Core from the mini-shield and the problem disappeared.

What I can't figure out is that the problem is not with friendlyARM's OS. So the problem could be related to the way uboot performs its scan ?

What do you think about it ?

Thanks.

This is what is displayed with the FriendlyARM version:

 

U-Boot SPL 2017.11 (May 10 2018 - 18:05:50)
DRAM: 512 MiB(408MHz)
CPU Freq: 408MHz
Trying to boot from MMC2


U-Boot 2017.11 (May 10 2018 - 18:05:50 +0800) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyElec NanoPi H3
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 1, SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
eMMC exist, PC6=1
BOARD: nanopi-neo-core
starting USB...
No controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr [...]

 

We can see that the USB scan says it did not find any controllers

9 hours ago, epsilonrt said:

So the problem could be related to the way uboot performs its scan ?

What do you think about it ?

Its 2022 and you are using u-boot from 2020. Latest images and repository have 2022.07. This is first problem that needs to be adjusted. Nobody knows anyomore which bugs are hidden in that old version https://github.com/armbian/build/commit/3cb7175c667da480e59ef5b9bb23e238b4955cdf

No, I'm using Armbian version 22.08, but it doesn't work. On the other hand, it works with the version of FriendlyARM which dates from 2017...

On 10/14/2022 at 6:18 PM, epsilonrt said:

No, I'm using Armbian version 22.08, but it doesn't work. On the other hand, it works with the version of FriendlyARM which dates from 2017...

I don't know why, but images indeed had old boot loader. I have rebuild images (22.08.6) and they work fine on my Nanopi Neo. Boot log: https://paste.armbian.com/aqinezihen

 

Serial console:
 

U-Boot 2022.07-armbian (Oct 15 2022 - 16:00:51 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  256 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) 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/boot.scr
4021 bytes read in 3 ms (1.3 MiB/s)
## Executing script at 43100000
U-boot loaded from SD

 

You were right I solved the problem with version 22.08.4

Thank you for your help.

On the other hand, there is always another problem which is that the board has a random MAC address and not that of the manufacturer... I solved the problem with an overlay file in device tree.

nanopi-neo-stable-mac.dts

13 minutes ago, epsilonrt said:

On the other hand, there is always another problem which is that the board has a random MAC address and not that of the manufacturer... I solved the problem with an overlay file in device tree.

Not happening to me. On any of those:
 

dtb-5.15.72-sunxi
dtb-5.19.14-sunxi

 

Anyway, problems solved! 

In fact the problem has not disappeared, I have just changed NanoPi and the problem reappears... As soon as I switch to the old FriendlyARM system the problem disappears.

 

U-Boot SPL 2021.10-armbian (Aug 30 2022 - 06:46:03 +0000)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2021.10-armbian (Aug 30 2022 - 06:46:03 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial
Out:   serial
Err:   serial
Net:   phy interface0

Error: ethernet@1c30000 address not set.
No ethernet found.

starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0xd8d80
Device NOT ready
   Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus usb@1c1d400 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
3964 bytes read in 4 ms (967.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
267 bytes read in 3 ms (86.9 KiB/s)
9711899 bytes read in 407 ms (22.8 MiB/s)
8387520 bytes read in 355 ms (22.5 MiB/s)
Found mainline kernel configuration
32454 bytes read in 12 ms (2.6 MiB/s)
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo
504 bytes read in 9 ms (54.7 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
399 bytes read in 4 ms (96.7 KiB/s)
Applying user provided DT overlay nanopi-neo-stable-mac.dtbo
4185 bytes read in 8 ms (510.7 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0x7ffbc0 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9711835 Bytes = 9.3 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 496bc000, end 49fff0db ... OK
   Loading Device Tree to 4964b000, end 496bbfff ... OK

I will try to recompile the latest version like you.

6 minutes ago, epsilonrt said:

In fact the problem has not disappeared, I have just changed NanoPi and the problem reappears..

Looking at your u-boot version it seems you haven't flashed correct image.

 

Images from download section (22.08.6) have boot loader:
 

U-Boot 2022.07-armbian (Oct 15 2022 - 16:00:51 +0000) Allwinner Technology

 

With the new version, it's worse ! it keeps crashing and rebooting...

 

U-Boot SPL 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0xd8d80
Device NOT ready
   Request Sense returned 00 00 00
prefetch abort
pc : [<eff6fffa>]          lr : [<5ffa3c81>]
reloc pc : [<d9fe6ffa>]    lr : [<4a01ac81>]
sp : 5bf60008  ip : 0000001c     fp : 5ffde6a2
r10: 5ffe5340  r9 : 5bf68ec0     r8 : 00000000
r7 : 00000000  r6 : 5bf92e78     r5 : a0000000  r4 : 5bf6d188
r3 : eff6ffff  r2 : 00000000     r1 : 00000000  r0 : 5bf6d188
Flags: NzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: 0000 0000 0000 0000 (0000) 0000
Resetting CPU ...

resetting ...

U-Boot SPL 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0x248d80
Device NOT ready
   Request Sense returned 04 44 81
prefetch abort
pc : [<eff6fffa>]          lr : [<5ffa3c81>]
reloc pc : [<d9fe6ffa>]    lr : [<4a01ac81>]
sp : 5bf60008  ip : 0000001c     fp : 5ffde6a2
r10: 5ffe5340  r9 : 5bf68ec0     r8 : 00000000
r7 : 00000000  r6 : 5bf92e78     r5 : a0000000  r4 : 5bf6d188
r3 : eff6ffff  r2 : 00000000     r1 : 00000000  r0 : 5bf6d188
Flags: NzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: 0000 0000 0000 0000 (0000) 0000
Resetting CPU ...

resetting ...

U-Boot SPL 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... Device NOT ready
   Request Sense returned 04 44 81
prefetch abort
pc : [<eff6fffa>]          lr : [<5ffa3c81>]
reloc pc : [<d9fe6ffa>]    lr : [<4a01ac81>]
sp : 5bf60008  ip : 0000001c     fp : 5ffde6a2
r10: 5ffe5340  r9 : 5bf68ec0     r8 : 00000000
r7 : 00000000  r6 : 5bf92e78     r5 : a0000000  r4 : 5bf6d188
r3 : eff6ffff  r2 : 00000000     r1 : 00000000  r0 : 5bf6d188
Flags: NzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: 0000 0000 0000 0000 (0000) 0000
Resetting CPU ...

resetting ...

 

As I said at the beginning of this post, I'm using Nano Pi Core LTS with the mini-Shield, the previous message corresponds to this scenario.

When I put the same SD card with the new Armbian version in a NanoPi Neo 1.3, I have this :

 

U-Boot 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) 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/boot.scr
4021 bytes read in 4 ms (981.4 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
182 bytes read in 4 ms (43.9 KiB/s)
9710442 bytes read in 404 ms (22.9 MiB/s)
8387264 bytes read in 350 ms (22.9 MiB/s)
Found mainline kernel configuration
32454 bytes read in 11 ms (2.8 MiB/s)
504 bytes read in 8 ms (61.5 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost1.dtbo
504 bytes read in 8 ms (61.5 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
4185 bytes read in 9 ms (454.1 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0x7ffac0 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9710378 Bytes = 9.3 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 496bd000, end 49fffb2a ... OK
   Loading Device Tree to 4964c000, end 496bcfff ... OK

Starting kernel ...

 

So it works, the problem comes from there, you are on a NanoPi Neo, and I am on a NanoPi Neo Core with minishield.

This issue is present on almost all NanoPi Neo Core with minishield, so it is not a hardware issue. Also, all boards that have this problem work fine with the old FriendlyARM system.

There would therefore be a difference to take into account between the NanoPi Neo and the NanoPi Neo Core.

After several tries, I just figured out why I have a NanoPi Neo Core with mini-shield that works with the new version.

In fact, it is equipped with an M2 SSD, as soon as it is in place, the system boots correctly.

The minishield's JMS567-LGBB1A controller happens to use the USB3 bus (attached the diagram).

 

When I install the SSD, I have this:

 

U-Boot 2022.07-armbian (Oct 15 2022 - 16:08:01 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
Core:  63 devices, 17 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:   serial
Err:   serial
Net:   phy interface1
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 2 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0

 

It is this line :

scanning bus usb@1c1d000 for devices... 2 USB Device(s) found

that is different. Without SSD, I have this:

scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0x248d80
Device NOT ready
   Request Sense returned 04 44 81

 

Once again, I remind you, everything works correctly with the old FriendlyARM system, we have this:

 

BOARD: nanopi-neo-core
starting USB...
No controllers found

 

So the uboot code is different, it doesn't scan USB buses. I'm going to find out if you can disable USB bus scanning in uboot...

I read the u-boot documentation: https://github.com/ARM-software/u-boot/blob/master/doc/README.usb

I plan to disable USB bus scan by u-boot. It seems to match the CONFIG_USB_STORAGE definition in u-boot/include/configs

I would have to do it with a patch: https://github.com/armbian/build/tree/master/patch/u-boot/u-boot-sunxi ?

Could you tell me if there is an Armbian tutorial for reconfiguring u-boot ?

Is it necessary to rebuild the whole image or can we change u-boot on an existing image ?

Thanks for your help.

47 minutes ago, epsilonrt said:

Could you tell me if there is an Armbian tutorial for reconfiguring u-boot ?

U-boot is not Armbian thing. We build it. 
 

47 minutes ago, epsilonrt said:

Is it necessary to rebuild the whole image or can we change u-boot on an existing image ?

You can build u-boot / kernel only - 1st switch in manual. You get deb files which you install to the system and update via armbian-config ... if system boots. If not, you need to flash it manually. Manually means - extracting binaries from that deb file alongside with the script that does the flashing. And run commands by hand.

Apparently this board will need modified u-boot configuration which is defined in build system this way. Example of generating a dedicated configuration that doesn't exists upstream. For enabling USB scan its probably a switch within u-boot. Like I said, this is outside Armbian and I would tell you if I know, but without digging into the code (manuals are usually within the code), I have no clue. Check what FriendlyElec did to the u-boot they are using. Its some old one, so many things could be done differently ... but sometimes you can get some clues out of it. Possible solution is setting CONFIG_USB_EHCI_HCD to n ...

Hope this helps.

Thank you very much Igor !

Yes it helps me.

I will keep you posted on the solution found, so that it benefits others.