Hello Sergio, I am using bare metal as well without OS and lwIP 1.4.1. So I don't see most of the functions being mentioned. Looks like I would need to bring 2.0.0.RC2 (quite some work). in my case I am using the drivers from TM4C. I checked and
psNetif->output = etharp_output; So what you are suggesting that I modify the etharp_output to process the LLDP transmit packet? Regards Amit On Wed, Aug 3, 2016 at 3:18 PM, Sergio R. Caprile <[email protected]> wrote: > I sent my response before you answered to Simon, so I couldn't know your > problem was in the output path without violating causality. I think some > states penalize that... ;^) > > When the stack needs to send a frame, it will call netif->output. That > pointer is usually setup at the init function for the netif driver (see > ethernetif_init()). My driver sets up etharp_output() for that, and I > followed the guidelines in the wiki link I sent you, I suggest you follow > that. I'm using bare metal, not an OS, and I don't remember if there is a > constraint for this (it is for input stage). > > Anyway, that will eventually call netif->linkoutput() which is what you > probably want to use. Remember you are using bare Ethernet over your driver > in your port; you are not (yet) using lwIP. > > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
