Single-Edge Nibble Transmission (SENT) Module: Highlights
Single-Edge Nibble Transmission (SENT) Module: Highlights
HIGHLIGHTS
This section of the manual contains the following major topics:
SENTxCON1 SENTxSTAT
SENTxCON2 SENTxSYNC
SENTxCON3 SENTxDATH/L
SENTxTX
Output SENTx Edge
Driver Control
SENTxRX
Edge Sync Period Control and
Detect Detector Error Detection
Legend:
R = Readable bit W = Writable bit U = Unimplemented bit, read as ‘0’
-n = Value at POR ‘1’ = Bit is set ‘0’ = Bit is cleared x = Bit is unknown
Note 1: This bit is read-only in Receive mode and writable (settable and clearable) in Transmit mode.
Note 1: This bit is read-only in Receive mode and writable (settable and clearable) in Transmit mode.
Sync Period Status Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 CRC Pause (optional)
Pause Pulse
Message Frame
The Sync period starts the message frame, and is used for synchronization of TTICK between the
transmitter and receiver. When configured for Transmit mode, the module drives the line low for
5 Ticks and to a high-impedance state for 51 Ticks.
A four-bit status nibble follows the Sync pulse and may be used for device status, identification,
or alternatively, used as additional data. The status nibble is formatted the same as a data nibble.
After the status nibble is one or more (up to six) data nibbles. These are 4 bits in length and are
encoded as the data value plus 12 Ticks. This yields a minimum value of 12 Ticks for 0h and a
maximum value of 27 Ticks for Fh. When configured for Transmit mode, the module drives the
line low for 5 Ticks and into a high-impedance state for the remaining 7 to 22 Ticks.
The CRC data nibble follows the data payload. This is a 4-bit CRC of the six data nibbles only.
The CRC is calculated using a polynomial of, x4 + x3 + x2 + 1, with a seed value of ‘0101’. It is
then padded with ‘0’ to help detect shift errors. The CRC nibble is formatted the same as a data
nibble.
Since the data values are encoded in the time between falling edges, the SENT protocol may
produce a variable length message. In some applications, the Pause Pulse period is used to pad
the message length so that messages will always be received at a constant time interval. The
module provides support to automatically calculate the Pause duration needed for periodic trans-
missions. When configured for Transmit mode, the module drives the line low for 5 Ticks and into
a high-impedance state for the remaining Pause time.
Note: A SENT message frame will always have a status and CRC nibble. The shortest
message frame with one data nibble (SENTxCON1<2:0> = 001) will have a length
of one Sync and three nibbles.
SENTxCON1 SENTxSTAT
SENTxCON2 SENTxSYNC
SENTxCON3 SENTxDATH/L
SENTxTX
SENTx Edge Output
Control Driver
Sync (56 Ticks) Status Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 CRC Sync (56 Ticks)
SNTEN
5 Ticks
SENTxIF
NIB<2:0> 000 000 001 010 011 100 101 110 111 000
SYNCTXEN
Pause Sync (56 Ticks) Status Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 CRC Pause Sync (56 Ticks)
(12-768 Ticks)
SENTxIF
NIB<2:0> 000 000 001 010 011 100 101 110 111 000
PAUSE
Sync (56 Ticks) Status Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 CRC
SNTEN
5 Ticks Low
NIB<2:0> 000 000 001 010 011 100 101 110 111 000
SYNCTXEN
SENTxCON1 SENTxSTAT
SENTxCON SENTxSYNC
SENTxCON3 SENTxDATH/L
SENTxRX
Edge Sync Period Control and
Detect Detector Error Detection
Where:
FRCV = FCY/Prescaler
Note: The SENT protocol allows no more than 1.5625% (1 part in 64) timing variation
between successive messages. To verify this condition is met, save the value
captured in SENTxSYNC after each data frame is received, then compare it to the
value received during the next data frame.
Line Idle Sync (56 Ticks) Status Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 CRC Pause Sync (56 Ticks)
(12-768 Ticks)
SENT Data In
SENTxIF
NIB<2:0> 000 000 001 010 011 100 101 110 111 000
PAUSE
SYNC
IDLE
Note: The receiver is in the Idle state when the SENT data line has been high for more
than the maximum time allowed for a Sync period (SYNCMAXx bits register value).
Table 9-1: Special Function Registers Associated with the SENT Module
All
File Name Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Resets
SENTxCON1 SNTEN — SNTSIDL — RCVEN TXM TXPOL CRCEN PPP SPCEN — PS — NIBCNT2 NIBCNT1 NIBCNT0 0006
SENTxCON2 TICKTIME<15:0> (Transmit modes) or SYNCMAX<15:0> (Receive mode) FFFF
SENTxCON3 FRAMETIME<15:0> (Transmit modes) or SYNCMIN<15:0> (Receive mode) FFFF
SENTxSTAT — — — — — — — — PAUSE NIB2 NIB1 NIB0 CRCERR FRMERR RXIDLE SYNCTXEN 0000
SENTxSYNC Synchronization Time Period (Transmit modes) 0000
SENTxDATH Status Nibble Data Nibble 1 Data Nibble 2 Data Nibble 3 0000
SENTxDATL Data Nibble 4 Data Nibble 5 Data Nibble 6 CRC Data Nibble 0000
Legend: — = unimplemented, read as ‘0’. Reset values are shown in hexadecimal.
2013-2014 Microchip Technology Inc.
SENT Module
10.0 RELATED APPLICATION NOTES
This section lists application notes that are related to this section of the manual. These
application notes may not be written specifically for 16-bit devices, but the concepts are pertinent
and could be used with modification and possible limitations. The current application notes
related to the SENT module are:
Note: Please visit the Microchip web site (www.microchip.com) for additional application
notes and code examples for the dsPIC33/PIC24F family of devices.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
QUALITY MANAGEMENT SYSTEM Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
CERTIFIED BY DNV Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
== ISO/TS 16949 ==
are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.