i.MX8MP – DPP Authentication & Configuration succeed, but STA never connects

[Niranjan123]

Hi Everyone,

I am testing Wi-Fi Easy Connect (DPP) between two boards:

• AP / Configurator: i.MX8MP + PCIE8997
• STA / Enrollee: i.MX8MP + PCIE8997
• hostapd / wpa_supplicant version: 2.10
• Firmware: nxp/pcieuart8997_combo_v4.bin

The goal is to provision the STA using DPP (QR-code based) and have it automatically connect to the AP.

---

Test Procedure (Working up to DPP Configuration)

AP (Configurator + AP)

contents of hostapd.conf

ctrl_interface=/var/run/hostapd
interface=uap0
driver=nl80211
# Regulatory domain (MANDATORY)
country_code=IN
ieee80211d=1
ieee80211h=1
hw_mode=g
channel=1
ssid=DPP_AP111
ignore_broadcast_ssid=0
ieee80211n=1
wpa=2
wpa_key_mgmt=DPP 
rsn_pairwise=CCMP
ieee80211w=2
auth_algs=1
wpa_pairwise=CCMP

hostapd -B /etc/hostapd.conf
hostapd_cli
dpp_configurator_add
dpp_configurator_get_key 1

STA (Enrollee)

Contents of wpa_supplicant.conf 
ctrl_interface=/var/run/wpa_supplicant
update_config=1
pmf=2
dpp_config_processing=2

wpa_supplicant -i mlan0 -c /etc/wpa_supplicant.conf -dd
wpa_cli
dpp_bootstrap_gen type=qrcode mac=cc:47:40:34:03:c7 chan=81/1
dpp_bootstrap_get_uri 1
dpp_listen 2412

AP (after scanning QR)

dpp_qr_code DPP:C:81/1;M:cc47403403c7;V:2;K:...;;
dpp_auth_init peer=1 conf=sta-dpp ssid=4450505f4150313131 configurator=1

---

Observed Logs on STA (Successful DPP Exchange)

DPP-AUTH-SUCCESS
DPP-CONF-RECEIVED
DPP-CONFOBJ-AKM dpp
DPP-CONFOBJ-SSID DPP_AP111
CTRL-EVENT-NETWORK-ADDED 0
DPP-NETWORK-ID 0

This confirms:

• DPP authentication succeeds
• Configuration object is received
• Network profile is created

---

Problem

After successful DPP configuration:

wpa_state=SCANNING

The STA never transitions to AUTHENTICATING / ASSOCIATING / COMPLETED
and does not connect to the AP.

---

Additional Observations

1. Wpa_Supplicant.conf

After Association wpa_supplicant.conf gets updated

ctrl_interface=/var/run/wpa_supplicant
update_config=1
pmf=2
dpp_config_processing=2
network={
  ssid="DPP_AP111"
  key_mgmt=DPP
  ieee80211w=2
  dpp_connector="eyJ0eXAiOiJkcHBDb24iLCJraWQiOiJkZFVCYndxcmI0NWswRTZULXBMeTA2LTBiSHFEcjh5VF9kMVE0ZXNzTm84IiwiYWxnIjoiRVMyNTYifQ.eyJncm91cHMiOlt7Imdyb3VwSWQiOiIqIiwibmV0Um9sZSI6InN0YSJ9XSwibmV0QWNjZXNzS2V5Ijp7Imt0eSI6IkVDIiwiY3J2IjoiUC0yNTYiLCJ4IjoicGVySG04WU5LeEI4aXJVaHpGdTZhY2NmbWRrZWRfTlc5TjI3d1Q4QVNjcyIsInkiOiI0ZnpRSnpRMVZIUFJYRVp0SmRIaU9UN1lpZzZ0MWFEUV9UQ2xJWEdJajFNIn19.vF4YeK7jm9MvhaOPyXQyqfTVilXVlaXBld1hOT39103-p4H0o0-ZoABOc5tBt5C9rTiCrSXwekjtiFNkG1j9EA"
  dpp_netaccesskey=3077020101042037fd78c44c01284da378cb1e4c336efb04978d0a0fb440bde71ac18578057212a00a06082a8648ce3d030107a14403420004a5eac79bc60d2b107c8ab521cc5bba69c71f99d91e77f356f4ddbbc13f0049cbe1fcd02734355473d15c466d25d1e2393ed88a0eadd5a0d0fd30a52171888f53
  dpp_csign=3039301306072a8648ce3d020106082a8648ce3d030107032200031f7b6fad27dea1268e22ed3bd9ba2cd465956c0d9e6ab1427dac2a4cf02180c6
  dpp_pp_key=3039301306072a8648ce3d020106082a8648ce3d030107032200034bb0283100708e2e726551e328d999345ac2588b9a74313894268f9ed3ae9697
}

