Wi-Fi Easy Connect (DPP) – Errors despite following NXP documentation
Hello,
I am trying to configure Wi-Fi Easy Connect (DPP) by following the NXP documentation below:
https://docs.nxp.com/bundle/RM00297/page/connectivity-features/topics/wi-fi_easy_connect_dpp.html
I followed all the steps as described (including the wpa_supplicant configuration), but I am still encountering errors during the process.
I have attached screenshots/photos of the errors I am seeing for reference.
Could you please help me understand:
What might be causing these errors?
If there are any additional configuration steps or common pitfalls not covered in the documentation?
Any guidance or suggestions would be appreciated.
Dear NXP Support Team,
We have followed the DPP (Wi-Fi Easy Connect) procedure as suggested in the ticket and are now able to achieve successful DPP authentication and configuration between the AP and STA.
Below is the current status and the issue we are facing:
Observations
DPP-AUTH-SUCCESS is received on both AP and STA
DPP-CONF-SENT and DPP-CONF-RECEIVED are successful
Network profile is added successfully (CTRL-EVENT-NETWORK-ADDED)
GAS query and DPP configuration exchange complete without errors
However, after configuration, the STA:
Does not associate with the AP
Remains in wpa_state=SCANNING
No CTRL-EVENT-CONNECTED is observed
Logs (Summary)
DPP authentication and configuration complete successfully
STA triggers scan (CTRL-EVENT-SCAN-STARTED / RESULTS)
No association attempt follows the scan
STA does not move beyond SCANNING state
Suspected Causes
We suspect this may be related to one of the following:
Channel / Band mismatch
DPP exchange happens on channel 2412 (2.4 GHz)
AP configuration or operating channel may not match the provisioned band
STA not triggering auto-connect after DPP
Possibly requires explicit set_network <id> disabled 0
Or select_network <id> after provisioning
Driver / firmware limitation
DPP completes but association is not triggered automatically
Request for Support
Could you please help clarify:
Expected behavior after DPP-CONF-SUCCESS
Should STA auto-associate, or is an explicit connect required?
Reference hostapd.conf and wpa_supplicant.conf
Specifically for i.MX platforms with DPP Connector mode
Any known limitations or patches required on (i.MX8MP class platforms) where:
DPP provisioning succeeds
But association does not occur
Whether any additional commands are required post-DPP to trigger association
We have attached the complete command sequence and logs for both AP and STA for reference.
Looking forward to your guidance.
Best regards,
Niranjan
