Hello everybody. Since I have a lot of problems to get the TCP IP stack running on the CortexA53, I wanted to ask if there is someone who also uses it and has managed to get the TCP IP stack running. Used HW + SW: Zynq UltraScale+ Cortex a53 64 bit compiler Hope someone can help me

Hi Philipp, I think you can use the code you provided, if uncached memory is addressable by 32-bit word. I would propose you to add some verbose debugging print to emacps_check_rx to see more details about the received descriptor. I beleive this case is normal: ( xemacpsif->rxSegments[ head ].ad…

I think you can use the code you provided, if uncached memory is addressable by 32-bit word. How can I make sure that this is true? ( xemacpsif->rxSegments[ head ].address & XEMACPS_RXBUF_NEW_MASK ) == 0 i mean this leads that ethMsg is NULL. emacps_check_rx: unable to allocate a Network Bu…

“emacps_check_rx: unable to allocate a Network Buffer” I beleive it means lack of memory in TCP/IP stack. That is too general. The error message occurs when the pool of network buffers is empty. The total number of network buffers is determined by ipconfigNUM_NETWORK_BUFFER_DESCRIPTORS. Mind y…

[image] Mulle: How can I make sure that this is true? You can check addresses of memory returned by pucGetUncachedMemory(). Is it possible for you to share you current code? I got zcu104 board today, so able to help by direct debugging.

[image] htibosch: That is too general. The error message occurs when the pool of network buffers is empty. The total number of network buffers is determined by ipconfigNUM_NETWORK_BUFFER_DESCRIPTORS . Mind you that at start-up, ipconfigNIC_N_RX_DESC network buffers are needed for the DMA buffe…

Here are my code: main func: main.c (13.3 KB) NetworkInterface: NetworkInterface.c (16.0 KB) uncachedmemory: uncached_memory.c (3.7 KB) uncached_memory.h (568 Bytes) x_emacpsif_data: x_emacpsif_physpeed.c (27.0 KB) x_topology.h (1.5 KB) x_emacpsif.h (4.2 KB) x_emacpsif_dma.c (20.0 KB) x_emacpsif_h…

Hello @Maxim.Vechkanov and @htibosch , I was able to find out yesterday why he always comes into the break at this point: if (((xemacpsif->rxSegments[head].address & XEMACPS_RXBUF_NEW_MASK) == 0) || (pxDMA_rx_buffers[head] == NULL)) { break; } This happens because in XEmacPs_Start he checks …

Unlike the previous version, US+ GEM supports multiple queues. The pointers are set using XEmacPs_SetQueuePtr() function of Xilinx’s driver. Also, since it has more than one descriptors queue, it is mandatory to terminate all the queues which are not used by writing a BD with deasserted “new” and …

How does you change the code that you can ping? i can’t ping because of missing arp announcement.

FreeRTOS + TCP/IP on Arm Cortexa53

Kernel

Mulle (Philipp Mularczyk) July 6, 2020, 5:13pm 24

Yeah.
I will post it here tomorrow.

Xilinx ultrascale A53 Free RTOS + TCP /UDP

Topic		Replies	Views
FreeRTOS+TCP minor bug-finds Kernel	49	2244	March 13, 2015
FreeRTOS+TCP zero copy driver and statically allocated buffers Kernel	25	2091	November 14, 2021
FreeRTOS+TCP in AMD/Xilinx Vitis 2024 Libraries	58	1735	October 28, 2025
Xilinx ultrascale A53 Free RTOS + TCP /UDP Xilinx	14	2024	January 27, 2021
FreeRTOS+UDP Kernel	28	1206	March 29, 2015

FreeRTOS + TCP/IP on Arm Cortexa53

Related topics