FDT creation failed!

[Hayk Arzumanyan]

Hello. I have own developed custom boards with H3 processor.

One of it works nice, second one doesn't boot.

Here is the serial output.

 

U-Boot 2020.04-armbian (Jun 01 2020 - 18:57:23 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: 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@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 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
3789 bytes read in 3 ms (1.2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
201 bytes read in 2 ms (97.7 KiB/s)
10307086 bytes read in 492 ms (20 MiB/s)
7236216 bytes read in 347 ms (19.9 MiB/s)
Found mainline kernel configuration
29463 bytes read in 8 ms (3.5 MiB/s)
4185 bytes read in 9 ms (454.1 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    10307022 Bytes = 9.8 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 4962b000, end 49fff5ce ... OK
   Loading Device Tree to 495bb000, end 4962afff ... OK
fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed
 - must RESET the board to recover.

 

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

 

Have any suggestions?

What is fdt_find_or_add_subnode: memory: FDT_ERR_BADSTRUCTURE
ERROR: arch-specific fdt fixup failed??

[Igor]

On 8/28/2020 at 5:24 PM, Hayk Arzumanyan said:

I have own developed custom boards with H3 processor

Allwinner H3 sub-forum is dedicated to board we know and we decide to support. Moving to general areas.

[Hayk Arzumanyan]

My boards are 1:1 copy of Orange Pi One. It's not unknown board. And Armbian is Buster server stable version from https://www.armbian.com/orange-pi-one/

[Werner]

42 minutes ago, Hayk Arzumanyan said:

 1:1 copy

If that would be true it would boot just fine and I have several OrangePi One SBCs laying around at my space

[Hayk Arzumanyan]

Werner it's true. I'm not here to lie ))) I'm not asking what do you have. I'm asking do you know FDT creation failed problem what does it mean???

I haven't only these two boards. I have a lot of 1:1 copy Orange Pi One boards they boot fine. Only in one board it happens.

 

And I don't understand FDT creation failed it's RAM or H3 processor problem.

[Werner]

I serioulsy don't wanted to imply you are lying. Heaven forbid!

For the issue itself I unfortunately cannot answer your question since I don't know how and why this happens.

 

However Igor is right anyways. it is a board that is not supported since it is custom made so it is correct to move the topic to general discussion / p2p help.

[Igor]

59 minutes ago, Hayk Arzumanyan said:

1:1 copy of Orange Pi One. It's not unknown board

Scheme is the same - is PCB also 100% identical?
 

[Hayk Arzumanyan]

Yes, it's identical. 10 times checked.