54l15+7002eb problem

RE: 54l15+7002eb problem

William.wei — Wed, 23 Jul 2025 06:00:06 GMT

thanks amanda,

this is sdk problem, and new ncs version solves it.

Regards,

William.

RE: 54l15+7002eb problem

Amanda Hsieh — Fri, 04 Apr 2025 18:29:31 GMT

Hi,

[quote user="William.wei"]

1.wifi connect -s "Nordicsh" -p "Nordic20201908" -k 1, it fails

2.wifi connect -s "Nordicsh" -p "Nordic20201908" -k 2, it fails

3. wifi connect -s "Nordicsh" -p "Nordic20201908" -k 9

[/quote]

If it works with -k 9 and not with -k 1/2 that means the AP is configured in WPA-PSK. wifi scan should give the details of the AP security type.

And for the other connection issues, by default the sample doesn’t have any AP provisioning done, so it won’t connect to Wi-Fi automatically. The user has to provision to initiate the Wi-Fi connection: Please see Technical Documentation for details, which explains why initiatingthe connecting using wifi shells works.

But I see that the Wi-Fi credentials module is only enabled for nrf7002dk/nrf5340/cpuapp/ns board, for nrf54L15dk. It needs to be enabled manually (we can make this automatic for all boards). Once the module is enabled, the user can either choose WIFI_CREDENTIALS_STATIC or WIFI_CREDENTIALS_SHELL (wifi_cred shell) to provision the AP.

In this scenario, we need wpa_supplicant debug logs not the driver ones. We will also elaborate Technical Documentation on when to elaborate supplicant or driver logs,

Here is the PR https://github.com/nrfconnect/sdk-nrf/pull/21402

for improving debug docs https://github.com/nrfconnect/sdk-nrf/pull/21404

-Amanda H.

RE: 54l15+7002eb problem

William.wei — Thu, 20 Mar 2025 02:13:30 GMT

Hi Amanda,

no improvment with your build command, i even tried main branch, still no improvement for this moment.

i tried several routers, still same problem.

[00:00:00.436,026] <inf> wifi_nrf_bus: SPIM spi@c8000: freq = 8 MHz
[00:00:00.444,786] <inf> wifi_nrf_bus: SPIM spi@c8000: latency = 0
[00:00:00.572,282] <inf> wifi_nrf: Management buffer offload enabled

*** Booting nRF Connect SDK v2.9.99-0479f0880eba ***
*** Using Zephyr OS v4.0.99-ff01b5fcc223 ***
[00:00:00.723,419] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.732,582] <inf> network: Bringing network interface up and connecting to the network
uart:~$ wifi connect -s "Jayant" -p "tangjingyang" -k 1
Connection requested
[00:00:18.305,435] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 96:55:b3:41:7d:7a (SSID='Jayant' freq=24 37 MHz)
[00:00:18.811,918] <inf> wpa_supp: wlan0: Trying to associate with 96:55:b3:41:7d:7a (SSID='Jayant' freq=2437 MHz)
[00:00:18.967,349] <inf> wpa_supp: wlan0: Associated with 96:55:b3:41:7d:7a
[00:00:18.977,745] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:19.039,136] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 96:55:b3:41:7d:7a [PTK=CCMP GTK=CCMP]
[00:00:19.052,653] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 96:55:b3:41:7d:7a completed [id=0 id _str=]
Connected
[00:00:19.149,562] <inf> network: Network connectivity established
[00:00:24.753,064] <inf> transport: Connected to MQTT broker
[00:00:24.761,992] <inf> transport: Hostname: test.mosquitto.org
[00:00:24.770,538] <inf> transport: Client ID: 423282540EEAB297
[00:00:24.778,989] <inf> transport: Port: 1883
[00:00:24.785,978] <inf> transport: TLS: No
[00:00:24.792,724] <inf> transport: Subscribing to: 423282540EEAB297/my/subscribe/topic
[00:00:25.061,309] <inf> transport: Subscribed to topic 423282540EEAB297/my/subscribe/topic

