This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C1294NCPDT: Ethernet Issue standard query MDNS protocol

Part Number: TM4C1294NCPDT

Tool/software:

Hi team,

I am currently working with the TM4C1294NCPDT microcontroller's Ethernet peripheral for high-speed data transmission. While the continuous data transfer generally works, I am encountering an issue where the transmission suddenly gets stuck.

Here are the specifics of the situation:

  • Source Address: 192.168.1.1
  • Destination Address: Broadcast 192.168.1.255

During the time when the data transmission gets stuck, I receive an mDNS response, after which data transmission ARp will sending.

.

How to increase the Stack Size in lwip ?

Then what we can do.....!

Thanks & Regards

Aravind.S.R

  • While the continuous data transfer generally works, I am encountering an issue where the transmission suddenly gets stuck.

    Hi,

      You are not providing enough information to diagnose the problem. They only thing I see is that the transmission is stuck after running for a while.

      How long after running did you see the transmission stuck?

      How large is the UDP datagrams you are trying to transmit?

      You seem to suggest that the data is going out of the LAN because the destination is a broadcast address? What if you are transmitting within the same LAN subnet?

    How to increase the Stack Size in lwip ?

    At the processor level you can increase the stack and heap size using CCSunder the Arm linker options. Below is an example to set the processor stack size to 2048. You can also change the heap size if you need to. I'm not sure if your problem is related to the processor stack size or not. 

    At the lwip level, there are various options to configure the memory in the lwipopts.h file. You can play with them. For example you can uncomment MEMP_NUM_UDP_PCB and change to a larger value. The default is 4 if MEMP_NUM_UDP_PCB is not defined. Check the other options in lwipopts.h file. 

    #define MEMP_NUM_UDP_PCB 4

      

  • Hi Charles,

              

    We are encountering in our project, which involves data transmission using the LWIP stack with the UDP protocol.

    1. Source IP Address (Board): 192.168.1.1
    2. Destination IP Address (Board): 192.168.1.255 (Broadcast)
    3. Monitoring Laptop IP Address: 192.168.1.50

    We have configured our system to continuously transmit data from the board to the monitoring laptop or pc. The data transmission works correctly some time; however, we face intermittent issues when the laptop or pc provides mDNS (Multicast DNS) services to the board. During these instances, data transmission errors occur, causing interruptions.

    This problem is not consistent across all systems. While some systems continue to transmit data 

    Thanks & Regards.

    Aravind.SR

  • I don't know the cause to your problem. I have a few questions. 

    - If there is no MDNS then the board will continue to transmit? Is that correct? In another word, the board will only get stuck after a MDNS and you have not found other circumstances the board will get stuck.

    - When it gets stuck, and if you use the debugger to examine the processor, where is the code stuck at? 

    - You said the problem is not consistent across all systems. Does that mean you have other boards running the same firmware will not get stuck when MDNS is sent out by the PC? Please confirm.

     - You seem to be sending 1240 bytes of datagram continuously using UDP. For experiment purpose, does it make a difference if you reduce to lower payload?