Porting picoTCP HW

PicoTCP can run on several different hardware architectures and can be integrated with virtu- ally any operating system or within a standalone application. It is possible to run PicoTCP on big-endian as well as little-endian CPU configurations. PicoTCP uses gcc-specific tags that may not be compatible with other compilers. The amount of resources needed may vary depending on the modules that are compiled-in. However, adapting to a specific hardware platform or for a particular use may require some integration effort.

Warning:

ensure that the license of your Board Support Package (BSP) is compatible with the license of PicoTCP you are using before distributing any derivative works.

PicoTCP relies on a simple set of system-specific calls that must be implemented externally from the target. Briefly, the interface needed for the stack to run is composed by:

• A mechanism to allocate memory dynamically on the target (malloc/free)
• A stable, monotonic time source variable, in milliseconds, to update internal timers

For the memory allocation interface, two symbols have to be defined by the system:

• void *pico_zalloc(uint32_t size) - memory allocator that allocates an object of the given size and set its content to 0

• void pico_free(void *ptr) - memory deallocator