In Nrf7002dk facing issue with TWT Powersave Mechanism

Hi,

1. I was facing issue with my nordic device saying 

[02:16:46.206,481] <err> net_pkt: Data buffer (1328) allocation failed.
[02:16:46.206,481] <wrn> net_conn: pkt cloning failed, pkt 0x2003a454 dropped

continuously , attached video below for your reference.

 2. I need to test TWT powersave using Nrf7002dk, what i was doing was 

  • Initially turning on powersave using " wifi ps on "
  • Connecting wifi using " wifi connect SSID Password "
  • After successful connection starting ping to the nordic ip which i took from "net iface show" through my laptop which is in the same network and ping is happening.
  • Now entering " wifi twt setup 0 0 2 2 0 0 1 0 20000 3000000 " command and output occurred as uart:~$ wifi twt setup 0 0 2 2 0 0 1 0 20000 3000000
    TWT operation TWT setup with dg: 2, flow_id: 2 requested
    TWT response: TWT reject
    TWT Dialog token: 2
    TWT flow ID: 2
    TWT negotiation type: TWT individual negotiation
    TWT responder: true
    TWT implicit: true
    TWT announce: false
    TWT trigger: false
    TWT wake interval: 19968 us
    TWT interval: 3002000 us
    ======================

But even after i have given wake interval it should go to sleep and should wake after the given wake interval time, but i was not happening in that way, it was continuously pinging or reachable without sleep.

3. When i was giving net tcp connect IP Port it was disconnecting with errors

uart:~$ net tcp connect 172.40.9.203 5001
Connecting from 172.40.9.248:0 to 172.40.9.203:5001
TCP connection failed (-116)
[00:13:28.327,423] <err> os: ***** BUS FAULT *****
[00:13:28.327,423] <err> os: Precise data bus error
[00:13:28.327,423] <err> os: BFAR Address: 0xc809
[00:13:28.327,453] <err> os: r0/a1: 0x00000000 r1/a2: 0x00000002 r2/a3: 0x0000c809
[00:13:28.327,453] <err> os: r3/a4: 0x20012e60 r12/ip: 0x200298f4 r14/lr: 0x0004d67f
[00:13:28.327,453] <err> os: xpsr: 0x21000000
[00:13:28.327,453] <err> os: Faulting instruction address (r15/pc): 0x000738a4
[00:13:28.327,484] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:13:28.327,484] <err> os: Current thread: 0x20002af8 (tcp_work)
[00:13:28.390,502] <err> coredump: #CD:BEGIN#
[00:13:28.396,270] <err> coredump: #CD:5a4501000300050019000000
[00:13:28.403,594] <err> coredump: #CD:4102004400
[00:13:28.409,698] <err> coredump: #CD:000000000200000009c80000602e0120f49802207fd60400a438070000000021
[00:13:28.420,501] <err> coredump: #CD:98d4002000000000000000000000000000000000000000000000000000000000
[00:13:28.431,304] <err> coredump: #CD:00000000
[00:13:28.437,225] <err> coredump: #CD:4d0100f82a0020c02b0020
[00:13:28.444,366] <err> coredump: #CD:70230020a47d0020000000000080f20000000000000000000000000000000000
[00:13:28.455,169] <err> coredump: #CD:00000000000000000000000000000000a447002000000000ffffffffffffffff
[00:13:28.466,003] <err> coredump: #CD:00000000ffffffff000000000000000070d4002000000000502b0020502b0020
[00:13:28.476,806] <err> coredump: #CD:000100001dd70400f82a00200000000000000000903500207463705f776f726b
[00:13:28.487,609] <err> coredump: #CD:0000000000000000000000000000000000000000000000000000000020d10020
[00:13:28.498,413] <err> coredump: #CD:0004000000000000301600200000000000000000000000000000000000000000
[00:13:28.509,216] <err> coredump: #CD:0000000000000000
[00:13:28.515,838] <err> coredump: #CD:4d010020d1002020d50020
[00:13:28.522,979] <err> coredump: #CD:f0f0f0f0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.533,782] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.544,586] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.555,419] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.566,223] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.577,026] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.587,829] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.598,632] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.609,436] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.620,239] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.631,042] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.641,845] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.652,648] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.663,452] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.674,255] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.685,058] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:13:28.695,861] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa7035002045db0400
[00:13:28.706,665] <err> coredump: #CD:e0330020887d0020f82a0020c1db0400fffffffff82a002080120020df320700
[00:13:28.717,498] <err> coredump: #CD:ffffffffffffffffffffffffed88002003000000ed88002000000000cf040600
[00:13:28.728,302] <err> coredump: #CD:70070020f4980220ed880020487e0700b8d30020030000000723060035230600
[00:13:28.739,105] <err> coredump: #CD:03000000d47207001b000000d2880020072306000d2b06000300000000000000
[00:13:28.749,908] <err> coredump: #CD:0000000000000000d0410000b03c0020f87d07000a000000a519090018000000
[00:13:28.760,711] <err> coredump: #CD:1b00000049260600f87d07008926060051260600c0d400201c000000ab5a0000
[00:13:28.771,514] <err> coredump: #CD:3ed400203b3307005029002051260600a6190900000000000000000005160200
[00:13:28.782,318] <err> coredump: #CD:48d40020a319090050010000181a002000000000d61d00007035002045db0400
[00:13:28.793,121] <err> coredump: #CD:e0330020887d0020f82a0020c1db0400fffffffff82a0020a4470020df320700
[00:13:28.803,955] <err> coredump: #CD:ffffffffffffffffffffffff2ddd04000000000000ed00e0887d002000000000
[00:13:28.814,758] <err> coredump: #CD:f4980220f1d40400a8bf000000000061f2ffffffa44700200000000002000000
[00:13:28.825,561] <err> coredump: #CD:09c80000602e0120f49802207fd60400a4380700000000210000000044930220
[00:13:28.836,364] <err> coredump: #CD:8cffffff156b0600449302208cfffffff82a0020d4930220b07d0020a1d70400
[00:13:28.847,167] <err> coredump: #CD:ffffffffffffffff00000000aaaaaaaaaaaaaaaa1dd704000000000000000000
[00:13:28.857,971] <err> coredump: #CD:0000000000000000000000000000000000000000ddfc050000000000aaaaaaaa
[00:13:28.868,743] <err> coredump: #CD:END#
[00:13:28.874,328] <err> fatal_error: Resetting system

I need help on both points, ASAP because it was stopping my testing. 

  • Hi,

     

    Please test zperf/iperf without TWT enabled first, to ensure that your overall setup is as expected.

    Håkon Alseth said:
    This will make it wake up for 20 ms each 60 seconds.

    This was incorrect, as per your latest video. You are now setting 20 ms active and 60 ms period. Is this wanted timing? It does not make sense to use TWT for such a low period.

     

    Kind regards,

    Håkon

  • Hi,

    Please test zperf/iperf without TWT enabled first, to ensure that your overall setup is as expected.

    without enabling TWT Zperf is working fine.

    This was incorrect, as per your latest video. You are now setting 20 ms active and 60 ms period. Is this wanted timing? It does not make sense to use TWT for such a low period.

    what is the correct time periods to use TWT powersave, can you provide the wake interval and twt interval for the same.

    And also if you see my sniffer in action frames i was not getting proper information for TWT setup and no announced, unannounced, accept or Request TWT related information also.

    Regards,

    Jaswanth.

  • Hi,

     

    Jaswanth Rajigiri said:

    what is the correct time periods to use TWT powersave, can you provide the wake interval and twt interval for the same.

    And also if you see my sniffer in action frames i was not getting proper information for TWT setup and no announced, unannounced, accept or Request TWT related information also.

    You shall get a feedback in the shell application if TWT was accepted or rejected. But I still see that you're using an older version of the SDK (v2.5.0?), and I would strongly recommend that you update and test on newer versions.

    You can also have a look at this sample, as it includes traffic generation:

    https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/wifi/twt/README.html

     

    What access point model are you using?

     

    Kind regards,

    Håkon

Related