 |
Electronic Components Datasheet Search |
|
|
Electronic Components Datasheet Search |
|
CP3SP33SMS/NOPB Datasheet(PDF) 192 Page - Texas Instruments |
|
|
|||||||||||||||||||||||||||||
CP3SP33SMS/NOPB Datasheet(HTML) 192 Page - Texas Instruments |
|
|
192 / 407 page  TX_ONCE_RTR 1110 CAN schedules TX RTR received TX done Transmit request cancelled CPU writes 1000 Remote transmission request sent - now wait to receive a data frame TX request delayed by a TX request of higher priority message Transmit request cancelled CPU writes 1000 CAN schedules TX TX request CPU writes 1100 TX request CPU writes 1110 CPU writes 1010 TX_BUSY2 1111 TX done transmit failed TX_RTR 1010 TX_NOT_ACTIVE 1000 TX_BUSY0 1101 RX_READY 0010 TX_ONCE 1100 transmit failed DS042 CP3SP33 SNOSCW5 – MAY 2013 www.ti.com 22.6.4 TX Buffer States The transmission process can be started after software has loaded the buffer registers (data, ID, DLC, PRI) and set the buffer status from TX_NOT_ACTIVE to TX_ONCE, TX_RTR, or TX_ONCE_RTR. When the CPU writes TX_ONCE, the buffer will be TX_BUSY as soon as the CAN module has scheduled this buffer for the next transmission. After the frame could be successfully transmitted, the buffer status will be automatically reset to TX_NOT_ACTIVE when a data frame was transmitted or to RX_READY when a remote frame was transmitted. If the CPU configures the message buffer to TX_ONCE_RTR, it will transmit its data contents. During the transmission, the buffer state is 1111b as the CPU wrote 1110b into the status section of the CNSTAT register. After the successful transmission, the buffer enters the TX_RTR state and waits for a remote frame. When it receives a remote frame, it will go back into the TX_ONCE_RTR state, transmit its data bytes, and return to TX_RTR. If the CPU writes 1010b into the buffer status section, it will only enter the TX_RTR state, but it will not send its data bytes before it waits for a remote frame. Figure 22-25 illustrates the possible transmit buffer states. Figure 22-25. Transmit Buffer States 22.7 Interrupts Each CAN module has one dedicated ICU interrupt vector for all interrupt conditions. In addition, the data frame receive event is an input to the MIWU (see Section 17). The interrupt process can be initiated from the following sources. • CAN data transfer – Reception of a valid data frame in the buffer. (Buffer state changes from RX_READY to RX_FULL or RX_OVERRUN.) – Successful transmission of a data frame. (Buffer state changes from TX_ONCE to TX_NOT_ACTIVE or RX_READY.) – Successful response to a remote frame. (Buffer state changes from TX_ONCE_RTR to TX_RTR.) – Transmit scheduling. (Buffer state changes from TX_RTR to TX_ONCE_RTR.) 192 Dual CAN Interfaces Copyright © 2013, Texas Instruments Incorporated Submit Documentation Feedback Product Folder Links :CP3SP33 |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |
English ▼
English
Chinese
German
Japanese
Russian
Korean
Spanish
French
Italian
Portuguese
Polish
Vietnamese
Indian
Mexican
British
New Zealand
