CMX-MicroNet

To receive literature  fill in request

CMX System's  high level TCP/IP stack CMX-MicroNet will work with virtually all 8, 16 and 32-bit processors while only needing the minimum of ROM and RAM.   

This stack executes directly on the microcontroller generating SLIP, PPP and modem protocols via its UART.  Ethernet drivers are available for most common on chip interfaces providing fast local networks and good PC interaction.  No proprietary protocols, intermediate gateways or special hardware is required to use MicroNet.

Most developers using the popular 8- and 16-bit processors, as well as users of 32 bit single chip systems such as ARM and ColdFire, had given up hope of ever achieving networked communication with their products because most stacks were simply too big. MicroNet provides  these protocols running natively on even the smallest of 8 bit micros which means that now you have an economical solution to networking, especially for devices that will be running in remote locations.

How is it done ?

Well first of all this stack was written from scratch with embedded systems in mind.

Secondly the majority of applications that it will be used for will involve the development of code for both ends of the application by the same team or the use of a standard such as a browser.  Because of the level of control that this gives there are a significant number of infrequently used ( yet memory hungry ) aspects of the full TCP/IP spec which can be left out in order to keep code size down. To reduce the space overhead fragmented packets are available as an option and without it the "sliding window" option used for large blocks of data is not supported.  PPP can negotiate IP addresses and handle PAP passwords but other options are ignored.  CMX-MicroNet can run under a real time operating system such as CMX-RTX  but it does not need an RTOS and will run quite happily without one.

CMX-MicroNet was the first system available that allows TCP/IP and other protocols to be run natively on small processors, thereby enhancing design flexibility and cost effectiveness.

Why use TCP/IP as my protocol?
Using one of the TCP/IP family of protocols next time you need to communicate with or between micros makes a lot of sense.  For one thing it saves you re-inventing the wheel.  Once you are using TCP/IP you can easily take advantage of a whole group of higher level protocols that build on their foundations such as PPP, FTP, HTTP and POP3.

Whats provided

CMX-MicroNet can operate stand alone or in conjunction with an RTOS.  It provides support for multiple Sockets, TCP, PPP, UDP, SLIP, and IP with Ethernet, PPP, DHCP, TFTP, BOOTP, FTP, SMTP, SNMP and HTTP Web Server being options.  Requesting a web page can result in the display of information from the micro and mechanisms are supplied to input values and invoke functions.  Connectivity is currently supported for Dial Up or Direct serial connection as well as a number of different Ethernet chips and Wireless Ethernet for the Intersil Prism chipset.

No proprietary protocols, gateways, or hardware is required to use the system.  Source code is supplied and no license fee is required to create unlimited ROMs for a single application.  It has been designed for ease of porting to DSPs.

CPU's Supported plus some other legacy and specialist chips