Hi 3110 - V Rev K

HI-3110, HI-3111, HI-3112, HI-3113
Avionics CAN Controller

February 2017 with Integrated Transceiver
GENERAL DESCRIPTION FEATURES
The HI-3110 is a standalone Controller Area Network · Implements CAN version 2.0B with programmable bit
(CAN) controller with built in transceiver. The device rate up to 1Mbit/sec. ISO 11898-5 compliant.
provides a complete, integrated, cost-effective solution for · Configurable to support ARINC 825 and
avionics applications implementing the CAN 2.0B CANaerospace Standards.
specification and can be configured to comply with both the
ARINC 825 (General Standardization of CAN Bus Protocol · Serial Peripheral Interface (SPI) (20MHz).
for Airborne Use) and CANaerospace standards. The HI- · Standard, Extended and Remote frames supported.
3110 is capable of transmitting and receiving standard
data frames, extended data frames and remote frames. · 8 maskable identifier filters.
The internal transceiver allows direct connection to the · Filtering on ID and first two data bytes for both
CAN bus without using external components and coupled Standard and Extended Identifiers.
with the host Serial Peripheral Interface (SPI), results in
minimal board space. · Loopback mode for self-test.
· Monitor (Listen-only) and Low Power Sleep Modes
The HI-3110 provides the optimum solution for
with automatic wake-up possible.
applications where minimum host (MCU) overhead is
required, filtering unwanted messages using a maskable · 8-message Transmit and Receive FIFOs.
identifier filter and storing up to 8 messages in the receive · Internal 16-bit free running counter for time tagging of
FIFO. A flexible interrupt scheme allows real time transmitted or received messages.
servicing of the FIFO by the host, if required.
Transmissions are handled using an 8 message transmit · Permanent dominant timeout protection.
FIFO. A Transmit Enable pin can be used by the host to · Short Circuit Protection of -58V to + 58V on CAN_H,
initiate a transmission. The device also provides monitor CAN_L and SPLIT pins (ISO 11898-5).
or listen-only mode, low power sleep mode, loopback
mode for self-test and a re-transmission disable capability · Re-transmission disable capability.
(necessary to implement TTCAN protocol). · Transmit Enable pin.
The HI-3111 is a digital only version of the HI-3110 (no · Industrial and Full Extended temperature ranges
transceiver). This version provides a “protocol only” supported:
solution for customers who wish to use an external o o
Industrial: -40 C to + 85 C.
transceiver and may be used in situations where the o o
Extended: -55 C to + 125 C.
customer requires galvanic isolation between the bus and
digital protocol logic. The HI-3112 provides an option of a
CLKOUT pin instead of a SPLIT pin, which may be used as
PIN CONFIGURATION (Top View)
the main system clock or as a clock input for other devices
in the system. Finally, the HI-3113 provides all options VLOGIC 1 18 INT
(both CLKOUT and SPLIT pins) in a very compact QFN-44 OSCOUT 2 17 MR

package.
OSCIN 3 16 CS
The HI-3110 family is available in industrial and full GP1 4 3110PSI 15 SO
extended temperature ranges, with a “RoHS compliant”
GP2 5 3110PST 14 SI
lead-free option. The design has been independently
3110PSM
validated by C&S group, GmbH, an ISO/IEC 17025 TXEN 6 13 SCK
accredited test house. A copy of the test report is available
SPLIT 7 12 STAT
from Holt on request.
GND 8 11 VDD
CANL 9 10 CANH
18-Pin Plastic SOIC - WB Package
HOLT INTEGRATED CIRCUITS

(DS3110 Rev. K) www.holtic.com 02/17
HI-3110, HI-3111, HI-3112, HI-3113
BLOCK DIAGRAM
VLOGIC
REGISTERS
BIT
CS TIMING
SPI BUS SCK SPI DECODE/
SI ENCODE
SO GND
TRANSMIT
LOGIC & FIFO
TXEN TXD
(HI-3111 only)
HISTORY
FIFO TRANSCEIVER
VDD
GP2
CANH
GP1 INTERRUPTS ERROR
STAT AND STATUS CANL
STATUS & CONTROL
INT RECEIVE
LOGIC & FIFO
SPLIT
(see ordering
information)
FILTERS
16-BIT
OSCIN TIME-TAG RXD
OSCILLATOR COUNTER (HI-3111 only)
OSCOUT (1,2,4,8-BIT
CLK DIV.)
MR
16-BIT
CLKOUT CLOCK DIV
(see ordering OUT
information)
Figure 1. Block Diagram
PRIMARY FUNCTIONS OF HI-3110 LOGIC BLOCKS

SPI PROTOCOL BLOCK 8 message FIFO with optional filters
Handles data transfers between the host and the chip Forwards message data and optional time stamp to the host
REGISTERS BLOCK ERROR BLOCK

Stores configuration data Detects and records errors for protocol management
BIT TIMING BLOCK STATUS AND INTERRUPT

Sets the data strobe and bit period Provides hardware and software options for managing
communications
TRANSMIT BLOCK
Manages transmission protocol OSCILLATOR
8 message FIFO Configuration chooses either the crystal oscillator or and
Confirmation and time stamp of each message sent external clock
is available in the History FIFO
TRANSCEIVER
RECEIVER BLOCK Analog interface connects directly to the CAN bus
Manages reception protocol

2
HI-3110, HI-3111, HI-3112, HI-3113
PIN DESCRIPTIONS
SIGNAL FUNCTION DESCRIPTION NOTES
SCK INPUT SPI Clock. Data is shifted into or out of the SPI interface using SCK 50K ohm pull-down
CS INPUT Chip Select. Data is shifted into SI and out of SO when CS is low. 50K ohm pull-up
SI INPUT SPI interface serial data input 50K ohm pull-down
SO OUTPUT SPI interface serial data output
INT OUTPUT Active high. Programmable interrupt output
STAT OUTPUT Active high. Programmable status output.
TXEN INPUT Active high. Transmit Enable pin. When the TXEN pin is asserted, any message 100K ohm pull-down
in the Transmit FIFO will be automatically loaded to the Transmit buffer and sent
if the bus is available. This pin is logically ORed with the TXEN and TX1M bits
in the CTRL1 register. When the TXEN pin is reset, messages loaded to the
FIFO will not be sent until TXEN or TX1M bits are set in the CTRL1 register.
OSCIN INPUT Crystal input. A parallel resonant crystal can be connected between OSCIN and
OSCOUT. If an external clock is used, it should be connected to the OSCIN pin
and the OSCOUT pin should be left floating. The internal oscillator should be
shut off by setting the OSCOFF bit in the CTRL1 register.
OSCOUT OUTPUT Crystal output. If an external clock is used, this pin should be left floating and
disabled by setting the OSCOFF bit in the CTRL1 register.
GP1 OUTPUT General purpose pin 1, which can be programmed to reflect the values of
interrupt and status flag bits.
GP2 OUTPUT General purpose pin 2, which can be programmed to reflect the values of
interrupt and status flag bits.
CLKOUT OUTPUT Clock output pin with programmable frequency divider.
SPLIT OUTPUT VDD/2 output bias (Powered off in Sleep Mode and when the common mode
bias is greater than 25V).
CANH BUS I/O CAN bus line high.
CANL BUS I/O CAN bus line low.
TXD OUTPUT Transmit Data Out. Connect to TXD input pin on CAN transceiver (e.g. HI-3000). HI-3111 only
RXD INPUT Receive Data In. Connect to RXD output pin on CAN transceiver (e.g. HI-3000). HI-3111 only
5V Logic Tolerant
MR INPUT Active High. Device Master Reset input pin. Asserting this pin resets all registers 50K ohm pull-down
and memory buffers to their default state at start-up.
VDD POWER 5V supply voltage input.
VLOGIC POWER 3.3V supply voltage input. This supply is used to drive the host digital logic I/O.
It can either be connected directly to VDD (+5V) or a +3.3V supply.
GND POWER Supply voltage ground.

3
HI-3110, HI-3111, HI-3112, HI-3113
FUNCTIONAL OVERVIEW RECEIVER

The receiver state machine automatically handles all CAN
The HI-3110 is the first single chip product to integrate both 2.0B protocol requirements. The receiver supports eight
the CAN (Controller Area Network) protocol and analog sets of filters and masks and each allows filtering of a full
interface transceiver on a single IC. The protocol conforms
CAN ID (extended or not) and two bytes of data. Even when
to CAN version 2.0B and is compliant with ISO 11898-
1:2003(E) specification. The transceiver is compliant with filtering is enabled, message data is always accessible as
ISO 11898-5 specification. received via the Temporary Receive Buffer, and retrievable
by SPI op codes 0x42 and 0x44.
Configuration options include an internal Loopback mode If the Filter/Mask option is set (FILTON bit in Control Register
that does not disturb the bus, a Monitor only mode, and a 1), only messages that match one of the 8 stored data
Sleep mode that includes an option to either wake up patterns are passed into the FIFO. Note that the Mask option
automatically when data is present on the bus, or by host allows certain bits of the programmed filter bits to be “don't
command. The following sections describe some of the key care.” If the Filter/Mask option is not set, then all valid
features. messages are passed to the FIFO. When the FIFO is full (8
completed messages received), the next received message
SPI and REGISTERS is not loaded in the FIFO.
To minimize the footprint, a 20 MHz standard four wire SPI
(Serial Peripheral Interface) is provided to manage the flow ERROR CONTROL
of data between the host microcontroller and the HI-3110. Errors are detected per ISO 11898-1:2003(E) and
Complete messages are loaded and retrieved with single detections are counted and used by the protocol state
SPI op codes. On the receive side, SPI op code options may machines. Active, Passive, and Bus Off conditions are
be used to retrieve the whole message or just the data. An managed per the CAN standard. A configuration bit is
option to include a time tag or no time tag may also be provided to allow automatic recovery from Bus Off.
specified. On the transmit side, each message can be
assigned an identifier which allows monitoring of the STATUS and INTERRUPTS
Transmit History FIFO to confirm the successful completion The Message Status Register, MESSTAT, provides
of a transmission along with the time stamp. In addition the information about the current state of the receiver and
transmitter logic automatically assembles the message transmitter operation. In addition, the Interrupt Flag
frame based on the data presented. Register, INTF, monitors 8 operational conditions, any or all
of which may be directed to the INT pin by enabling bits in the
BIT TIMING Interrupt Enable Register, INTE. Similarly, the Status Flag
Bit timing is controlled with standard CAN options. These Register, STATF, bits reflect the status of selected FIFO and
include control of the Resychronization Jump Width (SJW), Error properties. Any or all of these conditions may be
Prop delay Phase Seg 1 (TSeg1), Phase Seg 2 (TSeg2), the directed to the STAT pin by setting the enable bits in the
number of samples, and the derivation of Tq from the system Status Flag Enable Register, STATFE.
clock using a prescaler. The maximum bit rate is 1 MBit/sec. To provide additional hardwired flag options, the GP1 and
Upon reset, the chip automatically enters Initialization mode GP2 pins may also be programmed to reflect any of the
which allows programming of the Bit Timing before entering Interrupt or Status Flag bits.
Normal mode.
OSCILLATOR and TIME TAG
TRANSMITTER A configuration bit allows a choice for the source of the
The transmitter state machine automatically handles all system clock. Either the on-board crystal oscillator may be
CAN 2.0B protocol requirements. Messages for selected or an external clock may be provided at the OSCIN
transmission are first loaded into a FIFO and transmission pin.
may start upon availability of data in the FIFO. Assertion of On product versions with the CLKOUT pin, a programmable
the TXEN pin or configuration bits in Control Register 1 allow division of the system clock is provided. The clock source for
either continuous transmission until the FIFO is empty or the 16 bit Time Tag Counter is derived from a separate
only one message from the FIFO at a time. One shot (no programmable division of the system clock. SPI op codes
retry) transmission may also be enabled by setting the OSM provide for reading and resetting the Time Tag Counter.
and TX1M bits. SPI op codes are provided to clear the TRANSCEIVER
Transmit FIFO and to abort transmission. The HI-3110 contains an integrated transceiver operating
4
HI-3110, HI-3111, HI-3112, HI-3113
from 5V and the line driver is capable of maintaining a