2. Interface Capabilities

iw list | grep -A5 "Supported interface modes"

Output:

managed
AP
AP/VLAN
monitor
P2P-client

• No explicit P2P-GO support
• No DPP-related capability visible

---

3. Firmware & Driver

• Firmware in use:
  nxp/pcieuart8997_combo_v4.bin
• wifi_mod_para.conf does not expose any DPP-related parameters

---

Conclusion / Suspicion

Although DPP authentication and configuration exchange succeed, the STA never connects to the AP.

This makes me suspect that:

• The PCIE8997 firmware supports only partial DPP
  • Authentication & config exchange works
  • Connector-based association does not
• Or additional firmware / driver enablement is required for full DPP support

---

Questions

1. Is full DPP (Wi-Fi Easy Connect, including connector-based association) supported on PCIE8997 with i.MX8MP?
2. If yes:
   • Which firmware version supports it?
   • Are there any required module parameters or driver patches?
3. If no:
   • Is DPP limited to authentication/config exchange only on this chipset?

Any clarification from NXP would be greatly appreciated.

[Christine_Li]

Hi， @Niranjan123 

Thanks for creating case to us.

I will check and reply to you ASAP.

Best regards,

Christine.

[Christine_Li]

Hi， @Niranjan123 

Do you see below logs on your side?

> mlan0: DPP-CONF-RECEIVED
mlan0: DPP-CONFOBJ-AKM dpp
mlan0: DPP-CONFOBJ-SSID dpp_test
mlan0: DPP-CONNECTOR 
mlan0: DPP-C-SIGN-KEY 
mlan0: DPP-PP-KEY 
mlan0: DPP-NET-ACCESS-KEY 
<3>DPP-CONF-RECEIVED
> mlan0: DPP-NETWORK-ID 0
<3>DPP-CONFOBJ-AKM dpp
<3>DPP-CONFOBJ-SSID dpp_test
<3>DPP-CONNECTOR 
<3>DPP-C-SIGN-KEY 
<3>DPP-PP-KEY 
<3>DPP-NET-ACCESS-KEY 
<3>CTRL-EVENT-NETWORK-ADDED 0
<3>DPP-NETWORK-ID 0

If you also see above info, I think DPP connection is already created.

I also attach my test steps for your reference.

Please let me know if you still have any other concerns on this case.

Best regards,

Christine.

[Niranjan123]

Hi @Christine_Li 
I have attached the logs i got below

AP side (Configurator) where we are running hostapd_cli

root@imx8mp-lpddr4-evk:~# hostapd_cli 
hostapd_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <[email protected]> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.

Selected interface 'uap0'

Interactive mode

