[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RE : [lwip-users] Project based on lwip - design strategies

From: Marko Panger
Subject: Re: RE : [lwip-users] Project based on lwip - design strategies
Date: Wed, 03 Oct 2007 12:32:27 +0200
User-agent: Thunderbird (Windows/20070728)


I have my own written RTOS with mailboxes, events, semaphores,.... The only part that required kernel modifications was adding the pointer to the "struct sys_timeouts" structure in the task control block. In summary it took me about 5 days (few hours of night work :)) to get familiar with all files, setup and porting the sys_arch.c file and to implement a SLIP connection on windows. Now I'm able to ping my device. Next stem is to bring up a PPP conenction and to understand how the netconn API works. I will use netconn as is a good compromise between performance and development speed.


address@hidden wrote:

I implemented a gprs based remote maintenance on our freescale power pc architecture with an ENEA OSE realtime OS for my final PGDip work. This OS is so braindead in my opinion that it was to complicate to write some os system call mailbox wrappers in the sys_arch.c. Therefore I decided to use the callback API with NO_SYS defined. With this approach I guess I saved some weeks of painful porting. Perhaps it depends on the OS, at least there are some less braindead OS around. I had a look to the uc/OS-II from Labrosse and found some sys_arch.c using uC/OS-II. But unfortunately I can't provide you this port. Try to find a uc/OS-II sys_arch.c this will give you good ideas and a good starting point.



lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]