|
2 | 2 |
|
3 | 3 | {IDF_TARGET_STRAP_BOOT_2_GPIO:default="GPIO8", esp32="GPIO2", esp32s2="GPIO46", esp32s3="GPIO46", esp32p4="GPIO36", esp32c5="GPIO27"} |
4 | 4 |
|
5 | | -{IDF_TARGET_BOOTLOADER_OFFSET:default="0", esp32="1000", esp32s2="1000", esp32p4="2000"} |
| 5 | +{IDF_TARGET_BOOTLOADER_OFFSET:default="0x0", esp32="0x1000", esp32s2="0x1000", esp32p4="0x2000", esp32c5="0x2000"} |
6 | 6 |
|
7 | 7 | .. _boot-mode: |
8 | 8 |
|
@@ -224,7 +224,7 @@ Depending on the kind of hardware you have, it may also be possible to manually |
224 | 224 |
|
225 | 225 | **chksum:** |
226 | 226 |
|
227 | | - If value of “chksum” == value of “csum”, it means flash has been read correctly during booting. |
| 227 | + If value of "chksum" == value of "csum", it means flash has been read correctly during booting. |
228 | 228 |
|
229 | 229 | The rest of boot messages are used internally by Espressif. |
230 | 230 |
|
@@ -290,15 +290,23 @@ Depending on the kind of hardware you have, it may also be possible to manually |
290 | 290 | Early Flash Read Error |
291 | 291 | """""""""""""""""""""" |
292 | 292 |
|
293 | | - :: |
| 293 | + .. only:: esp8266 |
| 294 | + |
| 295 | + :: |
| 296 | + |
| 297 | + flash read err, 0 |
| 298 | + |
| 299 | + .. only:: not esp8266 |
| 300 | + |
| 301 | + :: |
294 | 302 |
|
295 | | - flash read err, {IDF_TARGET_BOOTLOADER_OFFSET} |
| 303 | + Invalid header <value at {IDF_TARGET_BOOTLOADER_OFFSET}> |
296 | 304 |
|
297 | | - This fatal error indicates that the bootloader tried to read the software bootloader header at address 0x{IDF_TARGET_BOOTLOADER_OFFSET} but failed to read valid data. Possible reasons for this include: |
| 305 | + This fatal error indicates that the bootloader tried to read the software bootloader header at address {IDF_TARGET_BOOTLOADER_OFFSET} but failed to read valid data. Possible reasons for this include: |
298 | 306 |
|
299 | 307 | .. list:: |
300 | 308 |
|
301 | | - - There isn't actually a bootloader at offset 0x{IDF_TARGET_BOOTLOADER_OFFSET} (maybe the bootloader was flashed to the wrong offset by mistake, or the flash has been erased and no bootloader has been flashed yet.) |
| 309 | + - There isn't actually a bootloader at offset {IDF_TARGET_BOOTLOADER_OFFSET} (maybe the bootloader was flashed to the wrong offset by mistake, or the flash has been erased and no bootloader has been flashed yet.) |
302 | 310 | - Physical problem with the connection to the flash chip, or flash chip power. |
303 | 311 | - Flash encryption is enabled but the bootloader is plaintext. Alternatively, flash encryption is disabled but the bootloader is encrypted ciphertext. |
304 | 312 |
|
@@ -326,7 +334,7 @@ Depending on the kind of hardware you have, it may also be possible to manually |
326 | 334 | mode:DIO, clock div:1 |
327 | 335 |
|
328 | 336 |
|
329 | | - This is normal boot output based on a combination of eFuse values and information read from the bootloader header at flash offset 0x{IDF_TARGET_BOOTLOADER_OFFSET}: |
| 337 | + This is normal boot output based on a combination of eFuse values and information read from the bootloader header at flash offset {IDF_TARGET_BOOTLOADER_OFFSET}: |
330 | 338 |
|
331 | 339 | .. list:: |
332 | 340 |
|
|
0 commit comments