• Menu
  • Product
  • Email
  • PDF
  • Order now
  • Programming Examples and Debug Strategies for the DCAN Module

    • SPRACE5A May   2019  – May 2021 F29H850TU , F29H859TU-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384S , TMS320F28386D , TMS320F28386S , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

       

  • CONTENTS
  • SEARCH
  • Programming Examples and Debug Strategies for the DCAN Module
  1.   1
  2.   2
    1.     3
  3.   4
  4.   5
    1.     6
    2.     7
    3.     8
      1.      9
      2.      10
      3.      11
  5.   12
    1.     13
      1.      14
    2.     15
    3.     16
    4.     17
    5.     18
  6.   19
  7.   20
  8. IMPORTANT NOTICE
search No matches found.
  • Full reading width
    • Full reading width
    • Comfortable reading width
    • Expanded reading width
  • Card for each section
  • Card with all content

 

APPLICATION NOTE

Programming Examples and Debug Strategies for the DCAN Module

Trademarks

C2000 and Code Composer Studio are trademarks of Texas Instruments Incorporated.

All trademarks are the property of their respective owners.

1 Introduction

CAN is a serial protocol that was originally developed for automotive applications. Due to its robustness and reliability, it now finds applications in diverse areas such as Industrial equipment, appliances, medical electronics, trains, air crafts, and so forth. CAN protocol features sophisticated error detection (and isolation) mechanisms and lends itself to simple wiring at the physical level.

Figure 1-1 shows the typical implementation of the CAN bus.

GUID-1821171A-6156-4211-9A8D-C6B60D21237C-low.gif Figure 1-1 Typical Implementation of a CAN Bus

1.1 TMS320F28xx DCAN Features

  • Full implementation of CAN protocol, version 2.0B
  • 32 mailboxes, each with the following properties:
    • Configurable as receive or transmit
    • Configurable with standard or extended identifier
    • Has a programmable receive mask (every mailbox has its own mask)
    • Supports data and remote frame
    • Composed of 0 to 8 bytes of data
    • Employs a programmable interrupt scheme with two interrupt levels
  • Automatic reply to a remote request message
  • Automatic retransmission of a frame in case of loss of arbitration or error

2 Program Descriptions

This section provides a brief description of the example projects, along with applicable waveforms captured with an oscilloscope. Note that the examples are within C2000Ware.

  • can_ex1_loopback.c

This example illustrates the use of self-test mode. A message is transmitted once per second, using a simple delay loop for timing. The message that is sent is a 2 byte message that contains an incrementing pattern. This example sets up the CAN controller in "External" Loopback test mode. Data transmitted is visible on the CANTXA pin and is received internally back to the CAN Core. It is important that the GPIO mapping in device.h file in this project is edited to reflect the GPIO pins that are used for CAN function in your hardware. Otherwise, the transmitted data will not be seen on CANTXA pin.

Figure 2-1 shows the activity on the CANTXA pin.

GUID-20210518-CA0I-25K7-DC7Q-SJWVCWMKHWCK-low.png Figure 2-1 can_ex1_loopback
  • can_ex2_loopback_interrupts.c

Similar to can_ex1_loopback.c, but uses interrupts.

  • can_ex3_external_transmit.c

This example shows basic setup of CAN in order to transmit and receive messages. It sets up CAN-A as the transmitter and CAN-B as the receiver. A receive interrupt is asserted on CAN-B to verify the received data.

  • can_ex4_simple_transmit.c

This example illustrates how to setup the CAN module for transmission. It could prove very useful to check the hardware connections of the CAN circuit.

Figure 2-2, Figure 2-3 and Figure 2-4 show how data is stored in the IFxDATA registers.

Figure 2-2 CAN_IF1DATA Register
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Data_3 Data_2 Data_1 Data_0
R/W-0h R/W-0h R/W-0h R/W-0h
Figure 2-3 CAN_IF1DATB Register
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Data_7 Data_6 Data_5 Data_4
R/W-0h R/W-0h R/W-0h R/W-0h
GUID-20210504-CA0I-Z8VX-B9SQ-NGXKPFX9NRDN-low.png Figure 2-4 IFxDATA Registers in CCS Expressions Window

With the above configurations, data is transmitted in the order shown in Figure 2-5.

Figure 2-5 depicts the waveform on the CANTXA pin.

GUID-20210518-CA0I-CD2W-PZJK-FNSB9ZSDRW2J-low.png Figure 2-5 can_ex4_simple_transmit

Figure 2-6 shows the waveform at the CANRXA pin. Note that during the ACK phase, the transmitting node transmits a recessive, but it is driven low by the receiver.

GUID-660B6230-F497-415D-A4F7-17805E4708CC-low.gif Figure 2-6 Waveform at the CANRXA Pin
  • can_ex5_simple_receive.c

This example is a simple illustration of how to setup the CAN module for reception. This example could prove very useful to generate an ACK for another CAN node.

  • can_ex8_Remote_Tx.c

This example demonstrates the ability of the CAN-A module to transmit a Remote-frame and receive a response in the same mailbox. CAN-B node is configured to respond to the Remote frame. If CAN-B is not available, a CAN bus analyzer may be used to provide a response. Note that the response time from such equipment may be more, because it involves some overhead due to the application running on the PC.

Figure 2-7 shows the response from a bus analyzer. Note that it takes about 13 ms for the response to show up on the bus.

GUID-3474E44A-A588-4E45-81B1-FDF32D235798-low.gif Figure 2-7 can_ex8_Remote_Tx-PEAK

Figure 2-8 shows the response from CAN-B. Response is in microseconds in this case.

GUID-9BC1C7AE-C09A-4A1C-8539-FE34BD85670C-low.gif Figure 2-8 can_ex8_Remote_Tx-28x
  • can_ex9_Remote_Answer.c

Figure 2-9 demonstrates the ability of the module to respond to a Remote-frame. A remote frame is transmitted from the CAN bus analyzer and the module responds.

GUID-CD8A047D-401B-4551-8F28-1A1AF9628FBB-low.gif Figure 2-9 can_ex9_Remote_Answer
  • can_ex10_Mask.c

This example demonstrates acceptance mask filtering. It can be used to evaluate the effects of MXtd & MDir bits. Table 2-1 shows the various scenarios and the outcomes. Mailbox direction was set to Receive (Dir = 0) , An extended ID was written to the mailbox (Xtd = 1) and filtering enabled (UMask = 1). MXtd and MDir bits were cycled through the four possible combinations.

  • An Ext ID frame, satisfying the filtering criterion, is transmitted. MXtd & Mdir bits have no bearing on the frame reception in all four cases.
    Table 2-1 Extended ID Frame (passing filter criterion)
    MXtd Mdir Outcome
    1 1 Frame received
    1 0 Frame received
    0 1 Frame received
    0 0 Frame received
  • An STD ID frame, with exact match for the 11 applicable bits (bits 28:18), is transmitted. In the case where MXtd is 0, the Xtd bit of the mailbox was not used for filtering. Rather, the 11 applicable bits were found to be matching and, hence, the frame was received.
    Table 2-2 Standard ID Frame (exact match)
    MXtd Mdir Outcome
    1 1 Frame not received
    1 0 Frame not received
    0 1 Frame received
    0 0 Frame received
  • An STD ID frame, with passing filter criterion for the 11 applicable bits (bits 28:18), is transmitted. In the case where MXtd is 0, the Xtd bit of the mailbox was not used for filtering. Rather, the 11 applicable bits were found to be matching and the hence the frame was received.
    Table 2-3 Standard ID Frame (passing filter criterion)
    MXtd Mdir Outcome
    1 1 Frame not received
    1 0 Frame not received
    0 1 Frame received
    0 0 Frame received

It is important to remember that the stored Message Identifier will be over-written by the identifier of the received frame. In order for acceptance filtering to work correctly for subsequent frames, the message object must be reinitialized with the original identifier.

3 Debug and Design Tips to Resolve/Avoid CAN Communication Issues

This section illustrates some of the common mistakes and oversights while implementing a CAN bus. This is followed by some debugging tips useful to troubleshoot bus issues.

3.1 Minimum Number of Nodes Required

Unless working in the self-test mode, a minimum of two nodes are needed on the CAN bus for the following reason: When a node transmits a frame on the CAN bus, it expects an acknowledgment (ACK) from at least one other node on the network. Any time a CAN node successfully receives a message it will automatically transmit an ACK, unless that feature has been turned off "silent mode", where a node receives the frame, but does not provide an ACK; the DCAN module has this feature). The node that provides the ACK does not need to be the intended recipient of the frame, although it could very well be. (All active nodes on the bus will provide an ACK, regardless of whether they are the intended recipients of that frame or not).

When the transmitting node does not receive an ACK, it results in an ACK error and the transmitting node keeps re-transmitting the frame forever. The Transmit Error Counter (TEC) will increment to 128 and stop there. REC stays at 0. Node will not go bus-off. In this situation, the TxRqst bit for the transmitting mailbox does not get set. No interrupts will be generated either. If another node is brought into the network, the TEC will start decrementing (all the way to 0) with every successful transmit.

3.2 Why a Transceiver is Needed

One cannot directly connect CANTX of node-A to CANRX of node-B and vice versa and expect successful CAN communication. In this case, CAN is unlike other serial interfaces like SCI or SPI. For example, SCI can be made to work with a RS232 transceiver or through a direct connection (SCITX of one node to SCIRX of another node and vice versa). However, CAN bus needs a CAN transceiver for the following reason: In addition to converting the single-ended CAN signal for differential transmission, the transceiver also loops back the CANTX pin to the CANRX pin of a node. This is because a CAN node needs to be able to monitor its own transmission. Why?

  • This has to do with the ACK requirement mandated by the CAN protocol. When a node transmits a frame on the CAN bus, it expects an ACK from at least one other node on the network. For the ACK phase, the transmitter puts out a 1 and expects to read back a 0.
  • During arbitration, a node with a higher-priority MSGID needs to be able to override a 1 with a 0. Here again, the transmitter needs to be able to read back the transmitted data. When a node puts out a 1 and reads back a 0 during the arbitration phase, it loses arbitration.

3.3 Debug Checklist

This section highlights some common mistakes in the design and implementation of a CAN bus network.

3.3.1 Programming Issues

  • Is clock to the CAN module enabled? Check for this if writes to CAN registers are not going through. Clock is enabled through a bit in the PCLKCRn register.
  • Comment all EDIS from your code until you get it to work. You could add it later. Many registers and bits are EALLOW protected and a write may not go through if EALLOW is not active.
  • Try your code without interrupts first. Use polling instead. Once polling works, you can add interrupts later.
  • If a specific mailbox is not working, have you attempted to use a different mailbox? Have the mailboxes been enabled and the mailbox direction correctly configured?
  • When attempting to initiate communication on the bus for the very first time, ensure that the the mailbox in the transmitting node and the receiving node are programmed with the same MSGID. Do not use Acceptance Mask Filtering initially. Filtering could be added later once it is confirmed there are no hardware issues with the bus.

3.3.2 Physical Layer Issues

  • Has the bus been terminated correctly (with 120-Ω) at either ends (only)? The bus must be terminated only at either ends and with a 120-Ω resistor. In other words, no more than two terminator resistors may be present on the bus, unless split termination is followed, in which case there will be two resistors on either ends. While designing a CAN bus system, it is important that the termination resistors can be enabled/disabled from outside the system enclosure. This scheme makes it easy when nodes have to be added/removed to/from the network.
  • Are all CAN nodes configured for the same bit-rate? Mis-matched node bit rates would repeatedly introduce error frames on the bus. Capture the output of a node on the oscilloscope to physically verify the bit-time.
  • Have you tried a lower bit-rate? Say, 50 kbps, for example? Timing issues concerning propagation delays may be caught trying a lower bit-rate. Ensure that CANBTR register has the programmed value.
  • Have you tried to reduce the bus length and number of nodes?
  • Before the occurrence of the error condition, were any error-frames seen on the bus? This could point to timing violations or noise issues.
  • How many nodes are there in the bus? (In non-self-test mode, there must be at least two nodes on the network, due to the acknowledge (ACK) requirement mandated by the CAN protocol)

3.3.3 Hardware Debug Tips

  • To see the waveform until the ACK phase, a transceiver must be connected to the node. Without a transceiver, the node immediately goes into an error state.
  • Check if the CAN frame is correctly seen at the CANRX pin of the MCU and it is of the expected bit-rate.
  • If using an oscilloscope with a built-in CAN trigger, make sure that the signal configured for triggering matches the signal being probed on the board. Many oscilloscopes are capable of triggering on CAN-transmit (CANTX), CAN-receive (CANRX), CAN_H and CAN_L signals, in addition to Start-of_Frame (SOF), Remote frames, Error frames and specific MSGIDs.
  • If the scope does not decode the waveform, make sure input threshold value for the channel is correct. This is similar to the “trigger level” that is normally used for signals.

4 Helpful Migration and Project Execution Tips

This section provides some tips for GPIO reconfiguration, project cloning, migrating from eCAN and bit-timing configuration.

4.1 GPIO Reconfiguration

The example programs run under the Driverlib frame work. They were tested with the following GPIO configuration for the CAN pins (see Table 4-1).

