Based on kernel version 6.11
. Page generated on 2024-09-24 08:21 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 | .. SPDX-License-Identifier: GPL-2.0-only ================================== PLDM Firmware file format overview ================================== A PLDM firmware package is a binary file which contains a header that describes the contents of the firmware package. This includes an initial package header, one or more firmware records, and one or more components describing the actual flash contents to program. This diagram provides an overview of the file format:: overall file layout +----------------------+ | | | Package Header | | | +----------------------+ | | | Device Records | | | +----------------------+ | | | Component Info | | | +----------------------+ | | | Package Header CRC | | | +----------------------+ | | | Component Image 1 | | | +----------------------+ | | | Component Image 2 | | | +----------------------+ | | | ... | | | +----------------------+ | | | Component Image N | | | +----------------------+ Package Header ============== The package header begins with the UUID of the PLDM file format, and contains information about the version of the format that the file uses. It also includes the total header size, a release date, the size of the component bitmap, and an overall package version. The following diagram provides an overview of the package header:: header layout +-------------------------+ | PLDM UUID | +-------------------------+ | Format Revision | +-------------------------+ | Header Size | +-------------------------+ | Release Date | +-------------------------+ | Component Bitmap Length | +-------------------------+ | Package Version Info | +-------------------------+ Device Records ============== The device firmware records area starts with a count indicating the total number of records in the file, followed by each record. A single device record describes what device matches this record. All valid PLDM firmware files must contain at least one record, but optionally may contain more than one record if they support multiple devices. Each record will identify the device it supports via TLVs that describe the device, such as the PCI device and vendor information. It will also indicate which set of components that are used by this device. It is possible that only subset of provided components will be used by a given record. A record may also optionally contain device-specific package data that will be used by the device firmware during the update process. The following diagram provides an overview of the device record area:: area layout +---------------+ | | | Record Count | | | +---------------+ | | | Record 1 | | | +---------------+ | | | Record 2 | | | +---------------+ | | | ... | | | +---------------+ | | | Record N | | | +---------------+ record layout +-----------------------+ | Record Length | +-----------------------+ | Descriptor Count | +-----------------------+ | Option Flags | +-----------------------+ | Version Settings | +-----------------------+ | Package Data Length | +-----------------------+ | Applicable Components | +-----------------------+ | Version String | +-----------------------+ | Descriptor TLVs | +-----------------------+ | Package Data | +-----------------------+ Component Info ============== The component information area begins with a count of the number of components. Following this count is a description for each component. The component information points to the location in the file where the component data is stored, and includes version data used to identify the version of the component. The following diagram provides an overview of the component area:: area layout +-----------------+ | | | Component Count | | | +-----------------+ | | | Component 1 | | | +-----------------+ | | | Component 2 | | | +-----------------+ | | | ... | | | +-----------------+ | | | Component N | | | +-----------------+ component layout +------------------------+ | Classification | +------------------------+ | Component Identifier | +------------------------+ | Comparison Stamp | +------------------------+ | Component Options | +------------------------+ | Activation Method | +------------------------+ | Location Offset | +------------------------+ | Component Size | +------------------------+ | Component Version Info | +------------------------+ | Package Data | +------------------------+ Package Header CRC ================== Following the component information is a short 4-byte CRC calculated over the contents of all of the header information. Component Images ================ The component images follow the package header information in the PLDM firmware file. Each of these is simply a binary chunk with its start and size defined by the matching component structure in the component info area. |