TTCAN

User’s Manual

Revision 1.6

3.4.2 Transmission Request Registers

 

 

 

 

 

 

 

 

 

Transmission Request 1 Register

15 14 13 12 11 10 9 8

7

6 5 4 3 2 1 0

 

 

(addresses 0x81 & 0x80)

 

 

 

 

 

TxRqst16-9

 

TxRqst8-1

 

 

 

 

 

 

 

 

Transmission Request 2 Register

TxRqst32-25

 

TxRqst24-17

 

 

(addresses 0x83 & 0x82)

 

 

 

 

 

r

 

r

 

 

 

 

 

 

 

 

 

 

 

TxRqst32-1Transmission Request Bits (of all Message Objects)

one The transmission of this Message Object is requested and is not yet done. zero This Message Object is not waiting for transmission.

These registers hold the TxRqst bits of the 32 Message Objects. By reading out the TxRqst bits, the CPU can check for which Message Object a Transmission Request is pending. The TxRqst bit of a specific Message Object can be set/reset by the CPU via the IFx Message Interface Registers or (when not in time triggered mode) by the Message Handler after reception of a Remote Frame or after a successful transmission.

3.4.3 New Data Registers

New Data 1 Register

15 14 13 12 11 10 9 8

7

6 5 4 3 2 1 0

(addresses 0x91 & 0x90)

 

 

 

NewDat16-9

 

NewDat8-1

 

 

 

 

New Data 2 Register

NewDat32-25

 

NewDat24-17

(addresses 0x93 & 0x92)

 

 

 

r

 

r

 

 

 

 

 

 

NewDat32-1New Data Bits (of all Message Objects)

one The Message Handler or the CPU has written new data into the data por- tion of this Message Object.

zero No new data has been written into the data portion of this Message Object by the Message Handler since last time this flag was cleared by the CPU.

MsgLstThese registers hold the NewDat bits of the 32 Message Objects. By reading out the NewDat bits, the CPU can check for which Message Object the data portion was updated. The NewDat bit of a specific Message Object can be set/reset by the CPU via the IFx Message Interface Registers or by the Message Handler after reception of a Data Frame or after a successful transmission.

3.4.4 Interrupt Pending Registers

manual_about.fm

Interrupt Pending 1 Register

15 14 13 12 11 10 9 8

7

6 5 4 3 2 1 0

(addresses 0xA1 & 0xA0)

 

 

 

IntPnd16-9

 

IntPnd8-1

 

 

 

 

Interrupt Pending 2 Register

IntPnd32-25

 

IntPnd24-17

(addresses 0xA3 & 0xA2)

 

 

 

r

 

r

 

 

 

 

 

 

IntPnd32-1Interrupt Pending Bits (of all Message Objects)

one This message object is the source of an interrupt. zero This message object is not the source of an interrupt.

These registers hold the IntPnd bits of the 32 Message Objects. By reading out the IntPnd bits, the CPU can check for which Message Object an interrupt is pending. The IntPnd bit of a specific Message Object can be set/reset by the CPU via the IFx Message Interface Registers or by the Message Handler after reception or after a successful transmission of a frame. This will also affect the value of IntId in the Interrupt Register.

BOSCH

- 28/77 -

11.11.02

Page 28
Image 28
Bosch Appliances TTCAN user manual Transmission Request Registers, New Data Registers, Interrupt Pending Registers