<div dir="ltr"><span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND</span><br><div><span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Might be caused a config change in U-boot?</span></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 26, 2018 at 6:10 PM Andrew Jeffery <<a href="mailto:andrew@aj.id.au">andrew@aj.id.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 27 Jun 2018, at 01:49, Patrick Venture wrote:<br>
> I assume this is just a recipe change such that I need to now specify<br>
> something -- with OpenBMC v2.1 I see:<br>
> <br>
> """<br>
> U-Boot 2016.07 (May 24 2018 - 12:55:55 -0700)<br>
> <br>
> DRAM: 120 MiB<br>
> WARNING: Caches not enabled<br>
> Flash: 64 MiB<br>
> *** Warning - bad CRC, using default environment<br>
> <br>
> In: serial<br>
> Out: serial<br>
> Err: serial<br>
> Net: aspeednic#0<br>
> Error: aspeednic#0 address not set.<br>
> <br>
> Hit any key to stop autoboot: 0<br>
> ## Loading kernel from FIT Image at 20080000 ...<br>
> Using 'conf@1' configuration<br>
> Trying 'kernel@1' kernel subimage<br>
> Description: Linux kernel<br>
> Type: Kernel Image<br>
> Compression: uncompressed<br>
> Data Start: 0x20080128<br>
> Data Size: 1721352 Bytes = 1.6 MiB<br>
> Architecture: ARM<br>
> OS: Linux<br>
> Load Address: 0x40008000<br>
> Entry Point: 0x40008000<br>
> Hash algo: sha1<br>
> Hash value: de140d9d803c22f731c4d99a4250979489383a81<br>
> Verifying Hash Integrity ... sha1+ OK<br>
> ## Loading ramdisk from FIT Image at 20080000 ...<br>
> Using 'conf@1' configuration<br>
> Trying 'ramdisk@1' ramdisk subimage<br>
> Description: obmc-phosphor-initramfs<br>
> Type: RAMDisk Image<br>
> Compression: lzma compressed<br>
> Data Start: 0x2022ad00<br>
> Data Size: 1592362 Bytes = 1.5 MiB<br>
> Architecture: ARM<br>
> OS: Linux<br>
> Load Address: unavailable<br>
> Entry Point: unavailable<br>
> Hash algo: sha1<br>
> Hash value: 9f6f2feb110e27e07f81bb60bb372b4083672f19<br>
> Verifying Hash Integrity ... sha1+ OK<br>
> ## Loading fdt from FIT Image at 20080000 ...<br>
> Using 'conf@1' configuration<br>
> Trying 'fdt@1' fdt subimage<br>
> Description: Flattened Device Tree blob<br>
> Type: Flat Device Tree<br>
> Compression: uncompressed<br>
> Data Start: 0x20224624<br>
> Data Size: 26139 Bytes = 25.5 KiB<br>
> Architecture: ARM<br>
> Hash algo: sha1<br>
> Hash value: 37864a4c4a608d5f4e370bbccf93ccbe3e77462d<br>
> Verifying Hash Integrity ... sha1+ OK<br>
> Booting using the fdt blob at 0x20224624<br>
> Loading Kernel Image ... OK<br>
> Loading Ramdisk to 47213000, end 47397c2a ... OK<br>
> Loading Device Tree to 47209000, end 4721261a ... OK<br>
> <br>
> Starting kernel ...<br>
> """<br>
> <br>
> With v2.2 I see:<br>
> """<br>
> U-Boot 2016.07 (Jun 25 2018 - 10:07:57 -0700)<br>
> <br>
> DRAM: 120 MiB<br>
> WARNING: Caches not enabled<br>
> Flash: 64 MiB<br>
> *** Warning - bad CRC, using default environment<br>
> <br>
> In: serial<br>
> Out: serial<br>
> Err: serial<br>
> Net: aspeednic#0<br>
> Error: aspeednic#0 address not set.<br>
> <br>
> Hit any key to stop autoboot: 0<br>
> libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND<br>
<br>
>From below it looks like u-boot finds the kernel in the FIT, but your ramdisk is "corrupt". The error above suggests something is missing from the FIT. Can you check the initrd/ramdisk node in your FIT to make sure it is present and uses all the correct options and paths with respect to the initrd you intended to package?<br>
<br>
Might also be helpful to provide the content of the .its file.<br>
<br>
> ## Loading kernel from FIT Image at 20080000 ...<br>
> Using 'conf@aspeed-bmc-quanta-q71l.dtb' configuration<br>
> Trying 'kernel@1' kernel subimage<br>
> Description: Linux kernel<br>
> Type: Kernel Image<br>
> Compression: uncompressed<br>
> Data Start: 0x20080124<br>
> Data Size: 1723192 Bytes = 1.6 MiB<br>
> Architecture: ARM<br>
> OS: Linux<br>
> Load Address: 0x40008000<br>
> Entry Point: 0x40008000<br>
> Hash algo: sha1<br>
> Hash value: 95ed76c9361d9f6f991a6a859a06eb7626af80df<br>
> Verifying Hash Integrity ... sha1+ OK<br>
> Wrong Ramdisk Image Format<br>
> Ramdisk image is corrupt or invalid<br>
> """<br>
> <br>
> I figured I'd reach out first as I'm sure this will be familiar to someone :D<br>
> <br>
> Patrick<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Regards,<div>Kun</div></div></div>