> dpp_configurator_add
1> 
> dpp_configurator_get_key 1
30770201010420d9d09afaeddd3c41979e4ce8e4c244dc1fda630809d1ae8e1d56e71cc55062baa00a06082a8648ce3d030107a14403420004a3c43ddd47492223305c738f42e195b7862317534eb3d51ff29956682a407eaf590f9f22aec9c68faa463a6ee388e92f145676aaab5e3d22cf3bd2e2de70ee50> 
> dpp_configurator_sign conf=ap-dpp configurator=1 ssid=4450505f4150313131
<3>DPP-CONF-RECEIVED 
<3>DPP-CONFOBJ-AKM dpp
<3>DPP-CONFOBJ-SSID DPP_AP111
<3>DPP-CONNECTOR eyJ0eXAiOiJkcHBDb24iLCJraWQiOiIzdlI4WlVKbjY5bEJDcGtCQ3AwX1h6WHRFYU5zX2pPN3FHTF96dmRINFRzIiwiYWxnIjoiRVMyNTYifQ.eyJncm91cHMiOlt7Imdyb3VwSWQiOiIqIiwibmV0Um9sZSI6ImFwIn1dLCJuZXRBY2Nlc3NLZXkiOnsia3R5IjoiRUMiLCJjcnYiOiJQLTI1NiIsIngiOiJWdFFxYVhQblF0dnJIZnVrUXlUdTJiMUprNzE2aGEyWGtqZFNnR0MtaHNRIiwieSI6IkNpcHVGZEJORjBHVy13N3U3aV9vZi1lSldWaG1NRDFvczM5eUJFVkczcFEifX0.9GT21qj6r0muo28vfRMok8Z3GvtzFWh0UYp9ZVIofU-PLZBAkSsia0daZTD7rsOxGo_lAnK5TLBze_fy547t6A
<3>DPP-C-SIGN-KEY 3039301306072a8648ce3d020106082a8648ce3d03010703220002a3c43ddd47492223305c738f42e195b7862317534eb3d51ff29956682a407eaf
<3>DPP-NET-ACCESS-KEY 307702010104200e94c49fd980df00e91e4e75441d906727bf6525f78850f671d82f41aa223180a00a06082a8648ce3d030107a1440342000456d42a6973e742dbeb1dfba44324eed9bd4993bd7a85ad979237528060be86c40a2a6e15d04d174196fb0eeeee2fe87fe789595866303d68b37f72044546de94
OK
> 
> 
> dpp_qr_code DPP:C:81/1;M:cc47403403c7;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgADFGdzTeKwa2w07obrVS0RqLxIEJ+oW2jlnNXa7YrL3Tk=;;
1> 
> 
> dpp_auth_init peer=1 conf=sta-dpp netrole=ap ssid=4450505f4150313131 configurator=1
<3>DPP-TX dst=cc:47:40:34:03:c7 freq=2412 type=0
OK
> <3>DPP-TX-STATUS dst=cc:47:40:34:03:c7 result=SUCCESS
<3>DPP-RX src=cc:47:40:34:03:c7 freq=2412 type=1
<3>DPP-AUTH-DIRECTION mutual=0
<3>DPP-TX dst=cc:47:40:34:03:c7 freq=2412 type=2
<3>DPP-TX-STATUS dst=cc:47:40:34:03:c7 result=SUCCESS
<3>DPP-AUTH-SUCCESS init=1
<3>DPP-CONF-REQ-RX src=cc:47:40:34:03:c7
<3>DPP-BAND-SUPPORT 81,82,83,84,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130
<3>DPP-RX src=cc:47:40:34:03:c7 freq=2412 type=11
<3>DPP-CONF-SENT 
<3>DPP-RX src=cc:47:40:34:03:c7 freq=2412 type=5

In STA side (Enrolee) where we are running wpa_cli

root@imx8mp-lpddr4-evk:~# wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <[email protected]> and contributors


This software may be distributed under the terms of the BSD license.
See README for more details.

Selected interface 'mlan0'

Interactive mode

