AnsweredAssumed Answered

SDK2.0: 'fdt: not creating '/sys/firmware/fdt': CRC check failed'

Question asked by chris warth on Jan 25, 2017
Latest reply on Jan 30, 2017 by Pavel Chubakov

Why do I always see this message during boot?

[    3.666500] fdt: not creating '/sys/firmware/fdt': CRC check failed

 

I see the same error on other boot logs posted on this forum, e.g. SDK 2.0 inittab entries not found booting from /dev/mmcblk0p2 

 

This particular log came from booting the pre-built .itb image from SDK2.0_LS1046ABSP_V0.4 from an sdcard,

 

kernel_load=0xa0000000
bootm ${kernel_load}:kernel@1 - ${kernel_load}:fdt@1

 

With a little wider context, it looks like this,

[ 3.647927] fsl_generic: FSL DPAA Generic Ethernet driver
[ 3.653528] rtc-pcf2127 1-0051: pcf2127_get_datetime: read error
[ 3.659533] rtc-pcf2127 1-0051: hctosys: unable to read the hardware clock
[ 3.666500] fdt: not creating '/sys/firmware/fdt': CRC check failed
[ 3.731190] VFS: Mounted root (ext2 filesystem) on device 179:1.
[ 3.738413] devtmpfs: mounted
[ 3.741553] Freeing unused kernel memory: 476K (ffff800000b3a000 - ffff800000bb1000)
[ 3.749307] Freeing alternatives memory: 48K (ffff800000bb1000 - ffff800000bbd000)

 

Does this message indicate an error?  Why would a prebuild image from NXP have a bad CRC on the flattened device tree?

Outcomes