LoPy4 RED LED after OTA method B firmware flash (meaning?)

  • Hello all:

    I am using a LoPy4 with firmware version 1.20.0.rc13.

    I am updating the firmware version from 1.20.0.rc13 to 1.20.2.rc6, via FileZilla (FTP) using the method B described here: https://docs.pycom.io/updatefirmware/ota/

    However, this is what happens:

    1. Upon sucessful transfer of appimg.bin to the /flash/sys/ directory, I then reset the LoPy4.
    2. When the LoPy4 boots again, it shows a RED LED for 2 or 3 seconds, and then moves to the standard blue heartbeat.
    3. I can then no longer access the LoPy4 via the UART0 pins, and have to performe a safe boot to then perform a full flash erase via pycom-fwtool-cli and then manually flash the firmware via the CLI.
    4. When the firmware (v1.20.2.rc6) is manually flashed, the LoPy no longer exhibits the RED LED prior to the standard heartbeat and all is well again.

    What happens:

    1. Firmware flashing via OTA method B results in what I presume is a corrupted flash, and the LoPy4 no longer communicates via serial.
    2. Additionally, the LoPy4 exhibits a RED LED for 2 or 3 seconds after boot when in this state.

    What should happen:

    1. After flashing the firmware via OTA method B and resetting, the LoPy4 should fall back into the standard hearbeat with no prior LED color. And should be able to communicate via REPL on UART0.

    Any ideas, guys? What does the RED LED mean?

    Thank you in advance,


  • @Fatoumata-Thiam Hello. I no longer kept looking into the issue. Whenever that happened, I just went into safeboot and then flashed the firmware again using the CLI tool from Pycom.

    Here's a github thread with some more advice that was given to me: https://github.com/pycom/pycom-micropython-sigfox/issues/496

    Maybe it helps you.



  • Hello, did you finally solve this issue? I am having the same problem.

Log in to reply

Pycom on Twitter