Specifically optimized for DSP systems, this stack can operate as a background process using only the remaining processing time after all other tasks are completed, and thereby not influencing the real-time performance of the DSP system. Does not require an underlying operating system, but can be used in a preemptive or cooperative RTOS environment. All functions are non-blocking and interruptable at any time.
Supported Network Protocols
| Protocol | Usage |
|---|---|
| ZeroConf/AutoIP | automatic client configuration (IP address assignment) |
| ARP | Address Resolution Protocol, resolves the IP address to a hardware MAC address. No user action is required. If an address is unknown, an ARP request is generated automatically. |
| IP | Internet Protocol. All data transferred by DNS, DHCP, ICMP, UDP and TCP is automatically packed into IP packets. |
| ICMP | Internet Control Message Protocol. The D.SignT.TCP/IP protocol stack responds to “ping” requests to test a connection |
| UDP | User Datagram Protocol, provides a one-to-one or one-to-many connectionless data path. Data transmitted via UDP is not guaranteed to reach its destination. This protocol has very low overhead and is especially useful for transmitting non-critical data like audio and video streams, or any other realtime data where retransmissions cannot be tolerated. |
| TCP | Transmission Control Protocol, provides reliable, connection-oriented, one-to-one connections. All data is acknowledged by the receiver and retransmitted automatically if required. This protocol should be used for critical data like software uploads, commands, etc. |
| DHCP | Dynamic Host Configuration Protocol. This protocol has been developed to ease maintenance of a TCP/IP network. A DHCP server manages the allocation of IP addresses and provides additional network configuration data like gateways, DNS servers etc. The TCP/IP stack integrates the client functions required to obtain an IP address, DNS server, and gateway. |
| DNS | Domain Name System. This protocol allows to use symbolic host names instead of numerical IP addresses. The TCP/IP stack integrates the client functions to query a DNS server to resolve a host name. |
| FTP | File Transfer Protocol, based on TCP. A FTP server library exists, which allows to upload programs and parameters to the module´s Flash Memory, or download log files and data from the DSP. The FTP server is widely configurable: users, passwords, directories, files, and access restrictions are maintained in a simple data structure. |
| HTTP | Hypertext Transfer Protocol, based on TCP. We do provide a HTTP server framework, which passes GET and POST parameters to a user-defined callback function, hence providing the required flexibility for dynamic data. The DSP can send static HTML pages and images as well as inserting the current value of variables, generate images from data acquisition buffers, etc. on demand. |
| TELNET | Terminal-based communications for maintenance and updates |
| SMTP | Simple Mail Transfer Protocol. Send and Email message or notification |
| SNTP | Simple Network Time Protocol. Obtain the current time from a network/Internet server |
Device Support
Now available for the D.Module2.C6557. Additional ports available for the Texas Instruments C2000, C5000 and C6000 families, the TMS320CV33 and the Analog Devices ADSP-21065 processor.
D.Module2.C6657
- 1.25GHz Dual-Core TMS320C6657 DSP
- 10/100/1000Base-T Ethernet Interface
- USB 1.1 Interface