Re: [lwip-users] ip_addr_copy alignment issue

2017-10-08 Thread Ran Shalit
=/com.arm.doc.faqs/ka15414.html Regards, Ran On Tue, Sep 26, 2017 at 1:14 PM, Ran Shalit wrote: > Dirk, > > Thanks a lot for the idea with the compilation flag. > That was the key. I wasn't familiar with this feature before. > > Best Regards, > Ran > > On Sun, Sep 24, 20

Re: [lwip-users] ip_addr_copy alignment issue

2017-09-26 Thread Ran Shalit
> > Ciao > Dirk > > > On Sun, Sep 24, 2017 at 2:47 PM, Ran Shalit wrote: >> >> Hello, >> >> I get stuck in ip_addr_copy when called by ip_input. >> I am using MEM_ALIGNMENT 4, and packed structs. >> I tried many stuff, but nothing yet helped. &

Re: [lwip-users] ip_addr_copy alignment issue

2017-09-25 Thread Ran Shalit
Hello, There seems to be a checksum issue that prevented a scussful ping. (although it looked OK in wireshark) After disabling CHECKSUM_BY_HARDWARE (for some reason it was defined) , it works without any issues now. Best Regards, Ran On Mon, Sep 25, 2017 at 10:31 AM, Wayne Uroda wrote: > Hi Ra

Re: [lwip-users] ip_addr_copy alignment issue

2017-09-25 Thread Ran Shalit
I've found that IAR use similiar flag; --no_unaligned_access. So, now I get progressed , and see packes recieved and send. Yet, for some reason althoyugh everything looks without errors in wireshark, I get "request time out" for ping from PC. I tried to ping from several PC but it didn't help. Can

Re: [lwip-users] ip_addr_copy alignment issue

2017-09-24 Thread Ran Shalit
flag that tells the compiler it can assume this > capability (sorry forgot the name of the flag, something like > -munaligned-access, google it). Maybe this points you in the right > direction. > > > Ciao > Dirk > > > On Sun, Sep 24, 2017 at 2:47 PM, Ran Shalit wr

Re: [lwip-users] ip_addr_copy alignment issue

2017-09-24 Thread Ran Shalit
Hello, I would like to add that I did the same porting with latest release 2.0.3, yet I get the same problem (get stuck in ip_addr_copy_from_ip4) Best Regards, Ran On Sun, Sep 24, 2017 at 3:47 PM, Ran Shalit wrote: > Hello, > > I get stuck in ip_addr_copy when called by ip_input. >

[lwip-users] ip_addr_copy alignment issue

2017-09-24 Thread Ran Shalit
Hello, I get stuck in ip_addr_copy when called by ip_input. I am using MEM_ALIGNMENT 4, and packed structs. I tried many stuff, but nothing yet helped. If I try MEM_ALIGNMENT 1, I get stuck in much earlier phase. I'm using lwip 1.4.1 , which is a stable release as I understand. Is there any idea

[lwip-users] memp_malloc: out of memory in pool

2017-09-20 Thread Ran Shalit
Hello, I am trying to port lwip to uc/os (I use lwip 1.4.1). But I get on packet recieve, immediately at first try "out of memory in pool " error as following: " pbuf_alloc(length= 96) memp_malloc: out of memory in pool PBUF_POOL pbuf_alloc: allocated pbuf 0" I observed memp_malloc(memp_t) rout

[lwip-users] Alignment issue in etharp_raw() ?

2017-09-10 Thread Ran Shalit
Hello, I have issue on using lwip (1.3.1) porting for uc/os . It seems that the OS hangs on executing : etharp_raw()-> hdr->dipaddr = *(struct ip_addr2 *)ipdst_addr; On further investigation, it seems that the problem is that ipdst_addr is not 4 byte aligned but only 2 byte aligned (address

Re: [lwip-users] malloc limitation

2017-09-06 Thread Ran Shalit
On Wed, Sep 6, 2017 at 3:26 PM, Patrick Klos wrote: > On 9/6/2017 1:55 AM, Ran Shalit wrote: >> >> Hello, >> >> I porting lwip into uc/os, but noticed that lwip use malloc() >> operation, and I have limitation with this OS, thet malloc is limited >> to

[lwip-users] Received packets thread

2017-09-06 Thread Ran Shalit
Hello, Our Ethernet driver does not provide interrupt, and can only use polling. I though that I can use rx thread as part of the threads created with sys_thread_new. But I am not sure about its priority related to tcpip thread , and the rate for polling if there is new received packet. Is there

[lwip-users] malloc limitation

2017-09-06 Thread Ran Shalit
Hello, I porting lwip into uc/os, but noticed that lwip use malloc() operation, and I have limitation with this OS, thet malloc is limited to 4045. Does it mean that it might fail ? Thank you, Ran ___ lwip-users mailing list lwip-users@nongnu.org https