detectable signal for bus lengths well in excess of
MONITOR MODE
recommended CAN 2.0B standards. The digital logic and IO Monitor mode (also known as listen-only or silent mode)
can be powered from 3.3V or 5V. allows the HI-3110 to monitor all bus activity without
disturbing the bus. No messages or dominant bits (such as
PROTECTION FEATURES ACK or active error frame bits) are transmitted to the bus
The BUS and SPLIT pins are protected against ESD to over while in this mode. Also, the error counters are reset and
4KV (HBM) and from shorts between -58V to +58V deactivated. Messages from the bus are received in the
same way as Normal Mode and messages that are not
continuous, as specified in ISO 11898-5.
acknowledged by another node on the bus are ignored i.e.
In addition, a Permanent Dominant Timeout protection is
any frame containing an error will be ignored. Acceptance
implemented by means of an independent counter filters can be set up to reject or accept specific messages
monitoring the dominant transmission state and into the FIFO and all interrupt flags are set as required in the
automatically shutting off the transmission if it exceeds usual way. Monitor mode is activated by programming the
typically 2ms. MODE<2:0> bits to <010> in the CTRL0 register.
SLEEP MODE
MODES OF OPERATION The HI-3110 can be placed in a low power sleep mode if
there is no bus activity and the transmit FIFO is empty. In
The HI-3110 supports five modes of operation, namely,
this mode, the internal oscillator and all analog circuitry
Initialization Mode, Normal Mode, Loopback Mode, Monitor
(transceiver) are off, drawing typically less than 20mA. Note
Mode and Sleep Mode.
that the SPI bus is active during sleep mode, so it is possible
for the host to communicate with the HI-3110 while it is
INITIALIZATION MODE
asleep (e.g. load transmit FIFO). Sleep mode is exited by
Initialization mode is used to configure the device before selecting an alternative mode of operation, or automatic
normal operation. Bit timing registers and acceptance wake up following bus activity can be enabled by setting the
filters and masks can only be modified in this mode. WAKEUP bit in the CTRL0 register - in this case a low power
Initialization mode is the default mode following RESET and receiver monitors the bus for a detectable dominant bit..
can also be activated by programming the MODE<2:0> bits The device will wake up in Monitor Mode. Note that it will
to <1xx> in the CTRL0 register. Switching to Initialization take a finite time for the oscillator and analog circuitry to
mode resets the receiver and transmitter. During come back on line. Since the internal oscillator takes a finite
initialization mode, the error counters are held reset. time to wake up, the message which caused the wake-up
may not be stored.
NORMAL MODE
Sleep mode is activated by programming the MODE<2:0>
Normal mode is the standard operating mode of the HI-3110. bits to <011> in the CTRL0 register. However, the actual
In this mode, the HI-3110 can transmit, receive and mode change will only occur whenever the CAN bus is quiet.
acknowledge messages from the CAN bus, handling all If the chip is transmitting, the mode change is delayed until
aspects of the CAN protocol. Normal mode is activated by the transmission is complete. If there is bus activity, the
programming the MODE<2:0> bits to <000> in the CTRL0 mode change is delayed until the receiver protocol control
register. detects an inter-message gap.
LOOPBACK MODE CAN PROTOCOL OVERVIEW

Loopback mode is used for self-test. The transceiver digital The HI-3110 supports Standard, Extended and Remote
input is fed back to the receiver without being transmitted to Frames, as defined in the CAN specification IS0 11898-
the bus. Messages are transmitted from the transmit FIFO 1:2003(E) (also known as CAN 2.0B).
in the usual way and received by the receive FIFO as if they
were received from a remote node on the bus. BIT ENCODING
Acceptance filters can be set up to accept or reject specific CAN frames are encoded according to the Non-Return-To-
messages into the FIFO and all interrupt flags are set as Zero (NRZ) method with bit stuffing. NRZ means that the
required in the usual way. While in this mode, any bus generated bit level is constant during the total bit time and
activity is ignored. Loopback is activated by programming consecutive bits do not return to a neutral or rest condition.
the MODE<2:0> bits to <001> in the CTRL0 register.
5
HI-3110, HI-3111, HI-3112, HI-3113
This means that a bit stream of “1s” or “0”s appears errors by computing a 15-bit CRC sequence from the
continuous on the bus. A logic “0” is called a dominant bit previous bit stream (SOF, arbitration field, control field and
and a logic “1” is called a recessive bit. data field, excluding stuff bits). The last bit in the CRC field is
the CRC delimiter bit (always recessive).
Bit stuffing is used to ensure frequent enough transitions
occur to achieve synchronization. Every time a transmitter After the CRC field is the Acknowledge Field (ACK Field).
detects five consecutive bits of the same polarity in the bit The first bit is the ACK Slot bit. A transmitting node sends a
stream to be transmitted, it inserts a bit of opposite polarity recessive bit (logic 1) during the ACK slot. Any node which
into the actual transmitted bit stream. receives the message error-free acknowledges the
reception by placing a dominant bit (logic 0) in the ACK slot,
This bit stuffing rule applies to the Start-of-Frame field, over-writing the recessive bit of the transmitter. The final bit
arbitration field, control field, data field and CRC sequence. in the ACK field is a recessive ACK delimiter bit. Therefore,
The CRC delimiter, ACK field and End-Of-Frame fields are of the dominant ACK slot bit is surrounded on each side by a
fixed form and not stuffed (see below for definition of these recessive bit.
fields). Furthermore, Error frames and Overload frames are
also of fixed form and not stuffed. Each data frame is delimited by an End-Of-Frame field
(EOF). The EOF consists of seven recessive bits.
An example of how the bits in a stuffed bit stream might look
is shown below. Following the EOF, there is a gap to the next frame called the
Interframe Space (IFS) . The IFS consists of two bit fields,
00101011111O0000I1100000I11000 Intermission and Bus-Idle. The Intermission consists of
three recessive bits, however the following notes apply:
0 = dominant bit, O = dominant stuffed bit. a) detection of a dominant bit on the bus at the third slot is
1 = recessive bit, I = recessive stuffed bit. interpreted as a SOF,
b) detection of a dominant bit in either the first or second
MESSAGE FRAMES slots results in generation of an overload frame (see below).
STANDARD DATA FRAME The bus idle period is of arbitrary length and consists of
The standard data frame is shown in figure 2. The frame recessive bits. A dominant bit detected during this period is
starts with a Start-of-Frame (SOF) bit. This is a dominant bit interpreted as a SOF.
that identifies the start of the data frame on the bus.
EXTENDED DATA FRAME
The SOF is followed by the 12-bit arbitration field. The The extended data frame is shown in figure 3. In this frame
arbitration field consists of an 11-bit identifer, ID28 - ID18, format, SOF is followed by a 32-bit arbitration field consisting
and the Remote Transmission Request (RTR) bit. The RTR of a 29-bit identifier, ID28 - ID0. The first 11 most significant
bit is used to distinguish between a data frame (RTR bit bits of the ID are know as the base identifier. This is followed
dominant, logic 0) and a remote frame (RTR bit recessive, by the Substitute Remote Request (SRR) bit, which is
logic 1). defined as recessive. Following the SRR bit is the IDE bit,
which is defined as recessive for extended data frames.
Following the arbitration field is the 6-bit control field. The
Note that the SRR bit is in the same slot as the RTR bit of the
first bit of the control field is the Identifier Extension flag bit
standard frame and the IDE bits are also in corresponding
(IDE). This is used to distinguish between standard and
slots. This means if standard and extended identifier data
extended identifiers and must be dominant (logic 0) for
frames with identical base identifiers are transmitted
standard data frames. The next bit, r0, is specified by the
simultaneously, the standard identifier data frame will win
CAN protocol as a reserved bit for future expansion. This bit
arbitration (see Bitwise Arbitration section below).
must be transmitted dominant, but receivers must be
capable of receiving either a dominant or recessive bit. The The SRR and IDE bits are followed by the remaining 18 bits
final 4 bits of the control field make up the data length code of the identifier (extended ID) and the last bit of the
(DLC). The binary value of this 4-bit field specifies the arbitration field is the RTR bit. The RTR bit has the same
number of data bytes in the data payload (0 - 8 bytes). Note: function as in the standard frame format.
All binary combinations greater than or equal to <1 0 0 0>
specify 8 bytes of data. Following the arbitration field is the 6-bit control field. The
first two bits, r1 and r0, are specified by the CAN protocol as
After the control field is the data field, which contains a data reserved bits for future expansion. Both these bits must be
payload equal to the number of bytes specified by the DLC transmitted dominant, but receivers must be able to receive
(see note above). all combinations of dominant or recessive bits. The final 4
bits of the control field is the data length code (DLC). The
The data field is followed by the 16-bit Cyclic Redundancy
binary value of this 4-bit field specifies the number of data
Check (CRC) field. This is used to check transmission
bytes in the data payload (0 - 8 bytes). Note: All binary
6
HI-3110, HI-3111, HI-3112, HI-3113
combinations greater than or equal to <1 0 0 0> specify 8
bytes of data.

7
HI-3110, HI-3111, HI-3112, HI-3113
Standard Data Frame
.....
Bus Idle or SOF
IFS
1 1 1 1 1 1 1 1 1 1 1
Intermission
EOF
7
ACK Del
ACK Slot bit
CRC Del KEY.
1
SOF Start-Of-Frame
IDxx Identifier bit xx
RTR Remote Transmission Request bit
IDE Identifier Extension Flag
CRC Field
r0 Reserved bit 0
DLCx Data Length Code bit x
15
16
CRC Del Cyclic Redundancy Check Delimiter

ACK Slot bit Acknowledge Slot bit
ACK Del Acknowledge Delimiter
EOF End-Of-Frame
IFS Interframe space
Data Frame (44 + 8n bits)
8
8n (0 £ n £ 8)
Data Field
......
8
DLC0
Length
Control Field
Code
Data
4
DLC3
6
r0 Reserved bit
IDE
0 0
RTR
ID18
Arbitration Field
Base Identifier
12
ID23
11
ID28
SOF
0
Figure 2. Standard Frame Format.

8
HI-3110, HI-3111, HI-3112, HI-3113
Extended Data Frame
........
Bus Idle or SOF
IFS
1 1 1 1 1 1 1 1 1 1 1
Intermission
EOF
7
ACK Del
ACK Slot bit
CRC Del
1
KEY.
CRC Field
SOF Start-Of-Frame
15
16
IDxx Identifier bit xx

SRR Substitute Remote Request bit
IDE Identifier Extension Flag
RTR Remote Transmission Request bit
r1 Reserved bit 1
r0 Reserved bit 0
DLCx Data Length Code bit x
CRC Del Cyclic Redundancy Check Delimiter
8
ACK Slot bit Acknowledge Slot bit

ACK Del Acknowledge Delimiter
8n (0 £ n £ 8)
Data Field
EOF End-Of-Frame
....
IFS Interframe space

Data Frame (64 + 8n bits)
DLC0
Control Field
Length
Code
Data
4
6
DLC3
r0
r1 Reserved bits
RTR
0
ID0
Extended Identifier
18
ID9
Arbitration Field
32
ID17
IDE
1 1
SRR
ID18
Base Identifier
ID23
11
ID28
SOF
0
Figure 3. Extended Frame Format.

9
Remote Frame
Remote Frame with Extended ID (64 bits)
32 6 16 7
Arbitration Field Control Field CRC Field EOF IFS
11 18 4 15
10
SOF
ID28
ID23
ID18
SRR
IDE
ID17
ID9
ID0
RTR
r1
r0
DLC3
DLC0
CRC Del
ACK Slot bit
ACK Del
0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 .....
Base Identifier Extended Identifier Data
Length
Code

Intermission
Reserved bits
Bus Idle or SOF
HI-3110, HI-3111, HI-3112, HI-3113
No Data Field. See NOTE regarding Data Length Code.
Figure 4. Remote Frame Format (Extended Identifier).

Error Frame
Data Frame with error detected during data transmission
32 6 8n (0 £ n £ 8)
Arbitration Field Control Field Data Field
11 18 4 8 8
SOF
ID28
ID23
ID18
SRR
IDE
ID17
ID9
ID0
RTR
r1
r0
DLC3
DLC0
0 1 1 0 ....
Base Identifier Extended Identifier Data
Length
11
Code
Error Frame
Reserved bits
Error Flag Field
Figure 5. Error Frame Format.

Intermission
6 Up to 6 bits 8
Active Error Error
HI-3110, HI-3111, HI-3112, HI-3113
Error Echo Delimiter

Flag Flag
0 0 0 0 0 0 0 0 .... 0 0 1 1 1 1 1 1 1 1 1 1 1
Data Frame or Remote Frame
7
EOF IFS
Overload Frame
.... 1 1 1 1 1 1 1 1 0
12
Overload Frame
Illegal Dominant Bit in IFS
Figure 6. Overload Frame Format

Overload Flag Field
HI-3110, HI-3111, HI-3112, HI-3113
Intermission
6 Up to 6 bits 8
Overload Overload Overload
Flag Echo Delimiter
Flag
0 0 0 0 0 0 0 0 .... 0 0 1 1 1 1 1 1 1 1 1 1 1
HI-3110, HI-3111, HI-3112, HI-3113
BIT WISE ARBITRATION
Bitwise arbitration works by comparing each node’s
The CAN standard resolves data contention on the bus transmitted data bit by bit. All nodes are synchronized by
using a scheme called Carrier Sense Multiple adjusting individual bit times as a function of bit time quanta
Access/Collision Detection-Carrier Resolution (CSMA/CD- (see section on bit timing). Synchronization takes place on
CR). recessive to dominant edges. A Hard Synchronization at the
start of each frame and subsequent re-synchronizations
Carrier Sense: Each node waits for a period without bus during a message frame ensures corresponding bits match
activity (bus idle state) before attempting transmission. in time during a given transmission cycle. When a node
Multiple Access: Every node on the bus has equal access transmits a recessive bit on the bus, but detects a dominant
to the bus for transmitting. bit on it’s receiver, it realizes arbitration is lost and it
Collision Detection: Collisions occur if two nodes attempt immediately ceases transmission and becomes a receiver.
to transmit at the same time. It will then wait for the next bus idle state and attempt to re-
Collision Resolution: Collisions are resolved by bitwise transmit. Eventually, lower priority messages will gain
arbitration. Highest priority messages (lowest binary access to the bus. Figure 7 shows an example of how this
identifiers) are sent first without delay and lower-priority works for a frame with a standard identifier.
messages are automatically re-transmitted later. A dominant
bit (logic 0) has priority over a recessive bit (logic 1).
Start-OF-Frame
Standard ID Arbitration Field

