EC800Q-EU not starting properly

Please could somebody tell me if my module has an internal hardware fault…

Whilst diagnosing why (on a previously healthy module) I could not get a working “AT” interface on the main UART, I connected to the debug interface. On boot from DBG_TX @115200 I saw the following output.

[Quec][Flash]:Abnormal Erased block not found(i=78)

I’ve previously seen this module healthy.

Now I just see garbled output, with some of the initial boot ascii interspersed.

I’ve a feeling the hardware is cooked. Does that line confirm that suspiscion?

Thanks

Rob

Hi Rob,

Thank you for sharing the debug log.

Based on the log, the message:

[Quec][Flash]: Abnormal Erased block not found(i=78)

indicates a low-level issue related to the module’s internal flash memory during the boot process.

Combined with the garbled boot output and the inability to access the AT command interface, it appears that the module is entering a boot loop. This typically occurs when the bootloader or system image is unable to complete initialization due to a flash-related error.

There are two possible causes:

  1. Flash corruption (for example, after an interrupted firmware update or unexpected power loss).
  2. Internal flash hardware failure, especially if the module was previously operating normally and no firmware update was performed before the issue occurred.

As a first step, we recommend attempting to recover the module by entering forced download mode:

  • Pull the USB_BOOT pin low (connect it to GND) before powering on the module.
  • Connect the module to a PC and check whether it can be detected in download mode.
  • If it is detected successfully, try reflashing the firmware.

If the module cannot enter download mode, or the same flash error persists after reflashing, the module is likely experiencing an internal flash hardware failure and may need to be replaced.

To help us further confirm the root cause, could you also provide:

  • The module part number and firmware version (if known).
  • Whether any firmware upgrade (QFlash/QFirehose/DFOTA) was performed before this issue occurred.
  • Whether the issue is observed on a single module or multiple modules.

We will be happy to continue investigating once we have the above information.

have you tried to reflash the firmware?

Hi @robevo ,

Are you still facing the issue?

Thanks for checking in.
It was a failed module.

Hi @robevo

Thanks for the update, I will close this thread