- 您現(xiàn)在的位置：買賣IC網(wǎng) > PDF目錄366891 > CR16MCS9VJE8 Microcontroller PDF資料下載
參數(shù)資料
| 型號(hào)： | CR16MCS9VJE8 |
| 英文描述： | Microcontroller |
| 中文描述： | 微控制器 |
| 文件頁(yè)數(shù)： | 152/157頁(yè) |
| 文件大?。?/td> | 1256K |
| 代理商： | CR16MCS9VJE8 |
第1頁(yè)第2頁(yè)第3頁(yè)第4頁(yè)第5頁(yè)第6頁(yè)第7頁(yè)第8頁(yè)第9頁(yè)第10頁(yè)第11頁(yè)第12頁(yè)第13頁(yè)第14頁(yè)第15頁(yè)第16頁(yè)第17頁(yè)第18頁(yè)第19頁(yè)第20頁(yè)第21頁(yè)第22頁(yè)第23頁(yè)第24頁(yè)第25頁(yè)第26頁(yè)第27頁(yè)第28頁(yè)第29頁(yè)第30頁(yè)第31頁(yè)第32頁(yè)第33頁(yè)第34頁(yè)第35頁(yè)第36頁(yè)第37頁(yè)第38頁(yè)第39頁(yè)第40頁(yè)第41頁(yè)第42頁(yè)第43頁(yè)第44頁(yè)第45頁(yè)第46頁(yè)第47頁(yè)第48頁(yè)第49頁(yè)第50頁(yè)第51頁(yè)第52頁(yè)第53頁(yè)第54頁(yè)第55頁(yè)第56頁(yè)第57頁(yè)第58頁(yè)第59頁(yè)第60頁(yè)第61頁(yè)第62頁(yè)第63頁(yè)第64頁(yè)第65頁(yè)第66頁(yè)第67頁(yè)第68頁(yè)第69頁(yè)第70頁(yè)第71頁(yè)第72頁(yè)第73頁(yè)第74頁(yè)第75頁(yè)第76頁(yè)第77頁(yè)第78頁(yè)第79頁(yè)第80頁(yè)第81頁(yè)第82頁(yè)第83頁(yè)第84頁(yè)第85頁(yè)第86頁(yè)第87頁(yè)第88頁(yè)第89頁(yè)第90頁(yè)第91頁(yè)第92頁(yè)第93頁(yè)第94頁(yè)第95頁(yè)第96頁(yè)第97頁(yè)第98頁(yè)第99頁(yè)第100頁(yè)第101頁(yè)第102頁(yè)第103頁(yè)第104頁(yè)第105頁(yè)第106頁(yè)第107頁(yè)第108頁(yè)第109頁(yè)第110頁(yè)第111頁(yè)第112頁(yè)第113頁(yè)第114頁(yè)第115頁(yè)第116頁(yè)第117頁(yè)第118頁(yè)第119頁(yè)第120頁(yè)第121頁(yè)第122頁(yè)第123頁(yè)第124頁(yè)第125頁(yè)第126頁(yè)第127頁(yè)第128頁(yè)第129頁(yè)第130頁(yè)第131頁(yè)第132頁(yè)第133頁(yè)第134頁(yè)第135頁(yè)第136頁(yè)第137頁(yè)第138頁(yè)第139頁(yè)第140頁(yè)第141頁(yè)第142頁(yè)第143頁(yè)第144頁(yè)第145頁(yè)第146頁(yè)第147頁(yè)第148頁(yè)第149頁(yè)第150頁(yè)第151頁(yè)當(dāng)前第152頁(yè)第153頁(yè)第154頁(yè)第155頁(yè)第156頁(yè)第157頁(yè)
www.national.com
152
26.0
Appendix
The following document describes problems identified in the
CR16 modules.
26.1
CR16CAN
26.1.1
Under certain conditions it occurs that the CR16CAN module
receives a frame, sent by itself even though the loopback fea-
ture is disabled.
This condition consists of two parts, which both must be true
to cause this malfunction.
A) The first part is that a transmit buffer and at least one re-
ceive buffer are configured with the same identifier. Let's call
this identifier ID_RX_TX here. With regard to the receive
buffer, this means that the buffer identifier and the corre-
sponding filter masks are setup in a way that the buffer is able
to receive frames with the identifier ID_RX_TX.
B) The second part is that the CAN communication must take
place in the following sequence:
1. A message with the identifier ID_RX_TX from another
CAN node is received into the receive buffer.
2. A message with the identifier ID_RX_TX is sent by the
CR16CAN module immediately after the reception took
place (Note).
After this communication the frame sent by the CR16CAN
module will be copied into the next receive buffer available
for the identifier ID_RX_TX.
Note:
If a frame with an identifier different to ID_RX_TX is
sent or received in between the steps 1 and 2, the problem
does not occur.
CR16CAN Problem Descriptions:
26.1.2
When a frame is received into the hidden receive buffer, the
CR16CAN module scans through all CAN message buffers.
During this sequence all receive buffers (RX-buffers) capable
of receiving this frame are tagged (RX-tag). If the message
was received correctly the frame is copied into first tagged
buffer (lowest buffer number).
Every CAN node also monitors frames being transmitted in
order to switch from transmitter to receiver after a lost arbitra-
tion. In order to do this the CR16CAN module also receives
transmitted frames into the hidden receive buffer.
The scanning sequence is also applied to transmitted
frames. This means, the identifier in the hidden receive buffer
is compared with the RX-buffer identifiers. As the identifier is
the same as with the last receive scanning sequence, the
RX-tags will not be changed.
A CAN buffer receive tag is only updated in the following cas-
es:
— A new scanning sequence has overwritten the old re-
ceive tags due to a different identifier mask under com-
parison.
— The CPU has changed the CAN buffer status in the
CNSTAT.ST-field to any value which disables the buffer
to receive a message (e.g. RX_NOT_ACTIVE or any
TX-state)
— The CPU has changed the CAN buffer identifier.
CR16CAN Problem Cause
Applied to the CAN communication sequence described
above, this means that the transmitted message, currently
present in the hidden receive buffer will be copied into the
same receive buffer and the message received from the oth-
er CAN node will be overwritten.
Example
Buffer Settings
Filter Masks:
GMSKB = 0x0000
GMSKX = 0x000F
Buffer configuration:
CAN Communication Sequence A:
(BUFFLOCK disabled)
1. Message sent from another CAN node received into
buffer 1.
Buffer 1 and buffer 2 are tagged for reception of this
message.
2. CPU reads out data from CAN buffer 1 and resets the
buffer state from RX_FULL to RX_READY (Note 1).
3. CAN buffer 0 sends a frame (status set to TX_ONCE).
4. Status of CAN buffer 1 changes to RX_FULL, because it
has received the message sent by buffer 0 (Note 2).
Note:
1. Step 2 does not need to be done. In case the buffer
1 status is not updated to RX_READY, the buffer status will
change from RX_FULL to RX_OVERRUN in step 4.
Note:
2. As BUFFLOCK is disabled, all messages with the
identifier ID_RX_TX will be copied into buffer 1. Buffer 2 does
not receive any message.
CAN Communication Sequence B:
(BUFFLOCK enabled)
1. Message sent from another CAN node received into
buffer 1. Buffer 1 is locked now.
Buffer 1 and buffer 2 are tagged for reception of this
message.
2. CAN buffer 0 sends a frame.
3. Status of CAN buffer 2 changes to RX_FULL, because it
has received the message sent by buffer 0.
CAN Communication Sequence C
(CR16CAN does NOT receive a frame sent by itself.)
CAN
Buffer
Number
CAN Buffer
Status
Buffer
Identifier
Identifier
Mask
0
TX_NOT_ACTIVE 0x15555550 0x1555555X
1
RX_READY
0x15555551 0x1555555X
2
RX_READY
0x15555552 0x1555555X
3
RX_READY
0x15555003 0x1555500X
X = don't care
相關(guān)PDF資料 |
PDF描述 |
|---|---|
| CR16MCS9VJE8Y | Microcontroller |
| CR16MCT5VJE7Y | Microcontroller |
| CR16HCS5VJE8 | Microcontroller |
| CR16HCS9VJE7Y | Microcontroller |
| CR16HCS9VJE8Y | Microcontroller |
相關(guān)代理商/技術(shù)參數(shù) |
參數(shù)描述 |
|---|---|
| CR16MCS9VJE8/NOPB | 功能描述:16位微控制器 - MCU RoHS:否 制造商:Texas Instruments 核心:RISC 處理器系列:MSP430FR572x 數(shù)據(jù)總線寬度:16 bit 最大時(shí)鐘頻率:24 MHz 程序存儲(chǔ)器大小:8 KB 數(shù)據(jù) RAM 大小:1 KB 片上 ADC:Yes 工作電源電壓:2 V to 3.6 V 工作溫度范圍:- 40 C to + 85 C 封裝 / 箱體:VQFN-40 安裝風(fēng)格:SMD/SMT |
| CR16MCS9VJE80 | 制造商:NSC 制造商全稱:National Semiconductor 功能描述:Family of 16-bit CAN-enabled CompactRISC Microcontrollers |
| CR16MCS9VJE81 | 制造商:NSC 制造商全稱:National Semiconductor 功能描述:Family of 16-bit CAN-enabled CompactRISC Microcontrollers |
| CR16MCS9VJE82 | 制造商:NSC 制造商全稱:National Semiconductor 功能描述:Family of 16-bit CAN-enabled CompactRISC Microcontrollers |
| CR16MCS9VJE83 | 制造商:NSC 制造商全稱:National Semiconductor 功能描述:Family of 16-bit CAN-enabled CompactRISC Microcontrollers |
發(fā)布緊急采購(gòu)，3分鐘左右您將得到回復(fù)。