MDEV-868-PRC datasheet(40/55 Pages) LINX

40 / 55 page

–

EEXFLAG - Extended Exception Flags

Volatile Address = 0xCD - 0xCF

These volatile registers contain flags for various events. Similar to the

EXCEPT register, they provide a separate bit for each exception.

When an exception occurs, the associated bit is set in this register. If the

corresponding bit in the EEXMASK is set and EXMASK is zero, the EX

status line is set. Reading an EEXFLAG register does not clear the register.

Writing to an EEXFLAG register causes the register to be set to the

BIT_AND(current_value, new_value). This provides a way of clearing bits

that have been serviced without clearing a bit that has been set since the

flag register was read. This prevents a loss of notification of an exception.

some flags are also cleared internally. Unless otherwise noted, exceptions

are cleared by writing a zero to the corresponding register bit.

Flag EX_TXDONE is set when a data packet has been transmitted. If the

packet was sent with acknowledgement enabled, this flag indicates that

the acknowledgment has also been received.

Flag EX_RXWAIT is 1 when there are buffered incoming data bytes which

have not been sent to the UART. It is cleared by reading or discarding all

data bytes.

Flag EX_UNENCRYPT is 1 when a received packet is not encrypted. This

can only occur when SECOPT:EN_UNC=1.

Flag EX_SEQDEC is 1 when a received encrypted packet has a smaller

sequence number than the previously received packet. Possible causes

are an attempt to replay a previous message by an attacker, receiving a

message from a different transmitter or restarting the transmitter.

Figure 78: HumPRCTM Series Transceiver Extended Exception Code Registers

HumPRCTM Series Extended Exception Flags Registers

Name

Volatile

Address

Description

EEXFLAG2

0xCD

Byte 2 of the extended exception flags

EEXFLAG1

0xCE

Byte 1 of the extended exception flags

EEXFLAG0

0xCF

LSB of the extended exception flags

HumPRCTM Series Transceiver Extended Exception Codes

Bit

Exception Name

Description

EEXFLAG0 (0xCF)

EX_BUFOVFL

Internal UART buffer overflowed.

EX_RFOVFL

Internal RF packet buffer overflowed.

EX_WRITEREGFAILED Attempted write to register failed.

EX_NORFACK

Acknowledgement packet not received after

maximum number of retries.

EX_BADCRC

Bad CRC detected on incoming packet.

EX_BADHEADER

Bad CRC detected in packet header.

EX_BADSEQID

Sequence ID was incorrect in ACK packet.

EX_BADFRAMETYPE

Unsupported frame type specified.

EEXFLAG1 (0xCE)

EX_TXDONE

A data packet has been transmitted.

EX_RXWAIT

Received data bytes are waiting to be read.

EX_UNENCRYPT

Received packet was not encrypted. This can

only occur when SECOPT: EN_UNENC=1.

EX_SEQDEC

Received encrypted packet sequence number is

less than previous.

EX_SEQSKIP

Received encrypted sequence number is more

than one higher the previous sequence number.

EX_JOIN

The Join Process has been started, which can

result in register changes and write lockouts.

6 - 7

Reserved

EEXFLAG2 (0xCD)

0 - 7

Reserved

Figure 79: HumPRCTM Series Transceiver Extended Exception Codes

Flag EX_SEQSKIP is 1 when a received encrypted packet has a sequence

number that is more than one higher than the previously received packet.

Possible causes are an attempt to replay a previous message by an

attacker, receiving a message from a different transmitter or restarting the

transmitter.

MDEV-868-PRC Datasheet(PDF) 40 Page - Linx Technologies

MDEV-868-PRC Datasheet(HTML) 40 Page - Linx Technologies

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

Datasheet Download

Link URL