Attachments (5) Download All
Nordic Case Info
  • Case ID: 341003
Options

54l15+7002eb problem

William.wei

hi support team,

i have one problem for 54l15+7002 in ncs2.9.0

I am afraid that I need your help.

 

I was porting MQTT demo and PERIPHERAL_UART demo together and want to provide it to customer Ao-Zheng.

For 7002dk, it runs normal, but for 54l15+7002eb, it fails.  

 

So, I return to MQTT demo, here is the problem:

 mqtt2.zip

Attachment is MQTT demo changed in prj.conf , adding:

CONFIG_WIFI_CREDENTIALS_STATIC=y

#CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_PSK=y

CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_WPA_PSK=y

CONFIG_WIFI_CREDENTIALS_STATIC_SSID="Nordicsh"

CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="Nordic20201908"

 

54L15+7002EB stops at somewhere, however, when I test it with shell, it still can work.

Please see log_release1.txt, and log_release2.txt

 

Fullscreen log_release1.txt Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[00:00:00.508,177] <inf> wifi_nrf_bus: SPIM spi@c8000: freq = 8 MHz
[00:00:00.516,902] <inf> wifi_nrf_bus: SPIM spi@c8000: latency = 0
[00:00:00.642,884] <inf> wifi_nrf: Management buffer offload enabled
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
[00:00:00.792,898] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.802,325] <inf> network: Bringing network interface up and connecting to the network
uart:~$ wifi disconnect
[00:01:28.158,924] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Disconnect requested
uart:~$ wifi connect -s "Nordicsh" -p "Nordic20201908" -k 1
Connection requested
[00:01:48.034,105] <inf> wpa_supp: wlan0: SME: Trying to authenticate with a4:f3:3b:c6:15:60 (SSID='Nordicsh' freq=2417 MHz)
[00:01:48.419,674] <inf> wpa_supp: wlan0: Trying to associate with a4:f3:3b:c6:15:60 (SSID='Nordicsh' freq=2417 MHz)
[00:01:48.465,743] <inf> wpa_supp: wlan0: Associated with a4:f3:3b:c6:15:60
[00:01:48.475,822] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:01:51.556,986] <inf> wpa_supp: wlan0: CTRL-EVENT-DISCONNECTED bssid=a4:f3:3b:c6:15:60 reason=15
Connection request failed (1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Fullscreen log_release2.txt Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[00:00:00.508,337] <inf> wifi_nrf_bus: SPIM spi@c8000: freq = 8 MHz
[00:00:00.517,062] <inf> wifi_nrf_bus: SPIM spi@c8000: latency = 0
[00:00:00.643,076] <inf> wifi_nrf: Management buffer offload enabled
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
[00:00:00.793,841] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.803,523] <inf> network: Bringing network interface up and connecting to the network
uart:~$ wifi disconnect
[00:00:06.810,923] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Disconnect requested
uart:~$ wifi connect -s "Nordicsh" -p "Nordic20201908" -k 1
Connection requested
[00:00:29.717,629] <inf> wpa_supp: wlan0: SME: Trying to authenticate with a4:f3:3b:c6:15:60 (SSID='Nordicsh' freq=2417 MHz)
[00:00:30.103,204] <inf> wpa_supp: wlan0: Trying to associate with a4:f3:3b:c6:15:60 (SSID='Nordicsh' freq=2417 MHz)
[00:00:30.149,359] <inf> wpa_supp: wlan0: Associated with a4:f3:3b:c6:15:60
[00:00:30.159,440] <inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:33.232,823] <inf> wpa_supp: wlan0: CTRL-EVENT-DISCONNECTED bssid=a4:f3:3b:c6:15:60 reason=15
Connection request failed (1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

after I add following configs:

CONFIG_WIFI_LOG_LEVEL_DBG=y

CONFIG_WIFI_NRF70_LOG_LEVEL_DBG=y

CONFIG_NET_BUF_LOG_LEVEL_DBG=y

CONFIG_MQTT_SAMPLE_TRIGGER_LOG_LEVEL_DBG=y

CONFIG_MQTT_SAMPLE_NETWORK_LOG_LEVEL_DBG=y

CONFIG_MQTT_SAMPLE_TRANSPORT_LOG_LEVEL_DBG=y

 Please see the logs in log_debug1.txt and log_debug2.txt .

 log_debug1.txt

Fullscreen log_debug2.txt Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[00:00:00.436,336] <inf> wifi_nrf_bus: SPIM spi@c8000: freq = 8 MHz
[00:00:00.445,061] <inf> wifi_nrf_bus: SPIM spi@c8000: latency = 0
[00:00:00.458,889] <dbg> wifi_nrf: zep_shim_pr_dbg: Signature: 0xdead1eaf
[00:00:00.468,138] <dbg> wifi_nrf: zep_shim_pr_dbg: num_images: 4
[00:00:00.476,733] <dbg> wifi_nrf: zep_shim_pr_dbg: version: 0x1020d00
[00:00:00.485,757] <dbg> wifi_nrf: zep_shim_pr_dbg: feature_flags: 1
[00:00:00.494,603] <dbg> wifi_nrf: zep_shim_pr_dbg: ====
[00:00:00.502,433] <dbg> wifi_nrf: zep_shim_pr_dbg: image[0] type: 0
[00:00:00.511,287] <dbg> wifi_nrf: zep_shim_pr_dbg: image[0] len: 1240
[00:00:00.520,301] <dbg> wifi_nrf: zep_shim_pr_dbg: ====
[00:00:00.528,131] <dbg> wifi_nrf: zep_shim_pr_dbg: image[1] type: 1
[00:00:00.536,984] <dbg> wifi_nrf: zep_shim_pr_dbg: image[1] len: 46360
[00:00:00.546,083] <dbg> wifi_nrf: zep_shim_pr_dbg: ====
[00:00:00.553,914] <dbg> wifi_nrf: zep_shim_pr_dbg: image[2] type: 2
[00:00:00.562,767] <dbg> wifi_nrf: zep_shim_pr_dbg: image[2] len: 952
[00:00:00.571,698] <dbg> wifi_nrf: zep_shim_pr_dbg: ====
[00:00:00.579,529] <dbg> wifi_nrf: zep_shim_pr_dbg: image[3] type: 3
[00:00:00.588,385] <dbg> wifi_nrf: zep_shim_pr_dbg: image[3] len: 30920
[00:00:00.597,485] <dbg> wifi_nrf: zep_shim_pr_dbg: ====
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

By the way,  using shell to connect to MQTT server is unstable.

 

Regards,

William.

  • 0

    Hi, 

    For 7002dk, it runs normal, but for 54l15+7002eb, it fails.  

    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.

    54L15+7002EB stops at somewhere

    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. 

  • 0 in reply to Amanda Hsieh

    Hi Amanda,

    Amanda Hsieh said:
    Do you build with - mqtt_SHIELD="nrf7002eb_interposer_p1;nrf7002eb"?

    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 .

    Amanda Hsieh said:
    Could you share the log?

    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

  • 0 in reply to William.wei

    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.

  • 0 in reply to Amanda Hsieh

    Hi Amanda，

    is there any reply?

    Regards,

    WIlliam.

  • 0 in reply to William.wei

    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:

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

    Logs:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    [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
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

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

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

    Logs:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    [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"
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1 2
Terms of service