ID28
ID18
RTR
TXCAN: Node 1 1
0
TXCAN: Node 2 1
0
TXCAN: Node 3 1
0
CAN Bus differential

signal (not to scale)
Node 2 loses arbitration
Node 3 loses arbitration
Figure 7. Bitwise Arbitration.

13
HI-3110, HI-3111, HI-3112, HI-3113
The CAN standard divides the bit time into four segments,
BIT TIMING namely, synchronization segment (Sync Seg), propagation
time segment (Prop Seg), phase buffer segment 1 (Phase
The CAN protocol supports a broad range of bit rates, from a
Seg1) and phase buffer segment 2 (Phase Seg2). This is
few kHz up to 1MHz (Note: the minimum bit rate of the HI-
illustrated in figure 8. The HI-3110 fixes the Sync Seg at
3110 is limited to 40kHz by the permanent dominant timeout
1Tq. Prop Seg and Phase Seg1 are treated as one time
protection of the transceiver). Every node on the network
segment, TSeg1, which is programmable from 2Tq to 16Tq.
has it’s own clock generator (typically a quartz oscillator),
Phase Seg2 is a second time segment, TSeg2, which is
however the bit rate must obviously be the same for every
programmable from 2Tq to 8Tq (Note: Not all combinations
node on the bus. Therefore, each CAN node must be
are valid, see below for examples).
configurable to generate the nominal bit rate as a function of
it’s own oscillator frequency, fOSC. This is done by generating
a time quanta (TQ) clock, whose period tTQ is related to the Synchronization Segment (Sync Seg)
oscillator frequency by a Baud Rate Prescaler value, BRP as
follows: The Sync Seg is the first segment of the bit time and is used
to synchronize the various nodes on the bus. A bit edge is
tTQ = 2•BRP/fOSC (1) expected to occur within the Sync Seg.
The TQ clock is used to construct the bit time in terms of time Propagation Time Segment (Prog Seg)
quanta, such that one time quantum, Tq, equals one TQ
clock period, tTQ, as shown in figure 8 below. The Prog Seg is used to compensate for physical delays on
The CAN system nominal bit rate (BR) is defined in terms of the bus, which include signal propagation delay time on the
the nominal bit time, tb, as bus and internal node delay times. For two nodes A and B
communicating on the bus, Prog Seg must be greater than
BR = 1/tb (2) or equal to the sum of both nodes internal delays plus twice
the bus line propagation delay between the two nodes.
Therefore, the nominal bit rate is related to the TQ clock
period by the following relationship
BR = 1/(tTQ x (number of time quanta per bit)) (3)
tOSC
OSC
tTQ Baud Rate Prescaler
TQ
Clock
Nominal bit time, tb

Tq
Sync TSeg1 = TSeg2 = Sync TSeg1 TSeg2

Seg Prop Seg + Phase Seg 1 Phase Seg2 Seg
Sample
Point
Figure 8. CAN Bit Time

14
HI-3110, HI-3111, HI-3112, HI-3113
Phase Buffer Segment 1 and Phase Buffer frame.
Segment 2 (Phase Seg1 and Phase Seg2) Re-synchronization results in the shortening or
The phase buffer segments are used to compensate for lengthening of the bit time such that the position of the
phase errors on the bus. Phase Seg1 can be lengthened or sample point is shifted with respect to the edge causing the
Phase Seg2 can be shortened duringthe re-synchronization re-synchronization. For e > 0, Phase Seg 1 is lengthened by
bit period automatically by the HI-3110 so that the bit time the magnitude of the phase error, up to a maximum of SJW.
can be adjusted to account for phase errors. The upper limit For e < 0, Phase Seg 2 is shortened by the magnitude of the
by which the lengthening ( or shortening) can occur is set by phase error, up to a maximum of SJW.
the re-synchronization jump width (SJW), explained in
more detail below.
Examples
1) CAN bit rate (BR) = 125kHz, fOSC = 12MHz.
Sample Point Assume sample point (at end of TSeg1) will occur at 75% of
The sample point is the point in the bit time at which the bit bit time. Hence, for Sync Seg = 1Tq, TSeg1 = 5 Tq and
logic level is interpreted. It is located at the end of Phase TSeg2 = 2Tq. Therefore, total bit time will be 8Tq. Chose
Seg1. The HI-3110 also allows three sample points to be SJW = 1Tq.
For 125kHz, the bit time needs to be 1/125kHz = 8μs.
taken. In this case, two other sample points are taken prior
Hence, 1Tq = 1μs. Using equation (1) => BRP = 6.
to the end of Phase Seg1 (at one-half TQ intervals) and the
value of the bit is determined by a majority decision. Three 2) CAN bit rate (BR) = 1MHz, fOSC = 32MHz.
sample points are typically only used at low bit rates. Note: Assume sample point (at end of TSeg1) will occur at 75% of
ARINC 825 states that there shall be only one sample per bit, bit time. For Sync Seg = 1Tq, then TSeg1 = 11Tq and TSeg2
taken at the end of Phase Seg1. = 4Tq. Therefore, total bit time will be 16Tq. Chose SJW =
1Tq.
The time required for the logic to determine the bit level of a
For 1MHz, the bit time needs to be 1/1MHz = 1μs. Hence,
sampled bit is known as the information processing time
1Tq = 62.5ns. Using equation (1) => BRP = 1.
(IPT). According to the standard, IPT can be up to 2Tq.
Since Phase Seg2 occurs after the sample point, Phase Note: Choosing the sample point at 75% of the bit time is a
Seg2 must be greater than or equal to the worst case IPT requirement of ARINC 825. The oscillator frequency must
(2Tq). be chosen such that a valid value of BRP (integer) can
generate the TQ clock (e.g. in example 2 above, using a
lower oscillator frequency than 32MHz results in BRP < 1).
Phase Errors (e)
If a bit edge occurs within the Sync Seg as expected, there is
no phase error (e = 0). However, if an edge occurs outside
Sync Seg, a phase error is deemed to have occurred. If the
edge occurs after Sync Seg (edge occurs “late”), the phase
error is positive (e > 0), whereas if the edge occurs before
Sync Seg (edge occurs “early”), the phase error is negative
(e < 0).
Synchronization
Synchronization is carried out only on recessive-to-
dominant bit edges and is used to ensure the bit times of all
nodes on the bus are synchronized. This is necessary for
arbitration and message acknowledgment to function
properly. Only one synchronization can occur per bit time.
Hard synchronization forces the bit edge to lie within the

Sync Seg, regardless of the phase error. Hard
synchronization only occurs on reception of the start of a

15
HI-3110, HI-3111, HI-3112, HI-3113
REGISTERS
This section describes the HI-3110 registers. All register bits are active high. Unless otherwise indicated, all registers are reset
in software to the logic zero condition after Master Reset. For all registers, bit 7 is the most significant:
REGISTER R/W DESCRIPTION SPI WRITE SPI READ

OP-CODE OP-CODE
CTRL0 R/W Control Register 0 0x14 0xD2

CTRL1 R/W Control Register 1 0x16 0xD4
BTR0 R/W Bit Timing Register 0 0x18 0xD6
BTR1 R/W Bit Timing Register 1 0x1A 0xD8
TEC R/W Transmit Error Counter Register 0x26 0xEC
REC R/W Receive Error Counter Register 0x24 0xEA
MESSTAT R Message Status Register N/A 0xDA
ERR R Error Register N/A 0xDC
INTF R Interrupt Flag Register N/A 0xDE
INTE R/W Interrupt Enable Register 0x1C OxE4
STATF R Status Flag Register N/A 0xE2
STATFE R/W Status Flag Enable Register 0x1E 0xE6
GPINE R/W General Purpose Pins Enable Register 0x22 0xE8
TIMERUB R Free-Running Timer Upper Byte Register N/A 0xFA*
TIMERLB R Free-Running Timer Lower Byte Register N/A 0xFA*
Note: Free-running counter registers, TIMERUB:TIMERLB are read with a single SPI Op-code (0xFA) as a 16-
bit value in two SPI data bytes.
Power-On-Reset
Following power-on, the HI-3110 will automatically perform a Master Reset and return all registers to the default state.
Following reset, the device will default to Initialization Mode to allow programming of Control and Bit Timing Registers (see
following sections).

16
HI-3110, HI-3111, HI-3112, HI-3113
CONTROL REGISTER 0: CTRL0
ES P
R EU
O 2
M E1
W E0
0
BO ET
TT IV1
E
IV
D
D
D
AK
D
D
O
TT
M
M
(Write, SPI Op-code 0x14)
(Read, SPI Op-code 0xD2)
7 6 5 4 3 2 1 0
MSB LSB
Bit Name R/W Default Description

7-5 MODE2:0 R/W 1,0,0 Mode select bits <2:0>.
These bits select the mode of operation as follows.
000: Normal Mode. Normal CAN operation.
001: Loopback Mode. The transceiver digital input is fed back to the receiver without
disturbing the bus. This mode can be used for test purposes,
allowing the HI-3110 to receive its own messages.
010: Monitor Mode. The HI-3110 can be set up to monitor bus activity without
transmitting to the bus (no ACK bits or error frames are sent in this
mode). Receive filters can be programmed in Initialization Mode to
buffer selected messages.
011: Sleep Mode. The HI-3110 can be placed in a low power sleep mode if there is no
bus activity and the transmit FIFO is empty. Sleep mode is exited
by selecting an alternative mode of operation, or automatic wake
up following bus activity can be enabled by setting the WAKEUP
bit. The device will wake up in Monitor mode.
1xx: Initialization Mode. The device must be in this mode for bit timing and filter set-up.
This is the default following reset. The host exits initialization
mode by selecting an alternative mode of operation.
4 WAKEUP R/W 0 Wake-Up Enable.

When this bit is set, the HI-3110 will automatically wake up from Sleep Mode to Monitor Mode
when it detects activity on the bus.
1 = Automatic wake-up enabled. When the device wakes up from
Sleep Mode, the WAKEUP bit will be set in the Interrupt Flag
Register, INTF. A hardware interrupt can be generated at the INT
pin by setting the WAKEUPIE bit in the Interrupt Enable Register.
0 = Automatic wake-up not enabled. In this case, wake-up from Sleep
Mode is initiated by the host by selecting another mode of
operation. When WAKEUP = 0, all bus activity is ignored.
3 RESET R/W 0 Setting this bit causes HI-3110 reset to occur. Following reset, the CTRL0 register should be
written with < 1 x x x 0 x x x >. This will clear the RESET bit and also avoid unpredictable
behavior by ensuring the part is programmed to Initialization Mode, ready for set-up.
A reset may also be performed by setting the MR pin or issuing the “MR” SPI command, 0x56.
1 = Master Reset (same as MR pin = 1).
0 = Normal Operation (same as MR pin = 0).
2 BOR R/W 0 Bus-off Reset.

When this bit is set, automatic bus-off recovery is initiated following 128 occurrences of 11
consecutive recessive bits on the bus. The HI-3110 will become error-active with both its error
counters set to zero and resume operation in Normal Mode.
1 = Automatic bus-off recovery.
0 = The host is responsible for bus-off recovery (default).
1-0 TDIV1:0 R/W 0,0 Time Tag Clock Division Bits <1:0>. See TIMERUB and TIMERLB register descriptions.
00 = No division (counts every bit clock).
01 = Divide by 2 (counts every 2 bit clocks).

17
HI-3110, HI-3111, HI-3112, HI-3113
CONTROL REGISTER 1: CTRL1
0
F
LK 1
IV
- OF
C DIV
O ON
D
TX N
1M
SM
SC
LT
E
LK
TX
FI
O
C
7 6 5 4 3 2 1 0
MSB LSB

7 TXEN R/W 0 Transmission Enable.
This bit is logically ORed with the TXEN pin. When this bit is asserted, each message in the
FIFO will be sequentially loaded to the transmit buffer and sent if the bus is available. If this bit
is not set, a transmission can be enabled by either the TXEN pin or the TX1M bit. If the TXEN
pin is pulled low during a transmission, the current message being transmitted will be
completed. Any additional messages in the FIFO will not be transmitted.
1 = Enable transmission and send any messages in FIFO (until
empty if TXEN is held set).
0 = Wait for transmission enable or TX1M bit set before sending next
message in FIFO.
6 TX1M R/W 0 Enable transmission of only next message.

This bit is applicable only if TXEN = 0. It is reset automatically upon completion of a successful
transmission or by initiation of transmission if the OSM bit is set.
1 = Enable transmission of only next message in FIFO when TXEN = 0.
0 = Wait for transmission enable or TX1M bit set before sending next
message in FIFO.
5 OSM R/W 0 One-Shot Mode Enable.

