[U-Boot] [PATCH v3 47/54] fdt: Provide debug info when a device tree cannot be found
Simon Glass
sjg at chromium.org
Tue Jun 23 23:39:09 CEST 2015
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 at chromium.org>
---
Changes in v3: None
Changes in v2: None
lib/fdtdec.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/fdtdec.c b/lib/fdtdec.c
index add9adc..a78d577 100644
--- a/lib/fdtdec.c
+++ b/lib/fdtdec.c
@@ -568,6 +568,13 @@ int fdtdec_prepare_fdt(void)
puts("Missing DTB\n");
#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");
+# 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
return -1;
}
--
2.4.3.573.g4eafbef
More information about the U-Boot
mailing list