| Question : Is NexGenIP® compatible with any OS? |
Yes. NexGenIP® uses generic functions that are exported from NexGenOS®
which, in its turn, wraps these functions around those exported by the used OS or RTOS, and in this way NexGenIPreg; does not depend on any specific architecture.
Once the product has been compiled for a particular processor, it can be delivered either as a binary library or as source code. When supplied as a binary library, the user can port NexGenIPreg;
to an OS or add specific drivers since these features are handled in NexGenOS®, i.e. in the low-level layer interface.
For more information, please check the technical support section of NexGenOS®.
|
| Question : What is a typical size for NexGenIP®? |
NexGenIP® is carefully layered. Thus, if your application requires only UDP, IP , ICMP, ARP, and Ethernet, only these features need to be linked. Each software layer has a clean implementation
and can be seen as a separate module, able to work with the other modules but there are no direct dependencies between them.
Depending on the chosen features, NexGenIP® needs between 24 KO and 60 KO for the code and at least 4 KB of RAM. Additional RAM might be necessary, depending on the application requirements (buffer size and number of sockets).
All sizes mentioned apply to ARM7's Thumb architecture.
|
| Question : Can NexGenIP® be used without an OS? |
Yes. NexGenIP® is configured at compilation and then generated for your environment. If you do not have an OS, the NexGenOS® low-level layer directly interfaces
the hardware and NexGenIP® activates an internal function which will be called each time your application is dealing with the socket interface.
|
| Question : How many tasks are required in RTOS mode? |
NexGenIP® requires 2 tasks. The first one to enqueue the packets and the second one to deal with a timer used for some protocol retransmissions.
All other resources depend on the application. Generally one task is necessary for each connection, but through the select mode it is also possible to have multiple connections using only one socket.
|
| Question : What protocols are supported? |
NexGenIP® has been built according to the relevant RFCs and consequently supports TCP, UDP, IP, ICMP, IGMP, ARP, and different link-level layers, such as Ethernet and PPP (Point-to-Point).
An asynchronous socket interface and a BSD 4.4 soket-like interface have furthermore been added. Additionnal features, like Multicast and Selective ACKnowledge, are available in NexGenIP® version 1.3b.
|
| Question : How is NexGenIP® delivered? |
NexGenIP® is delivered either as a binary library or in well-commented source code. In both cases, NexGenOS®
is delivered in source code for the OS and drivers as well as their dependencies, and thus even with the binary library a user can integrate NexGenIP® into its own environment.
The provided documentation includes a programming manual and if the source code is ordered a specification/implementation guide is delivered on demand.
|
|
