EasyManuals Logo

Espressif Systems ESP User Manual

Default Icon
191 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #185 background imageLoading...
Page #185 background image
Chapter 5. Hardware related
5.6 Production Test
5.6.1 Why can some modules download rmware normally when using DIO/DOUT, but
encounter program abnormality when using QOUT/QIO?
Firstly, please check the modes supported by 󰝙ash in the module and whether the module routing meets the
requirements of modes.
Secondly, please check the QE bit of the status register of 󰝙ash, which determines whether the 󰝙ash supports
the QUAD mode or not.
Di󰝗erent ESP chips/modules use 󰝙ashes from di󰝗erent manufacturers. Some 󰝙ashes have QE disabled by
default. Thus, it is necessary to check whether the 󰝙ash supports Quad mode through actual testing.
When ROM boots a second stage bootloader, the secondary read will fail if the con󰝘guration parameters are
read in the QIO mode because the QE bit is disabled.
It is recommended to program 󰝘rmware in the DIO mode and to con󰝘gure the QIO mode in menuconfig.
The con󰝘guration enables the QE bit in the second stage bootloader and then boots the app bin to use the
QUAD mode.
5.6.2 How to get the production test tool?
CHIP: ESP32 | ESP8266
Please click production test tool to download.
5.6.3 When I use the esptool.py burn_custom_mac command to write the
user-dened MAC address, why is the MAC address read by the esptool.py
read_mac command still factory default?
The esptool.py read_mac command can only read the MAC address written in eFuse BLOCK0 by
default, but the user-de󰝘ned MAC address written with the esptool.py burn_custom_mac command
is in eFuse BLOCK3. You may use the espefuse.py get_custom_mac command to check the MAC
address written to eFuse BLOCK3.
For more information, please refer to esptool documentation.
5.6.4 When downloading bin les to ESP32-WROVER-E (16 MB ash) using Flash
Download Tool, multiple separate bin les can be downloaded successfully, but
downloading the combined rmware (12 MB) failed. Why?
Since the combined 󰝘rmware is mostly 0xFFwith relatively high compression rate, the amount of
data after decompression would be relatively large for the same length of compressed data, resulting in
a timeout error (default 7 seconds) after a long download time. To solve this issue, in Flash Download
Tool, go to configure > esp32 > spi_download, and disable the compression con󰝘guration
option as follows:
compress = False
no_compress = True
Espressif Systems 168
Submit Document Feedback
Release master

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Espressif Systems ESP and is the answer not in the manual?

Espressif Systems ESP Specifications

General IconGeneral
BrandEspressif Systems
ModelESP
CategoryMotherboard
LanguageEnglish