> dpp_bootstrap_gen type=qrcode mac=cc47403403c7 chan=81/1
1
> 
> dpp_bootstrap_get_uri 1
DPP:C:81/1;M:cc47403403c7;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgADFGdzTeKwa2w07obrVS0RqLxIEJ+oW2jlnNXa7YrL3Tk=;;
> 
> 
> dpp_listen 2412
OK
> 
<3>DPP-RX src=ce:47:40:33:1c:c1 freq=2412 type=0
<3>DPP-TX dst=ce:47:40:33:1c:c1 freq=2412 type=1
<3>DPP-TX-STATUS dst=ce:47:40:33:1c:c1 freq=2412 result=SUCCESS
<3>DPP-RX src=ce:47:40:33:1c:c1 freq=2412 type=2
<3>DPP-AUTH-SUCCESS init=0
<3>GAS-QUERY-START addr=ce:47:40:33:1c:c1 dialog_token=181 freq=2412
<3>GAS-QUERY-DONE addr=ce:47:40:33:1c:c1 dialog_token=181 freq=2412 status_code=0 result=SUCCESS
<3>DPP-CONF-RECEIVED 
<3>DPP-CONFOBJ-AKM dpp
<3>DPP-CONFOBJ-SSID DPP_AP111
<3>DPP-CONNECTOR eyJ0eXAiOiJkcHBDb24iLCJraWQiOiIzdlI4WlVKbjY5bEJDcGtCQ3AwX1h6WHRFYU5zX2pPN3FHTF96dmRINFRzIiwiYWxnIjoiRVMyNTYifQ.eyJncm91cHMiOlt7Imdyb3VwSWQiOiIqIiwibmV0Um9sZSI6InN0YSJ9XSwibmV0QWNjZXNzS2V5Ijp7Imt0eSI6IkVDIiwiY3J2IjoiUC0yNTYiLCJ4IjoiZndIcDRoWm5STHd6ckNZTERQbGlENXJqc3ZNNVVwRV9RajRVM2dFenN1MCIsInkiOiJTYjBCVkhzRG5KYWVSZUZGRF82WVVCOHVwQzhzR3VhMDJpek5HeHpZc2ZVIn19.LbG7j42LlRl6w2RzZUnFgEijKB67y5SZAq3M9A_KNpTbOA4mhdJ4ZL0dkBBTAB9-giwkBycSfeNdAsUUOMCkWA
<3>DPP-C-SIGN-KEY 3039301306072a8648ce3d020106082a8648ce3d03010703220002a3c43ddd47492223305c738f42e195b7862317534eb3d51ff29956682a407eaf
<3>DPP-PP-KEY 3039301306072a8648ce3d020106082a8648ce3d030107032200036541a485abf646d25456c98467d62e4b37bd4690dfa54148f1014eba5ffeddcc
<3>DPP-NET-ACCESS-KEY 30770201010420b57cacac2877bd3fdb00719f8b98ec4ad513bfc1b8d6114e51a9b131da0773d8a00a06082a8648ce3d030107a144034200047f01e9e2166744bc33ac260b0cf9620f9ae3b2f33952913f423e14de0133b2ed49bd01547b039c969e45e1450ffe98501f2ea42f2c1ae6b4da2ccd1b1cd8b1f5
<3>CTRL-EVENT-NETWORK-ADDED 0
<3>DPP-NETWORK-ID 0
<3>DPP-TX dst=ce:47:40:33:1c:c1 freq=2412 type=11
<3>DPP-TX-STATUS dst=ce:47:40:33:1c:c1 freq=2412 result=SUCCESS
<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>DPP-TX dst=ce:47:40:33:1c:c1 freq=2412 type=5
<3>DPP-TX-STATUS dst=ce:47:40:33:1c:c1 freq=2412 result=SUCCESS

STA is able to find the network, but when checked the status of the connection it is Scanning not Connected.

> > list_networks
network id / ssid / bssid / flags
0  DPP_AP111  any 

Please let me know what the issue is, I have attached the wpa_supplicant log.

[Christine_Li]

Hi, @Niranjan123 

Thanks for your info and sorry for my late reply because I was blocked by other priority thread.

I will test it today with your steps, then let you know my results.

Best regards,

Christine.

[Christine_Li]

Hi, @Niranjan123 

I could not finish setting up the test environment today.

Will share you the result tomorrow, sincerely apologize again for the delay reply because of other priority thread.

Best regards,

Christine.

[Christine_Li]

Hello, @Niranjan123 