Table 4-1 GPIO Pin Mapping Used for the Examples
CAN FunctionGPIO
CANTXAGPIO71
CANRXAGPIO70
CANTXBGPIO72
CANRXBGPIO73

The C2000Ware examples, by default, have the following GPIO configuration for CAN operation:

#define DEVICE_GPIO_CFG_CANRXA      GPIO_30_CANRXA  // "pinConfig" for CANA RX
#define DEVICE_GPIO_CFG_CANTXA      GPIO_31_CANTXA  // "pinConfig" for CANA TX
#define DEVICE_GPIO_CFG_CANRXB      GPIO_10_CANRXB  // "pinConfig" for CANB RX
#define DEVICE_GPIO_CFG_CANTXB      GPIO_8_CANTXB   // "pinConfig" for CANB TX

This may have to be modified depending on which GPIO pins are used for CAN operation in your hardware. This is a very important step and, if applicable, must be done for every example project. Use the procedure discussed in Section 4.1.1 to change the GPIO configuration.

4.1.1 How to Change the GPIO Assignment for the CAN Pins

The example C file has the following statements:

GPIO_setPinConfig(DEVICE_GPIO_CFG_CANRXA);
GPIO_setPinConfig(DEVICE_GPIO_CFG_CANTXA);
GPIO_setPinConfig(DEVICE_GPIO_CFG_CANRXB);
GPIO_setPinConfig(DEVICE_GPIO_CFG_CANTXB);
  • The function GPIO_setPinConfig(uint32_t pinConfig) is in gpio.c file.
  • The argument DEVICE_GPIO_CFG_CANRXA is in device.h file.
#define DEVICE_GPIO_CFG_CANRXA      GPIO_30_CANRXA  // "pinConfig" for CANA RX

The constant #define GPIO_30_CANRXA 0x00081C01U is defined in pin_map.h file.

To change the GPIO mapping, edit the device.h file as follows: (Table 4-1 was used as an example).

// Modified configuration 
#define DEVICE_GPIO_CFG_CANRXA      GPIO_70_CANRXA  // "pinConfig" for CANA RX
#define DEVICE_GPIO_CFG_CANTXA      GPIO_71_CANTXA  // "pinConfig" for CANA TX
#define DEVICE_GPIO_CFG_CANRXB      GPIO_73_CANRXB  // "pinConfig" for CANB RX
#define DEVICE_GPIO_CFG_CANTXB      GPIO_72_CANTXB  // "pinConfig" for CANB TX
Note:

device.h file is unique to every example directory in the workspace. The edits you make for one project will not get carried over across other projects.

For the ControlCARD, CANTXA is on GPIO31 and CANRXA is on GPIO30. CANTXB is on GPIO8 and CANRXB is on GPIO10. GPIOs will be different on Launchpad. For more information, see the board schematics in the /boards directory in C2000ware.

4.2 How to Duplicate (clone) an Existing Project

  1. All projects start their life as a .projectspec file. They exist in C:\ti\c2000\C2000Ware_1_00_05_00\driverlib\f2837xd\examples\cpu1\can\CCS directory. Note that the exact path would depend on the version of C2000ware installed in your computer.
    GUID-55E48C38-526C-4752-BCFE-860ECDC960B5-low.gifFigure 4-1 Directory Containing the .projectspec Files
  2. Make a copy of an existing .projectspec file. For example, suppose you want to create a new project called can_ex4_simple_transmit. Start by making a copy of can_ex1_loopback.projectspec and rename it as can_ex4_simple_transmit.projectspec.
  3. Open can_ex4_simple_transmit.projectspec and replace the two instances of can_ex1_loopback with can_ex4_simple_transmit, the name of the new testcase.
  4. In the C:\ti\c2000\C2000Ware_1_00_05_00\driverlib\f2837xd\examples\cpu1\can directory, make a copy of the can_ex1_loopback.c file and rename it as can_ex4_simple_transmit.c. This is very important because when the .projectspec file is imported into Code Composer Studio™, it copies the new file into the target directory when it executes the following statement: <file action="copy" path="../can_ex4_simple_transmit.c" targetDirectory="" />.
  5. Import the can_ex4_simple_transmit.projectspec file into CCS. Note that the project directories are created under C:\Users\Your_name\workspace_v8, not in: \ti\c2000\C2000Ware_1_00_05_00\driverlib\f2837xd\examples\cpu1\can.
    GUID-F9580843-8602-402E-9952-239DDBA624C0-low.gifFigure 4-2 Project Directories in CCS Workspace

