AzureRTOS Nx_TCP_Echo_Server on NUCLEO-H743ZI2

[Irek]

Hello everyone,

I use the NUCLEO-H743ZI2 board in my project and previously, Before I've used the MBed OS - it works well on this board, just I need to maximize TCP transfer speed as well as QSPI. So I decided to try another RTOS. After reading forums, I decided to try the Azure RTOS and Cube IDE. I chose the Nx_TCP_Echo_Echo_Server example as a starting point. I reconfigured it to use with NUCLEO-H743ZI2, and also I disabled DHCP as I don't need it. Also added plenty of printf functions at different steps in the app_netxduo.c. As result project can be build, and I see next messages in Terminal:

The network cable is connected.
nx_ip_interface_status_check == NX_SUCCESS.
nx_ip_address_set == NX_SUCCESS.
nx_tcp_socket_create == NX_SUCCESS .
nx_tcp_server_socket_listen == NX_SUCCESS .
TCP Server listening on PORT 5000
STM32 NX_APP_DEFAULT_IP_ADDRESS: 192.168.0.200
Next is the tx_semaphore_get

Then I try to ping the board I see the blinking LED on the Ethernet connector of the board but I get :

Ping statistics for 192.168.0.200:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Thus, it looks like the function

static VOID tcp_listen_callback(NX_TCP_SOCKET *socket_ptr, UINT port)
{
tx_semaphore_put(&TCPSemaphore);
}

never called.

I already spent two days trying to find solutions. All receipts which I found - like
https://community.st.com/t5/stm32-mcus/ethernet-not-working-on-stm32h7x3/ta-p/49479
I implemented them - the result is the same.

Does anyone have any idea where is the problem?
Thanks in advance.

[Irek]

---

@matt-crc 

---

Thank you for your recommendations - but if you briefly read my posts in this thread, you will find that I already tried many things. When I decided to change MBed Os to another RTOS, I have spent some time and read plenty of forums - so the choice of Azure RTOS was made after thought. But after 10 days of trying, I still haven't made any progress with quite simple task - make a TCP server. So I'd like to stay on Azure, but I don't know how I'm going to get a working configuration for my board yet. 

[mbarg.1]

Wold help if I can provide a reference design from where you can start?

[Irek]

---

@mbarg.1 wrote:

Wold help if I can provide a reference design from where you can start?

---

It will be very useful! I have ordered Nucleo-H723 for testing, but the H743ZI2 boards are already in the devices, so it will be good to use them.
Thank you in advance!

[Irek]

By the way, I succeed to start on H743ZI2 board the STM32_Nucleo_H723ZG_FreeRTOS_TCP example. 

I can ping my board and get response from TCP server.
But still, Azure RTOS seems more attractive...

[mbarg.1]

OK.

PLEASE:

• Open a new (empty) workspace;
• import this project;
• compile and build - you will get one warning, I excluded watchdog to enable easier debugging;
• Debug - you should get a welcome message on serial line - I use Putty, works with everything
• Look at NetXDuoEthIpInstance in Live Expression - you can see your MAC, IP and ongoing activity
• Try ping - should work.

Now you can have a look at the code - there are many lines which are part of our modular environment and you can remove them easily.

[Irek]

Thank you, Mike!

I successfully imported your project, compiled it - it was some minor problems, but finally as you wrote it was only one warning. I build project and run in debug mode. As result, I got response in the Putty, I also see some activity of the board in Wireshark, I found the IP address as you pointed out - and result, board do not respond to this IP. :( Disappointing. 

See attached screenshots.

So I am going to return to Azure RTOS when I got NUCLEO-H723ZG board. For now, I lost enough time. 

Once again for your help! 
With best regards, Irek

[mbarg.1]

Irek:

It looks like your STM32CubeIde installation is corrupted - indexer errors usually come from this - or did you use a non empty workspace or you do not have corect permission or an antivirus is blocking something...

By sure, NetXDuoEthIpInstance values does not make any sense, i do not believe you are on an non-local network.

Check what is going on in your environment or you will have same problems with H723.