OSM is intended to be used ONLY with the TX1M bit. If OSM is enabled and TX1M is set, the
controller transmits only once and does not attempt re-transmission upon loss of arbitration or
error. This feature is necessary to support the implementation of fixed time slots in the
Time-Triggered CAN standard (TTCAN). Note: Un-transmitted messages will remain in
the FIFO. If a new message is required on the next transmission cycle, the user must
first clear the FIFO with SPI command 0x54 and then reload the new message.
1 = Enable one-shot mode.

0 = Messages will re-transmit according to CAN protocol.
4 FILTON R/W 0 Filter on enable.

This bit is set to turn on the HI-3110 CAN ID filtering mechanism. The default after reset is
FILTON = 0, meaning filtering is turned off and every valid CAN message is accepted into the
receive FIFO. Note: The device must be in initialization mode in order to program the
acceptance filters and masks.
1 = Enable CAN ID filtering.
0 = No CAN ID filtering (every valid message accepted into
receive FIFO).
3 OSCOFF R/W 0 Oscillator off. This bit should be set to a one if an external clock is used. In this case the
external clock is connected to the OSCIN pin and OSCOUT should be left floating.
1 = Shuts off external OSCOUT pin.
0 = OSCOUT pin enabled.
2 Not used R/W 0

1-0 CLKDIV1:0 R/W 00 External CLKOUT division bits <1:0>
00: Divide by 1.
01: Divide by 2.
10: Divide by 4.
11: Divide by 8.

18
HI-3110, HI-3111, HI-3112, HI-3113
BIT TIMING REGISTER 0: BTR0
SJ 1
BR 0
P0
BR 4
BR 3
BR 2
BR 5
P1
W
W
P
P
P
P
BR
SJ
7 6 5 4 3 2 1 0
MSB LSB
BTR0 defines the value of the Re-synchronization Jump Width (SJW) and the Baud Rate Prescaler (BRP). This register can be read
anytime and written only in init mode (MODE<2:0> bits set to <1xx> in the CTRL0 register).

7-6 SJW1:0 R/W 0 Re-synchronization Jump Width bits <1:0>.
These bits are used to compensate for phase shifts between different clock oscillators on the
bus. They define the maximum number of time quanta (Tq) a bit can be shortened or
lengthened to allow a node achieve re-synchronization to the edge of an incoming signal.
Note that one time quantum (Tq) is the single unit of time within a bit time (see Bit Timing
section).
SJW bits <1:0>

00: SJW = 1 Tq
01: SJW = 2 Tq
10: SJW = 3 Tq
11: SJW = 4 Tq
Note: ARINC 825 states that the Re-synchronization Jump Width shall be 1 Tq
5-0 BRP5:0 R/W 0 Baud Rate Prescaler bits <5:0>.

The baud rate prescaler relates the system oscillator frequency, fOSC, to the CAN bit time as
described in the bit timing section.
BRP bits <5:0>

000000: BRP = 1
000001: BRP = 2
000010: BRP = 3
000011: BRP = 4
.
etc.
.
111111: BRP = 64

19
HI-3110, HI-3111, HI-3112, HI-3113
BIT TIMING REGISTER 1: BTR1
0
E -2
E -0
E -3
E -2
E -1
EG -1
1-
TS 2
TS G2
TS G1
TS G1
TS G2
TS G1
TS P
EG
M
SA
(Write, SPI Op-code 0x1A)
7 6 5 4 3 2 1 0
MSB LSB
BTR1 configures the CAN protocol bit timing segments in terms of time quanta (Tq) and sets the number of sampling points. This
register can be read anytime and written only in init mode (MODE<2:0> bits set to <1xx> in the CTRL0 register).

7 SAMP R/W 0 Samples per bit.
This bit configures how many samples are taken per bit.
1 = three samples per bit.
0 = one sample per bit.
Notes: ARINC 825 states that there shall be only one sample per bit. Furthermore, it is
recommended to sample only once at higher CAN bit rates. Bit sampling occurs at the end of
Phase Seg1.
6-4 TSEG2-2:0 R/W 0 Time Segment 2 bits <2:0>.

Tseg2 = Phase Seg2 of the CAN protocol bit timing specification. Bits TSEG2-2:0 specify the
number of time quanta in Phase Seg2. Note: Not all combinations are valid, since Phase Seg
2 must be greater than SJW.
TSEG2 bits <2:0>

000: Not valid
001: Tseg2 = 2 Tq clock cycles
.
etc.
.
3-0 TSEG1-3:0 R/W 0 Time Segment 1 bits <3:0>.

Tseg1 = Prop Seg + Phase Seg1 of the CAN protocol bit timing specification. Bits TSEG1-3:0
specify the number of time quanta in Prop Seg + Phase Seg1. Note: Not all combinations are
valid, since Prop Seg + Phase Seg1 ³ Phase Seg 2. The CAN protocol states that the
minimum number of Tq in a bit time shall be 8.
TSEG1 bits <3:0>

0000: Not valid
.
.
.
Notes: ARINC 825 states that the sample point shall not be less than 75% of the bit time. In
this case, Tseg1 should be a minimum of 5Tq for Phase Seg2 (Tseg2) = 2Tq and SJW = 1Tq.

20
HI-3110, HI-3111, HI-3112, HI-3113
TRANSMIT ERROR COUNTER REGISTER: TEC

TEC7:0

(Read, SPI Op-code 0xEC)
7 6 5 4 3 2 1 0
MSB LSB
The TEC register reflects the current value of the CAN Transmit Error Counter. This register can be written by SPI command for test
purposes.

7-0 TEC7:0 R/W 0x00 Transmit Error Counter bits <7:0>.
0 £ TEC £ 95: Error active status.
96£ TEC £ 127: Error active status. Error warning flag, ERRW, set in STATF register. This
may be used to generate a hardware interrupt if ERRWIE bit is set in STATFE register.
128 £ TEC£ 255: Error passive status. Transmit error passive flag, TXERRP, set in ERR
register. ERRP also set in STATF register. This may be used to generate a hardware interrupt if
ERRPIE bit is set in STATFE register.
TEC > 255: Bus-off status. Bus-off flags, BUSOFF, set in ERR and STATF registers. The
latter may be used to generate a hardware interrupt if BUSOFFIE bit is set in STATFE register.
The HI-3110 will, after entering bus-off state, automatically recover to error active status
without host intervention if the BOR bit is set in control register CTRL0 and 128 x 11
consecutive recessive bits are detected on the bus. If the BOR bit is not set, bus-off recovery is
managed by the host.
RECEIVE ERROR COUNTER REGISTER: REC

REC7:0

(Read, SPI Op-code 0xEA)
7 6 5 4 3 2 1 0
MSB LSB
The REC register reflects the current value of the CAN Receive Error Counter. This register can be written by SPI command for test
purposes.

7-0 REC7:0 R/W 0x00 Receiver Error Counter bits <7:0>.
0 £ REC £ 95: Error active status.
96 £ REC £ 127: Error active status. Error warning flag, ERRW, set in STATF register. This
may be used to generate a hardware interrupt if ERRWIE bit is set in STATFE register.
128 £ REC £ 255: Error passive status. Receive error passive flag, RXERRP, set in ERR
register. ERRP also set in STATF register. This may be used to generate a hardware interrupt if
ERRPIE bit is set in STATFE register.

21
HI-3110, HI-3111, HI-3112, HI-3113
MESSAGE STATUS REGISTER: MESSTAT
FI IT3
FI IT2
M IT0
FI IT1
T0
TS T1
M G1
TS G0
TA
TA
LH
LH
LH
LH
TA
TA
FI
(Read only)
(Read, SPI Op-code 0xDA)
7 6 5 4 3 2 1 0
MSB LSB
This register reflects transmission status and also which filters were responsible for filtering valid received messages. It is read-only.

7-4 FILHIT3:0 R 0 Filter hit bits <3:0>.
These bit combinations indicate which filters were responsible for filtering received messages
.
0000: No filter matches the received message.
1000: Filter 0 matches, but filters 1, 2, 3, 4, 5, 6 or 7 may also match.
1001: Filter 1 matches, filter 0 does not, but filters 2, 3, 4, 5, 6 or 7 may also match.
1010: Filter 2 matches, filters 0 and 1 do not, but filters 3, 4, 5, 6 or 7 may also match.
1011: Filter 3 matches, filters 0 through 2 do not, but filters 4, 5, 6 or 7 may also match.
1100: Filter 4 matches, filters 0 through 3 do not, but filters 5, 6, or 7 may also match.
1101: Filter 5 matches, filters 0 through 4 do not, but filters 6 or 7 may also match.
1110: Filter 6 matches, filters 0 through 5 do not, but filter 7 may also match.
1111: Filter 7 matches, all other filters do not.
Note: Filter checking is carried out by the internal logic in order of increasing filter
number. Once a filter matches, no further checking takes place. Therefore, in
the case of more than one filter matching for a given message, the lowest
filter will be given priority and the FILHIT3:0 bits will reflect this value.
3-2 MTAG1:0 R 0 Message Tag bits <1:0>.

These bits will reflect the last two bits of the host assigned message tag of the last successful
transmission.
1-0 TSTAT1:0 R 0 Transmission Status bits <1:0>.

These bits reflect the transmission status.
00: Transmission not enabled (TXEN = 0).

01: Transmission is enabled (TXEN = 1), but FIFO is empty.
10: Waiting to transmit or re-transmit.
11: Transmitter is currently transmitting a message or a flag.

22
HI-3110, HI-3111, HI-3112, HI-3113
R
ERROR REGISTER: ERR
R R
KE R
TE P
ER F
XE P
R
U R
FR RR
C ER
AC ER
BI RR
TX O F
R R
ST R
FE
M
C
S
BU
(Read only)
(Read, SPI Op-code 0xDC)
7 6 5 4 3 2 1 0
MSB LSB
The ERR register indicates CAN bus status and protocol errors. It is read only. All bits default to 0 at power up and maintain their
current status following reset. Bits 4:0 are reset following a host read.

7 BUSOFF R 0 Bus-off status indicator.
This bit is set when TEC > 255. Node is in bus off condition. The bit is reset by HI-3110 when a
successful bus recovery sequence is detected (128 x 11 consecutive recessive bits). d the
FILHIT3:0 bits will reflect this value.
6 TXERRP R 0 Transmit Error Passive status indicator.

This bit is set when 128 £ TEC £ 255.
5 RXERRP R 0 Receive Error Passive status indicator.

This bit is set when 128 £ REC £ 255.
4 BITERR R 0 Bit Error.

A bit error was detected in a transmitted frame (the bit observed on the bus was opposite to
what was expected).
3 FRMERR R 0 Form Error.

A Form error was detected in a receive frame.
2 CRCERR R 0 CRC Error.

A CRC error was detected in a receive frame.
1 ACKERR R 0 Acknowledgement Error.

An ACK error was detected in a receive frame.
0 STUFERR R 0 Stuff Error.

A bit stuffing error was detected in a received frame.

23
HI-3110, HI-3111, HI-3112, HI-3113
INTERRUPT FLAG REGISTER: INTF
M P
C R
M S
BU PLT
TX IFO
F1 EU
R MP
M ER
ES
F0 ES
W G
H
AK
S
XT
XF
C
R
(Read only)
(Read, SPI Op-code 0xDE)
7 6 5 4 3 2 1 0
MSB LSB
The Interrupt Flag Register INTF bits will be set by HI-3110 when the corresponding related events described below occur. If
individual bits in the Interrupt Enable Register INTE are set, the INT pin will be latched high when any of the corresponding INTF bits
are set. This alerts the host that one of the conditions below has occurred. Reading this register will clear all bits and reset the INT pin.
The value of individual bits in the INTF register may also be reflected on the GP1 and GP2 pins by setting the correct bit combinations
in the General Purpose Pins Enable Register GPINE (see section General Purpose Pins Enable Register).

7 RXTMP R 0 Message received in temporary receive buffer (unfiltered).
This bit is set when a valid message is received in the temporary receive buffer.
6 RXFIFO R 0 Message received in FIFO (filtered).

This bit is set when a valid message passes the filter criteria and is passed from the
temporary receive buffer to the receive FIFO.
5 TXCPLT R 0 Successful transmission complete.

This bit is set when a message is successfully transmitted.
4 BUSERR R 0 Bus Error.

This bit is set when a bus error occurs. Bits 4:0 in the ERR register can be read to determine
the source of the error.
3 MCHG R 0 Mode Change bit.

This bit is set when the mode of operation is changed. Any pending transmissions in the
transmit FIFO will be completed (FIFO will be emptied) before the mode change occurs.
2 WAKEUP R 0 Wake-Up detected.

This bit is set when the HI-3110 wakes up from Sleep Mode in response to bus activity.
1 F1MESS R 0 Filter 1 passed a valid message.

This bit is set when receive filter one passes a valid message. FILHIT3:0 bits will also be set to
<1001> in the Message Status Register, MESSTAT.
0 F0MESS R 0 Filter 0 passed a valid message.

This bit is set when receive filter zero passes a valid message. FILHIT3:0 bits will also be set to
<1000> in the Message Status Register, MESSTAT.

