mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-13 00:17:23 +00:00
fdt: Provide debug info when a device tree cannot be found
It can be quite confusing with a new platform to figure out why the device tree cannot be located. Add some debug information for this case. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
parent
c4af6732c4
commit
cb5f97f707
1 changed files with 7 additions and 0 deletions
|
@ -568,6 +568,13 @@ int fdtdec_prepare_fdt(void)
|
||||||
puts("Missing DTB\n");
|
puts("Missing DTB\n");
|
||||||
#else
|
#else
|
||||||
puts("No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>\n");
|
puts("No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>\n");
|
||||||
|
# ifdef DEBUG
|
||||||
|
if (gd->fdt_blob) {
|
||||||
|
printf("fdt_blob=%p\n", gd->fdt_blob);
|
||||||
|
print_buffer((ulong)gd->fdt_blob, gd->fdt_blob, 4,
|
||||||
|
32, 0);
|
||||||
|
}
|
||||||
|
# endif
|
||||||
#endif
|
#endif
|
||||||
return -1;
|
return -1;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue