* Using a .dtb built with kernel from Yocto 3.1.1 with u-boot from Yocto 3.1.2 results in "base fdt does did not have a /__symbols__ node ..."
@ 2020-11-13 20:00 Brian Hutchinson
2020-12-07 21:18 ` Brian Hutchinson
0 siblings, 1 reply; 2+ messages in thread
From: Brian Hutchinson @ 2020-11-13 20:00 UTC (permalink / raw)
To: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
I have no clue what my problem is here.
I built imx8mm-evk.dtb (kernel version 5.4.51) in Yocto meta-freescale environment from Dunfell/Yocto 3.1.1, and then moved on to Dunfell/Yocto 3.1.2. Looks like u-boot version changed during that time. Small bump in kernel version too.
When I copy imx8mm-evk.dtb from previous Yocto release into my sdcard image built with Dunfell/Yocto 3.1.2 I get the following on boot:
BuildInfo:
- ATF b0a00f2
- U-Boot 2020.04-imx_v2020.04_5.4.24_2.1.0+g4979a99482
switch to partitions #0, OK
mmc2(part 0) is current device
flash target is MMC:2
Net: eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc2(part 0) is current device
21621248 bytes read in 87 ms (237 MiB/s)
Booting from mmc ...
43774 bytes read in 10 ms (4.2 MiB/s)
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Using Device Tree in place at 0000000043000000, end 000000004300dafd
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
No Space for dtb
ERROR: system-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.
It appears to be something with u-boot because if I flash sdcard with u-boot from previous Yocto release the issue goes away. I'd like to understand what is going on and why this is happening.
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 1826 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Using a .dtb built with kernel from Yocto 3.1.1 with u-boot from Yocto 3.1.2 results in "base fdt does did not have a /__symbols__ node ..."
2020-11-13 20:00 Using a .dtb built with kernel from Yocto 3.1.1 with u-boot from Yocto 3.1.2 results in "base fdt does did not have a /__symbols__ node ..." Brian Hutchinson
@ 2020-12-07 21:18 ` Brian Hutchinson
0 siblings, 0 replies; 2+ messages in thread
From: Brian Hutchinson @ 2020-12-07 21:18 UTC (permalink / raw)
To: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
I made an error in my original post. It was when I moved from Yocto 3.1.2 to 3.1.3 that I noticed this whole:
" failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
No Space for dtb
ERROR: system-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###"
... business, which appears to be associated with u-boot because I can dd if=imx-boot-imx8mmevk-sd.bin of=/dev/mmcblk2 bs=1k seek=33 using u-boot image from Yocto 3.1.2 and the issue goes away.
dd=if .
So nobody has seen this before???
Regards,
Brian
[-- Attachment #2: Type: text/html, Size: 1053 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-07 21:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-13 20:00 Using a .dtb built with kernel from Yocto 3.1.1 with u-boot from Yocto 3.1.2 results in "base fdt does did not have a /__symbols__ node ..." Brian Hutchinson
2020-12-07 21:18 ` Brian Hutchinson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).