0.4 firmware not working

[goby66666]

firmware 0.4 does not wok on my ESP 32 S3 board. After successful flashing my board keeps restartating
ESP_ERROR_CHECK failed: esp_err_t 0xffffffff (ESP_FAIL) at 0x4200a1d4
file: "./main/csi_collector.c" line 219
func: csi_collector_init
expression: esp_wifi_set_csi_config(&csi_config)

abort() was called at PC 0x4037e373 on core 0

[ruvnet]

Hardware Compatibility Note

Thanks for the detailed write-up. Your boards are original ESP32 (ESP32-D0WD and D0WDQ6-V3), not ESP32-S3. Our firmware currently targets ESP32-S3 only — the sdkconfig is set to CONFIG_IDF_TARGET="esp32s3" (Xtensa S3 ISA).

Why original ESP32 doesn't work out of the box

Difference	ESP32 (original)	ESP32-S3
CSI subcarriers	~52 (HT20)	~114 (HT20)
STBC HT-LTF2	Not supported	Supported
CSI API	esp_wifi_set_csi()	Same, but more fields
Our firmware	Not compiled for it	Target platform

What you can do

Your approach of rewriting app_main.c with the ADR-018 binary frame format (magic 0xC5110001) is exactly right — the Rust aggregator/parser doesn't care which ESP32 variant sends the frames, as long as the binary format matches. Your custom firmware is a valid workaround.

If you'd like to contribute an original-ESP32 build target, we'd welcome a PR. The main work would be:

1. Add sdkconfig.defaults.esp32 with CONFIG_IDF_TARGET="esp32"
2. Adjust subcarrier count assumptions in the frame serialization
3. Skip STBC HT-LTF2 config (not available on original ESP32)

See ADR-057 for the hardware support matrix. We've documented this as "unsupported but interoperable via ADR-018 frame format."

[goby66666]

Hello, thank you for your reply. I'm currently very confused. The development board I purchased is the ESP32-S3-DEevkicC-1 N16R8 based on the Espressif original ESP32-S3-WROOM-1U module, not the original version of ESP32 you mentioned. Here are the relevant pictures for your reference.

[goby66666]

The board uses the ESP32-S3-WROOM-1U module. I will try the new v0.4.1 firmware now, as the previous ESP_FAIL at csi_collector.c:219 matches the 'CSI not enabled' bug you just fixed in #241.

[ruvnet]

Thanks for the photos — that's definitely an ESP32-S3-DevKitC-1 (WROOM-1U module). My earlier reply about original ESP32 doesn't apply to your board, apologies for the confusion.

The error you're hitting (ESP_FAIL at csi_collector.c:219) was a known bug — CSI wasn't enabled in the sdkconfig menuconfig. This was fixed in v0.4.1 (PR #241).

Please try flashing the v0.4.1 firmware and let us know if the crash is resolved.

[ruvnet]

Fixed in v0.4.1 (PR #241). User confirmed they'll try the new firmware. Closing — reopen if the issue persists after flashing v0.4.1.