參數(shù)資料
型號(hào)： XA-C3
廠商： NXP Semiconductors N.V.
英文描述： XA 16-bit microcontroller family 32K/1024 OTP CAN transport layer controller 1 UART, 1 SPI Port, CAN 2.0B, 32 CAN ID Filters, transport layer co-proce
中文描述： 的XA 16位微控制器系列32K/1024檢察官可以傳輸層控制器1的UART，1個(gè)SPI端口，CAN 2.0B總線，32可以讀取器，傳輸層合作proce
文件頁數(shù)： 50/68頁
文件大小： 368K
代理商： XA-C3
Philips Semiconductors
Preliminary specification
XA-C3
XA 16-bit microcontroller family
32K/1024 OTP CAN transport layer controller
1 UART, 1 SPI Port, CAN 2.0B, 32 CAN ID filters, transport layer co-processor
2000 Jan 25
43
The Frame Info byte contains the following bits:
FRAME INFO
7
IDE
6
5
4
3
2
1
0
RTR
SEM1
SEM0
DLC.3
DLC.2
DLC.1
DLC.0
The actual incoming Screener ID which caused the Match can be
retrieved from the MnMIDH and MnMIDL registers as shown in
Figure 39.
MNMIDH
15
ID.28
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
ID.27
ID.26
ID.25
ID.24
ID.23
ID.22
ID.21
ID.20
ID.19
ID.18
ID.17
ID.16
ID.15
ID.14
ID.13
MNMIDL
15
ID.12
14
13
12
ID.9
11
ID.8
10
ID.7
9
8
7
6
5
4
3
2
1
–
0
–
ID.11
ID.10
ID.6
ID.5
ID.4
ID.3
ID.2
ID.1
ID.0
IDE
Figure 39. Retrieving the Screener ID for an Extended CAN Frame
Fragmented Message Assembly
Masking of the 11/29 bit CAN Identifier field by User software (but
only the actualbits of the Identifier itself!) is disallowed for any
Message Object which employs auto–Fragmentation assembly. The
identifier which resulted in the Match is, therefore, known
unambiguously and is not included in the receive buffer. If the
software needs access to this information, it can retrieve it from the
appropriate MnMIDH and MnMIDL registers.
As subsequent frames of a Fragmented message are received, the
new data bytes are appended to the end of the previously received
packets. This process continues until a complete multi–frame
message has been received and stored.
If an object is enabled with FRAG = 1, under protocols DeviceNet,
CANopen, and OSEK (Prtcl1 Prtcl0
≠
00), the first CAN frame data
byte is used to encode Fragmentation information only. That byte
will not be stored in the buffer area. The storage will start with the
second data byte (Data Byte 2) and proceed to the end of the frame.
See Figure 40.
Byte count
Data Byte 2
Data Byte 3
…
Data Byte DLC
Data Byte 2 (next)
Data Byte 3 (next)
…
Direction of increasing
address
Figure 40. Memory Image for Fragmented CTL Messages
(FRAG = 1 and Prtcl1 Prtcl0
≠
00)
If an object is enabled with FRAG = 1, with CAN as the system
protocol (Prtcl1 Prtcl0 = 00), then CAN frames are stored
sequentially in that object’s message buffer using the format shown
in . Also, if [Prtcl1 Prtcl0] = 00, Rx Buffer Full is defined as “l(fā)ess than
9 bytes remaining” after storage of a complete CAN frame. When
the DMA pointer wraps around, it will be reset to offset ‘1’ in the
buffer, not offset ‘0’, and there will be no Byte Count written.
FrameInfo
Data Byte 1
Data Byte 2
…
Data Byte DLC
FrameInfo (next)
Data Byte 1 (next)
Data Byte 2 (next)
…
Direction of increasing
address
dd
Direction of increasing
Figure 41. Memory Image for CAN Frame Buffering (FRAG = 1
and Prtcl1 Prtcl0
=
00)
During buffer access, the DMA will generate addresses
automatically starting from the base location of the buffer. If the DMA
has reached the top of the buffer, but the message has not been
completely transferred to memory yet, the DMA will wrap around by
generating addresses starting from the bottom of the buffer again.
Some time before this happens, a warning interrupt will be
generated so that the User application can take the necessary
action to prevent data loss.
The top location of the buffer is determined by the size of the buffer
as specified in MnBSZ.
The XA-C3 automatically receives, checks and reassembles up to
32 Fragmented messages automatically. When the FRAG bit is set
on a particular message, the message handler hardware will use the
Fragmentation information contained in Data Byte 1 of each frame.
To enable automatic Fragmented message handling for a certain
Message Object, the User is responsible for setting the FRAG bit in
the object’s MnCTL register.
The message handler will keep track of the current address location
and the number of bytes of each CTL message as it is being
assembled in the designated message buffer location. After an “End
of Message” is decoded, the message handler will finish moving the
complete message and the byte count into the message buffer via
相關(guān)PDF資料
PDF描述
XA-G39 XA 16-bit microcontroller family XA 16-bit microcontroller 32K FLASH/1K RAM, watchdog, 2 UARTs
XA-G49 XA 16-bit microcontroller family 64K FLASH/2K RAM, watchdog, 2 UARTs
XA-H3 CMOS 16-bit highly integrated microcontroller
XA-H4 Single-chip 16-bit microcontroller
XACA04SPEC0304 CONTROL STATION 4WAY
相關(guān)代理商/技術(shù)參數(shù)
參數(shù)描述
XAC50PC1-300X 制造商:WINCH 功能描述: 制造商:Winchester Electronics 功能描述:
XAC50PF2A010 制造商: 功能描述: 制造商:undefined 功能描述:
XAC66PD3A700 制造商:WINCHESTER 功能描述:
XAC66PF2A016 制造商: 功能描述: 制造商:undefined 功能描述:
XAC66PF2B016 制造商: 功能描述: 制造商:undefined 功能描述:
發(fā)布緊急采購(gòu)，3分鐘左右您將得到回復(fù)。

采購(gòu)需求

(若只采購(gòu)一條型號(hào)，填寫一行即可)

發(fā)布成功！您可以繼續(xù)發(fā)布采購(gòu)。也可以進(jìn)入我的后臺(tái)，查看報(bào)價(jià)

發(fā)布成功！您可以繼續(xù)發(fā)布采購(gòu)。也可以進(jìn)入我的后臺(tái)，查看報(bào)價(jià)

*型號(hào) *數(shù)量 廠商 批號(hào) 封裝
添加更多采購(gòu)

我的聯(lián)系方式

*
*
*