24
HI-3110, HI-3111, HI-3112, HI-3113
F0 ES E
W GI E
M SIE
S IE
C IE
INTERRUPT ENABLE REGISTER: INTE
M PI
XF IE
H I
IE
C R
AK E
BU PLT
TX IFO
F1 EU
R MP
M ER
ES
XT
R
(Write SPI Op-code 0x1C)
(Read, SPI Op-code 0xE4)
7 6 5 4 3 2 1 0
MSB LSB
Setting bits in the Interrupt Enable Register causes a hardware interrupt to be generated at the INT pin when the
corresponding bits in the Interrupt Flag Register are set by HI-3110 as a result of the related events described below.

7 RXTMPIE R/W 0 Enable interrupt when a message is received in the temporary receive buffer (unfiltered).
Setting this bit causes a hardware interrupt to be generated at the INT pin when the RXTMP bit
is set in the INTF register.
6 RXFIFOIE R/W 0 Enable interrupt when a message is received in the receive FIFO (filtered).
Setting this bit causes a hardware interrupt to be generated at the INT pin when the
RXFIFO bit is set in the INTF register.
5 TXCPLTIE R/W 0 Enable interrupt when a successful transmission is complete.

Setting this bit causes a hardware interrupt to be generated at the INT pin when the TXCPLT bit
4 BUSERRIE R/W 0 Enable interrupt when a bus error occurs.

Setting this bit causes a hardware interrupt to be generated at the INT pin when the BUSERR
bit is set in the INTF register.
3 MCHGIE R/W 0 Enable interrupt when a mode change occurs.

Setting this bit causes a hardware interrupt to be generated at the INT pin when the MCHG bit
2 WAKEUPIE R/W 0 Enable interrupt when HI-3110 wakes up from Sleep Mode.
Setting this bit causes a hardware interrupt to be generated at the INT pin when the WAKEUP
1 F1MESSIE R/W 0 Enable interrupt when filter one passes a message.

Setting this bit causes a hardware interrupt to be generated at the INT pin when the F1MESS
0 F0MESSIE R/W 0 Enable interrupt when filter zero passes a message.

Setting this bit causes a hardware interrupt to be generated at the INT pin when the F0MESS

25
HI-3110, HI-3111, HI-3112, HI-3113
STATUS FLAG REGISTER: STATF
LL
XF F
XF Y
TX U L L
ER ISF
R OF
TX T Y
FU
R MT
ER W
BU P
M
R
R
S
H
F
TX
(Read-only)
7 6 5 4 3 2 1 0
MSB LSB
The Status Flag Register STATF bits will be set by HI-3110 when the corresponding related events described below occur. Unlike the
Interrupt Flag Register, reading this register will NOT clear all bits. These bits are reset automatically by HI-3110 when the described
status for each bit changes (e.g. if TXMTY is set and a message is loaded to the transmit FIFO, TXMTY will be automatically cleared
by HI-3110). If individual bits in the Status Flag Enable Register STATFE are set, the STAT pin will pulse high when any of the enabled
STATF bits are set. The value of individual bits in the STATF register may also be reflected on the GP1 and GP2 pins by setting the
correct bit combinations in the General Purpose Pins Enable Register GPINE.

7 TXMTY R 1 Transmit FIFO is empty.
This bit is set when the transmit FIFO is empty. This is the default following Reset.
6 TXFULL R 0 Transmit FIFO is full.

This bit is set when the transmit FIFO is full.
5 TXHISF R 0 Transmit history FIFO full.

This bit is set when the transmit history FIFO is full. Up to eight messages can be stored in the
transmit history FIFO (Note: a user generated message tag and a time tag are stored with each
message).
4 ERRW R 0 Error warning flag.

This bit is set when 96 £ (TEC or REC) £ 127.
3 ERRP R 0 Error passive indicator.

This bit is set when the device enters error passive mode.
2 BUSOFF R 0 BUSOFF indicator.

This bit is set when the device enters bus-off state.
1 RXFMTY R 1 Receive FIFO empty.

This bit is set when the receive FIFO is empty. This is the default following Reset.
0 RXFFULL R 0 Receive FIFO full.

This bit is set when the receive FIFO is full.

26
HI-3110, HI-3111, HI-3112, HI-3113
FE
R MT E
FU FE
H FE
R FE
F FE
F
STATUS FLAG ENABLE REGISTER: STATE
LL
R E
S E
XF F
XF Y
TX U L L
ER WF
ER ISF
R OF
TX T Y
BU PF
M
TX
(Write, SPI Po-code 0x1E)
7 6 5 4 3 2 1 0
MSB LSB
Setting bits in the Status Flag Enable Register causes the STAT pin to go high when any of the corresponding bits in the Status Flag
Register are set by HI-3110 as a result of the related events described below.

7 TXMTYFE R/W 0 Transmit FIFO empty status flag enable.
Setting this bit causes the status of the TXMTY bit in the Status Flag Register to be output on
the STAT pin.
6 TXFULLFE R/W 0 Transmit FIFO full status flag enable.

Setting this bit causes the status of the TXFULL bit in the Status Flag Register to be output on
the STAT pin.
5 TXHISFFE R/W 0 Transmit History FIFO full status flag enable.

Setting this bit causes the status of the TXHISF bit in the Status Flag Register to be output on
the STAT pin.
4 ERRWFE R/W 0 Error warning status flag enable (96 £ (TEC or REC) £ 127).
Setting this bit causes the status of the ERRW bit in the Status Flag Register to be output on the
STAT pin.
3 ERRPFE R/W 0 Error Passive status flag enable.

Setting this bit causes the status of the ERRP bit in the Status Flag Register to be output on the
STAT pin.
2 BUSOFFFE R/W 0 Bus-off status flag enable.

Setting this bit causes the status of the BUSOFF bit in the Status Flag Register to be output on
the STAT pin.
1 RXFMTYFE R/W 0 Receive FIFO empty status flag enable.

Setting this bit causes the status of the RXFMTY bit in the Status Flag Register to be
output on the STAT pin.
0 RXFFULLFE R/W 0 Receive FIFO full status flag enable.

Setting this bit causes the status of the RXFFULL bit in the Status Flag Register to be output on
the STAT pin.

27
HI-3110, HI-3111, HI-3112, HI-3113
GENERAL PURPOSE PINS ENABLE REGISTER: GPINE
GPINE7:4 GPINE3:0

7 6 5 4 3 2 1 0
MSB LSB
Setting bits in the General Purpose Pins Enable Register allows the user to reflect the values of the Interrupt Flag bits in the INTF
Register or the Status Flag bits in the STATF Register on the GP1 andGP2 pins.

7-4 GPINE7:43:0 R/W 0000 Reflect status of interrupt flag bits in INTF or status flag bits in STATF on GP2 pin as follows:
0000: GP2 pin is asserted when F0MESS bit is set in register INTF.
0010: GP2 pin is asserted when WAKEUP bit is set in register INTF.
0011: GP2 pin is asserted when MCHG bit is set in register INTF.
0100: GP2 pin is asserted when BUSERR bit is set in register INTF.
0101: GP2 pin is asserted when TXCPLT bit is set in register INTF.
0110: GP2 pin is asserted when RXFIFO bit is set in register INTF.
0111: GP2 pin is asserted when RXTMP bit is set in register INTF.
1000: GP2 pin is asserted when RXFFULL bit is set in register STATF.
1001: GP2 pin is asserted when RXFMPTY bit is set in register STATF.
1010: GP2 pin is asserted when BUSOFF bit is set in register STATF.
1011: GP2 pin is asserted when ERRP bit is set in register STATF.
1100: GP2 pin is asserted when ERRW bit is set in register STATF.
1101: GP2 pin is asserted when TXHISF bit is set in register STATF.
1110: GP2 pin is asserted when TXFULL bit is set in register STATF.
1111: GP2 pin is asserted when TXMPTY bit is set in register STATF.
3-0 GPINE3:0 R/W 0000 Reflect status of interrupt flag bits in INTF or status flag bits in STATF on GP1 pin as follow:
0010: GP1 pin is asserted when WAKEUP bit is set in register INTF.
0011: GP1 pin is asserted when MCHG bit is set in register INTF.
0100: GP1 pin is asserted when BUSERR bit is set in register INTF.
0101: GP1 pin is asserted when TXCPLT bit is set in register INTF.
0110: GP1 pin is asserted when RXFIFO bit is set in register INTF.
0111: GP1 pin is asserted when RXTMP bit is set in register INTF.
1000: GP1 pin is asserted when RXFFULL bit is set in register STATF.
1001: GP1 pin is asserted when RXFMPTY bit is set in register STATF.
1010: GP1 pin is asserted when BUSOFF bit is set in register STATF.
1011: GP1 pin is asserted when ERRP bit is set in register STATF.
1100: GP1 pin is asserted when ERRW bit is set in register STATF.
1101: GP1 pin is asserted when TXHISF bit is set in register STATF.
1110: GP1 pin is asserted when TXFULL bit is set in register STATF.
1111: GP1 pin is asserted when TXMPTY bit is set in register STATF.

28
HI-3110, HI-3111, HI-3112, HI-3113
FREE-RUNNING TIMER UPPER BYTE: TIMERUB LOWER BYTE: TIMERLB

T15:8 T7:0
(Read-only)
(Read, SPI Op-code 0xFA)
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
MSB LSB MSB LSB

7-0 T15:8 R/W 0x00 Free Running Timer Upper Byte, bits <15:8>.
The 16-bit free-running timer starts counting from zero following RESET. The timer counts
linearly up to 0xFFFF and then wraps around to 0x0000. Note: A timer overrun is not
flagged by the HI-3110. The timer is clocked by the HI-3110 bit clock and continuously
increments by the bit rate (default). The user may program the timer to 2, 4 or 8 bit clocks by
setting the TTDIV1:0 bits in Control Register 0, CTRL0.
The timer may be reset by the host after any interrupt condition (e.g. reading the receive buffer,
transmit FIFO empty, etc), by issuing an SPI instruction (see Table 1, SPI Instruction Set).
7-0 T7:0 R/W 0x00 Free Running Timer Lower Byte, bits <7:0>.
NOTE: A single SPI Op-code (0xFA) reads the16-bit timer value in two SPI data bytes,
TIMERUB and TIMERLB. TIMERUB is read first.

29
HI-3110, HI-3111, HI-3112, HI-3113
SERIAL PERIPHERAL INTERFACE

SERIAL PERIPHERAL INTERFACE (SPI) BASICS edges on SCK latch input data into the master and slave
devices, starting with each byte’s most-significant bit. The
The HI-3110 uses an SPI synchronous serial interface for HI-3110 SPI can be clocked at 20 MHz.
host access to internal registers and data FIFOs. Host
serial communication is enabled through the Chip Select Multiple bytes may be transferred when the host holds CS
(CS) pin, and is accessed via a three-wire interface low after the first byte transferred, and continues to clock
consisting of Serial Data Input (SI) from the host, Serial SCK in multiples of 8 clocks. A rising edge on CS chip
Data Output (SO) to the host and Serial Clock (SCK). All select terminates the serial transfer and reinitializes the
read / write cycles are completely self-timed. HI-3110 SPI for the next transfer. If CS goes high before a
full byte is clocked by SCK, the incomplete byte clocked
The SPI (Serial Peripheral Interface) protocol specifies into the device SI pin is discarded.
master and slave operation; the HI-3110 operates as an
SPI slave. In the general case, both master and slave simultaneously
send and receive serial data (full duplex), per Figure 9
The SPI protocol defines two parameters, CPOL (clock below. However the HI-3110 operates half duplex,
polarity) and CPHA (clock phase). The possible CPOL- maintaining high impedance on the SO output, except
CPHA combinations define four possible "SPI Modes". when actually transmitting serial data. When the HI-3110
Without describing details of the SPI modes, the HI-3110 is sending data on SO during read operations, activity on
operates in mode 0 where input data for each device its SI input is ignored. Figures 10 and 11 show actual
(master and slave) is clocked on the rising edge of SCK, behavior for the HI-3110 SO output.
and output data for each device changes on the falling
edge (CPHA = 0, CPOL = 0). Be sure to set the host SPI
logic for mode 0.
As seen in Figure 9, SPI Mode 0 holds SCK in the low state

when idle. The SPI protocol transfers serial data as 8-bit
bytes. Once CS chip select is asserted, the next 8 rising
SCK (SPI Mode 0) 0 1 2 3 4 5 6 7
SI MSB LSB
High Z High Z
SO MSB LSB
CS
Figure 9. Generalized Single-Byte Transfer Using SPI Protocol Mode 0

30
HI-3110, HI-3111, HI-3112, HI-3113
HOST SERIAL PERIPHERAL INTERFACE, cont.

HI-3110 SPI COMMANDS Multiple byte read or write cycles may be performed by
transferring more than one byte before CS is negated.
For the HI-3110, each SPI read or write operation begins Tables 2 - 5 define the required number of bytes for each
with an 8-bit command byte transferred from the host to the instruction.
device after assertion of CS. Since HI-3110 command byte
reception is half-duplex, the host discards the dummy byte Note: SPI Instruction op-codes not shown in Tables 2 - 5
it receives while serially transmitting the command byte. are “reserved” and must not be used. Further, these op-
codes will not provide meaningful data in response to read
Figures 10 and 11 show read and write timing as it appears commands.
for a single-byte and dual-byte register operation. The
command byte is immediately followed by a data byte Two instruction bytes cannot be “chained”; CS must
comprising the 8-bit data word read or written. For a single be negated after the command, then reasserted for the
register read or write, CS is negated after the data byte is following Read or Write command.
transferred.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
SCK
MSB LSB
SI
Op-Code Byte MSB LSB MSB

