Infineon C166 Series Application Note
  1. Manuals
  2. Brands
  3. Infineon Manuals
  4. Microcontrollers
  5. C166 Series
  6. Application note

Infineon C166 Series Application Note

Connecting to can
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
A p p l i c a t i o n N o t e , V 1 . 0 , F e b . 2 0 0 4
AP29000
CAN
Co nnec tin g C1 66 a nd C5 00
Micr ocon tro l ler to CAN
.
Micr ocon tro l lers
N e v e r
s t o p
t h i n k i n g .

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the C166 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Infineon C166 Series

Summary of Contents for Infineon C166 Series

  • Page 1 A p p l i c a t i o n N o t e , V 1 . 0 , F e b . 2 0 0 4 AP29000 Co nnec tin g C1 66 a nd C5 00 Micr ocon tro l ler to CAN Micr ocon tro l lers N e v e r...
  • Page 2 V 1.0 Previous Version: Page Subjects (major changes since last revision) Updated Layout to Infineon Corporate Design, updated release to 1.0, Content unchanged! Controller Area Network (CAN): License of Robert Bosch GmbH We Listen to Your Comments Any information within this document that you feel is wrong, unclear or missing at all? Your feedback will help us to continuously improve the quality of this document.
  • Page 3 Infineon Technologies Components may only be used in life-support devices or systems with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system, or to affect the safety or effectiveness of that device or system.

  • Page 4: Table Of Contents

    Standard CAN, Extended CAN ..............2 3.6.2 Basic CAN, Full CAN................. 2 The Infineon CAN Devices C167CR, C515C and SAE 81C90/91....2 The Microcontroller Families C500 and C166 at a Glance......2 The CAN Module on the C167CR / C515C ........... 2 4.2.1...
  • Page 5 AP29000 Connecting C166 and C500 Microcontroller to CAN Table of Contents Connecting the C511 / C513 to CAN using the serial interface of the SAE 81C91 ....................2 A proposal for the CAN Bus Cables .............. 2 Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C......................

  • Page 6: Abbreviations And Symbols

    AP29000 Connecting C166 and C500 Microcontroller to CAN Abbreviations and Symbols Abbreviations and Symbols The following abbreviations and symbols are used throughout this application note: ABUS "Allgemeine Bitserielle Universelle Schnittstelle" (VW protocol) BL1, BL2 Bit timing registers of the SAE 81C90/91 Baudrate Prescaler Bit Stream Processor Bit Timing Logic...
  • Page 7 This application note describes the CAN Protocol, Infineon CAN devices and different options for connecting devices of the Infineon C166 and C500 microcontroller families to the Controller Area Network (CAN). It replaces the German application note "CAN- Anschluß für die Mikrocontrollerfamilien C166 and C500".

  • Page 8: Introduction

    AP29000 Connecting C166 and C500 Microcontroller to CAN Introduction Introduction Ever increasing quantities of electronic devices are fitted to modern motor vehicles. Examples of such devices include engine management systems, active suspension, ABS, gear control, lighting control, air conditioning, airbags and central locking. All this means more safety and more comfort for the driver and of course a reduction of fuel consumption and exhaust emissions.
  • Page 9 These protocols mostly differ in transfer rate, signal coding, message format, error detection, and error handling. The CAN protocol was defined by Bosch in the mid-eighties. For some time Infineon have also offered CAN devices such as the stand-alone Full-CAN controller SAE 81C90/91 and the C167CR and the C515C microcontrollers (high-end 16-bit or 8- bit microcontrollers respectively with an on-chip CAN module).

  • Page 10: The Controller Area Network (Can)

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) The Controller Area Network (CAN) CAN Basics CAN is an asynchronous serial bus system with one logical bus line. It has an open, linear bus structure with equal bus nodes. A CAN bus consists of two or more nodes. The number of nodes on the bus may be changed dynamically without disturbing the communication of other nodes.

  • Page 11: Addressing And Bus Arbitration

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) Addressing and Bus Arbitration In the CAN protocol it is not bus nodes that are addressed, but the address information is contained in the messages that are transmitted. This is done via an identifier (part of each message) which identifies the message content (e.g.

  • Page 12: The Different Can Frames And Their Formats

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) The different CAN Frames and their Formats 3.3.1 Data Frame 3.3.1.1 Standard CAN Data Frame Standard Data Frame Inter Frame Space recessive Level 1 1 1 0...64 1 1 1 dominant Level Bus Idle...
  • Page 13 AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) The SOF is followed by the Arbitration Field consisting of 12 bits, the 11-bit Identifier (reflecting the contents and priority of the message) and the RTR bit (Remote Transmission Request bit).

  • Page 14: Extended Can Data Frame

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) 3.3.1.2 Extended CAN Data Frame Inter Frame Space Extended Data Frame recessive Level 0...64 1 1 1 dominant Level Bus Idle Intermission End of Frame ACK Delimiter Acknowledge Field ACK Slot...

  • Page 15: Remote Frame

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) In the Extended CAN Data Frame the Start Of Frame bit (SOF) is followed by the Arbitration Field consisting of 32 bits. The first 11 bits are the 11 most significant bits of the 29-bit Identifier ("Base-ID").

  • Page 16: Extended Can Remote Frame

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) Standard Remote Frame Inter Frame Space recessive Level 1 1 1 1 1 1 dominant Level Bus Idle Intermission End of Frame ACK Delimiter Acknowledge ACK Slot Field CRC Delimiter CRC Field...

  • Page 17: Error Frames, Overload Frame, Interframe Space

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) Inter Frame Space Extended Remote Frame recessive Level 1 1 1 dominant Level Bus Idle Intermission End of Frame ACK Delimiter Acknowledge ACK Slot Field CRC Delimiter CRC Field CRC Sequence Data Length Code...

  • Page 18: Overload Frame

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) If an “error-active” node detects a bus error then the node interrupts transmission of the current message by generating an “active error flag”. The “active error flag” is composed of six consecutive dominant bits.

  • Page 19: Interframe Space

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) 3.3.3.3 Interframe Space Interframe Space separates a preceeding frame (of whatever type) from a following Data or Remote Frame. Interframe space is composed of at least 3 recessive bits, these bits are termed the Intermission.

  • Page 20: Error Detection And Error Handling

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) The PROP_SEG (Propagation Segment) is used to compensate for signal delays across the network. These delays are caused by signal propagation delay on the bus line and through the electronic interface circuits of the bus nodes. PROP_SEG may be 1, 2, 3, ..., 8 or more Time Quanta long.

  • Page 21: Different Can Implementations

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) Form Error If a transmitter detects a dominant bit in one of the four segments End of Frame, Interframe Space, Acknowledge Delimiter or CRC Delimiter then a Form Error has occured and an Error Frame is generated.

  • Page 22: Basic Can, Full Can

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Controller Area Network (CAN) CAN modules specified after CAN V2.0 part A are only able to transmit and receive Standard Frames according to the Standard CAN protocol. Messages using the 29-bit identifier cause errors.

  • Page 23: The Infineon Can Devices C167Cr, C515C And Sae 81C90/91

    3.2. To meet the requirements of today’s and future embedded control applications Infineon developed the SAB 80C166 in 1990 being the first member of the 16-bit microcontroller family C166. The controllers own a registerbank-oriented CPU with a four-stage pipeline being able to process most of the instructions in just one machine cycle of 80 ns @ 25 MHz CPU clock.
  • Page 24 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 XCS# BHE# CAN TxD ADDRESS [7:0] XBUS Interface Controller CAN RxD DATA [15:0] XINTR0# XCLK XRST Figure 6 Block Diagram of the CAN module (connected to the C167CR here) The CAN module is made of two major blocks.
  • Page 25 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 The second block of the CAN module on the C167CR and the C515C is the CAN controller itself, which is derived from the stand-alone component AN 82527. The CAN controller provides all resources that are required to run the Standard CAN protocol (11-bit identifiers) as well as the Extended CAN protocol (29-bit identifiers).
  • Page 26 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 • The Bit Timing Logic (BTL) monitors the busline input CAN_RxD and handles the busline related bit timing according to the CAN protocol. The BTL synchronises on a...

  • Page 27: Control Registers Of The Can Controller

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 4.2.2 Control Registers of the CAN Controller All registers reside in the already mentioned 256-byte wide CAN address areas (shown in figure 8) together with the message objects. The most important registers are now described.
  • Page 28 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 EF00 EF00 Control / Status General Registers Register EF10 Message Object 1 EF20 EF02 Message Object 2 Interrupt EF30 Register Message Object 3...

  • Page 29: The Message Objects

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 It has an additional individually programmable acceptance mask for the complete Arbitration Field called Mask of Last Message which is ANDed with the global mask that corresponds to the incoming message.
  • Page 30 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 Message Object Message Control Low Start Address Message Control High Upper Arbitration Low Upper Arbitration High Lower Arbitration Low Lower Arbitration High Message Configuration...

  • Page 31: Initialization Of The Can Controller

    CAN bus communication. Please also read section 5.4.1 for more information about the initialization of this device. Further information about the CAN module can be found in section 5 or in the Infineon literature "Description of the On-Chip CAN-Module" and the manuals of the C167CR and the C515C.

  • Page 32: Functional Blocks Of The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 4.3.2 Functional blocks of the SAE 81C90/91 The functional blocks of the SAE 81C90/91 are shown in figure 12. Time Transmit Serial Check...

  • Page 33: The Most Important Control Registers Of The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 The Message Memory contains the 16 message objects. The SAE 81C90/91 as well owns a Bit-Stream-Prozessor (BSP), which controls the complete CAN protocol, handles the different CAN frames (Data Frame, Remote Frame), and performs the frame check.
  • Page 34 AP29000 Connecting C166 and C500 Microcontroller to CAN The Infineon CAN Devices C167CR, C515C and SAE 81C90/91 The SAE 81C90/91 contains no implementation of the physical layer, which again requires a CAN transceiver. Further information about the SAE 81C90/91 Stand Alone Full CAN Controller can be found in section 5 or in the corresponding Data Sheet.

  • Page 35: Examples For The Connection Of Infineon Microcontrollers To Can

    • In some versions / production steps of the C167CR, CAN_TxD is configured as output by hardware and therefore cannot be used as general purpose I/O pin P4.6. Please contact your distributor or your local Infineon office if you need further information about this subject.
  • Page 36 AP29000 Connecting C166 and C500 Microcontroller to CAN Examples for the Connection of Infineon Microcontrollers to CAN Figure 13 Connection of the C167CR to CAN Figure 14 shows the connection between the C515C and the CAN bus. This time the CAN module is connected to the CAN transceiver via the port pins "RXDC"...

  • Page 37: Connecting The Sab 80C166 To Can Using The Parallel Interface Of The Sae 81C90

    AP29000 Connecting C166 and C500 Microcontroller to CAN Examples for the Connection of Infineon Microcontrollers to CAN Figure 14 Connection of a C515C to CAN Connecting the SAB 80C166 to CAN using the parallel interface of the SAE 81C90 Of course not all members of the C500- and C166 family own an integrated CAN module.
  • Page 38 AP29000 Connecting C166 and C500 Microcontroller to CAN Examples for the Connection of Infineon Microcontrollers to CAN Figure 15 Connection of a SAB 80C166 to CAN via the SAE 81C90 (parallel) The SAE 81C90 obtains its defined reset via the RSTOUT# pin of the SAB 80C166.

  • Page 39: Connecting The C511 / C513 To Can Using The Serial Interface Of The Sae 81C91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Examples for the Connection of Infineon Microcontrollers to CAN Note: If a complete external CAN transceiver chip is used, the best way is to evaluate the signal digitally as shown in this application note. But the SAE 81C90/91 also has an input comparator implemented on-chip in case no such transceiver IC is used.

  • Page 40: A Proposal For The Can Bus Cables

    AP29000 Connecting C166 and C500 Microcontroller to CAN Examples for the Connection of Infineon Microcontrollers to CAN Every access to the SAE 81C91 is started by activating the device (CS# = 0), performed by a port pin (e.g. P1.6). Pin P1.5 of the C511 / C513 then selects a read (W# = 1) or a write (W# = 0) operation via the W# input of the CAN controller.

  • Page 41: Ways Of Handling The Sae 81C90/91 And The Can Module On The C167Cr / C515C

    "C". They show just one way to solve a certain problem and they don't claim for optimized code. For better understanding the reader should also refer to the Infineon information "Description of the On-Chip CAN-Module", the SAE 81C90/91 Data Sheet, and the C515C User's Manual.
  • Page 42 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C #define DB3_M1 *(unsigned char*) 0xef1a #define DB4_M1 *(unsigned char*) 0xef1b #define DB5_M1 *(unsigned char*) 0xef1c #define DB6_M1 *(unsigned char*) 0xef1d #define DB7_M1 *(unsigned char*)
  • Page 43 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Extract from the include file for the SAE 81C90/91 (according to the specification 01/97): Register Addresse */ #define *(unsigned char far*) 0x...00 #define...

  • Page 44: Configuration Of The Bit Timing

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Configuration of the Bit Timing Before initializing the CAN controllers, one has to think about the internal frequencies of the devices as well as the baudrate of the CAN bus.
  • Page 45 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Please note that TSEG1, TSEG2, BRP and SJW are the numerical values of the respective fields to be programmed in the respective registers of the controllers, t q represents one BTL cycle (see section 2.4).
  • Page 46 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C ⇒ Example: C167CR CPU clock: 20 MHz = 100 ns CAN_CLOCK ⇒ = 1 / baudrate = 8 µs Desired CAN baudrate: 125 kBit/s Using equation (7) results in the following table with the valid values of (TSEG1 + TSEG2).

  • Page 47: Ways Of Handling The Can Module

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C This means that TSEG1 and TSEG2 should be programmed to the following values: TSEG1 = TSEG2 = General rules for the SJW: ≤...
  • Page 48 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • In the Bit Timing Register, the baudrate then can be configured (e.g. to 125 kbit/s) (see also section 5.3). /* load Bit Timing Register */ C167CR: = 0x4944;...
  • Page 49 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • If Extended CAN is used, then the "Upper Global Mask Long" and the "Lower Global Mask Long" have to be initialized according to the identifier bits to be used for acceptance filtering (application specific).
  • Page 50 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C /* 2 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 (Ident.-Bits */ /* 0 9 8 7 6 5 4 3...
  • Page 51 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Direction of the object (please also see table below): DIR = 1: transmit Data Frames; receive and answer Remote Frames (in the following called "transmit object"), DIR = 0: transmit Remote Frames;...
  • Page 52 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Example for an Extended CAN receive object with 3 bytes data length: C167CR / C515C: MCFG_Mn = 0x34; /*Mess. Configur. Reg. n (EFn6h/F7n6h)*/ /* 0 0 1 1 0 1 0 0 */ /*|<-DLC->| D X - - */...
  • Page 53 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C /* 4 3 2 1 0 |res| (Id.-Bits 1 1 1 9 8 7 6 5 */ 0 - 12) 2 1 0 /* ⇒...
  • Page 54 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C If the programmer wishes the data bytes to be in a defined state, he can set all data bytes of the message object to zero now: C167CR / C515C: DB0_Mn = 0x00;...

  • Page 55: The Transmission Of A Data Frame With The Can Module

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C Now the CAN module waits for 11 consecutive recessive bits on the CAN bus (bus idle) and can then participate in the bus communication. 6.4.2 The Transmission of a Data Frame with the CAN Module Make sure that you have configured a valid message object as transmit object...

  • Page 56: The Transmission Of A Remote Frame With The Can Module

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C By resetting "CPUUPD" and setting the Transmission Request field "TXRQ" in the Message Control Register, the CAN controller resets NEWDAT and transmits the Data Frame: C167CR: MCR_Mn = 0xE7FF;...

  • Page 57: Evaluation Of A Received Message With The Can Module

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • Then the node which is supposed to provide the requested data will receive the Remote Frame and answer it with the corresponding Data Frame. If this Data Frame is received, the CAN controller sets NEWDAT in the Message Control Register.
  • Page 58 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C If a Data Frame is received in a receive object (DIR=0) and NEWDAT=0 in the corresponding Message Control Register, the CAN controller sets NEWDAT and the data in the Data Field is written into the data bytes of the corresponding receive object.

  • Page 59: Ways Of Handling The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C General hints concerning the interrupt handling: 1. When resetting INTPND, also the corresponding value in the INTID in the interrupt register is cleared.
  • Page 60 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • Now the baudrate is configured via the registers BRPR, BL1, and BL2. The values for the parameters TSEG1, TSEG2, SJW in the registers BL1 and BL2 as well as the value of the baudrate prescaler in the register BRPR are equivalent to those in the Bit Timing Register of the C167CR (not C515C because of the missing prescaler!) and can also be calculated the same way (see section 5.3).
  • Page 61 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C OC = 0x18; /* (Addr. 02h) DOM=LOW, RECESSIVE=HIGH */ 0 0 0 1 1 0 The Clock Control Register is used to determine the output frequency of the SAE 81C90/91's CLK pin.
  • Page 62 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • Please note that after a Remote Frame has been sent out (RTR=1), the corresponding Data Frame is not stored in the same message object. The SAE 81C90/91 could be used as follows: •...

  • Page 63: The Transmission Of A Data Frame / Remote Frame With The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C BYTE0MSGm = 0x00; /* end with writing to data */ /* byte 0! */ • After resetting the bits RES and IM, the initialization of the device is completed. = 0x00;...

  • Page 64: Evaluation Of A Received Message With The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • To transmit a Remote Frame, make sure that you have configured a message object "n" (e.g. MO 2) that handles Remote Frames (RTR = 1) and that carries the right identifier and "0"...

  • Page 65: How To Use The Basic Can Features Of The Can Module And The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C • Then, via the Receive Ready Registers RRR1 and RRR2, the ISR can trace for which message object new data has been received (eg. MO 5). if ((INT &...
  • Page 66 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C It is therefore not possible to configure MO 15 to receive both Data Frames and Remote Frames! The DLC and the contents of the Arbitration Registers is "don't care". Which kind of identifiers will be stored in MO 15 depends on the configuration of the Mask of Last Message (MOLM) and the Global Mask (GM).
  • Page 67 AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C 2. The CAN controller then sets • INTPND and NEWDAT (if MO 15 is configured to receive Data Frames (DIR = 0)) or •...

  • Page 68: The Monitor Mode Of The Sae 81C90/91

    AP29000 Connecting C166 and C500 Microcontroller to CAN Ways of handling the SAE 81C90/91 and the CAN Module on the C167CR / C515C 6.6.2 The Monitor Mode of the SAE 81C90/91 The Monitor Mode of the SAE 81C90/91 works with message object 0 and is enabled by setting bit MM in the CTRL Register (CTRL.0) to "1"...
  • Page 69 : / / w w w . i n f i n e o n . c o m Published by Infineon Technologies AG...

This manual is also suitable for:

C500 series

Table of Contents