Keeloq Hopping Decoder

Keeloq Hopping Decoder

HCS512 KEELOQ® Code Hopping Decoder FEATURES DESCRIPTION Security The Microchip Technology Inc. HCS512 is a code hop- ping decoder designed for secure Remote Keyless • Secure storage of Manufacturer’s Code Entry (RKE) systems. The HCS512 utilizes the pat- • Secure storage of transmitter’s keys ented KEELOQ code hopping system and high security • Up to four transmitters can be learned learning mechanisms to make this a canned solution ® when used with the HCS encoders to implement a uni- •KEELOQ code hopping technology directional remote keyless entry system. • Normal and secure learning mechanisms PACKAGE TYPE Operating PDIP, SOIC • 4.0V – 6.0V operation • 4 MHz external RC oscillator LRNIN 1 18 RFIN • Learning indication on LRNOUT LRNOUT 2 17 NC • Auto baud rate detection • Power saving SLEEP mode NC 3 16 OSCIN Other MCLR 4 HCS512 15 OSCOUT GND 5 14 VDD • Stand-alone decoder • On-chip EEPROM for transmitter storage S0 6 13 DATA • Four binary function outputs–15 functions S1 7 12 CLK • 18-pin DIP/SOIC package S2 8 11 SLEEP Typical Applications S3 9 10 VLOW • Automotive remote entry systems • Automotive alarm systems • Automotive immobilizers BLOCK DIAGRAM • Gate and garage openers RFIN Reception Register • Electronic door locks • Identity tokens DECRYPTOR • Burglar alarm systems EEPROM CONTROL DATA CLK Compatible Encoders LRNIN All KEELOQ encoders and transponders configured for OSCIN OSCILLATOR MCLR the following setting: SLEEP • PWM modulation format (1/3-2/3) OUTPUT CONTROL •TE in the range from 100 μs to 400 μs S0 S1S2 S3 VLOW LRNOUT • 10 x TE Header • 28-bit Serial Number The Manufacturer’s Code, transmitter keys, and syn- • 16-bit Synchronization counter chronization information are stored in protected on- • Discrimination bits equal to Serial Number 8 LSbs chip EEPROM. The HCS512 uses the DATA and CLK • 66- to 69-bit length code word. inputs to load the Manufacturer’s Code which cannot be read out of the device. © 2011 Microchip Technology Inc. DS40151E-page 1 HCS512 The HCS512 operates over a wide voltage range of during normal operation to derive the crypt 3.0 volts to 6.0 volts. The decoder employs automatic key and decrypt the received code word’s baud rate detection which allows it to compensate for encrypted portion. wide variations in transmitter data rate. The decoder - Secure Learn contains sophisticated error checking algorithms to The transmitter is activated through a special ensure only valid codes are accepted. button combination to transmit a stored 60-bit seed value used to generate the transmitter’s 1.0 SYSTEM OVERVIEW crypt key. The receiver uses this seed value to derive the same crypt key and decrypt the Key Terms received code word’s encrypted portion. The following is a list of key terms used throughout this • Manufacturer’s code – A unique and secret 64- data sheet. For additional information on KEELOQ and bit number used to generate unique encoder crypt Code Hopping, refer to Technical Brief 3 (TB003). keys. Each encoder is programmed with a crypt key that is a function of the manufacturer’s code. • RKE - Remote Keyless Entry Each decoder is programmed with the manufac- • Button Status - Indicates what button input(s) turer code itself. activated the transmission. Encompasses the 4 button status bits S3, S2, S1 and S0 (Figure 8-2). 1.1 HCS Encoder Overview • Code Hopping - A method by which a code, viewed externally to the system, appears to The HCS encoders have a small EEPROM array which change unpredictably each time it is transmitted. must be loaded with several parameters before use. The most important of these values are: • Code word - A block of data that is repeatedly transmitted upon button activation (Figure 8-1). • A crypt key that is generated at the time of pro- • Transmission - A data stream consisting of duction repeating code words (Figure 8-1). • A 16-bit synchronization counter value • Crypt key - A unique and secret 64-bit number • A 28-bit serial number which is meant to be used to encrypt and decrypt data. In a symmetri- unique for every encoder cal block cipher such as the KEELOQ algorithm, The manufacturer programs the serial number for each the encryption and decryption keys are equal and encoder at the time of production, while the ‘Key Gen- will therefore be referred to generally as the crypt eration Algorithm’ generates the crypt key (Figure 1-1). key. Inputs to the key generation algorithm typically consist • Encoder - A device that generates and encodes of the encoder’s serial number and a 64-bit manufac- data. turer’s code, which the manufacturer creates. • Encryption Algorithm - A recipe whereby data is Note: The manufacturer code is a pivotal part of scrambled using a crypt key. The data can only be the system’s overall security. Conse- interpreted by the respective decryption algorithm quently, all possible precautions must be using the same crypt key. taken and maintained for this code. • Decoder - A device that decodes data received from an encoder. • Decryption algorithm - A recipe whereby data scrambled by an encryption algorithm can be unscrambled using the same crypt key. • Learn – Learning involves the receiver calculating the transmitter’s appropriate crypt key, decrypting the received hopping code and storing the serial number, synchronization counter value and crypt key in EEPROM. The KEELOQ product family facil- itates several learning strategies to be imple- mented on the decoder. The following are examples of what can be done. - Simple Learning The receiver uses a fixed crypt key, common to all components of all systems by the same manufacturer, to decrypt the received code word’s encrypted portion. - Normal Learning The receiver uses information transmitted DS40151E-page 2 © 2011 Microchip Technology Inc. HCS512 FIGURE 1-1: CREATION AND STORAGE OF CRYPT KEY DURING PRODUCTION Production HCS512 Programmer Transmitter Serial Number EEPROM Array Serial Number Crypt Key Sync Counter Key . Manufacturer’s Generation Crypt . Code Algorithm Key . The 16-bit synchronization counter is the basis behind A receiver may use any type of controller as a decoder, the transmitted code word changing for each transmis- but it is typically a microcontroller with compatible firm- sion; it increments each time a button is pressed. Due ware that allows the decoder to operate in conjunction to the code hopping algorithm’s complexity, each incre- with an HCS512 based transmitter. Section 5.0 ment of the synchronization value results in greater provides detail on integrating the HCS512 into a sys- than 50% of the bits changing in the transmitted code tem. word. A transmitter must first be ‘learned’ by the receiver Figure 1-2 shows how the key values in EEPROM are before its use is allowed in the system. Learning used in the encoder. Once the encoder detects a button includes calculating the transmitter’s appropriate crypt press, it reads the button inputs and updates the syn- key, decrypting the received hopping code and storing chronization counter. The synchronization counter and the serial number, synchronization counter value and crypt key are input to the encryption algorithm and the crypt key in EEPROM. output is 32 bits of encrypted information. This data will In normal operation, each received message of valid change with every button press, its value appearing format is evaluated. The serial number is used to deter- externally to ‘randomly hop around’, hence it is referred mine if it is from a learned transmitter. If from a learned to as the hopping portion of the code word. The 32-bit transmitter, the message is decrypted and the synchro- hopping code is combined with the button information nization counter is verified. Finally, the button status is and serial number to form the code word transmitted to checked to see what operation is requested. Figure 1-3 the receiver. The code word format is explained in shows the relationship between some of the values greater detail in Section 8.2. stored by the receiver and the values received from the transmitter. FIGURE 1-2: BUILDING THE TRANSMITTED CODE WORD (ENCODER) EEPROM Array ® KEELOQ Crypt Key Encryption Algorithm Sync Counter Serial Number Button Press 32 Bits Information Serial Number Encrypted Data Transmitted Information © 2011 Microchip Technology Inc. DS40151E-page 3 HCS512 FIGURE 1-3: BASIC OPERATION OF RECEIVER (DECODER) 1 Received Information EEPROM Array Button Press 32 Bits of Manufacturer Code Information Serial Number Encrypted Data Check for Serial Number 2 Match Sync Counter Crypt Key 3 KEELOQ® Decryption Algorithm Perform Function Decrypted Check for 5 Indicated by Synchronization 4 button press Counter Match NOTE: Circled numbers indicate the order of execution. 2.0 PIN ASSIGNMENT Decoder Buffer PIN I/O (1) Description Function Type(1) 1LRNIN I TTL Learn input - initiates learning, 10K pull-up required on input 2 LRNOUT O TTL Learn output - indicates learning 3 NC — TTL Do not connect 4MCLR I ST Master clear input 5 Ground P — Ground connection 6 S0 O TTL Switch 0 7 S1 O TTL Switch 1 8 S2 O TTL Switch 2 9 S3 O TTL Switch 3 10 VLOW O TTL Battery low indication output 11 SLEEP I TTL Connect to RFIN to allow wake-up from SLEEP 12 CLK I/O TTL/ST (2) Clock in Programming mode and Synchronous mode 13 DATA I/O TTL/ST (2) Data in Programming mode and Synchronous mode 14 VDD P — Power connection 15 OSCOUT (1MHZ) O TTL Oscillator out (test point) 16 OSCIN (4MHz) I ST Oscillator in – recommended values 4.7 kΩ and 22 pF 17 NC — — 18 RFIN I TTL RF input from receiver Note 1: P = power, I = in, O = out, and ST = Schmitt Trigger input. 2: Pin 12 and Pin 13 have a dual purpose.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    35 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us