Dear Andy, In message <mm1p123mb126008da9e9df7f8f08bb81eb2...@mm1p123mb1260.gbrp123.prod.outlook.com> you wrote: > > Is it just not possible for the zImages in RAM to be decoded as per the > uImages ?
You can decode only the information that is in there. uImage adds an extra 64 byte header with informnation I considered useful to have, like names, timestamp, checksum. > If I simply use mkimage to convert the image back as a uImage ( essentially > take off the first 64 bytes ? ) then iminfo will display the kernel info You confuse things here. mkimage _adds_ a 64 byte header to create the uImage file from zImage (or similar). iminfo displays this uImage header. Similar when using FIT images. > The uImage file is only 64 bytes smaller so hasn't fundamentally been > uncompressed but also offsetting the iminfo by the 64 bytes makes no odds > either Wrong, uImage has 64 bytes header _added_ - and all this has nothing to do with compression at all. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de panic: kernel trap (ignored) _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
