Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP32-C6 "wifi:FTM Initiator mode not supported!" (IDFGH-14436) #15216

Open
3 tasks done
thielemans opened this issue Jan 15, 2025 · 0 comments
Open
3 tasks done

ESP32-C6 "wifi:FTM Initiator mode not supported!" (IDFGH-14436) #15216

thielemans opened this issue Jan 15, 2025 · 0 comments
Assignees
Labels
Status: Opened Issue is new Type: Bug bugs in IDF

Comments

@thielemans
Copy link

thielemans commented Jan 15, 2025

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.

v5.4

Espressif SoC revision.

ESP32-C6 (QFN40) (revision v0.1)

Operating System used.

Windows

How did you build your project?

Command line with idf.py

If you are using Windows, please specify command line type.

PowerShell

Development Kit.

ESP32-C6-DevKitC-1 V1.2

Power Supply used.

USB

What is the expected behavior?

WiFi FTM example should run on ESP32-C6 as it is listed as supported in the example and C6 datasheet.

What is the actual behavior?

WiFi responds that FTM Initiator mode is not supported although documentation indicates this should work.

I (13831) ftm_station: Requesting FTM session with Frm Count - 32, Burst Period - 200mSec (0: No Preference)
E (13831) wifi:FTM Initiator mode not supported!
E (13841) ftm_station: Failed to start FTM session

Steps to reproduce.

  1. Verify FTM Initiator support and FTM Responder support is enabled.
  2. Optionally enable FTM report logging (tested with enabled and disabled).
  3. WiFi FTM example built for ESP32-C6 using idf.py or VScode (tested with both environments).
  4. Flashed on two separate ESP32-C6 devices
  5. Device A put in softAP mode
  6. Optionally connect device B in STA mode (tested with and without this step)
  7. Device B: "ftm -I -s

Debug Logs.

ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x1 (POWERON),boot:0x1c (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x40875720,len:0x16b8
load:0x4086c110,len:0xe84
load:0x4086e610,len:0x304c
entry 0x4086c11a
I (23) boot: ESP-IDF v5.4 2nd stage bootloader
I (24) boot: compile time Jan 15 2025 16:53:00
I (24) boot: chip revision: v0.1
I (24) boot: efuse block revision: v0.2
I (27) boot.esp32c6: SPI Speed      : 80MHz
I (31) boot.esp32c6: SPI Mode       : DIO
I (35) boot.esp32c6: SPI Flash Size : 2MB
I (38) boot: Enabling RNG early entropy source...
I (43) boot: Partition Table:
I (45) boot: ## Label            Usage          Type ST Offset   Length
I (52) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (58) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (65) boot:  2 factory          factory app      00 00 00010000 00100000
I (71) boot: End of partition table
I (75) esp_image: segment 0: paddr=00010020 vaddr=420a0020 size=1e298h (123544)                                                                                                              map
I (105) esp_image: segment 1: paddr=0002e2c0 vaddr=40800000 size=01d58h (  7512)                                                                                                              load
I (107) esp_image: segment 2: paddr=00030020 vaddr=42000020 size=9aa38h (633400)                                                                                                              map
I (226) esp_image: segment 3: paddr=000caa60 vaddr=40801d58 size=18998h (100760)                                                                                                              load
I (247) esp_image: segment 4: paddr=000e3400 vaddr=4081a6f0 size=03c00h ( 15360)                                                                                                              load
I (257) boot: Loaded app from partition at offset 0x10000
I (258) boot: Disabling RNG early entropy source...
I (268) cpu_start: Unicore app
I (276) cpu_start: Pro cpu start user code
I (276) cpu_start: cpu freq: 160000000 Hz
I (277) app_init: Application information:
I (277) app_init: Project name:     ftm
I (280) app_init: App version:      v5.4
I (284) app_init: Compile time:     Jan 15 2025 16:52:39
I (289) app_init: ELF file SHA256:  285e1d942...
I (293) app_init: ESP-IDF:          v5.4
I (297) efuse_init: Min chip rev:     v0.0
I (300) efuse_init: Max chip rev:     v0.99
I (304) efuse_init: Chip rev:         v0.1
I (308) heap_init: Initializing. RAM available for dynamic allocation:
I (314) heap_init: At 40823770 len 00058EA0 (355 KiB): RAM
I (320) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (325) heap_init: At 50000000 len 00003FE8 (15 KiB): RTCRAM
I (331) spi_flash: detected chip: generic
I (334) spi_flash: flash io: dio
W (337) spi_flash: Detected size(8192k) larger than the size in the binary image                                                                                                              header(2048k). Using the size in the binary image header.
I (349) sleep_gpio: Configure to isolate all GPIO pins in sleep state
I (355) sleep_gpio: Enable automatic switching of GPIO sleep configuration
I (362) coexist: coex firmware version: 49a8cdc
I (380) coexist: coexist rom version 5b8dcfa
I (381) main_task: Started on CPU0
I (381) main_task: Calling app_main()
I (381) pp: pp rom version: 5b8dcfa
I (381) net80211: net80211 rom version: 5b8dcfa
I (391) wifi_init: rx ba win: 6
I (391) wifi_init: accept mbox: 6
I (391) wifi_init: tcpip mbox: 32
I (391) wifi_init: udp mbox: 6
I (391) wifi_init: tcp mbox: 6
I (401) wifi_init: tcp tx win: 5760
I (401) wifi_init: tcp rx win: 5760
I (401) wifi_init: tcp mss: 1440
I (411) wifi_init: WiFi IRAM OP enabled
I (411) wifi_init: WiFi RX IRAM OP enabled
I (411) wifi_init: WiFi SLP IRAM OP enabled
I (421) phy_init: phy_version 320,348a293,Sep  3 2024,16:33:12
W (491) phy_init: saving new calibration data because of checksum failure, mode(                                                                                                             0)
W (501) wifi:ACK_TAB0   :0x   90a0b, QAM16:0x9 (24Mbps), QPSK:0xa (12Mbps), BPSK                                                                                                             :0xb (6Mbps)
W (501) wifi:CTS_TAB0   :0x   90a0b, QAM16:0x9 (24Mbps), QPSK:0xa (12Mbps), BPSK                                                                                                             :0xb (6Mbps)
W (511) wifi:(agc)0x600a7128:0xd20439f0, min.avgNF:0xce->0xd2(dB), RCalCount:0x4                                                                                                             3, min.RRssi:0x9f0(-97.00)
W (521) wifi:(TB)WDEV_PWR_TB_MCS0:19
W (521) wifi:(TB)WDEV_PWR_TB_MCS1:19
W (521) wifi:(TB)WDEV_PWR_TB_MCS2:19
W (531) wifi:(TB)WDEV_PWR_TB_MCS3:19
W (531) wifi:(TB)WDEV_PWR_TB_MCS4:19
W (531) wifi:(TB)WDEV_PWR_TB_MCS5:19
W (541) wifi:(TB)WDEV_PWR_TB_MCS6:18
W (541) wifi:(TB)WDEV_PWR_TB_MCS7:18
W (541) wifi:(TB)WDEV_PWR_TB_MCS8:17
W (551) wifi:(TB)WDEV_PWR_TB_MCS9:15
W (551) wifi:(TB)WDEV_PWR_TB_MCS10:15
W (551) wifi:(TB)WDEV_PWR_TB_MCS11:15

 ===============================================================
 |                  Steps to test FTM Initiator                 |
 |                                                              |
 |  1. Use 'scan' command to scan AP's. In results, check AP's  |
 |     with tag '[FTM Responder]' for supported AP's            |
 |  2. Optionally connect to the AP with 'sta <SSID> <password>'|
 |  3. Initiate FTM with 'ftm -I -s <SSID>'                     |
 |______________________________________________________________|
 |                  Steps to test FTM Responder                 |
 |                                                              |
 |  1. Start SoftAP with command 'ap <SSID> <password>'         |
 |  2. Optionally add '-c <ch>' to set channel, '-b 40' for 40M |
 |  3. Use 'help' for detailed information for all parameters   |
 ================================================================


Type 'help' to get the list of commands.
Use UP/DOWN arrows to navigate through command history.
Press TAB when typing command name to auto-complete.
I (691) main_task: Returned from app_main()
ftm> scan
I (2771) ftm_station: sta start to scan
I (5271) ftm_station: [test][rssi=-33][FTM Responder]
I (5291) ftm_station: sta scan done
ftm> ftm -I -s test
I (13831) ftm_station: Requesting FTM session with Frm Count - 32, Burst Period - 200mSec (0: No Preference)
E (13831) wifi:FTM Initiator mode not supported!
E (13841) ftm_station: Failed to start FTM session
ftm> wifi:FTM Initiator mode not supported!wifi:FTM Initiator mode not supported!I (13831) ftm_station: Requesting FTM sessio                                                                ftm> wifi:FTM Initiator mode not supported!wifi:FTM Initiator mode not supported!I (13831) ftm_station: Requesting FTM sessio                                                                n with Frm Count - 32, Burst Period - 200mSec (0: No Preference)

More Information.

No response

@thielemans thielemans added the Type: Bug bugs in IDF label Jan 15, 2025
@github-actions github-actions bot changed the title ESP32-C6 "wifi:FTM Initiator mode not supported!" ESP32-C6 "wifi:FTM Initiator mode not supported!" (IDFGH-14436) Jan 15, 2025
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new Type: Bug bugs in IDF
Projects
None yet
Development

No branches or pull requests

4 participants