• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 422 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Query regarding LWIP used by starterware of OMAPL138 for Ethernet Echo

Vaishak R
Intellectual 495 points
Other Parts Discussed in Thread: OMAPL138

Hi,

I'm able to successfully build the example code Ethernet Echo of Starterware.

But when debugging the code ,the code gets stuck in the function udp_bind()  function of Locator_Config and keeps searching for  / comparing for parameter passed struct udp_pcb *pcb with the list of struct udp_pcb *udp_pcbs.

Before udp_bind() is called , udp_new() and udp_recv() is getting called.

what does the struct udp_pcb *udp_pcbs contains , as it has been defined globally and it is not getting anything assigned to it in function udp_bind ?

 

  • 0
    TI__Mastermind 20790 points

    Vaishak,

    You see the udp_bind definition at the udp.c file (OMAPL138_StarterWare_1_10_03_03\third_party\lwip-1.3.2\src\core). Please check in that project is it used as a API call through lib.
    This function explains with this arguments as below,
    pcb: UDP PCB to be bound with a local address ipaddr and port.
    ipaddr: local IP address to bind with. Use IP_ADDR_ANY to bind to all local interfaces.
    port: local UDP port to bind with. Use 0 to automatically bind to a random port between UDP_LOCAL_PORT_RANGE_START and  UDP_LOCAL_PORT_RANGE_END.
    ipaddr & port are expected to be in the same byte order as in the pcb.

    I hope,You know how to debug in CCS using step into(F5 Key) for udp_bind call.

  • 0 in reply to Pubesh
    TI__Mastermind 20790 points

    Vaishak,

    You find the "third_party" folder which contains third party software modules that are used by the StarterWare applications. These modules are typically included directly in application builds as source instead of being compiled into static libraries.

    Here, udp_bind call used to binds the pcb to a local address. The IP-address argument "ipaddr" can be IP_ADDR_ANY to indicate that it should listen to any local IP address. The function currently always return ERR_OK.

  • 0 in reply to Pubesh
    Intellectual 495 points

    Hi,

    I have gone through the document provided by Swedish Institute of Computer Science in OMAPL138 Starterware.

    It provides the overview TCP/IP stack implemented by them .

    Can somebody suggest the code documentation for stack provided in the OMAPL138 Staterware.