將韌體中的img檔案提取后進行了修改，再次打包后binwalk發現少了一個uImage header，原始img檔案中的第二uImage header的作用是什么？應該如何生成
修改后img
0 0x0 uImage header, header size: 64 bytes, header CRC: 0xCF874149, created: 2019-04-16 17:01:54, image size: 159744 bytes, Data Address: 0x18A0000, Entry Point: 0x1970000, data CRC: 0xD71C59F4, OS: Linux, CPU: ARM, image type: Standalone Program, compression type: none, image name: "custom"
64 0x40 Squashfs filesystem, little endian, version 4.0, compression:xz, size: 157085 bytes, 10 inodes, blocksize: 1048576 bytes, created: 2019-04-16 17:01:54
修改前img
0 0x0 uImage header, header size: 64 bytes, header CRC: 0x60F68522, created: 2019-03-25 10:33:43, image size: 75960 bytes, Data Address: 0x18A0000, Entry Point: 0x1970000, data CRC: 0x1A0E8440, OS: Linux, CPU: ARM, image type: Standalone Program, compression type: none, image name: "custom"
64 0x40 Squashfs filesystem, little endian, version 4.0, compression:xz, size: 70161 bytes, 6 inodes, blocksize: 1048576 bytes, created: 2019-03-25 10:33:43
73816 0x12058 uImage header, header size: 64 bytes, header CRC: 0x597F1585, created: 2019-03-25 10:33:43, image size: 73728 bytes, Data Address: 0x18A0000, Entry Point: 0x1970000, data CRC: 0xB70DE304, OS: Linux, CPU: ARM, image type: Standalone Program, compression type: none, image name: "custom"
轉載請註明出處，本文鏈接：https://www.uj5u.com/qita/134281.html
標籤：驅動開發/核心開發
上一篇：太陽能跨季節儲熱資料采集建模
下一篇：串口通訊延遲