High Z High Z
SO
Data Byte
CS
Host may continue to assert CS

here to read sequential word(s)
when allowed by the instruction.
Each word needs 8 SCK clocks.
Figure 10. Single-Byte Read From a Register
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
SCK
SPI Mode 0
MSB LSB MSB LSB MSB LSB
SI
Op-Code Byte Data Byte 0 Data Byte 1

High Z
SO
CS
Host may continue to assert CS

here to write sequential byte(s)
when allowed by the SPI instruction.
Each byte needs 8 SCK clocks.
Figure 11. 2-Byte Write example

31
HI-3110, HI-3111, HI-3112, HI-3113
Table 1. SPI Instruction Set
SPI Instruction Command Data Field Bit Content

Hex
READ Commands
Read Temporary Receive

Buffer with Time Tag 0x42 15 bytes (see Table 5, bytes 2-16)
Read Temporary Receive

Buffer without Time Tag 0x44 13 bytes (see Table 5, bytes 4-16)
Read Next FIFO Message

with Time Tag 0x46 16 bytes (see Table 5, bytes 1-16)

without Time Tag 0x48 14 bytes (see Table 5, bytes 1 & 4-16)

Data only with Time Tag 0x4A 11 bytes (see Table 5, bytes 1-3 & 9-16)

Data only without Time Tag 0x4C 9 bytes (see Table 5, bytes 1 & 9-16)
Read Filter 0 ID 0xA2 6 bytes (see Table 4a)

Read Filter 4 ID 0xAA 6 bytes (see Table 4a)
Read Filter 5 ID 0xAC 6 bytes (see Table 4a)
Read Filter 6 ID 0xAE 6 bytes (see Table 4a)
Read Filter 7 ID 0xB2 6 bytes (see Table 4a)
Read Mask 0 ID 0xB4 6 bytes (see Table 4b)

Read Mask 3 ID 0xBA 6 bytes (see Table 4b)
Read Mask 4 ID 0xBC 6 bytes (see Table 4b)
Read Mask 5 ID 0xBE 6 bytes (see Table 4b)
Read Mask 6 ID 0xC2 6 bytes (see Table 4b)
Read Mask 7 ID 0xC4 6 bytes (see Table 4b)
Read Control Register 0 0xD2 1 byte (see CTRL0 Register Definition)

Read Control Register 1 0xD4 1 byte (see CTRL1 Register Definition)
Read Bit Timing Register 0 0xD6 1 byte (see BTR0 Register Definition)
Read Bit Timing Register 1 0xD8 1 byte (see BTR1 Register Definition)
Read Message Status Register 0xDA 1 byte (see MESSTAT Register Definition)
Read Error Register 0xDC 1 byte (see ERR Register Definition)
Read Interrupt Flag Register 0xDE 1 byte (see INTF Register Definition)
Read Status Flag Register 0xE2 1 byte (see STATF Register Definition)
Read Interrupt Enable Register 0xE4 1 byte (see INTE Register Definition)
Read Status Flag Enable Register 0xE6 1 byte (see STATFE Register Definition)

32
HI-3110, HI-3111, HI-3112, HI-3113
Table 1. SPI Instruction Set (cont.)

Hex
READ Commands (ctd)
Read General Purpose Pins

Enable Register 0xE8 1 byte (see GPINE Register Definition)
Read REC Register 0xEA 1 byte (see REC Register Definition)

Read TEC Register 0xEC 1 byte (see TEC Register Definition)
Read Transmit History FIFO 0xEE 3 bytes (see Table 3)
Reserved
(Factory test purposes only) 0x4E 13 bytes
Reserved
(Factory test purposes only) 0xF4 1 byte
Reserved
(Factory test purposes only) 0xF6 1 byte
Read Bus-Off Recessive Count 0xF8 1 byte
Read Time Tag 0xFA 2 bytes (see TIMERUB and TIMERLB

Register Definitions)
RESET Commands
Abort Transmission
(stops current transmission and
resets TXEN & TX1M) 0x52 None (see CTRL1 Register Definition)
Reset (Clear) Transmit FIFO

(resets TXEN & TX1M, but
completes current transmission) 0x54 None
Master Reset 0x56 None
Reset Time Tag Counter 0x58 None (see TIMERUB and TIMERLB
Register Definitions)
Reset Receive FIFO 0x5A None

33
HI-3110, HI-3111, HI-3112, HI-3113
Table 1. SPI Instruction Set (cont.)

Hex
WRITE Commands
Write one message to 4 to 12 bytes for Std frame or

Transmit FIFO 0x12 6 to 14 bytes for Ext frame
Write Control Register 0 0x14 1 byte (see CTRL0 Register Definition)

Write Control Register 1 0x16 1 byte (see CTRL1 Register Definition)
Write Bit Timing Register 0 0x18 1 byte (see BTR0 Register Definition)
Write Bit Timing Register 1 0x1A 1 byte (see BTR1 Register Definition)
Write Interrupt Enable Register 0x1C 1 byte (see INTE Register Definition)
Write Status Flag Enable Register 0x1E 1 byte (see STATFE Register Definition)
Write General Purpose Pins

Enable Register 0x22 1 byte (see GPINE Register Definition)
Write REC Register (Test only) 0x24 1 byte (see REC Register Definition)
Write TEC Register (Test only) 0x26 1 byte (see TEC Register Definition)
Write Filter 0 ID 0x62 6 bytes (see Table 4a)

Write Filter 4 ID 0x6A 6 bytes (see Table 4a)
Write Filter 5 ID 0x6C 6 bytes (see Table 4a)
Write Filter 6 ID 0x6E 6 bytes (see Table 4a)
Write Mask 0 ID 0x74 6 bytes (see Table 4b)

Write Mask 3 ID 0x7A 6 bytes (see Table 4b)
Write Mask 4 ID 0x7C 6 bytes (see Table 4b)
Write Mask 5 ID 0x7E 6 bytes (see Table 4b)

34
HI-3110, HI-3111, HI-3112, HI-3113
HI-3110 Transmit Buffer LOADING THE TRANSMIT FIFO VIA SPI
The transmit FIFO holds up to 8 messages and is loaded via
The HI-3110 transmit buffer consists of an eight message SPI instruction (see Table 1). The data format for the SPI
FIFO which allows transmission of up to eight messages. instruction is illustrated in Table 2. The host simply needs to
Messages are loaded to the transmit FIFO via SPI issue the SPI write command 0x12 followed by the SPI data
instruction. Similarly, an SPI instruction resets (clears) the field as described in Table 2. For standard frames, the SPI
transmit FIFO. data field has the format shown in Table 2(a). For extended
frames, the SPI data field has the format shown in Table 2(b).
Transmission from the FIFO is enabled by asserting the The HI-3110 will automatically interpret Standard or
Extended frames by decoding the IDE bit. The HI-3110 also
TXEN pin or setting the TXEN bit in CTRL1. If TXEN
decodes the data length code (DLC) and ignores data bytes
transmission is enabled, all loaded messages are greater than the DLC value (Note: a DLC of greater than 8 is
automatically sent if the bus is available. If TXEN is not automatically assumed to be equal to 8). The user has the
enabled, messages will not be sent until TXEN is set. If option of assigning a unique message tag to each message
TXEN is reset, a single message may also be sent by setting which can be used later to identify successfully transmitted
the TX1M bit in CTRL1. messages from the transmit history FIFO. One frame at a
time can be loaded to the transmit FIFO using SPI command
MESSAGE TRANSMISSION SEQUENCE 0x12. The byte format should be as shown in Table 2 and
A simplified transmission flow is illustrated in Figure 9. The the CS pin should remain low during the entire SPI
next message to be transmitted (or current message trying sequence.
to gain access to the bus) is loaded from the FIFO to the
Transmit Buffer. This will happen automatically if TXEN or
TX1M are set in CTRL1. TRANSMIT HISTORY FIFO
The Transmit History FIFO can optionally be used by the
If the bus is available, the message is sent. The host to keep a record of up to eight successfully transmitted
transmission can be aborted at any time using the Abort messages. A user-assigned message tag and a time tag are
Transmission SPI command (see Table 1). Care should be stored for each message. The data format is shown in Table
exercised when using the command as it may cause other 3. The time tag is assigned from the value of the free running
nodes on the bus to generate error frames if the message is counter upon receipt of an ACK bit. The transmit history
aborted prior to completing transmission. The current FIFO is cleared when read by SPI command 0xEE (see
transmission sequence can also be paused by resetting the Table 3).
TXEN bit in CTRL1 (or pulling TXEN pin low). In this case,
the current message will be completed and any remaining
messages in the transmit FIFO will not be transmitted. SINGLE FRAME TRANSMISSION
If the current message transmission goes ahead, two things For single frame transmission, use TX1M, bit 6, Register
can happen: CTRL1. When using TX1M for single frame transmission,
a) The message is successful, and the transmit buffer is now TXEN should be held low. Pulsing the TXEN pin for single
ready to receive the next message from the transmit FIFO. frame transmission is not recommended.
The transmit history FIFO is updated (see below).
b) The message is not successful due to lost arbitration or If single frame transmission is preferred using the TXEN pin,
message error. the user should load only ONE message to the FIFO and
i. Lost Arbitration: If arbitration is lost, the current hold TXEN high to transmit in the normal way. Following a
message stays in the Transmit Buffer for successful transmission, TXEN should be reset and the
re-transmission. FIFO re-loaded with the next message. A successful
ii. Message error: Flag BUSERR is set in the transmission may be confirmed by polling the Transmit
Interrupt Flag Register. An error frame is sent and History FIFO or by monitoring the Transmit FIFO empty flag,
an optional hardware interrupt may also be TXMTY, in the STATF register.
generated at the INT pin if enabled in the Interrupt
Enable Register (bit BUSERRIE = 1). If there is an
error, the current message stays in the Transmit
Buffer for automatic re-transmission in accordance
with the CAN protocol.
NOTE: If OSM is set, re-transmission will NOT

be attempted upon loss of arbitration or message
error. The existing message will remain in the FIFO.
If the user requires a new message on the next
transmission cycle, the FIFO must be cleared using
SPI command 0x54 and re-loaded with the new
message.

35
Transmit
Transmit Buffer keeps
Buffer current message
Load Transmit
Buffer with
next message
NO
Is CAN bus Generate
Write Tx FIFO available? Interrupt at pin
HI-3110 Transmit Message Flow Diagram
YES
YES
Message 8
Message 7 NO
Set BUSERR Is BUSERRIE
Message 6 Transmit message flag set?
Message
36
Message 5
Error
Message 4
Message 3
Message 2
NO
Message 1 Successful message Message error or
transmission? lost arbitration? Lost
Arbitration

YES
YES
TXEN = 1?
HI-3110, HI-3111, HI-3112, HI-3113
Write Transmit
NO History FIFO
YES
TX1M = 1?
NO
Figure 12. Simplified Transmission Flow Diagram

HI-3110, HI-3111, HI-3112, HI-3113
Table 2. SPI Transmit Data Format
a) Standard Frame Transmit
Byte Byte Content Bit Description (”x” = Don’t care)
7
6
5
4
3
2
MT
MT
MT
MT
MT
MT
x x
1 Message Tag*
28
21
ID
ID
2 ID28 to ID21
18
20
R
E
RT
ID
ID
ID
x x x
3 ID20 to ID18, RTR, IDE
C0
C3
C2
DL 1
C
DL
DL
DL
r0
x x x
4 r0, DLC3 to DLC0
0
DB
DB
5 *Data Byte 1
.
6 Data Byte 2 .
.
.
7 Data Byte 3 .
.
.
8 Data Byte 4 .
.
.
9 Data Byte 5 .
.
.
10 Data Byte 6 .
.
.
11 Data Byte 7 .
7
0
DB
DB
12 Data Byte 8
* Note: The Message Tag is a host-assigned identifier that is stored along with a time tag in the Transmit
History FIFO. It can be used by the host to log successfully transmitted messages at a later time.

37
HI-3110, HI-3111, HI-3112, HI-3113
Table 2. SPI Transmit Data Format

b) Extended Frame Transmit
Byte Content Bit Description (”x” = Don’t care)
7
6
5
4
3
2
MT
MT
MT
MT
MT
MT
x x
1 Message Tag*
28
21
ID
ID
2 ID28 to ID21
18
17
15
20
E
SR
ID
ID
ID
ID
ID
3 ID20 to ID18, SRR, IDE,
ID17 to ID15
14
7
ID
ID
4 ID14 to ID7
R
0
6
RT
ID
ID
5 ID6 to ID0, RTR
C3
C2
C1
C0
DL
DL
DL
DL
r1
r0
x x
6 r0, r1, DLC3 to DLC0
7
0
DB
DB
7 Data Byte 1
.
.
8 Data Byte 2 .
.
.
9 Data Byte 3 .
.
.
10 Data Byte 4 .
.
.
11 Data Byte 5 .
.
.
12 Data Byte 6 .
.
.
13 Data Byte 7 .
7
0
DB
DB
14 Data Byte 8
* Note: The Message Tag is a host-assigned identifier that is stored along with a time tag in the Transmit
History FIFO. It can be used by the host to log successfully transmitted messages at a later time.

