contiki-ng
uip
contiki-ng | uip | |
---|---|---|
2 | 5 | |
1,255 | 871 | |
1.7% | - | |
9.7 | 0.0 | |
6 days ago | over 7 years ago | |
C | C | |
BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
contiki-ng
- Ask HN: Are there any lean operating systems left?
-
I need to create a UDP server using uIP library on LPC1768. could you please share a code example with me or lead me to write it myself? thank you so much
As the other commenter pointed out, uIP seems to be from 9 years ago. From the issues in the project, I found it is part of Contiki. Are you developing using Contiki?
uip
- Show HN: MicroTCP, a minimal TCP/IP stack
-
I need to create a UDP server using uIP library on LPC1768. could you please share a code example with me or lead me to write it myself? thank you so much
As the other commenter pointed out, uIP seems to be from 9 years ago. From the issues in the project, I found it is part of Contiki. Are you developing using Contiki?
- Need help to use uIP library for running UDP on LPC1768
-
An HTTP server in a single .c file
The CPU architecture is actually the least of your concerns there—I'm pretty sure qemu-user can run httpdito on ARM with less than an order of magnitude performance overhead. There are a lot of embedded systems where an HTTP transaction per second per MHz would be more than sufficient.
The bigger problem is that the Raspberry Pico is a dual-core Cortex-M0+, which doesn't have an MMU, so it can't run Linux and especially can't handle fork(). But httpdito is basically scripting the Linux system call interface in assembly language—it needs to run on top of a filesystem, an implementation of multitasking that provides allocation of different memory to different tasks, and a TCP/IP stack. Any one of these is probably a larger amount of complexity than the 296 CPU instructions in httpdito.
The smallest TCP/IP stack I know of is Adam Dunkels's uIP. Running `sloccount .` in uip/uip cloned from https://github.com/adamdunkels/uip gives a count of 2796 lines of source code ("generated using David A. Wheeler's 'SLOCCount'."). uIP can run successfully on systems with as little as 2KiB of RAM, as long as you have somewhere else to put the code, but for most uses lwIP is a better choice; it minimally needs 10KiB or so. uIP is part of Dunkels's Contiki, which includes a fairly full-featured web server and a somewhat less-full-featured browser. I think he got both the server and the browser to run in 16KiB of RAM on a Commodore PET, but not at the same time.
(twIP http://dunkels.com/adam/twip.html is only 139 bytes of C source but doesn't support TCP or any physical-layer protocol such as Ethernet, PPP,or SLIP.)
However, Adam Dunkels has also written Miniweb http://dunkels.com/adam/miniweb/, which implements HTTP and enough of TCP and IP to support it, in 400 lines of C. It needs at least 30 bytes of RAM. Like twIP, it doesn't provide a physical layer. But that's solvable.
-
uIP's network device driver (and Contiki's version of uIP)
I am currently reviewing existing TCP/IP stacks for microcontrollers, and in particular uIP.
What are some alternatives?
Tasmota - Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
darkhttpd - When you need a web server in a hurry.