Closed doragasu closed 5 months ago
@doragasu Sorry to reply late. I have found the root cause, you should to change the XTAL to 26MHz (default is 40MHz) in the menuconfig for ESP32C2.
By the way, you can use esptool to check the chip version of your device: esptool.py -p /dev/ttyUSB0 chip_id
, the output like this:
esptool.py v4.7.0 Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... ESP32-C2 Chip is ESP32-C2 (revision v1.1) Features: WiFi, BLE Crystal is 26MHz MAC: 10:97:bd:f1:a2:7c Uploading stub... Running stub... Stub running... Warning: ESP32-C2 has no Chip ID. Reading MAC instead. MAC: 10:97:bd:f1:a2:7c Hard resetting via RTS pin...
@doragasu After changing the XTAL to 26MHz, the esp32c2 can sniffer, but the FCS error packet still can't be received, I'm debugging on this, will solve it ASAP.
Answers checklist.
IDF version.
v5.0
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32C2-12 Devkit
Power Supply used.
USB
What is the expected behavior?
When enabling RX promiscuous mode with WIFI_PROMIS_FILTER_MASK_FCSFAIL filter mask, FCS failed packets are also received.
What is the actual behavior?
FCS failed packets are never received.
Steps to reproduce.
Build and flash the following program on an ESP32 chip. It will receive FCS failed packets on channel 1 successfully. Then build and flash the same program on a ESP32-C2 chip. It will not receive FCS failed packets.
Debug Logs.
On the ESP32 chip you get these and the FCS failed frame messages: