I (12340306) slave_ctrl: ESP32 station is not connected with AP, can't get AP config

[matlam1989]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

I use two ARM Crotex-m4 MCU main control boards and ESP32C3 as the WiFi communication module.The main control board operates in AP mode, while the slave board operates in STA mode.When I debugged the main control board, the slave connected and sent a large number of communication messages, but eventually reported a communication interruption fault and disconnected the WiFi connection.Let the host main control normally again, clear the slave fault, and connect to the AP again, but it will never connect again.

Actual behavior (suspected bug)

When I reset the slave esp32c3 module and reconnected to the main control AP for communication, the communication became normal

Error logs or terminal output

I (12340306) slave_ctrl: ESP32 station is not connected with AP, can't get AP config
I (12340337) slave_ctrl: Get station mac address
I (12340338) slave_ctrl: mac [60:55:f9:7d:9b:30]

Steps to reproduce the behavior

1.The ESP32 AP module on the main control end disconnects SPI communication, and the slave continues to send messages for about 2 minutes after connecting.
2.The ESP32 AP module on the main control was connected to SPI communication, and the slave machine was connected to AP communication again. Despite repeated connections, it did not connect

Project release version

master

System architecture

other (details in Additional context)

Operating system

Linux

Operating system version

RTThread RTOS

Shell

other (details in Additional context)

Additional context

I used RTThread RTOS and ported the ESP hosted FG driver.

[mantriyogesh]

How is it different from #517?