4.3 How to Get Visibility Into Driverlib Files

While single-stepping through the test cases, if the code calls a function in a Driverlib file, CCS may display an error message as shown in Figure 4-3.

GUID-F85B0656-ED1A-4063-ABA7-4772751A8AC6-low.gifFigure 4-3 CCS Error Message

If this happens, click on “Locate File” and point to the Driverlib directory. For example, C:\Users\ Your_name\workspace_v7\can_ex2_loopback_interrupts\ device\driverlib.

4.4 Migrating From eCAN

This section provides some helpful hints if you are migrating from the eCAN module to the DCAN module. DCAN follows a very different register structure compared to eCAN and hence code written for one module cannot be migrated to another. The following section highlights the differences, but also illustrates the functional similarities between the two modules.

The following features are available in DCAN that are not available in eCAN:

  • Parity check mechanism for all RAM modules.
  • Automatic Retransmission (upon loss of arbitration) can be disabled.
  • Silent mode (Node listens passively).
  • Mailbox RAM may be combined to form FIFO buffers.
  • Data can be monitored on CANTX pin in self-test mode.

The following are the features that are available in eCAN that are not available in DCAN:

  • Timestamping of messages.
  • Transmission priority configuration (TPL).
  • Data-byte order configuration (DBO).
  • Direct access to the mailbox RAM by the CPU - In DCAN, mailbox RAM is accessed through the Interface (IFx) registers. The IFx registers may be thought of as a "window" through which the mailbox RAM is accessed.

Table 4-2 shows the equivalent registers and bit-fields in eCAN and DCAN and also some functional differences.

Table 4-2 eCAN-DCAN Registers and Bits Equivalence
FunctioneCANDCANComments
CAN module software reset bitCANMC.SRESCAN_CTL.SWR
Automatic bus-on (after bus-off)CANMC.ABOCAN_CTL.ABO
Self-test modeCANMC.STMCAN_CTL.TestFurther selection needed for DCAN in CAN_TEST register
Configuration modeCANMC.CCRCAN_CTL.Init
Configuration mode enabledCANES.CCECAN_CTL.CCE
Mailbox interrupt sourceCANGIFx.MIVyCAN_INT.INTnID
Interrupt line selection (for mailbox)CANMILCAN_IP_MUX21
Interrupt line selection (for error & status)CANGIM.GILHardwired to CANINT0
CAN to PIE interrupt line0 enableCANGIM.I0ENCAN_CTL.IE0
CAN to PIE interrupt line1 enableCANGIM.I1ENCAN_CTL.IE1
Transmit Error CounterCANTEC.TECCAN_ERRC.TEC
Receive Error CounterCANREC.RECCAN_ERRC.REC
Bus-off statusCANES.BOCANES.Boff
Early warning (TEC or REC = 96)CANES.EWCANES.EWarn
Error passiveCANES.EPCANES.EPass
Acceptance mask registerLAMCAN_IFxMSK
Acceptance mask filter for a MailboxLAM.LAMCAN_IFnMSK.MskMask bit behavior is opposite
Mailbox message-ID registerMSGIDCAN_IF1ARB
Mailbox enable or disableCANME.MEnCAN_IFnARB.MsgValIn DCAN, MBX can remain "enabled" while configuring the MSGID.
Extended IdentifierMSGID.IDECAN_IFxARB.Xtd
Mailbox directionCANMD.MDnCAN_IFxARB.Dir
Message IDMSGID.IDCAN_IFxARB.Id
Lost message indicationCANRML.RMLnCAN_IFxMCTL.MsgLst
Transmission requestCANTRS.TRSnCAN_IFxMCTL.TxRqst
# of bytes in a frameMSGCTRL.DLCCAN_IFxMCTL.DLC
Transmit or Receive priorityHigher numbered MBX has priorityLower numbered MBX has priority
Enabling/disabling interrupts for a specific mailbox CANMIM IFnMCTL.TxIE or IFnMCTL.RxIE

4.5 Configuring the CANBTR Register

In this section, the usage of the various bit-fields in the CANBTR register is illustrated.

The formula for bit-rate is:

Equation 1. GUID-B4A0C570-37F4-450B-9EBB-8CC154B872DD-low.gif

Where BRP is the value of (BRPreg + 1) and Bit-time = (TSEG1reg + 1) + (TSEG2reg + 1) + 1

In the above equations BRPreg , TESG1reg and TSEG2reg represent the actual values written in the corresponding fields in the CANBTR register. The parameters TSEG1reg, TSEG2reg, SJWreg, and BRPreg are automatically enhanced by 1 when the CAN module accesses these parameters. If the BRPE field is used, it should be concatenated with the BRP field.

