2000 Jan 04 40
Philips Semiconductors Product specification
Stand-alone CAN controller SJA1000
Table 25 TX frame information (SFF); CAN address 16
Notes
1. Frame format.
2. Remote transmission request.
3. Don’t care; recommended to be compatible to receive buffer (0) in case of using the self reception facility (self test).
4. Data length code bit.
Table 26 TX identifier 1 (SFF); CAN address 17; note 1
Note
1. ID.X means identifier bit X.
Table 27 TX identifier 2 (SFF); CAN address 18; note 1
Notes
1. ID.X means identifier bit X.
2. Don’t care; recommended to be compatible to receive buffer (RTR) in case of using the self reception facility (self
test).
3. Don’t care; recommended to be compatible to receive buffer (0) in case of using the self reception facility (self test).
Table 28 TX frame information (EFF); CAN address 16
Notes
1. Frame format.
2. Remote transmission request.
3. Don’t care; recommended to be compatible to receive buffer (0) in case of using the self reception facility (self test).
4. Data length code bit.
Table 29 TX identifier 1 (EFF); CAN address 17; note 1
Note
1. ID.X means identifier bit X.
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
FF
(1)
RTR
(2)
X
(3)
X
(3)
DLC.3
(4)
DLC.2
(4)
DLC.1
(4)
DLC.0
(4)
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.28 ID.27 ID.26 ID.25 ID.24 ID.23 ID.22 ID.21
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.20 ID.19 ID.18 X
(2)
X
(3)
X
(3)
X
(3)
X
(3)
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
FF
(1)
RTR
(2)
X
(3)
X
(3)
DLC.3
(4)
DLC.2
(4)
DLC.1
(4)
DLC.0
(4)
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.28 ID.27 ID.26 ID.25 ID.24 ID.23 ID.22 ID.21
2000 Jan 04 41
Philips Semiconductors Product specification
Stand-alone CAN controller SJA1000
Table 30 TX identifier 2 (EFF); CAN address 18; note 1
Note
1. ID.X means identifier bit X.
Table 31 TX identifier 3 (EFF); CAN address 19; note 1
Note
1. ID.X means identifier bit X.
Table 32 TX identifier 4 (EFF); CAN address 20; note 1
Notes
1. ID.X means identifier bit X.
2. Don’t care; recommended to be compatible to receive buffer (RTR) in case of using the self reception facility (self
test).
3. Don’t care; recommended to be compatible to receive buffer (0) in case of using the self reception facility (self test).
Table 33 Frame Format (FF) and Remote Transmission Request (RTR) bits
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.20 ID.19 ID.18 ID.17 ID.16 ID.15 ID.14 ID.13
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.12 ID.11 ID.10 ID.9 ID.8 ID.7 ID.6 ID.5
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
ID.4 ID.3 ID.2 ID.1 ID.0 X
(2)
X
(3)
X
(3)
BIT VALUE FUNCTION
FF 1 EFF; extended frame format will be transmitted by the CAN controller
0 SFF; standard frame format will be transmitted by the CAN controller
RTR 1 remote; remote frame will be transmitted by the CAN controller
0 data; data frame will be transmitted by the CAN controller
6.4.13.3 Data Length Code (DLC)
The number of bytes in the data field of a message is
coded by the data length code. At the start of a remote
frame transmission the data length code is not considered
due to the RTR bit being logic 1 (remote). This forces the
number of transmitted/received data bytes to be 0.
Nevertheless, the data length code must be specified
correctly to avoid bus errors, if two CAN controllers start a
remote frame transmission with the same identifier
simultaneously.
The range of the data byte count is 0 to 8 bytes and is
coded as follows:
DataByteCount = 8 × DLC.3 + 4 × DLC.2 + 2 × DLC.1 +
DLC.0
For reasons of compatibility no data length code >8 should
be used. If a value >8 is selected, 8 bytes are transmitted
in the data frame with the Data Length Code specified in
DLC.
6.4.13.4 Identifier (ID)
In Standard Frame Format (SFF) the identifier consists of
11 bits (ID.28 to ID.18) and in Extended Frame Format
(EFF) messages the identifier consists of 29 bits
(ID.28 to ID.0). ID.28 is the most significant bit, which is
transmitted first on the bus during the arbitration process.
The identifier acts as the message’s name, used in a
receiver for acceptance filtering, and also determines the
bus access priority during the arbitration process.
2000 Jan 04 42
Philips Semiconductors Product specification
Stand-alone CAN controller SJA1000
The lower the binary value of the identifier the higher the
priority. This is due to the larger number of leading
dominant bits during arbitration.
6.4.13.5 Data field
The number of transferred data bytes is defined by the
data length code. The first bit transmitted is the most
significant bit of data byte 1 at CAN address 19 (SFF) or
CAN address 21 (EFF).
6.4.14 RECEIVE BUFFER
The global layout of the receive buffer is very similar to the
transmit buffer described in the previous section.
The receive buffer is the accessible part of the RXFIFO
and is located in the range between CAN address
16 and 28. Each message is subdivided into a descriptor
and a data field.
Fig.8 Example of the message storage within the RXFIFO.
handbook, full pagewidth
MGK622
release
receive
buffer
command
64-byte
FIFO
incoming
messages
message 3
message 2
message 1
25
24
23
22
21
20
19
18
17
16
28
27
26
receive
buffer
window
CAN address
Message 1 is now available in the receive buffer.
6.4.14.1 Descriptor field of the receive buffer
The bit layout of the receive buffer is represented in Tables 34 to 36 for SFF and Tables 37 to 41 for EFF. The given
configuration is chosen to be compatible with the transmit buffer layout (see Section 6.4.13.2).
Table 34 RX frame information (SFF); CAN address 16
Notes
1. Frame format.
2. Remote transmission request.
3. Data length code bit.
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
FF
(1)
RTR
(2)
0 0 DLC.3
(3)
DLC.2
(3)
DLC.1
(3)
DLC.0
(3)

SJA1000/N1,112

Mfr. #:
Manufacturer:
NXP Semiconductors
Description:
IC STAND-ALONE CAN CTRLR 28-DIP
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet