TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

mathiaso — Mon, 25 Aug 2025 12:45:46 GMT

That's great, Jaroslav!

I'm happy to hear you figured it out.

If there are no further questions, please close the ticket.

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

Jaroslav Havel — Fri, 22 Aug 2025 18:10:54 GMT

Hello Mathias,

thank you for help. I already fixed trouble with socket, cause I had some syntax error inside code. Compilator didn't find it. Now, everything is ok, socket is working (TCP server runs on own thread).

Kind Regards

Jaroslav

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

Jaroslav Havel — Thu, 21 Aug 2025 16:08:33 GMT

Hi Mathias,

thanks for reply.

I am trying to use sockets, but if i open TCP server, after some little time, a get error.

[00:01:52.010,681] <err> os: ***** MPU FAULT *****
[00:01:52.010,711] <err> os:   Data Access Violation
[00:01:52.010,711] <err> os:   MMFAR Address: 0x8
[00:01:52.010,742] <err> os: r0/a1:  0x0005737d  r1/a2:  0xe000ed00  r2/a3:  0x0005737c
[00:01:52.010,742] <err> os: r3/a4:  0x00000008 r12/ip:  0x200061d8 r14/lr:  0x00003ba5
[00:01:52.010,772] <err> os:  xpsr:  0x29000000
[00:01:52.010,772] <err> os: Faulting instruction address (r15/pc): 0x0005999a
[00:01:52.010,803] <err> os: >>> ZEPHYR FATAL ERROR 19: Unknown error on CPU 0
[00:01:52.010,864] <err> os: Current thread: 0x20006618 (unknown)
[00:01:52.072,235] <err> coredump: #CD:BEGIN#
[00:01:52.077,301] <err> coredump: #CD:5a4502000300050013000000
[00:01:52.083,862] <err> coredump: #CD:4102004400
[00:01:52.089,233] <err> coredump: #CD:7d73050000ed00e07c73050008000000d8610020a53b00009a99050000000029
[00:01:52.099,273] <err> coredump: #CD:5819052000000000000000000000000000000000000000000000000000000000
[00:01:52.109,313] <err> coredump: #CD:00000000
[00:01:52.114,501] <err> coredump: #CD:4d010018660020b0660020
[00:01:52.120,910] <err> coredump: #CD:c8640020a8e90020000000000180000000000000000000000000000000000000
[00:01:52.130,950] <err> coredump: #CD:21f8050000000000d966020000000000000000009819052044fc002098190520
[00:01:52.141,021] <err> coredump: #CD:0100565143fc0020ffffffffffffffff40190520000000007066002070660020
[00:01:52.151,062] <err> coredump: #CD:00010000b82f042060ea000010000000840e0020081a05200000000000000000
[00:01:52.161,102] <err> coredump: #CD:2b0d0520fc03000018660020000000000000000000000000
[00:01:52.169,769] <err> coredump: #CD:4d0100b82f0420181a0520
[00:01:52.176,177] <err> coredump: #CD:f0f0f0f0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:01:52.186,248] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

My prj.conf looks like this:

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_WIFI=y
CONFIG_WIFI_NRF70=y

CONFIG_SERIAL=y
CONFIG_NRFX_UART0=y
CONFIG_UART_ASYNC_API=y
# WPA supplicant
CONFIG_WIFI_NRF70_LOG_LEVEL_INF=n
CONFIG_WIFI_NRF70_LOG_LEVEL_DBG=n
CONFIG_WIFI_NRF70_LOG_LEVEL_DEFAULT=n
CONFIG_WIFI_NRF70_LOG_LEVEL_WRN=n
CONFIG_WIFI_NRF70_LOG_LEVEL_OFF=n
CONFIG_WIFI_NRF70_LOG_LEVEL_ERR=n

CONFIG_WIFI_READY_LIB=y
CONFIG_WIFI_NM_WPA_SUPPLICANT=y
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_DBG=n
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_INF=n
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_DEFAULT=n
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_ERR=n
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_OFF=n
CONFIG_WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_WRN=n
CONFIG_NRF_WIFI_RPU_RECOVERY=y

CONFIG_WIFI_CREDENTIALS=y
CONFIG_WIFI_CREDENTIALS_STATIC=y
CONFIG_WIFI_CREDENTIALS_STATIC_SSID="xxxxxxxxx"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="yyyyyyyyyy"

# Networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_LOG=n
CONFIG_NET_IPV4=y
CONFIG_NET_UDP=y
CONFIG_NET_TCP=y
CONFIG_NET_DHCPV4=y

CONFIG_NET_MGMT_EVENT_LOG_LEVEL_DBG=n
CONFIG_NET_MGMT_EVENT_LOG_LEVEL_DEFAULT=n
CONFIG_NET_MGMT_EVENT_LOG_LEVEL_INF=n
CONFIG_NET_MGMT_EVENT_LOG_LEVEL_ERR=n
CONFIG_NET_MGMT_EVENT_LOG_LEVEL_WRN=n
CONFIG_NET_MGMT_EVENT_LOG_LEVEL_OFF=n



CONFIG_NET_PKT_RX_COUNT=32
CONFIG_NET_PKT_TX_COUNT=32
CONFIG_NRF70_RX_NUM_BUFS=16

# Below section is the primary contributor to SRAM and is currently
# tuned for performance, but this will be revisited in the future.
CONFIG_NET_BUF_RX_COUNT=64
CONFIG_NET_BUF_TX_COUNT=64
CONFIG_HEAP_MEM_POOL_SIZE=47000
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=32768
CONFIG_HEAP_MEM_POOL_IGNORE_MIN=y
CONFIG_NRF_WIFI_CTRL_HEAP_SIZE=20000
CONFIG_NRF_WIFI_DATA_HEAP_SIZE=40000
CONFIG_NET_TC_TX_COUNT=1

CONFIG_NET_IF_UNICAST_IPV4_ADDR_COUNT=1
CONFIG_NET_MAX_CONTEXTS=50
CONFIG_NET_CONTEXT_SYNC_RECV=y

CONFIG_INIT_STACKS=y

CONFIG_NET_L2_ETHERNET=y
CONFIG_NET_L2_WIFI_MGMT=y
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_DBG=n
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_INF=n
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_WRN=n
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_ERR=n
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_DEFAULT=n
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_OFF=n

CONFIG_WIFI_MGMT_SCAN_SSID_FILT_MAX=4

CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_INIT_TIMEOUT=0

CONFIG_NET_SOCKETS_POLL_MAX=15

# Memories
CONFIG_MAIN_STACK_SIZE=60000
CONFIG_NET_TX_STACK_SIZE=4096
CONFIG_NET_RX_STACK_SIZE=4096
CONFIG_STA_SAMPLE_START_WIFI_THREAD_STACK_SIZE=65400

# Debugging
CONFIG_STACK_SENTINEL=y
CONFIG_DEBUG_COREDUMP=y
CONFIG_DEBUG_COREDUMP_BACKEND_LOGGING=y
CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=y
CONFIG_SHELL_CMDS_RESIZE=n


# Kernel options
CONFIG_ENTROPY_GENERATOR=y

# Logging
CONFIG_LOG_BUFFER_SIZE=16384
CONFIG_POSIX_CLOCK=y

CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.1.99"
CONFIG_NET_CONFIG_MY_IPV4_NETMASK="255.255.255.0"
CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.1.1"

# printing of scan results puts pressure on queues in new locking
# design in net_mgmt. So, use a higher timeout for a crowded
# environment.
CONFIG_NET_MGMT_EVENT_QUEUE_TIMEOUT=5000

CONFIG_WIFI_MGMT_RAW_SCAN_RESULTS=n
CONFIG_WIFI_MGMT_RAW_SCAN_RESULTS_ONLY=n

CONFIG_WIFI_SCAN_DWELL_TIME_ACTIVE=50
CONFIG_WIFI_SCAN_DWELL_TIME_PASSIVE=130

CONFIG_WIFI_LOG_LEVEL_OFF=n
CONFIG_WIFI_LOG_LEVEL_INF=n

CONFIG_LOG_BACKEND_NET_AUTOSTART=n
CONFIG_LOG=n
CONFIG_LOG_DEFAULT_LEVEL=3

CONFIG_TIMER=y
CONFIG_COUNTER=y
CONFIG_CLOCK_CONTROL=y
CONFIG_CLOCK_CONTROL_NRF=y
CONFIG_NRFX_CLOCK=y
CONFIG_RTC_ALARM=y
CONFIG_RTC_UPDATE=y
CONFIG_NET_ICMPV4_ACCEPT_BROADCAST=y

#CONFIG_NET_BUF_DATA_SIZE=8192
CONFIG_NET_BUF_POOL_USAGE=y

CONFIG_NET_RX_DEFAULT_PRIORITY=7
CONFIG_MULTITHREADING=y

Any idea how to fix it?

Kind regards

Jaroslav

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

mathiaso — Thu, 21 Aug 2025 08:29:49 GMT

Hi, Jaroslav.

I got some input from a colleague that you should use POSIX sockets. Have a look at the HTTPS Client and UDP samples for references.

Best regards,
Mathias

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

Jaroslav Havel — Thu, 21 Aug 2025 05:51:29 GMT

Hi Mathias,

I have some news, that can help us solve problem with TCP server. I also implemented the TCP server in another project based on the SoftAP example. It's a different project, based on the fact that the nrf7002-DK behaves as an AP, there is no scan, etc., but the implementation of my TCP server is the same.I found exactly the same behavior of the TCP server. In the case when the TCP server receives several messages, it is blocked (frozen). It does not accept any more messages on a specific connection with the client. The number of messages is smaller (about 4 to 5), this is because the buffer sizes are specified differently.

I think the problem arises with memory release.

The implementation of the server and callback for receiving data is the same as in the main post.

Kind Regards

Jaroslav

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

Jaroslav Havel — Wed, 20 Aug 2025 13:06:10 GMT

Hi Mathias,

I thing for start it will be hard to understand each other. Maybe it is because I am not able to decribe my problem. But I can send project (in .zip) or a video when I show issue. If you are interested, please give me some contact or link for send a video or complete project.

Kind regards

Jaroslav

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

Jaroslav Havel — Wed, 20 Aug 2025 12:56:54 GMT

Hi, Mathias,

if I tryied to use sockets, I got error (operation is not supported). So I decided to use net_context and it seems to me it works. I don't think it matters.Let's not talk now about why I don't use sockets but net_context, I need to get it working on net_context (although maybe converting it to sockets could be a solution).

My problem is that my server stops receiving data after I got maybe 20 messanges. After maybe 20 messanges, my TCP server is not able to receive any data. If I close connection with client and re-open it, I am able to receive new 20 messanges (maybe 20). After this, the connection freezes. Only if I re-open connectin with client, I am able to receive data (only 20 messages and them freeze).

I want to be able receive messages without any limit on the number (using TCP). Each message could be 8192 bytes length. Maybe 100 messages per minute per connection.

Personally, I think the problem is in memories, buffers and packets management. I don't really understand it, I think my buffers are overflowing and then the packets are being dropped, which is why the callback for the receive event is not triggered.

I attached my settings in my previous post (main post) and I would like to ask for your assessment of whether I am working correctly with memory, buffers, packets, etc. I am not very familiar with this yet.

Kind regards

Jaroslav

RE: TCP server (using net_context) running on nrf7002-DK in STA mode stopping receiving data

mathiaso — Wed, 20 Aug 2025 12:33:05 GMT

Hi, Jaroslav.

We'll do our best to help you.

Could you please specify again what your specific problem is?

[quote user=""]I am working with net_context architecture. I try to use sockets, but it doesn't work.[/quote]

What specifically doesn't work when you're trying to use sockets?

[quote user=""]I added function, that will disconnect client, that didn't send message for some time (maybe 30 seconds). If I do disconnection of client and I do new connection, data start flow (only maybe 20 messages). If you do net_context unref and put.[/quote]

Is it that you're only able to receive 20 messages before a disconnect occurs?

[quote user=""]Could you please help me solve this problem, I want to be able read any count of messages.[/quote]

Or is it a different number of messages you're able to receive before the disconnect occurs?

Best regards,
Mathias