Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread goldsi...@gmx.de
Amena El Homsi wrote: For the outgoing packets, in low_level_output() function, We copy the headers from the pbuf RAM to the frame memory and we inform the HW of the address of the frame to be sent. Then HWMAC will send the frame over the air and after it is successfully sent and the ACK is

[lwip-users] Fragmented UDP package not triggering socket select

2017-11-15 Thread Bram Peeters
Hi, I am running into a strange problem where my application is waiting for data to arrive on and UDP socket via an (lwip_)select call, and it works fine if an ipv4 UDP packet with 828 bytes is send , but nothing happens when a fragmented (1480 + 43) packet arrives although the destination

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Amena El Homsi
For the outgoing packets, in low_level_output() function, We copy the headers from the pbuf RAM to the frame memory and we inform the HW of the address of the frame to be sent. Then HWMAC will send the frame over the air and after it is successfully sent and the ACK is received, HWMAC send us the

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread goldsimon
Amena El Homsi wrote: >> I tried to explain that before. Your ROM is not ROM. Data must be >kept >> unchanged until it is actually sent. How do you ensure this?? >> >Our System will take care of this, Data will be kept unchanged until it >is >actually sent. Headers are copied from the Pbuf_RAM

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Amena El Homsi
On Wed, Nov 15, 2017 at 3:15 PM, Simon Goldschmidt wrote: > Amena El Homsi wrote: > > Actually I had this understanding from this link http://www.nongnu.org/ > lwip/2_0_x/group__pbuf.html > > That page says "PBUF_ROM: pbuf data is stored in ROM". Could you tell us > from which

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Simon Goldschmidt
Amena El Homsi wrote: > Actually I had this understanding from this link  > http://www.nongnu.org/lwip/2_0_x/group__pbuf.html That page says "PBUF_ROM: pbuf data is stored in ROM". Could you tell us from which line on that page you have your understanding from? >  and from the Dunkels book "

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Amena El Homsi
On Wed, Nov 15, 2017 at 1:22 PM, Simon Goldschmidt wrote: > Amena El Homsi wrote: > > What I know is PBUF_ROM doesn't mean the actual ROM (stable for very > long) but it > > means that the data is immutable and it is located in memory which is > not managed > > by the pbuf

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Simon Goldschmidt
Amena El Homsi wrote: > What I know is PBUF_ROM doesn't mean the actual ROM (stable for very long) > but it > means that the data is immutable and it is located in memory which is not > managed > by the pbuf system. Am I wrong? Yes, you are wrong. ROM means stable for very long, not const :-)

Re: [lwip-users] Packet queuing to an ARP table entry

2017-11-15 Thread Amena El Homsi
Hi Simon, Thanks for you Reply! We are working on designing Low power Wireless SoC. We have few restrictions concerning the memory usage. Our memory system is divided in: 1. Instructions memory 2. Data memory 3. Frame memory Incoming and Outgoing frames should be saved in frame

Re: [lwip-users] Receiving data with lwip raw API

2017-11-15 Thread Simon Goldschmidt
Giuseppe Modugno wrote: > I tried to study httpd code and it's not clear to me. If > LWIP_HTTPD_SUPPORT_REQUESTLIST is defined, code that supports receving > data in multiple pbufs is enabled. > [..] > I don't understand why saving all the received pbufs until all data are > received. Why don't