38
HI-3110, HI-3111, HI-3112, HI-3113
Table 3. Transmit History FIFO Data Format
7
6
5
4
3
2
MT
MT
MT
MT
MT
MT
x x
1 Message Tag
14
13
12
15
11
10
9
8
TT
TT
TT
TT
TT
TT
TT
TT
2 Time Tag Upper Byte
6
5
4
3
1
0
7
2
TT
TT
TT
TT
TT
TT
TT
TT
3 Time Tag Lower Byte
HI-3110 Receive Buffers and Frame specific to Extended IDs should be written as zeros for
Standard IDs. The filter mechanism works by comparing the
Acceptance Filters filter ID to the CAN message ID. If the corresponding bit in
the mask ID is logic one, then the CAN ID bit must match the
filter ID for acceptance to occur. If a mask ID bit is logic zero,
RECEIVE BUFFERS then acceptance will occur regardless of the value of the
The HI-3110 has an extremely flexible receive buffer and ID CAN ID bit. In this case, the filter bits are don’t care.
filter scheme. Acceptance filters and masks may only be
programmed when the device is in Initialization Mode. Following reset, all eight filter and mask registers should be
The basic concept is shown in figure 13. All valid received loaded before enabling the FILTON bit. Note that following
messages (both standard or extended frames) are stored in reset, filter and mask bits are not reset, therefore the
the temporary receive buffer before passing through the FILTON bit may be set to enable filtering using the pre-reset
mask and filter values.
filter bank. The host can read the temporary receive buffer
using SPI commands 0x42 or 0x44 (see table 1). The filter
bank must be enabled by setting the FILTON bit in Control READING THE RECEIVE BUFFERS VIA SPI
Register, CTRL1. The default after reset is FILTON = 0, Table 1 summarizes the SPI instructions for reading the
which disables the filter bank and stores every valid receive buffers. The host has a choice of retrieving a
message received in the FIFO. With filtering enabled, it is message with a 16-bit time tag or not. The receive data
possible to filter up to eight extended identifiers plus the first format is shown in Table 5. The first data byte identifies
two associated data bytes. Any filtered messages will be whether the frame was standard or extended format and the
passed to the receive FIFO. Up to eight messages can be FILHIT2:0 bits identify which filter passed the message;
stored in the receive FIFO. All valid received messages <000> to <111>. If more than one filter passed the message,
the lowest value will be given priority and be identified by the
have a 16-bit time tag appended following transmission of
FILHIT2:0 bits. As can be seen in Table 5, bits specific to
the ACK bit. The user can decide to retrieve the time tag or extended frames will be read as zeros for standard frames.
not via dedicated SPI instructions (see Table 1). If the received data does not contain an 8 byte payload (8
data bytes), the HI-3110 will pad the remaining data bytes
with zeros. The host should keep CS low for the duration of
FILTER AND MASK ID FORMAT the SPI sequence.
The HI-3110 allows filtering of up to 8 unique extended
frames with the first two data bytes. Filtering is enabled by
setting the FILTON bit in Control Register 1, CTRL1. It the
FILTON bit is not set, then filtering is globally disabled and all
CAN IDs are accepted.
There is a specific SPI instruction for loading and reading

each filter and mask. The format is the same for both
standard and extended IDs and is shown in Table 4. Bits

39
HI-3110, HI-3111, HI-3112, HI-3113
Temporary Receive Buffer
ID Acceptance Filter 0
ID Mask Filter 0
MESSTAT Register
FILHIT3:0 bits
Yes
Match ? FILHIT3:0 = 1000
No
ID Mask Filter 1
Yes
No
Load Receive
FIFO
........
........
ID Mask Filter 7
Yes
No
Message not stored
Figure 13. Receive Buffer Structure

40
HI-3110, HI-3111, HI-3112, HI-3113
Table 4. SPI Filter and Mask ID Format
a) Filter ID Format
1
D2
D2
FI
FI
1 ID28 to ID21
2 ID20 to ID18, RTR, IDE,

ID17 to ID15
5
0
D1
D1
D1
D2
R
E
RT
FI
FI
FI
ID
FI
(Note: ID17 to ID15 should be written
as zeros for Standard ID)
D7
D1
FI
FI
3 ID14 to ID7
(Note: Written as zeros for Standard ID)
D0
D6
FI
FI
4 ID6 to ID0 x
B7
B0
FD
FD
5 Data Byte 1
B7
B0
FD
FD
6 Data Byte 2
b) Mask ID Format

8
1
D2
D2
MI
MI
1 ID28 to ID21
2 ID20 to ID18, RTR, IDE,

RT 8
5
0
ID17 to ID15
D1
D1
D1
D2
R
E
MI
MI
MI
MI
ID
(Note: ID17 to ID15 should be written

as zeros for Standard ID)
4
D7
D1
MI
MI
3 ID14 to ID7
D0
D6
MI
MI
4 ID6 to ID0 x
B7
B0
MD
MD
5 Data Byte 1
B7
B0
MD
MD
6 Data Byte 2

41
HI-3110, HI-3111, HI-3112, HI-3113
Table 5. SPI Receive Data Format
FI T2
FI T1
0
IT
1 Message Tag
I
I
LH
LH
LH
E
ID
FI
(Note: This byte does not apply to the x x x x
Temporary Receive Buffer)
2 Time Tag Upper Byte
14
13
12
15
11
10
9
8
TT
TT
TT
TT
TT
TT
TT
TT
(Note: This byte only applies to time tag
SPI instructions; see Table 1)
3 Time Tag Lower Byte
6
5
4
3
1
0
7
2
TT
TT
TT
TT
TT
TT
TT
TT
(Note: This byte only applies to time tag
SPI instructions; see Table 1)
28
21
ID
ID
4 ID28 to ID21
5 ID20 to ID18, SRR, IDE,

ID17 to ID15
18
17
15
20
E
SR
ID
ID
ID
ID
ID
(Note: SRR and ID17 to ID15 are
read as zeros for Std Frames)
14
7
ID
ID
6 ID14 to ID7
(Read as zeros for Std Frames)
7 ID6 to ID0, RTR
R
0
6
RT
ID
ID
(Note: ID6 to ID0 are

read as zeros for Std Frames)
C3
C2
C1
C0
DL
DL
DL
DL
r1
r0
8 r0, r1, DLC3 to DLC0 x x

(Note: r1 is read as zero for Std Frames)
7
0
DB
DB
9 Data Byte 1
.
.
10 Data Byte 2 .
.
.
11 Data Byte 3 .
.
.
12 Data Byte 4 .
.
.
13 Data Byte 5 .
.
.
14 Data Byte 6 .
.
.
15 Data Byte 7 .
7
0
DB
DB
16 Data Byte 8

42
HI-3110, HI-3111, HI-3112, HI-3113
TIMING DIAGRAMS
SERIAL INPUT TIMING DIAGRAM

t CPH
CS
tCHH
t CSS t SCKF t CSH
SCK
t DS t DH t SCKR
SI MSB LSB
SERIAL OUTPUT TIMING DIAGRAM

t CPH
CS
t SCKH tSCKL
SCK
t DV t CHZ
SO
MSB LSB
Hi Impedance Hi Impedance

43
HI-3110, HI-3111, HI-3112, HI-3113
ABSOLUTE MAXIMUM RATINGS

(Voltages referenced to Gnd = 0V)
Supply Voltages, VDD:..........................................................................7V Operating Temperature Range: (Industrial).........................-40°C to +85°C
VLOGIC:....................................................................7V (Hi-Temp) ........................-55°C to +125°C
DC Voltages at CANH, CANL:.................................................-58V to +58V

2
DC Voltages at all other pins:.........................................-0.5V to VDD +0.5V Maximum Junction Temperature ......................................................175°C
Storage Temperature Range: -65°C to +150°C
1
Electrostatic Discharge (ESD) , pins CANH, CANL ........................+/- 6kV Reflow Solder Temperature: ....................................................... 260°C
all other pins ...............................................................................+/- 4kV
NOTES:
1. Human Body Model (HBM).
2. Junction Temperature TJ is defined as TJ = TAMB + P × Rth, where TAMB is the ambient or operating temperature, P is the power dissipation and Rth is
a fixed thermal resistance value which depends on the package and circuit board mounting conditions.
Stresses above those listed under "Absolute Maximum Ratings" may cause permanent damage to the device. These are stress ratings only. Functional
operation of the device at these or any other conditions above those indicated in the operational sections of the specifications is not implied. Exposure
to absolute maximum rating conditions for extended periods may affect device reliability.

44
HI-3110, HI-3111, HI-3112, HI-3113
DC ELECTRICAL CHARACTERISTICS
VLOGIC = 3.3V or 5V, VDD = 5V. Operating temperature range (unless otherwise noted).
LIMITS
PARAMETER SYMBOL CONDITIONS UNIT
MIN TYP MAX
Supply
Supply Voltage VLOGIC 3.15 5.25 V
VDD 4.75 5.25 V
Supply Current All inputs/outputs open except the

oscillator configured for 24MHz and
with 60 Ohm resistors at CANH and
CANL to SPLIT
ILOGIC VLOGIC current: Operating 0.6 5 mA
Sleep 5.0 25 μA
IDD VDD current: Operating 6.3 15 mA
Sleep 15 30 μA
Logic Inputs
High-Level Input Voltage VIH 0.7VLOGIC V

Low-Level Input Voltage VIL 0.3VLOGIC V
Input source current IIH VIL = 0V, VLOGIC = 5.0V

CS (pull down) 100 200 μA
All other inputs 1.5 μA
Input sink current IIL VIH = 5.0V, VLOGIC = 5.0V

CS -1.5 μA
SCK, SI, MR (pull up) -200 -100 μA
TXEN (pull up) -100 -50 μA
Pull-up current (CS) IPU VPU = VLOGIC -200 -30 μA

Pull-down current (SI, SCK, MR pins) IPD VPD = GND 30 200 μA
(TXEN) IPD VPD = GND 15 100 μA
Logic Outputs
High-Level Output Voltage VOH IOH = -1mA 0.9VLOGIC V

Low-Level Output Voltage VOL IOL = 1mA 0.1VLOGIC V
Output sink current IOL VOUT = 0.4V 1.6 mA

Output source current IOH VOUT = VDD - 0.4V -1 mA
SO Output Leakage ISOL VOUT = VLOGIC Tri-state condition 10 μA
Oscillator Pins
OSCIN Feedback Resistor ROSC Control Register 1, bit 3 = 0
Input at VLOGIC or 0V 4 5 6 MΩ
Control Register 1, bit 3 = 1
Input to VLOGIC only (pull down) 4 5 6 MΩ
OSCOUT Drive Current IOSC VLOGIC = 3.3V, VIN = 3.3V, VOUT = 0.5V 0.85 1.1 mA
VLOGIC = 3.3V, VIN = 0V, VOUT = 2.8V -0.7 -0.45 mA

45
HI-3110, HI-3111, HI-3112, HI-3113
DC ELECTRICAL CHARACTERISTICS (ctd.)

VLOGIC = 3.3V or 5V, VDD = 5V. Operating temperature range (unless otherwise noted).
LIMITS
PARAMETER SYMBOL CONDITIONS UNIT
MIN TYP MAX
Bus Lines (pins CANH, CANL)

CANH dominant output voltage VO(CANH) See Fig 14. RL = 60 Ω 3 3.6 4.25 V
CANL dominant output voltage VO(CANL) 0.5 1.4 1.75 V
Matching of dominant output voltage,

VCC − VCANH − VCANL VOM See Fig. 14. RL = 60 Ω − 100 0 150 mV
Dominant differential output voltage VDIFF(d)(o) 45 Ω < RL < 65 Ω, see Fig. 15 1.5 3 V
Recessive differential output voltage VDIFF(r)(o) No Load − 50 0 50 mV
Recessive output voltage VCANH(r), No Load, see Fig. 14

VCANL(r) 2 0.5VDD 3 V
Dominant differential input voltage (receiver) VDIFF(d)(i) − 12 V < VCANH, VCANL < + 12 V 0.9 V
Recessive differential input voltage (receiver) VDIFF(r)(i) − 12 V < VCANH, VCANL < + 12 V 0 0.5 V
Differential input hysteresis (receiver) VDIFF(hys) − 12 V < VCANH, VCANL < + 12 V 70 mV
See Fig. 18
Input leakage current ICANH, ICANL VDD = 0 V (unpowered node) − 200 + 200 μA
Short circuit output current IO(sc) pin CANH, VCANH = -58 V − 200 mA
pin CANL, VCANL = +58 V 200 mA
See Fig. 16
Common mode input resistance RIN(CM) − 12 V < VCANH, VCANL < + 12 V 15 25 45 kΩ

Deviation between common mode input resistance RIN(CM)(m) VCANH = VCANL −3 +3 %
Differential input resistance RIN(DIFF) − 12 V < VCANH, VCANL < + 12 V 25 50 75 kΩ
SPLIT pin output voltage Vsplit Normal Mode 2.4 2.5 2.6 V
See Fig. 17
Common mode input capacitance1 (1Mbit/s data rate) CIN(CM) 20 pF

