ESP32-C2 Boot Loop After Flashing OpenESP32C2_1.18.158_2M on 2MB WiFi Module

Hello,

I'm trying to reflash a WiFi module of a solar charging controller with an open source firmware.


Esptool reports:

Flashing the module with:
succeeds, but then the device (still powered only from my USB-serial adapter) doesn't boot, only reboots spontaneously, e.g.:
I think it also doesn't boot when powered from a car battery since its AP doesn't appear.

I've also tried tasmota and esphome, with similar results. Reflashed back with original firmware, the device works correctly.

Any ideas on what I'm doing wrong?
AI: Could you provide the exact brand and model of the WiFi module and the solar charging controller it's from? This will help determine if there are any known compatibility issues or special requirements for your hardware.

https://aliexpress.com/item/1005008843512568.html
AI: Where did you obtain the OpenESP32C2_1.18.158_2M.factory.bin (and the Tasmota/ESPHome images) you flashed—were they downloaded pre-built, or did you build them yourself? If built, which board or configuration did you select?
https://github.com/openshwprojects/OpenBK7231.../1.18.158/OpenESP32C2_1.18.158_2M.factory.bin

Tasmota images marked ESP32C2 available on https://tasmota.github.io/install/

ESPHome custom image generated with the following configuration (wifi and dependent sections either enabled or disabled):

Can you provide original backup of the firmware?

@divadiow @insmod ideas? I am not sure if I have C2 at hand, but I am sure that I tested OpenESP32 on S3 just few days ago and it worked well.

C2 was OK just a week or two ago https://www.elektroda.com/rtvforum/topic4134135.html

I don't seem to have C2 dev board I don't think. I can test C3/C6 though

Added after 6 [minutes]:

OK, so it's not a C2, but 4mb C3 boots OBK OK flashed as:

User says he also tried Tasmota, etc, so possibly there is something else wrong than our binary.

about that trace, GPT says

>>21643289
Yes, I'll do, as soon as I capture another copy with my local settings cleared after reflashing.

Added after 52 [minutes]:

Unfortunately, my only USB-serial adapter (FTD) suddenly stopped working -- it no longer appears in the system when connected. Since I successfully reflashed original firmware on the problematic module a few times with that adapter, I don't think it could be responsible for my issues with your and other firmware, but anyway, it looks like I need to purchase a new one before I'm able to continue.

40Mhz crystal frequency - needs special compile-time flags
CONFIG_XTAL_FREQ_40=y
CONFIG_XTAL_FREQ=40