UM0541

Using DCP monitor

7/19

2

Using DCP monitor

2.1

Defining behavior

DCP monitor can work in two ways:

●

Polling

●

Autonomously

This means that the user can query information from an external tool (usually CPU

commander) or the application can send the information by itself.

2.1.1

Autonomously

In order to communicate with this mode, the user can call whenever needed within the code

the DCP_SendFrame function.

For parsing, the user should customize and register the DCP_Callback function.

Within this function all the necessary processing should be done. Parsing of the received

user command.

2.1.2

Polling

In order to work with this mode, no specifications are needed.

The external tool instructs the target to read or write data using the DCC_READ and

DCC_WRITE commands.

In this case there is no need of coding for the user. The only operation required is to initialize

the DCP by calling the DCP_Init function.

Note:

About endianness: the protocol works with big endianness. This means that all information

sent must be converted to big endian and all the information received must be converted to

the endianness of the receiving platform.

2.2

Configuring DCP

2.2.1

Communication API configuration

COM_API defines which communication API is used.

2.2.2

ACK management

ACK management can be enabled with ACK_MANAGEMENT_SEND.

ACK management on Rx can be enabled with ACK_MANAGEMENT_WAIT, specifying the

timeout for waiting in ms with ACK_MANAGEMENT_TIMEOUT. If the sender is waiting for

an ACK and it receives a frame, it simply processes the frame and still remains waiting for

the ACK.

2.2.3

DCP version

The version of the protocol is specified by DCP_VERSION.