Differential input capacitance1 (1Mbit/s data rate) CDIFF(CM) 10 pF

46
HI-3110, HI-3111, HI-3112, HI-3113
AC ELECTRICAL CHARACTERISTICS
VLOGIC = VDD = 5V. Operating temperature range (unless otherwise noted).
LIMITS
PARAMETER SYMBOL UNITS
MIN TYP MAX
SPI Interface Timing

SCK clock frequency fSCK 20 MHz
SCK clock period tCYC 50 ns
CS active after last SCK rising edge tCHH 5 ns
CS setup time to first SCK rising edge tCSS 10 ns
CS hold time after last SCK falling edge tCSH 25 ns
CS inactive between SPI instructions tCPH 25 ns
SPI SI Data set-up time to SCK rising edge tDS 5 ns
SPI SI Data hold time after SCK rising edge tDH 5 ns
SCK rise time tSCKR 2 ns
SCK fall ime tSCKF 2 ns
SCK pulse width high tSCKH 25 ns
SCK pulse width low tSCKL 25 ns
SO valid after SCK falling edge tDV 25 ns
SO high-impedance after CS inactive tCHZ 25 ns
CAN Bus Data Rate

Bit time tBit 1 25 μs
Bit rate fBit 40 1000 kHz
Time Out
Permanent dominant time-out tdom(TXD) 0.3 2 6 ms
External Clock
Maximum external clock frequency on OSCIN pin fOSC(max) 40 MHz

47
HI-3110, HI-3111, HI-3112, HI-3113
AC ELECTRICAL CHARACTERISTICS (ctd.)

VLOGIC = 3.3V, VDD = 5V. Operating temperature range (unless otherwise noted).
LIMITS
PARAMETER SYMBOL UNITS
MIN TYP MAX
SPI Interface Timing

SCK clock frequency fSCK 16.66 MHz
SCK clock period tCYC 66 ns
CS active after last SCK rising edge tCHH 5 ns
CS setup time to first SCK rising edge tCSS 10 ns
CS hold time after last SCK falling edge tCSH 25 ns
CS inactive between SPI instructions tCPH 25 ns
SPI SI Data set-up time to SCK rising edge tDS 5 ns
SPI SI Data hold time after SCK rising edge tDH 5 ns
SCK rise time tSCKR 2 ns
SCK fall ime tSCKF 2 ns
SCK pulse width high tSCKH 25 ns
SCK pulse width low tSCKL 25 ns
SO valid after SCK falling edge tDV 30 ns
SO high-impedance after CS inactive tCHZ 25 ns
CAN Bus Data Rate

Bit time tBit 1 25 μs
Bit rate fBit 40 1000 kHz
Time Out
Permanent dominant time-out tdom(TXD) 0.3 2 6 ms
External Clock
Maximum external clock frequency on OSCIN pin fOSC(max) 40 MHz

48
HI-3110, HI-3111, HI-3112, HI-3113
Internal
transceiver
RL VDIFF(d)(o)
VO(CANH)
VO(CANL)
Dominant
~3.5V: VO(CANH)
Recessive
~2.5V
~1.5V: VO(CANL)
Figure 14. CAN Bus Driver Circuit
Internal 300 W +/- 1%

transceiver CANH
0V
VDIFF(d)(o) RL
+_ -12V <= VTEST <= +12V

CANL 300 W +/- 1%
Figure 15. CAN Bus Driver (Dominant) Test Circuit
Internal
transceiver CANH
0V
+_ -58V or +58V
CANL
Figure 16. CAN Bus Driver Short-Circuit Test

49
HI-3110, HI-3111, HI-3112, HI-3113
HI-3110 CANH
Rs = 60 W
SPLIT
Rs = 60 W
CANL
Figure 17. Split-Termination Connection
CANH Internal
Transceiver
VDIFF(d)(i) RXD
VDIFF(d)(i) = VI(CANH) + VI(CANL)

CANL
VI(CANL)
Figure 18. CAN Bus Receiver Common Mode Voltage Test
C1
HI-3110 OSCIN
R Crystal
Resonator
OSCOUT
C2
R = 1.5 MW, C1 = C2 = 10pF typ.
Figure 19. Suggested Crystal Oscillator Circuit

50
HI-3110, HI-3111, HI-3112, HI-3113
ADDITIONAL PACKAGE CONFIGURATIONS AND PINOUTS
VLOGIC 1 18 INT VLOGIC 1 18 INT
OSCOUT 2 17 MR OSCOUT 2 17 MR
OSCIN 3 16 CS OSCIN 3 16 CS
GP1 4 15 SO GP1 4 15 SO
3111PSx 3112PSx
GP2 5 14 SI GP2 5 14 SI
TXEN 6 13 SCK TXEN 6 13 SCK
CLKOUT 7 12 STAT CLKOUT 7 12 STAT
RXD 8 11 TXD GND 8 11 VDD
GND 9 10 - CANL 9 10 CANH
18-Pin Plastic SOIC - WB Package 18-Pin Plastic SOIC - WB Package

VLOGIC
VLOGIC
OSCO
OSCO
INT
INT
MR
MR
-
-
-
-
-
-
-
-
-
-
-
-
44
43
42
41
40
39
38
37
36
35
34
44
43
42
41
40
39
38
37
36
35
34
- 1 33 - - 1 33 -
- 2 32 CS - 2 32 CS
OSCI 3 31 SO OSCI 3 31 SO
GP1 4 30 SI GP1 4 30 SI
- 5 29 SCK - 5 29 SCK
GP2 6 3113PCx 28 - GP2 6 3111PCx 28 -
TXEN 7 27 STAT TXEN 7 27 STAT
CLKOUT 8 26 - CLKOUT 8 26 -
- 9 25 - RXD 9 25 TXD
- 10 24 - - 10 24 -
- 11 23 - - 11 23 -
12
13
14
15
16
17
18
19
20
21
22
12
13
14
15
16
17
18
19
20
21
22
CANL
CANL
SPLIT
-
GND
GND
CANH
CANH
VDD
VDD
-
-
-
GND
GND
-
-
-
-
-
-
-
44 Pin Plastic QFN, 7mm x 7mm 44 Pin Plastic QFN, 7mm x 7mm

51
HI-3110, HI-3111, HI-3112, HI-3113
ORDERING INFORMATION
HI - 311x xx x x PART LEAD

NUMBER FINISH
Blank Tin / Lead (Sn / Pb) Solder
F 100% Matte Tin (Pb-free, RoHS compliant)
PART TEMPERATURE BURN

NUMBER RANGE FLOW IN
I -40°C TO +85°C I No
T -55°C TO +125°C T No
M -55°C TO +125°C M Yes
PART PACKAGE
NUMBER DESCRIPTION
PS 18 PIN PLASTIC WIDE BODY SOIC (18HW)
PC 44 PIN PLASTIC QFN (44PCS) (HI-3111 & HI-3113 only)
PART DESCRIPTION
NUMBER
3110 Integrated transceiver with SPLIT pin option
3111 Digital-only option, no transceiver
3112 Integrated transceiver with CLKOUT pin option
3113 Integrated transceiver with both SPLIT & CLKOUT pin options
(QFN-44 package (44PCS) only)

52
HI-3110, HI-3111, HI-3112, HI-3113
REVISION HISTORY
P/N Rev Date Description of Change

DS3110 New 09/7/10 Initial Release.
A 09/27/11 Updated DC Electrical Characteristics Table. Added “M grade” part to ordering information.
Added this revision history page.
B 1/17/12 Added statement regarding validation by C&S group, GmbH, to General Description.
Corrected typo in part number on p. 16. Clarified reset function on p. 17. Corrected Status
Flag Enable Register default bits from 0x82 to 0x00 on p. 27.
C 7/19/12 Clarify operation of One Shot Mode. Update Figure 12, Simplified Transmission Flow
Diagram.
D 9/20/12 Add additional package option, HI-3111PCx. Update Vlogic supply current (Ilogic) from 2mA
to 5mA max.
E 12/10/13 Updated name of ‘Configuration’ Registers on p. 16 to ‘Control’ Registers for consistency.
Updated QFN-44 and SOIC-18 package drawings. Clarify Free Running Timer read function
byte order. Update Reflow Solder Temperature in Absolute Maximum Ratings table.
F 02/26/14 Added “Maximum external clock frequency on OSCIN pin” to AC Characteristics Table.
G 06/16/14 Reflect parts HI-3111, HI-3112, HI-3113 in title.
H 10/23/15 Update SPI Output timing diagram. Update AC Characteristics for tCHZ.
I 03/23/16 Update SPI Command 0x12 functional description. Loads single frame to Transmit FIFO.
J 05/12/16 Include pin descriptions for HI-3111 variant. Update SPI clock frequency parameters for
operation at VLOGIC = 3.3V and VLOGIC = 5V.
K 02/02/17 Update block diagram to correct Time Tag Counter block connections.

53
PACKAGE DIMENSIONS
18-PIN PLASTIC SMALL OUTLINE (SOIC) - WB millimeters (inches)

(Wide Body) Package Type: 18HW
11.55
BSC 0.265 ± 0.065
(0.455)
(0.010 ± 0.003)
10.30 7.50 BSC

BSC
(0.406) (0.295)
See Detail A
0.41 ± 0.10 2.05

(0.016 ± 0.004) min.
(0.081)
1.27 0° to 8°
BSC 0.20 ± 0.10
(0.05) (0.008 ± 0.004)
0.835 ± 0.435
(0.033 ± 0.017)
BSC = “Basic Spacing between Centers”
is theoretical true position dimension and Detail A
has no tolerance. (JEDEC Standard 95)
44-PIN PLASTIC CHIP-SCALE PACKAGE (QFN) millimeters (inches)

Package Type: 44PCS
7.00 5.50 ± 0.050

BSC
(0.276) (0.217 ± 0.002)
0.50 BSC
(0.0197)
7.00 Top View 5.50 ± 0.050 Bottom

BSC
(0.276) (0.217 ± 0.002) View
0.25 ± 0.050
(0.010 ± 0.002)
0.400 ± 0.050
1.00 Electrically isolated heat (0.016 ± 0.002)
max 0.200 typ sink pad on bottom of
(0.039)
(0.008) package
Connect to any ground or
power plane for optimum
BSC = “Basic Spacing between Centers” thermal dissipation
is theoretical true position dimension and
has no tolerance. (JEDEC Standard 95)

54

Hi 3110 - V Rev K

Uploaded by

Copyright:

Available Formats

Hi 3110 - V Rev K

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hi 3110 - V Rev K

Uploaded by

Copyright:

Available Formats

HI-3110, HI-3111, HI-3112, HI-3113

Avionics CAN Controller

(both CLKOUT and SPLIT pins) in a very compact QFN-44 OSCOUT 2 17 MR

18-Pin Plastic SOIC - WB Package

HOLT INTEGRATED CIRCUITS

Figure 1. Block Diagram

PRIMARY FUNCTIONS OF HI-3110 LOGIC BLOCKS

REGISTERS BLOCK ERROR BLOCK

BIT TIMING BLOCK STATUS AND INTERRUPT

HOLT INTEGRATED CIRCUITS

HOLT INTEGRATED CIRCUITS

FUNCTIONAL OVERVIEW RECEIVER

from 5V and the line driver is capable of maintaining a

LOOPBACK MODE CAN PROTOCOL OVERVIEW

HOLT INTEGRATED CIRCUITS

Standard Data Frame

CRC Del Cyclic Redundancy Check Delimiter

Figure 2. Standard Frame Format.

HOLT INTEGRATED CIRCUITS

Extended Data Frame

IDxx Identifier bit xx

ACK Slot bit Acknowledge Slot bit

IFS Interframe space

Figure 3. Extended Frame Format.

HOLT INTEGRATED CIRCUITS

Remote Frame with Extended ID (64 bits)

HOLT INTEGRATED CIRCUITS

No Data Field. See NOTE regarding Data Length Code.

Figure 4. Remote Frame Format (Extended Identifier).

Data Frame with error detected during data transmission

Figure 5. Error Frame Format.

HOLT INTEGRATED CIRCUITS

Error Echo Delimiter

Figure 6. Overload Frame Format

HOLT INTEGRATED CIRCUITS

Standard ID Arbitration Field

CAN Bus differential

Node 2 loses arbitration

Node 3 loses arbitration

Figure 7. Bitwise Arbitration.

HOLT INTEGRATED CIRCUITS

BR = 1/(tTQ x (number of time quanta per bit)) (3)

tTQ Baud Rate Prescaler

Nominal bit time, tb

Sync TSeg1 = TSeg2 = Sync TSeg1 TSeg2

Figure 8. CAN Bit Time

HOLT INTEGRATED CIRCUITS

Hard synchronization forces the bit edge to lie within the

HOLT INTEGRATED CIRCUITS

REGISTER R/W DESCRIPTION SPI WRITE SPI READ

CTRL0 R/W Control Register 0 0x14 0xD2

HOLT INTEGRATED CIRCUITS

CONTROL REGISTER 0: CTRL0

Bit Name R/W Default Description

4 WAKEUP R/W 0 Wake-Up Enable.

2 BOR R/W 0 Bus-off Reset.

HOLT INTEGRATED CIRCUITS

CONTROL REGISTER 1: CTRL1