Thanks Marty,
I should have mentioned what version of lwip lib I use.
StellarisWare 10363 which is latest version still uses lwip1.3.2, so I
don't see the first line "mpcb->recv()", but I see the second line
inside udp_input() in udp.c.
I need to look over how/when arguments are filled up. pc
>> My question I don't see any arguments passed to callback functions :
udp_recv() and TFTPRecv().
>> How are the arguments going to be filled up and by whom??
Jin
After review of the udp.c code, it looks to me that udp_recv is a setup
function (not a callback...), and you use it to tell lwI
Hi all,
Hi,
I am now looking at qs-checkout example provided by StellarisWare10636.
The procedure of calling udp_recv() is below:
1. call TFTPQSInit(void) in tftp_qs.c
TFTPQSInit(void)
{
//
// Initialize the TFTP module and pass it our board-specific GET and PUT
// request handle
