Hi NXP,
Currently setting ap+station mode on NXP wifi module + rsb3730, the following is my topology:
ap1 (ssid: 1234) -------rsb3730(station + ap (ssid:nxp_ap , ip:192.168.8.1)) --------client
The following issues have been discovered so far:
1. When the station cannot connect to ap1, the client connected to nxp_ap, will ping loss when pinging device (ping 192.168.8.1)
2. When the station cannot connect to ap1,sometimes the ssid of nxp_ap cannot be scanned for a short time, but it will be scanned after about 5 seconds.
Attached is the captured device log.
Thank you~
Austin
Dear @austinlee12345 ,
Let me share a document for you.
The document shows how to setup softAP based on i.MX8MM-EVK + 88W8997, BSP version is 5.4.70 , and I also tested it on bsp version 6.6.3.
Thanks!
Regards,
weidong
Dear Weidong,
Yes, I have successfully set mlan0 and uap0 to ap+station. The problem I am currently encountering is: if mlan0 has been unable to connect to ap1 (ssid: 1234) , then uap0 will sometimes hang directly. If mlan0 has successfully connected to ap1 (ssid: 1234) , then everything is fine.
Attached are the steps we have taken to reproduce the problem so far.
Thank you~
BR,
Austin
Dear @austinlee12345 ,
Attachment is for your reference.
The doc is very similar to your application.
Try it, please!
Thanks!
Regards,
weidong
Dear Weidong,
Yes, I have set ap+sta according to the document you provided. This issue will not happen every time. There is a chance that the SSID of uap0 cannot be scanned or uap0 will stop working.
Thank you~
Regards,
Austin
Dear @austinlee12345 ,
I tested it for several times, It is very strange that I have not reproduced the issue you mentioned above.
-- OTA logs
Could you please provide OTA logs for me when the error occurred ?
Thanks!
Regards,
weidong
Dear Weidong,
The attachment is the log I captured using dmesg in the system.
The problem of uap0 stopping may occur after repeating the steps 20~30 times.
When sets the wrong psk in wpa_supplicant config and let mlan0 cannot asscoiate to the ap, I will wait for about 5~10 minutes to observe the status of uap0.
Thank you~
Regards,
Austin
Dear @austinlee12345
>.When sets the wrong psk in wpa_supplicant config and let mlan0 cannot asscoiate to the ap.
--wrong psk in wpa_supplicant is the only condition to cause the issue, right?
-- If password is correct, no issues, right?
[Additional information I need]
1. systemctl status connman.service
run the command, please! then copy logs to me.
2. If psk is not correct, connection will fail, wpa_supplicant should scan AP continuously, check it, then tell me, please!
Thanks!
Regards,
weidong
Dear Weidong,
>.When sets the wrong psk in wpa_supplicant config and let mlan0 cannot asscoiate to the ap.
--wrong psk in wpa_supplicant is the only condition to cause the issue, right? As long as mlan0 cannot connect to the ap, problems may occur.
-- If password is correct, no issues, right? YES
[Additional information I need]
1. systemctl status connman.service
run the command, please! then copy logs to me. --->The attachment is the captured log
2. If psk is not correct, connection will fail, wpa_supplicant should scan AP continuously, check it, then tell me, please! --->yes,wpa_supplicant should scan AP continuously
Thank you
Regards,
Austin
Dear @austinlee12345 ,
In your system, connmand ( connman.service) is also running:
====================================================
* connman.service - Connection service
Loaded: loaded (/lib/systemd/system/connman.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2024-04-18 05:33:26 UTC; 24h ago
Main PID: 641 (connmand)
Tasks: 1
Memory: 4.9M
CGroup: /system.slice/connman.service
`-641 /usr/sbin/connmand -n
====================================================
So when connection failed, scan will be continued.
Do you really need to use connmand Daemon process?
Regards,
weidong
Dear @austinlee12345 ,
Please create the main.conf file in /etc/connman/, if there is no connman directory, create it, please!
[General]
NetworkInterfaceBlacklist=wfd0,uap0,p2p0,muap0,mwfd0,p2p1
Then restart your board. and continue your settings and operations.
Regards,
weidong