Skip to main content

Firmware Flashing

Build and Download from Source​

For now, build the required program from source first. For the framework and board-level configuration, see Working with Arduino and Working with ESP-IDF. For first-time use, you can choose example 01 or 03 to confirm the expected behavior of the LED or e-paper.

  • Arduino IDE: Select the board and port, verify first, then upload.
  • ESP-IDF: After completing the board-level configuration in the selected example directory, run idf.py build and idf.py -p COM3 flash monitor, replacing the port with the actual value.

Prebuilt Firmware​

For the public firmware entry, see ESP32-S3-LR1121-ePaper-2.9 Example Programs and Firmware. Before use, check the hardware version, HF/LF RF version, framework version, source commit, and flashing manifest declared in the firmware package.

Image TypeAddress and File Selection Basis
Segmented imagesThe flasher_args.json generated from the same build or the firmware package manifest
Merged imageThe merged base address explicitly recorded in the firmware package
Arduino exported imageThe upload parameters of the corresponding build and the other required images; do not treat a single application file as complete firmware

The ESP32-S3-LR1121-ePaper-2.9-HF.bin and ESP32-S3-LR1121-ePaper-2.9-LF.bin retained in the resources have not yet established a correspondence with source commits, flashing offsets, and measured records. Do not infer the flash address from the file name, and do not treat them as build artifacts of the current 13 examples.

Manually Entering Download Mode​

Connect to the computer with a Type-C cable that supports data transfer. If automatic download fails:

  1. Hold down BOOT.
  2. Press and release RESET.
  3. Release BOOT, and confirm the newly appeared port in Device Manager.
  4. Select that port and download the program again.

After downloading, release BOOT and press RESET to run the program. If the device still outputs a waiting-for-download message, confirm that BOOT has been released.

Post-Flashing Checks​

  1. Open the serial monitor of the corresponding framework.
  2. Check the logs, screen, and peripheral behavior according to the selected example.
  3. Before running LoRaWAN, check the network configuration and local credentials.

Do not casually erase the entire Flash to troubleshoot ordinary connection issues. Erasing NVS will lose the LoRaWAN nonce, session, and frame counter state; ABP in particular needs to be handled in sync with the server. For related instructions, see Session and Frame Counter Issues.