stm32h563 Azure RTOS Netx Multihome Support

Eren Akyol 0

Hello, I have created and executed a TCP server project with Azure NetX library using Ethernet. Additionally, I need multihome support in this project. I want multiple clients to connect to a device with a single IP. Can you assist me with this?

status = _nx_ip_interface_attach(&ip_0, "port_2", IP_ADDRESS(0, 0, 0,0), 0xFFFFFF00UL, my_netx_driver);

Function is not working. You can look at the https://learn.microsoft.com/en-us/azure/rtos/netx/netx-dhcp-client/chapter2

Best regards, Eren Akyol

LeelaRajeshSayana-MSFT 16,786 Reputation points

2024-02-01T20:07:48.54+00:00

Hi @Eren Akyol Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

I am checking to see if you have looked into the sample demo_netx_duo_multihome_udp.c which provides details implementing the functionality. It would be helpful if you can share any specific errors you are facing with the implementation so that the community members and SMEs can better guide you overcome this issue.

Eren Akyol 0

/////////////////////////TCP Server Not Working Position//////////////////////////////

.
.
.

  ret = nx_ip_create(&NetXDuoEthIpInstance, "NetX Ip instance", IP_ADDRESS(192, 168, 0, 28), NX_APP_DEFAULT_NET_MASK, &NxAppPool, nx_stm32_eth_driver,
                     pointer, Nx_IP_INSTANCE_THREAD_SIZE, NX_APP_INSTANCE_PRIORITY);

  if (ret != NX_SUCCESS)
  {
    return NX_NOT_SUCCESSFUL;
  }

    /* Allocate the memory for ARP */
  if (tx_byte_allocate(byte_pool, (VOID **) &pointer, DEFAULT_ARP_CACHE_SIZE, TX_NO_WAIT) != TX_SUCCESS)
  {
    return TX_POOL_ERROR;
  }

  /* Enable the ARP protocol and provide the ARP cache size for the IP instance */

  /* USER CODE BEGIN ARP_Protocol_Initialization */
  /* Attach the second interface to IP_0. Note that this interface is attached during initialization time.
     Alternatively the second interface may also be attached in thread context, as illustrated below
     in thead_0_entry function. */
  ret = nx_ip_interface_attach(&NetXDuoEthIpInstance, "IP_0 Secondary Interface", IP_ADDRESS(193, 168, 0, 28), 0xFFFFFF00, nx_stm32_eth_driver);

  if (ret)
  {
	  while(1){

	  }
  }
  /* USER CODE END ARP_Protocol_Initialization */

  ret = nx_arp_enable(&NetXDuoEthIpInstance, (VOID *)pointer, DEFAULT_ARP_CACHE_SIZE);

  if (ret != NX_SUCCESS)
  {
    return NX_NOT_SUCCESSFUL;
  }
  
.
.
.

/////////////////////////TCP Server Working Position//////////////////////////////

.
.
.

  ret = nx_ip_create(&NetXDuoEthIpInstance, "NetX Ip instance", IP_ADDRESS(192, 168, 0, 28), NX_APP_DEFAULT_NET_MASK, &NxAppPool, nx_stm32_eth_driver,
                     pointer, Nx_IP_INSTANCE_THREAD_SIZE, NX_APP_INSTANCE_PRIORITY);

  if (ret != NX_SUCCESS)
  {
    return NX_NOT_SUCCESSFUL;
  }

    /* Allocate the memory for ARP */
  if (tx_byte_allocate(byte_pool, (VOID **) &pointer, DEFAULT_ARP_CACHE_SIZE, TX_NO_WAIT) != TX_SUCCESS)
  {
    return TX_POOL_ERROR;
  }

  /* Enable the ARP protocol and provide the ARP cache size for the IP instance */

  ret = nx_arp_enable(&NetXDuoEthIpInstance, (VOID *)pointer, DEFAULT_ARP_CACHE_SIZE);

  if (ret != NX_SUCCESS)
  {
    return NX_NOT_SUCCESSFUL;
  }
  
.
.
.

//////////////////////////////////////////////////////////////////////////////////////
First of all, thank @LeelaRajeshSayana-MSFT for your return

In the example I shared above, I simply add the "nx_ip_interface_attach" function to the running code and see the rejection variable that is the result of this function as NX_SUCCESS.
So the code does not hang in while(1). However, no connection can be established on the TCP Client side. When I do not add this function, I can connect with TCP Client.
What can be the problem?

1 answer

Eren Akyol 0 Reputation points

2024-06-23T15:22:27.4166667+00:00

Hello,

I couldn't run the code you provided. In fact, I'm not sure about the problem itself. In my project, I have a TCP/IP server application running. My main problem is that only one client can connect to the same IP and port at the same time. My project requirement is that multiple clients should be able to send queries to the same IP and port. I can achieve this structure with LWIP, but I couldn't set up the same structure with Azure RTOS NetX. One client works without a problem, but multiple clients cannot send queries. What can we do about this? Is there another community that can solve this problem?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

stm32h563 Azure RTOS Netx Multihome Support

1 answer

Your answer