Macros
CAN_STATUS

Macros

#define CAN_STATUS_SUCCESS   ((int_fast16_t)0)
 Successful status code. More...
 
#define CAN_STATUS_ERROR   ((int_fast16_t)-1)
 Generic error status code. More...
 
#define CAN_STATUS_NOT_SUPPORTED   ((int_fast16_t)-2)
 Not supported status code. More...
 
#define CAN_STATUS_TX_BUF_FULL   ((int_fast16_t)-3)
 Tx buffer full status code. More...
 
#define CAN_STATUS_NO_RX_MSG_AVAIL   ((int_fast16_t)-4)
 No received message available status code. More...
 

Detailed Description

Macro Definition Documentation

§ CAN_STATUS_SUCCESS

#define CAN_STATUS_SUCCESS   ((int_fast16_t)0)

Successful status code.

Functions return CAN_STATUS_SUCCESS if the function was executed successfully.

§ CAN_STATUS_ERROR

#define CAN_STATUS_ERROR   ((int_fast16_t)-1)

Generic error status code.

Functions return CAN_STATUS_ERROR if the function was not executed successfully and no more pertinent error code could be returned.

§ CAN_STATUS_NOT_SUPPORTED

#define CAN_STATUS_NOT_SUPPORTED   ((int_fast16_t)-2)

Not supported status code.

Functions return CAN_STATUS_NOT_SUPPORTED if the function is not supported either by the target hardware or the driver implementation.

§ CAN_STATUS_TX_BUF_FULL

#define CAN_STATUS_TX_BUF_FULL   ((int_fast16_t)-3)

Tx buffer full status code.

Functions return CAN_STATUS_TXBUF_FULL if the Tx buffers are full.

§ CAN_STATUS_NO_RX_MSG_AVAIL

#define CAN_STATUS_NO_RX_MSG_AVAIL   ((int_fast16_t)-4)

No received message available status code.

Functions return CAN_STATUS_NO_RX_MSG_AVAIL if there are no messages available in the Rx message ring buffer.

© Copyright 1995-2023, Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy policy | Terms of use | Terms of sale