ESP32-C6 is not processing FTM_Responder in Wi-Fi scans. (IDFGH-16897) #17962
Description
Answers checklist.
- I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
- I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
- I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
v6.1-dev-931-g683ddf8a6e
Espressif SoC revision.
ESP32-C6
Operating System used.
macOS
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
Waveshare ESP32-C6-Touch-AMOLED-1.32
Power Supply used.
USB
What is the expected behavior?
Utilizing the FTM example, when scanning SSIDs advertising the FTM_Responder should be recognized.
SSIDs are being marked with the FTM Responder.
Below is output from a ESP32-S3
I (653) main_task: Returned from app_main()
ftm> scan
I (5533) ftm_station: sta start to scan
...
I (8033) ftm_station: [arista_test_2g][rssi=-69][FTM Responder]
What is the actual behavior?
SSIDs advertising the FTM_Responder are not marked in the scan. However, you can see that the C6 is functioning as an FTM_Initiator.
Below is the same FTM example, but with an ESP32-C6
ftm> scan
I (2912) ftm_station: sta start to scan
...
I (5661) ftm_station: [arista_test_2g][rssi=-80]
...
ftm> ftm -I -s arista_test_2g -c8 -p3
W (110781) wifi:Haven't to connect to a suitable AP now!
I (110781) ftm_station: Requesting FTM session with Frm Count - 8, Burst Period - 300mSec (0: No Preference)
W (110781) wifi:Starting FTM session with 30:86:2d:00:00:00
W (110781) wifi:Mode: ASAP, Bursts: 1, FTM's per burst: 8, Burst Period: 300mSec, Burst Duration: 32000uSec
W (110791) wifi:FTM session ends with 6 valid readings out of 6 readings received, Avg raw RTT: 102.962 nSec, Avg RSSI: -66
I (110791) ftm_station: Estimated RTT - 102 nSec, Estimated Distance - 15.30 meters
Steps to reproduce.
- Load FTM example app on ESP32-C6
- Run scan functionality
- Any SSID advertising the FTM_Responder will not show as such.
- initiating FTM to the affected SSID will work assuming you are using the correct settings.
...
Debug Logs.
no crash, AP just is not processing beacon/probe response for FTM data.
Diagnostic report archive.
idf-diag-bf423226-1d12-45ee-9b12-8edfdc80cdaf.zip
More Information.
No response