Some FRM file aren't exactly the way the script expects.
Version information for pluto-169f-peakrdl-merged.frm:
gunzip: (stdin): unexpected end of file
cpio: premature end of archive
The difference found is that the hex data in object ramdisk@1 is in a different format. The script expects this:
ramdisk@1 {
description = "Ramdisk";
data = [1f 8b 08 00 00 00 00 00 02 03 cc 9b 0f 9c 55 65 99 c7 df 91
but some files are like this instead:
ramdisk@1 {
description = "Ramdisk";
data = <0x1f8b0800 0x00 0x203cc9b 0xd9815e5 0x75c7df95 0x4f111191
If we just change the square brackets to angle brackets, that almost works. But we also have to make sure each word is interpreted as four bytes. By default, xxd doesn't do that.
Some FRM file aren't exactly the way the script expects.
The difference found is that the hex data in object ramdisk@1 is in a different format. The script expects this:
but some files are like this instead:
If we just change the square brackets to angle brackets, that almost works. But we also have to make sure each word is interpreted as four bytes. By default, xxd doesn't do that.