If your target application communicates using DCC, you must configure the DCC mode. You can set the following DCC modes:
- Mode 0: raw DCC
Raw, unprocessed, data is fed to the client through the DCC register on the target.
- Mode 1: redirected raw DCC
In this mode, the data is fed over TCP/IP ports starting at 5000. Data is sent from the host to the target 4 bytes at a time. If fewer than 4 bytes are available, the data is padded with 0 bytes until it is 4 bytes long. Data from the target to the host is received 4 bytes at a time, and no padding or trimming is performed.
Note
It is recommended that you use the Virtual Ethernet/TTY mode (mode 2). However, if the Virtual Ethernet/TTY mode is unsuitable for your application, then you can use mode 1 DCC but you must also implement a suitable communications protocol.
- Mode 2: Virtual Ethernet/TTY mode
Virtual Ethernet/TTY is used for providing virtual serial and Ethernet connections to the target. As far as the debug host and the target are concerned, Virtual Ethernet/TTY mode is a debug hardware feature that provides:
A virtual Ethernet feature using the DCC channel and a collection of software tools in debug hardware and the host PC. It enables TCP/IP to be used to the target as though the target has an Ethernet port of its own.
A virtual serial port feature using the DCC channel and a collection of software tools in debug hardware and the host PC.
See also
PDF version