Re: [lwip-users] Debugging new driver

2013-06-06 Thread ella
Yes I put my traces after submitting packet to MAC DMA: SZ is payload size provided by lwIP as qbuf: /* Calculate frame length */ for( q=p; q!=NULL; q=q->next ) f_len += q->len; The DMA is not stuck so packets are leaving MAC. But I can't understand where are they

Re: [lwip-users] Debugging new driver

2013-06-06 Thread Pomeroy, Marty
Bastien I think the board side traces below indicate that 64 bytes are being sent: > 23.072 ETH:DMA_RX SZ:64 > 23.072 ETH:DMA_TX SZ:64 ... I'm assuming SZ is size. Marty -Original Message- From: lwip-users-bounces+martypomeroy=novabio@nongnu.org [mailto:lwip-users-bounces+ma

Re: [lwip-users] Debugging new driver

2013-06-06 Thread Pomeroy, Marty
Ella I'm working from memory here, and don't have time to try it. As I recall, Wireshark helped me find that my checksums were off. So yes, I think in promiscuous mode wireshark will show you bad packets and what is wrong with them. Marty -Original Message- From: lwip-users-bounces+mar

Re: [lwip-users] Debugging new driver

2013-06-06 Thread ella
HI, Will I catch a packet even it has some broken checksum or other fields? -- View this message in context: http://lwip.100.n7.nabble.com/Debugging-new-driver-tp21519p21525.html Sent from the lwip-users mailing list archive at Nabble.com. ___ lwip-u