another router log:

[00:00:00.436,090] <inf> wifi_nrf_bus: SPIM spi@c8000: freq = 8 MHz
[00:00:00.444,850] <inf> wifi_nrf_bus: SPIM spi@c8000: latency = 0
[00:00:00.572,313] <inf> wifi_nrf: Management buffer offload enabled

*** Booting nRF Connect SDK v2.9.99-0479f0880eba ***
*** Using Zephyr OS v4.0.99-ff01b5fcc223 ***
[00:00:00.723,447] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.732,608] <inf> network: Bringing network interface up and connecting to the network
uart:~$ wifi connect -s "Jayant" -p "tangjingyang" -k 1
Connection requested
[00:01:02.256,266] <inf> wpa_supp: wlan0: SME: Trying to authenticate with 96:55:b3:41:7d:7a (SSID='Jayant' freq=2437 MHz)
[00:01:02.644,302] <inf> wpa_supp: wlan0: Trying to associate with 96:55:b3:41:7d:7a (SSID='Jayant' freq=2437 MHz)
[00:01:02.692,569] <inf> wpa_supp: wlan0: Associated with 96:55:b3:41:7d:7a
[00:01:02.702,961] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:01:02.766,022] <inf> wpa_supp: wlan0: WPA: Key negotiation completed with 96:55:b3:41:7d:7a [PTK=CCMP GTK=CCMP]
[00:01:02.779,540] <inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to 96:55:b3:41:7d:7a completed [id=0 id_str=]
Connected
[00:01:02.866,620] <inf> network: Network connectivity established
[00:01:08.496,179] <inf> transport: Connected to MQTT broker
[00:01:08.505,017] <inf> transport: Hostname: test.mosquitto.org
[00:01:08.513,560] <inf> transport: Client ID: 423282540EEAB297
[00:01:08.522,012] <inf> transport: Port: 1883
[00:01:08.529,003] <inf> transport: TLS: No
[00:01:08.535,752] <inf> transport: Subscribing to: 423282540EEAB297/my/subscribe/topic
[00:01:08.858,893] <inf> transport: Subscribed to topic 423282540EEAB297/my/subscribe/topic

cli is working, no clue for me.

Regards,

William.

RE: 54l15+7002eb problem

Amanda Hsieh — Tue, 11 Mar 2025 13:51:50 GMT

Hi William,

Can you confirm the issue is resolved with the proposed build command
west build -p -b nrf54l15dk/nrf54l15/cpuapp -- -Dmqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb" -Dmqtt_SNIPPET=nrf70-wifi?

RE: 54l15+7002eb problem

Amanda Hsieh — Fri, 07 Mar 2025 19:53:06 GMT

The team tested the MQTT sample with NCS v2.9.0 and (nRF54L15+ Interposer+ EB) and observed a crash related to stack overflow after issuing wifi connect command.

Build command:

west build -p -b nrf54l15dk/nrf54l15/cpuapp -- -Dmqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb"

Logs:

[00:00:23.151,657] <err> os: ***** HARD FAULT *****
[00:00:23.157,150] <err> os:   Fault escalation (see below)
[00:00:23.163,403] <err> os: ***** USAGE FAULT *****
[00:00:23.169,050] <err> os:   Stack overflow (context area not valid)
[00:00:23.176,266] <err> os: r0/a1:  0x200177a0  r1/a2:  0x0007cea4  r2/a3:  0x200177e0
[00:00:23.184,945] <err> os: r3/a4:  0x0006680f r12/ip:  0x0000003c r14/lr:  0x0002865b
[00:00:23.193,618] <err> os:  xpsr:  0x21000006
[00:00:23.198,833] <err> os: Faulting instruction address (r15/pc): 0x0005b474
[00:00:23.206,737] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:23.214,632] <err> os: Fault during interrupt handling

