embedded Libs - Frequently Asked Questions

General

  • Must I use the version of FreeRTOS provided?
  • No, you don't. embTCP and embDUAL carry the version used for our development and testing, but as we only used the published API you should be able to more current releases. Of course, be sure to read the OS's upgrade notes and watch for changes in structure sizes before you use newer versions of FreeRTOS.
  • I don't see my chosen CPU listed on this site? When will embLibs be available?
  • Please contact InterNiche with your requirements.
  • Can I use an Operating System other than FreeRTOS?
  • To run on on different chips or using different operating systems, please contact InterNiche to discuss the availability of source code modules.
  • How do I access technical support for my embedded library?
  • Send an email to embSupport@iNiche.com and be sure to include the PRODUCT_CODE for your particular product. This 16 hex character string can be found in your xxxxdata.h file.
  • I do not see any way to add the library to a shopping cart. How can I license an embedded library?
  • These pages are strictly informational. To acquire a particular product, please select one of the sites listed in the 'Distributed By' details for the particular module that interests you.
  • Node Locked?
  • By restricting our libraries to particular components, you can be sure that it was tested on the specific component you decide to include in your product. No guessing about whether it will work on Chip XYZ, since we have tested it and "it will".
  • How much memory do these products require?
  • The specific page for each supported chip:tool combination includes the Code space required by each library as well as some empirically-derived RAM usage. In the case of an embTCP or embDUAL package, the Code calculations also include the Ethernet driver, BSP and size of the default RTOS configuration.
  • My question does not seem to be answered here. Where can I get more information?
  • The Embedded Libraries were developed by InterNiche Technologies, which will promptly respond to your questions. (Just be sure to provide your proper email address :)

TCP

  • If I decide to 'upgrade' from the TCP product to the DUAL, will my add-on embLib products still work?
  • Yes. If both TCP and DUAL libraries are available, then the HTTP, FTP and Telnet servers are all IPv4 and IPv6 capable.
  • [How] can I reduce the ROM and RAM requirements of the library?
  • As is described in the documentation, look closely at the tcpdata.c file. It contains array dimensions which can be reduced, capabilities which can be disabled and also references to menu commands which can be omitted.

DUAL

  • Can I run either IPv4 or IPv6, or must I run both?
  • Either at compile-time or init-time, you may specify which protocols are enabled.
  • If I enable both IPv4 and IPv6, do they really run at the same time?
  • Yes. The HTTP, FTP and Telnet libraries all serve both AF_NET and IF_INET6 sockets simultaneously, and so can your custom applications.
  • [How] can I reduce the ROM and RAM requirements of the library?
  • As is described in the documentation, look closely at the tcpdata.c file. It contains array dimensions which can be reduced, capabilities which can be disabled and also references to menu commands which can be omitted.

HTTP

  • How do I hook the library to my file system?
  • The product has a familiar fopen(), fclose()-type API which can be easily mapped to your own file system's library. The example provided with the product demonstrates this quite nicely.
  • Does the product come with working examples of how to process forms?
  • Yes. It also includes examples of how an application can create and present dynamic content.

FTP

  • How do I hook the library to my file system?
  • The product has a familiar fopen(), fclose()-type API which can be easily mapped to your own file system's library. The example provided with the product demonstrates this quite nicely.

TELNET

  • How many simultaneous telnet sessions will embTELNET support?
  • The number of connections are controlled by a compile-time configuration parameter contained in the file telnetdata.c.