Example 1

Assume the following parameters are desired with a CAN module clock of 200 MHz:

Bit-rate = 500 kbps, SJW = 4, TSEG1 = 9 & TSEG2 = 6.

This is achieved by writing a value of 0x000058D8 in the CANBTR register. Here, TSEG1reg = 8, TSEG2reg = 5, SJWreg = 3, and BRPreg = 24

Effective BRP value = (BRPreg + 1) = 25

Effective TSEG1 value = (TSEG1reg + 1) = 9

Effective TSEG2 value = (TSEG2reg + 1) = 6

Effective SJW value = (SJWreg + 1) = 4

Bit-time = (TSEG1reg + 1) + (TSEG2reg + 1) + 1 = 16

Plugging these numbers into the bit-rate equation:

Equation 2. GUID-1799866C-185F-450F-91C2-B1DD24B03A03-low.gif

Example 2

Assume the following parameters are desired with a CAN module clock of 200 MHz:

Bit-rate = 50 kbps, SJW = 4, TSEG1 = 9 & TSEG2 = 6.

This is achieved by writing a value of 0x000358F9 in the CANBTR register. Here, TSEG1reg = 8, TSEG2reg = 5, SJWreg = 3, BRPE = 11b , BRP = 111001b. Effective BRPreg = 11111001b (249). Note that BRPE field is concatenated with the BRP field.

Effective BRP value = (BRPreg + 1) = 250

Effective TSEG1 value = (TSEG1reg + 1) = 9

Effective TSEG2 value = (TSEG2reg + 1) = 6

Effective SJW value = (SJWreg + 1) = 4

Bit-time = (TSEG1reg + 1) + (TSEG2reg + 1) + 1 = 16

Plugging these numbers into the bit-rate equation:

Equation 3. GUID-B9FE36B7-858B-4BEE-80A4-E7B3F7CC2848-low.gif

5 References

  • Texas Instruments: Introduction to the Controller Area Network (CAN)
  • Texas Instruments: Controller Area Network Physical Layer Requirements
  • Texas Instruments: Basics of Debugging the Controller Area Network (CAN) Physical Layer
  • Texas Instruments: Calculator for CAN Bit Timing Parameters
  • Texas Instruments: Overview of 3.3V CAN (Controller Area Network) Transceivers
  • Texas Instruments: Simplify CAN Bus Implementations With Chokeless Transceivers
  • Texas Instruments: Critical Spacing of CAN Bus Connections
  • Texas Instruments: Improved CAN Network Security with TI’s SN65HVD1050 Transceiver
  • Texas Instruments: Message Priority Inversion on a CAN Bus
  • Texas Instruments: Piccolo MCU CAN Module Operation Using the On-Chip Zero-Pin Oscillator
  • Texas Instruments: C2000 Real-Time Control Peripherals Reference Guide
  • Texas Instruments: Programming Examples for the TMS320x28xx eCAN

IMPORTANT NOTICE AND DISCLAIMER

TI PROVIDES TECHNICAL AND RELIABILITY DATA (INCLUDING DATASHEETS), DESIGN RESOURCES (INCLUDING REFERENCE DESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND OTHER RESOURCES “AS IS” AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS.
These resources are intended for skilled developers designing with TI products. You are solely responsible for (1) selecting the appropriate TI products for your application, (2) designing, validating and testing your application, and (3) ensuring your application meets applicable standards, and any other safety, security, or other requirements. These resources are subject to change without notice. TI grants you permission to use these resources only for development of an application that uses the TI products described in the resource. Other reproduction and display of these resources is prohibited. No license is granted to any other TI intellectual property right or to any third party intellectual property right. TI disclaims responsibility for, and you will fully indemnify TI and its representatives against, any claims, damages, costs, losses, and liabilities arising out of your use of these resources.
TI’s products are provided subject to TI’s Terms of Sale (www.ti.com/legal/termsofsale.html) or other applicable terms available either on ti.com or provided in conjunction with such TI products. TI’s provision of these resources does not expand or otherwise alter TI’s applicable warranties or warranty disclaimers for TI products.
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2020, Texas Instruments Incorporated

 

Texas Instruments

© Copyright 1995-2025 Texas Instruments Incorporated. All rights reserved.
Submit documentation feedback | IMPORTANT NOTICE | Trademarks | Privacy policy | Cookie policy | Terms of use | Terms of sale