[00:00:23.221,063] <err> os: Current thread: 0x200019e0 (shell_uart)
[00:00:23.228,090] <err> os: Halting system

By using the nrf70-wifi snippet, the above issue was fixed, and I no longer see any issues with the sample functionality.
Build command:

west build -p -b nrf54l15dk/nrf54l15/cpuapp -- -Dmqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb" -Dmqtt_SNIPPET=nrf70-wifi

Logs:

[00:02:22.442,448] <inf> transport: Connected to MQTT broker
[00:02:22.451,728] <inf> transport: Hostname: test.mosquitto.org
[00:02:22.460,402] <inf> transport: Client ID: 5BB1E5BABB0120D0
[00:02:22.468,892] <inf> transport: Port: 1883
[00:02:22.475,916] <inf> transport: TLS: No
[00:02:22.482,696] <inf> transport: Subscribing to: 5BB1E5BABB0120D0/my/subscribe/topic
[00:02:22.785,074] <inf> transport: Subscribed to topic 5BB1E5BABB0120D0/my/subscribe/topic
[00:03:00.754,685] <inf> transport: Published message: "Hello MQTT! Current uptime is: 180742" on topic: "5BB1E5BABB0120D0/my/publish/topic"
[00:04:00.754,806] <inf> transport: Published message: "Hello MQTT! Current uptime is: 240742" on topic: "5BB1E5BABB0120D0/my/publish/topic"

RE: 54l15+7002eb problem

William.wei — Wed, 05 Mar 2025 09:12:42 GMT

Hi Amanda，

is there any reply?

Regards,

WIlliam.

RE: 54l15+7002eb problem

Amanda Hsieh — Thu, 20 Feb 2025 17:45:45 GMT

Hi William,

I see. It still works, but might take a long time. Our sample is provided for reference, and it is not optimized. I have raised an internal JIRA to ask the team for help to look into it. I will update the case when I collect enough information.

Regards,
Amanda H.

RE: 54l15+7002eb problem

William.wei — Thu, 20 Feb 2025 03:29:29 GMT

Hi Amanda,

[quote userid="77782" url="~/f/nordic-q-a/119109/54l15-7002eb-problem/523771"]Do you build with - mqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb"?[/quote]

yes,i connected 7002eb with 54l15, and i believe the HW is running, from the log we can see the interface is up.

for 54l15+7002eb, MQTT demo should connect to broker automatically, but it stop at somewhere for ever .

[quote userid="77782" url="~/f/nordic-q-a/119109/54l15-7002eb-problem/523771"]Could you share the log?[/quote]

i have proide 4 logs in previous post.

So let's look at log_release1.txt.

"line8 log shows:

00:00:00.802,325] <inf> network: Bringing network interface up and connecting to the network"

but it can't connect to broker, it should connect to broker in 10 seconds.

so i manually input wifi disconnect , timestamp shows it is 1minutes and 28 seconds later,

and then

1.wifi connect -s "Nordicsh" -p "Nordic20201908" -k 1, it fails

2.wifi connect -s "Nordicsh" -p "Nordic20201908" -k 2, it fails

3. wifi connect -s "Nordicsh" -p "Nordic20201908" -k 9

and it connects to borker.

and log_debug1.txt, we can it here:

Regards,

William

RE: 54l15+7002eb problem

Amanda Hsieh — Wed, 19 Feb 2025 21:09:12 GMT

Hi,

[quote user=""]For 7002dk, it runs normal, but for 54l15+7002eb, it fails. [/quote]

How does it fail? Do you have the interposer board with the nRF7002-EB? It would be good if you could provide a pic of your HW setup.

[quote user=""]54L15+7002EB stops at somewhere[/quote]

Could you share the log?

Do you build with - mqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb"?

Are your logs from the MQTT sample running on nRF54L15DK with nRF7002EB? They all seem to connect to the MQTT broker and subscribed as expected. I don't see any issues/errors from them.

Regards,
Amanda H.