I reproduced this issue locally with your steps.

Please see the logs in my side.

I will escalate this issue internally to our expert team, and once have any updates, I will let you know.

Best regards,

Christine.

[Christine_Li]

Hi， @Niranjan123 

Our internal team is still actively checking this issue.

Even shared one hostapd.conf to me, but I already verified locally, the issue is still there.

I can share the hostapd.conf to you also, but it might also not working on your side because it doesn't work on my side.

Please see below:

======

ctrl_interface=/var/run/hostapd

interface=uap0

driver=nl80211

hw_mode=g

channel=1

ieee80211n=1

ssid=unconfigured

wpa=2

wpa_key_mgmt=DPP

ieee80211w=1

======

Once have any updates, I will let you know.

By the way, as you might know that we will start our Chinese Festival public holiday after 2 days, from Feb 14th to Feb 23th. And I will be back to office on Feb 24th.

Since my response time may be slower during the holiday period, I would like to inform you in advance so we can manage the case smoothly.

The Spring Festival is one of the most important traditional festivals in China. According to Chinese culture, I would also like to wish you a Happy Spring Festival 🧧!

During the holiday, I will continue to check my email daily. If you need any additional support or have further questions, please feel free to contact me. I will do my best to assist you and support your project.

Best regards,

Christine.

[Niranjan123]

Hi @Christine_Li ,

Thank you for the update and for sharing the details regarding the hostapd configuration.

I appreciate your continuous support and for keeping us informed about the progress from your internal team. Please do let me know once there are any updates.

Also, thank you for informing us in advance about the holiday schedule. Wishing you a very Happy Spring Festival as well! 🧧 Hope you have a wonderful and joyful time with your family.

We truly appreciate your support, even during the holiday period.

Best regards,
Niranjan

[Christine_Li]

Hi, @Niranjan123 

We think the test steps on your side is not correct.

Need to use 3 devices to finished the DPP test.

Please see attached pdf or below link for your reference:

How to do DPP test with two 88W8997 and one IW612

Please let me know whether have any other concerns on this case, otherwise, please do not hesitate to mark my answer as a solution for this case. Thanks!

Best regards,

Christine.

[Niranjan123]

Hi @Christine_Li ,

Thank you for your earlier response and for sharing the reference document on performing the DPP test using two 88W8997 devices and one IW612.

We followed the steps provided in the shared document and executed the DPP test accordingly.

However, we are facing issues during the authentication stage. Please find the observed behavior below:

1. DUT (Initiator + Enrollee + STA)

Command executed:
DPP_AUTH_INIT peer=1 role=enrollee

Observed logs:

• DPP-TX dst=cc:47:40:34:03 freq=2412 type=0

• DPP-TX-STATUS dst=cc:47:40:34:03 freq=2412 result=SUCCESS

• DPP-AUTH-INIT-FAILED

2. CTT1 (Configurator)

Command executed:
DPP_AUTH_INIT peer=4 conf=ap-dpp configurator=1

Observed logs:

• FAIL

• DPP: Failed to set configurator parameters

We have also attached the document containing the exact steps we followed during the DPP test for your reference.

Kindly review and suggest the required corrections or debugging steps.

regards,
Niranjan

[Christine_Li]

Hi, @Niranjan123 

Thanks for your feedback.

I checked your logs, you are using this driver and FW version:

driver_version = PCIE8997--16.92.21.p137.4-MM6X16505.p4-GPL-(FP92)

It is pretty old, and I am using:

driver_version = PCIE8997--16.92.21.p153.7-MM6X16540.p33-GPL-(FP92)

You can get it through out github:

FW:

https://github.com/nxp-imx/imx-firmware

Driver:

GitHub - nxp-imx/mwifiex: WiFi extensions

Can you please help to update your driver and FW version then re-test again?

Best regards,

Christine.

[Christine_Li]

Hi, @Niranjan123 

Did you get any chance to test with our newer release like me?

Please let me know your results and whether still need help from my side.

Best regards,

Christine.