Re: [lwip-users] Problem: new socket (lwip 1.3 + freeRTOS 5.3)

2010-01-29 Thread Kieran Mansley
On Fri, 2010-01-29 at 06:34 -0800, acemax wrote: > I wanted to use the BSD Socket API. Portability reason. But I still think that the most likely explanation is not initialising the stack correctly. Perhaps you could show us your code that does that? Kieran ___

Re: [lwip-users] Problem: new socket (lwip 1.3 + freeRTOS 5.3)

2010-01-29 Thread acemax
It works when I use the netconn API: struct netconn *conn; char msg[]="testing" ; struct netbuf *buf; char * data; conn = netconn_new( NETCONN_UDP ); netconn_bind(conn, IP_ADDR_ANY, 1234 ); netconn_connect(conn, IP_ADDR_BROADCAST, 1235 );

Re: [lwip-users] Problem: new socket (lwip 1.3 + freeRTOS 5.3)

2010-01-28 Thread Kieran Mansley
On Wed, 2010-01-27 at 03:47 -0800, acemax wrote: > [Avatar] > 2010-01-26 21:07:59 UTC > Hello, > > I'm trying to implement the code below, but it stops in the line sock = > socket(AF_INET, SOCK_DGRAM, 0); > > the message is "sys_arch_timeouts: ptask != NULL" I would guess you haven't properly in

[lwip-users] Problem: new socket (lwip 1.3 + freeRTOS 5.3)

2010-01-27 Thread acemax
[Avatar] 2010-01-26 21:07:59 UTC Hello, I'm trying to implement the code below, but it stops in the line sock = socket(AF_INET, SOCK_DGRAM, 0); the message is "sys_arch_timeouts: ptask != NULL" the procedure sequence is: -lwip_socket (type=0, protocol=100) -alloc_socket (newcon=0x80173c) -sys_