ATAK51004-V2 User's Guide - Microchip...

ATAK51004-V2 ATAK51004-V2 User's Guide

Features

Full Car Access System Capability Multichannel RF Remote Keyless Entry (RKE) LF Passive Entry/Passive Start (PEPS) Vehicle Immobilization (IMM)

Open System Software: PEPS protocol with a high-precision 3D localization using AES-128 RKE RF rolling code using AES-128 AOIP ( open immobilizer protocol) immobilizer stack using AES-128 Scalable and configurable PC graphical user interface (GUI) for system visualization and viewing data communication

Body Computer Emulation Using ATmega2560 On the Main ATAB0001A CARS Interface Board

Kit Contents

Vehicle-Side PCBs: 1x ATAB0001A CARS interface board 1x ATAB5291B 6-channel LF coil driver PCB with built-in immobilizer base station

(ATA5291) 1x ATAB0003A RF receiver application board (ATA5782)

Fob and Transponder: 1x ATAB5702A RF transmitter with 3D LF PEPS and 3D LF immobilizer transponder

application board (ATA5702)

Other Accessories: 1x UHF SMA whip Antenna 1x ATAB-LFTX LCR PEPS antenna board (can be configured for pure L needed for

Immobilizer) 1x USB cable 1x 120/240VAC to 12VDC wall transformer Quick start user guide

Note: CR2032 lithium batteries required for the fob operation are not supplied in the kit.

2017 Microchip Technology Inc. User Guide DS50002644A-page 1

Table of Contents

Features.......................................................................................................................... 1

Kit Contents.....................................................................................................................1

1. Introduction................................................................................................................31.1. Immobilizer Support..................................................................................................................... 31.2. RKE Support................................................................................................................................ 41.3. PEPS Support.............................................................................................................................. 4

2. Kit System Setup....................................................................................................... 52.1. Hardware......................................................................................................................................52.2. PC Application Software...............................................................................................................7

3. System Operation.................................................................................................... 113.1. Immobilizer Operation................................................................................................................ 113.2. Remote Keyless Entry (RKE) Operation.................................................................................... 123.3. PEPS Operation.........................................................................................................................14

4. Programming Instructions........................................................................................314.1. Programming the ATmega2560 on ATAB0001A Interface Board...............................................314.2. Programming the ATA5702 on the ATAB5702A PEPS Fob Board.............................................334.3. Programming the ATA5782 on the ATAB0003A RF Receiver Board......................................... 35

5. Installing Virtual COM Port...................................................................................... 385.1. USB Driver Setup for Windows 7............................................................................................... 38

6. Errata (Version3_Rev3 Software Version)...............................................................43

7. Revision History.......................................................................................................44

8. Object of Declaration............................................................................................... 45

The Microchip Web Site................................................................................................ 46

Customer Change Notification Service..........................................................................46

Customer Support......................................................................................................... 46

Microchip Devices Code Protection Feature................................................................. 46

Legal Notice...................................................................................................................47

Trademarks................................................................................................................... 47

Quality Management System Certified by DNV.............................................................48

Worldwide Sales and Service........................................................................................49

ATAK51004-V2


1. IntroductionThis document provides set up and usage instructions for the Car Access Reference System (CARS)featuring remote keyless entry, passive entry/passive start, and vehicle immobilization functionality basedon the Microchip Technology Inc. GEN2 communication protocols. It offers a complete car access systemallowing the comprehensive family of car access products offered by Microchip Technology Inc. to beevaluated.

The reference designs utilized are both scalable and configurable, through either the PC application orsource code modifications, enabling adaptation of the basic hardware and software building blocks tomeet the most recent requirements for specialized systems.

Figure 1-1.System Block Diagram

1.1 Immobilizer SupportThe immobilizer is considered the system foundation because it must always work, even if the fob batteryis dead, and secures a vehicle against unauthorized engine starts. It consists of a base station placed inthe vehicle, which provides the LF (125 kHz) magnetic field enabling a wireless link with the transponderin the fob to be established. This LF immobilizer link is used to exchange power supply and digital databetween the vehicle and the passive transponder.

The implemented immobilizer system supports Microchip Technology Inc. Open Immobilizer Protocol(AOIP), which consists of an open/unlicensed protocol stack based on AES-128 encryption. First, theReadUID command is sent to the fob. The fob has to decode the ReadUID command and respond withits UID value. If the received UID value is correct (matches the stored UID), the start authenticationcommand is issued and challenge data is sent to the fob based on the authentication type (unilateral orbilateral). The fob receives the challenge, performs the encryption and sends a ciphered response back.This response is received by the base station and verified to complete the authentication process. Pleaserequest ATAN0088 documentation for more information about the AOIP protocol.

ATAK51004-V2


1.2 RKE SupportRemote Keyless Entry (RKE) functionality provides the means to lock/ unlock and even start the vehiclefrom a long distance with a fob carried by the user. The system consists of an RF receiver in the vehicleand an RF transmitter in the fob. Unlike Immobilizer operation, RKE operation requires a battery (CR2032or equivalent) be inserted in the fob.

The implemented RKE system supports Microchip messaging protocol (AVR411), which consists of aunidirectional UHF link that is secured based on an AES-128 rolling code algorithm. The messagecontains information that is used to verify the identity, authenticity of the user, and the intended action(command code). For more information about the RKE protocol, reference the Microchip AVR411application note found at www.microchip.com.

1.3 PEPS SupportAlso included in the kit is Passive Entry/Passive Start (PEPS) functionality, which provides a user theadded convenience of being able to lock/unlock and start a vehicle just by having the electronic fob withthem without the need to actively interact with it. It consists of a LF driver placed in the vehicle, whichgenerates a strong magnetic field on multiple (optional) LF PEPS antennas.

The passive fob implemented in the PEPS system is capable of waking up on this LF field and receivingthe incoming data via the unidirectional LF link. The fob also measures the strength of the magnetic fieldwhich is used to determine the position of the fob relative to the vehicle (outside or inside). It thenencrypts the received challenge data (using AES) and returns the correct cipher response, together withthe positioning information, to the vehicle via the unidirectional UHF link. See ATAN0073 documentationfor more information about the PEPS protocol.

ATAK51004-V2


http://www.microchip.com/

2. Kit System Setup

2.1 HardwareATAK51004-V2 kit hardware needs to be assembled before initial use. Follow the steps below toassemble the LF PCB, the RF receiver PCB and ATAB0001A interface board:

1. Remove the ATAB0001A interface board from the packaging and verify the jumper J13 on theATAB0001A interface board is set to position LF_DR - +12V as noted in Figure 2-1.

2. Insert the ATAB5291B LF driver/immobilizer base station in the LF_X1 and LF_X2 sockets on theATAB0001A interface board as shown in Figure 2-1.

3. Connect the LF antenna module:3.1. Connect the ATAB-LFTX LCR PEPS antenna module to J1 connector on ATAB5291B PCB.

3.2. Ensure the J1 jumper on the antenna module is set to the inductor ONLY ( )option.Note: For use of the antenna on the J2 J8 connectors, ensure the jumper on theantenna module is set to LCR.

4. Insert the ATAB0003A RF receiver adapter board in the UHF_X1 and UHF_X2 sockets on theATAB0001A interface board.

5. Connect the RF antenna to the ATAB0003A RF receiver adapter board at the X4 SMA connector.6. Connect 12VDC power supply to the J11 power socket on the ATAB5291B board.

Note: J11 powers the ATAB0001A interface board and ATAB0003A RF Receiver Adapter Board.Do not connect a power supply to J14 power socket on the ATAB0001A board.

All the hardware PCB modules come with the correct preprogrammed software configuration. Once thekit is assembled and the power connected, the correct power-up status of the kit is indicated by the LED0- LED7 LEDs immediately blinking.

ATAK51004-V2


Figure 2-1.CARS Hardware Connections

LF PEPS Antenna (ATAB-LFTX-

V4.0)

RF Antenna

ATAB0003A (RF PCB)

J1 set to inductor

only

ATmega2560 JTAG Header

ATmega2560 ISP Header

32UC3B1256 JTAG Header

USB Connector

Place jumper in LF_DR

+12V position on J13 header

ATAB5291B(LF PCB)

ATAK51004-V2


Figure 2-2.ATAK51004-V2 Complete Assembly

2.2 PC Application SoftwareThe system software consists of a PC GUI interface, which runs on a host PC and communicates with theATAB0001A interface board via the virtual COM port. The USB cable is connected to the PC and mini-USB port on the ATAB0001A interface board. There must be a USB driver (Windows 7 and later) installedto support a virtual COM port via a USB connection (see Section 5. Installing Virtual COM Port). TheUSB virtual COM port firmware is on the AT32UC3B1256 located on the ATAB0001A interface board.This firmware is preprogrammed and does not need to be updated.

1. Locate and execute the CARS_PC_Application.exe file on your host PC.2. Configure the COM settings:

2.1. Use the pull-down menu (COM>PORTs) to configure the COM port (see Section 5.Installing Virtual COM Port below in order to determine the COM port used).

2.2. Use the pull-down menu (COM>BAUD Rate) to configure the baud rate to 57600 as shownin Figure 2-3.

ATAK51004-V2


Figure 2-3.COM Port and Baud Rate Selection

Note: Use the pull-down menu (Help>About) to display the GUI Software revision.3. Open the virtual COM port (click on the COMxx: text in the bottom right hand side of the window).4. Use the pull-down menu (View>System Config) to open the System Configuration window as

shown in Figure 2-4.

ATAK51004-V2


Figure 2-4. System Configuration Window

Fobs UID is displayed when one is learned. If not, follow the learning

procedure (Step 6).

Click here to load the System

Software Version (Step 5).

5. Click on the clockwise arrow button to update the system firmware version and other variables. Thesystem software version loads correctly, as shown above, if the connection is valid (COM port isopen).

6. The actual UID of the fob must be learned by the base station and the secret keys must betransferred to the fob in order for the system to function properly.Note: The fob included with the kit comes pre-learned and its UID will be displayed underLearned Fobs section of the System Configuration window, as shown in Figure 2-4. If not, thenproceed with the following.

6.1. Place the fob in close proximity (

also displayed in the Learned Fobs section of the System Configuration window, as shownin Figure 2-4.Note: If the fob is unsuccessful in being learned, repeat step 6.2 a couple of times. If stillunsuccessful, try moving the fob position slightly on the coil and repeat step 6.2.

Note: Once the system has learned the fob, its UID value is stored in the ATmega2560EEPROM. Do not press the SW3 (Clear) push button switch on the ATAB0001A interfaceboard. Doing so erases all stored UID values. Without this stored value, the system cannotauthenticate the fob.

ATAK51004-V2


3. System OperationThe system includes the following features:

Immobilizer functionality: Supports AOIP Support for AES-128 encryption Passive fob authentication supporting unidirectional authentication (UA) Support for base station to transponder key learn sequence used during the pairing process Support for several utility immobilizer commands (such as communication or transponder

data management) RKE functionality:

Support for unidirectional AES-based rolling code protocol Use of multi-channel UHF messaging provides robustness against the effects of multipath or

in-band interference PEPS wake-up functions:

Selectable LF driver coil Selectable LF driver current (ICOIL = 50 mA to 1000 mA) LF driver polling support Configurable preamble and header settings for LF wake-up via source code updates Unidirectional UHF data return channel included

3.1 Immobilizer OperationThe immobilizer functionality is tested using the base station hardware (ATAB0001A/ATAB5291B) and thefob PCB. The UID, challenge, response and the result of this authentication are displayed in theimmobilizer status window of the PC application each time the authentication command is executed.

The immobilizer can be tested using the PC GUI running on the host PC as follows:

1. If not done so already, follow procedure detailed in Section 2.2 PC Application Software .2. Use the pull down menu (View>Immobilizer) to open the Immobilizer Status window as shown in

Figure 31.Figure 3-1. Immobilizer Status Window

The immobilizer status window contains the following data fields, see Figure 31: Immobilizer UID: Displays unique ID value received from the fob Immobilizer Challenge: Displays the most current challenge data sent to the fob Immobilizer Response: Displays the most current response data received from the fob Immobilizer Result: Displays the authentication status

ATAK51004-V2


3. Place the fob across the LF antenna module within a short distance (

3.2.2 Normal RKE OperationRKE functionality can be observed using the PC application or the visual LED feedback from theATAB0001A.

ATAB5702A-V2.3

All three buttons provide RKE command messages. Each button also has two types of press action.There are short button press and long button press events, with each type handled differently. Thefollowing table shows how these are currently configured. In all cases, the LED corresponding to thelearned memory position (LED0 LED3) blinks several times before staying continuously ON.

Table 3-1.ATAB5702A Push Buttons Functionality

S1 S2 S3

Short Press Lock Unlock Driver Door Open Trunk

Long Press Remote Start Unlock All Doors Close Trunk

All button presses, except a long press of S1, transmit using FSK modulation at 9.6 kBd. To carry out along-range remote start, a long press of S1 changes to ASK modulation at 1 kBd. This is due to the factthat as the transmitted data-rate decreases, the sensitivity of the receiver increases thus improving thelink budget of the system therefore increasing the range. The transmitting and receiving devices areseamlessly changed, demonstrating their power and flexibility.

In order to provide high-quality performance even in the presence of noise, three RKE messages are sentsequentially on three different UHF channels, referred to as Time and Frequency Domain Redundancy.This makes it more probable that at least one of the messages is received successfully.

For additional information on the RF protocol, see the AVR411 application note, and for other informationon time and frequency domain redundancy, see the ATAN0014 application note, found on http://www.microchip.com/

3.2.3 Using the RKE System with the GUIOnce one or more fobs are paired with the system, the RKE can be tested using the PC GUI running onthe host PC as follows:

1. If not done so already, follow procedure detailed in Section 2.2 PC Application Software.2. Use the pull-down menu (View> RKE Messaging) to open the RKE Message Status window as

shown in Figure 32.Figure 3-2. RKE Message Status Window

ATAK51004-V2


http://www.microchip.com/http://www.microchip.com/

The RKE status window contains the following data fields, see Figure 32: RF message S/N: Contains the UID returned by the fob. The same UID value for a given fob

is shown in the learned fobs section of the system configuration window. RF message counter: Displays the rolling code message counter value sent to the vehicle.

This value is incremented for every key push. All commands (e.g., lock and unlock) incrementthe counter value. The counter is checked against a window of valid counts on the vehicleside to prevent recording and replaying of past RKE messages from being accepted as valid,which is commonly referred to as Replay Attack.

RF message command: Decodes the most recent command received from the fob. RF message MAC: Displays the received 4-byte (32-bit) MAC. RF message result: Displays the result of the comparison between the expected MAC

(computed using AES-128) and the received MAC. RF channel: Displays which RF channel the message was received. RF RSSI: The signal strength at the UHF receiver is measured and displayed in three

formats. There is a decimal representation read directly from the UHF device followed by acalculated dBm value. Finally, there is a bar graph that provides visual representation.

3. Press any of the RKE buttons discussed in Section 3.2.2 Normal RKE Operation to send the RKEmessage.

3.3 PEPS OperationThe PEPS functionality is tested using the base station hardware (ATAB0001A/ATAB0003A/ ATAB5291B)and the fob PCB. The PEPS operation is configured (by the GUI) to send LF wake-up messages to thefob which then the fob responds with information via the RF channel.

3.3.1 System Configuration Window OverviewThe System Configuration window displays specific software information, reports the status of the learnedfobs, selects the PEPS authentication method and selects a PEPS fob to perform testing. It also is usedfor setting calibration values and provides an interface to read/write user data in each selected fob.

Use the pull-down menu (View>System Config) to open the System Configuration window as shown in Figure 3-3.

ATAK51004-V2


Figure 3-3.System Configuration Window

The System Configuration window contains the following sections and associated data fields, see Figure3-3:

The LF Antennas section includes controls used to select the antenna channel and the current andassociated vehicle ID.

Antenna channel: Selects which antenna channel is used to send the LF message from thevehicle. The antenna module must be connected to the corresponding port on the ATAB5291Bboard for this to function properly.Note: When antenna channel 1 is used, ensure the J1 jumper on the antenna module is set to theinductor ONLY ( ) option. When channels 2 through 6 are used, ensure the J1jumper on the antenna module is set to the LCR option.

Antenna current: Determines the amount of current flowing in the LF antenna during the LFmessage. This is directly related to the field strength at a given distance from the antenna.Therefore, any change to this value has a direct impact on the performance of the localizationduring PEPS.

Vehicle ID: Sets the wake-up value transmitted with the LF message. Only fobs that are lookingfor this value will wake up and respond. The vehicle ID is set in the fob during immobilizer learnmode and is user definable.

The learned fobs section lists up to four individual fob IDs paired with the system and saved in memory.

Learn button: Used to perform the initial pairing of any new fobs to the system using theImmobilizer LF field provided by the base station coil. See Section 2.2 PC Application Softwarestep 6 for details on the LF learn mode.

Clear button: Erases all the saved fob secret keys and configuration data from the system memory.Note: The system will no longer have full functionality until a fob is paired.

PEPS features section includes configuration settings, which affect PEPS messaging functions, includingthe type of authentication during polling as well as a polling interval.

ATAK51004-V2


Authentication radio buttons: Two possible authentication types are available. Selecting these hasan effect on the type of communication used during polling only.Note: If RKE learn (See Section 3.2.1 RF Learn Mode) was used then PEPS BA will not work forthat particular fob.

Polling options: Range checking and the determination of a desired threshold performance caneasily be done with polling. The checkbox starts the polling cycle, which repeats at a rate set inmilliseconds.

In/out threshold: Used to determine if a fob is inside or outside the vehicle by comparing thedistance scale result against the in/out threshold value. The boundary can be specified by manuallyentering a new value or by pressing the SW2 (RSSI) pushbutton switch on the ATAB0001Ainterface board.

Priority fob: Allows users to specify which fob is given priority when responding to a PEPScommand following the common slot of the anticollision process.

PEPS Fob Actions section allows selection and communication with an individual fob even with otherPEPS fobs present.

Selected fob: Allows direct access to an individual fob. Selecting Broadcast allowscommunication with any fob, even unlearned ones. This facilitates accessing a fob ID even if thevehicle ID for that specific fob is unknown.

Fob ID button: Provides a way to access the current fob ID, the vehicle ID, and battery status. S/W Ver button: Requests the current fob software version. Low Bat checkbox: Checked if the battery voltage in the current fob is below the low battery

threshold (approximately 2.6V). Fob Vehicle ID: The vehicle ID stored within the current fob. LF test tab: Used to display all the details relating to a test LF field measurement. Details such as

the external, internal RSSI values, and coil phase clock counts are displayed here. The distancescale value is determined by the combined result of all post-RSSI processing. In a standard PEPSmessage, the distance scale and the coil phase values are sent.Note: Three copies of each user memory block are stored in the fob. The fob compares thesecopies to ensure user memory has not been corrupted.

Parameter access tab: This is used to display general user memory sections of the fob EEPROMthat can be accessed via the PEPS system link. These are configured into 32 blocks of memorywith each block having 16 bytes of data available. The data can be displayed in HEX or ASCIIformat. To access the memory, the fob must first be put into a password-protected diagnostic modeby clicking the Enter Diag button. Then for several seconds the fob responds to read or writecommands.

Calibrate Fob button: This initiates a calibration cycle, which provides reference values since eachfob LF antenna coil axis has slightly different gains due to the antenna coil, capacitor, and ICtolerances. This is typically done at the end-of-line testing by the manufacturer, but is necessary toachieve consistent results. It only needs to be performed once for each fob.

3.3.2 PEPS Message Status Window OverviewThe System Configuration window displays the challenge/response information along with localizationdetails for each fob that is learned to the system.

Use the pull-down menu (View>PEPS Messaging) to open the PEPS Message Status window as shownin Figure 3-4.

ATAK51004-V2


Figure 3-4.PEPS Message Status Window

The PEPS Message Status window contains the following data fields, as seen in Figure 3-4:

Serial number: Displays the received fob ID. This should correspond to the value in the LearnedFobs section of the System Configuration window.

LF challenge: Displays the 4-byte LF challenge data, which was sent to the fob. This challengedata is sent during bilateral and unilateral authentication.

LF-encrypted challenge: Displays the 4-byte LF-encrypted data sent to the fob during bilateralauthentication only.

RF MAC: Displays the received RF MAC (message authentication code) value from the fob. Localization: Displays the current localization status of the current fob (e.g., inside or outside the

vehicle). This is determined by comparing the distance scale value against the In/Out Thresholdvalue displayed in the system configuration window.Note: Each fob section is highlighted in blue if the fob is found inside and pink if the fob is foundoutside. This allows easy determination from a distance while the range of the system is beingtested. The fob section will be highlighted in gray and the Distance Scale box will be highlighted inred when a LF measurement error occurs within the ATA5702.

Distance scale: Indicates the RSSI scale value received. Coil Phase Signature: Displays a three-digit binary code, where:

Bit Position Calculation using coilphase clock countvalues

Bit value if 90 < Calc.Result < 270

Otherwise

1 "Z Y" value"360" value x 360 1 02 "Z X" value"360" value x 360 1 03 "Y X" value"360" value X 360 1 0

ATAK51004-V2


Note: The Z-Y, Z-X, Y-X and 360 coil phase clock count values are found in the PEPS Fob Actionssection of the System Configuration window.

Battery low checkbox: Checked if the battery voltage in the current fob is below the low batterythreshold (approximately 2.6V).

Log file checkbox: Used to create a new record line in a comma separated variable (CSV)document for each received message when it is selected.

3.3.3 Identifying Fobs in RangeThe available fobs can be identified by sending out a broadcast, which returns the Fob# in the selectedfob field. To identify available fobs within the LF range:

1. If not done so already, follow the procedure detailed in Section 2.2 PC Application Software.Figure 3-5. Identifying Fobs in Range Test

2. Select Broadcast from the selected fob drop-down list within the PEPS fob actions section of theSystem Configuration window as shown in Figure 3-5.

3. Click the Fob ID button to send the broadcast request as shown in Figure 3-5. The available fobsrespond with their fob ID and their Fob# assignment. The associated vehicle ID is returned anddisplayed in the Fob Vehicle ID field.

4. Click the S/W Ver button as shown in Figure 3-5 to send the software version request to the fob.The software version number is returned and displayed in the S/W Ver field.Note: To use the broadcast function, only one fob should be in range and it must have a batteryinserted in the battery socket.

ATAK51004-V2


Note: Fobs in range, which are not paired with the current system, and fobs, which have adifferent vehicle ID, can also be identified as in range. If the located fob is paired with the system,the selected fob index changes to the location in the system to which the fob is believed to bestored. The fob ID should be verified by checking it against the list of learned fobs.

3.3.4 Fob Calibration OverviewIn a PEPS system, the learned fobs receive the LF signal and measure the magnetic field strength as areceive signal strength indicator (RSSI) value. This value is reported to the vehicle and is used todetermine the fobs position with respect to the transmitting LF antenna. To ensure RSSI accuracy, thefobs must be calibrated, including normalization and compensation, along all three LF antenna coil axes(X, Y and Z-axis). Typically, this calibration is performed during the final test using high precisionequipment at the fobs manufacturing facility. However, with the help of the GUI, the end-of-line calibrationsequence can be approximated by clicking the Calibrate Fob button in the system configuration window.

The normalization procedure is used to establish a relationship between a known magnetic flux densityand a measured RSSI value. Ideally, a Helmholtz coil would be used to perform this task but consideringthe constraints of the kit, this is not feasible. Instead, the RSSI value for each fob LF antenna coil (X, Yand Z) axis is measured at a fixed distance (e.g., 50cm) from the transmitting LF antenna. Arbitrarilyusing x-axis as the reference, the difference in measurements of the other two axes are stored inEEPROM as the Normalization Constants.

On the other hand, the compensation procedure accounts for any non-ideal influences (e.g., magneticflux disturbances due to adjacent ferrous bodies, temperature, and/or aging effects) and is based on thefollowing:

1. Measuring the internal RSSI values at reference conditions (end-of-line) denoted as Ref. RSSIwithin the PEPS Fob Actions section of the System Configuration window.

2. Measuring the current internal RSSI, (no external LF signal present) denoted as Int. RSSI withinthe PEPS Fob Actions section of the System Configuration window.

3. Measuring the current external RSSI, (external LF signal present) denoted as Ext. RSSI within thePEPS Fob Actions section of the System Configuration window.

The actual RSSI amplitude is then calculated by adding the error term [(1) - (2)] to the values measuredat (3). Using both of these procedures ensures that a constant RSSI is reported, regardless of the foborientation, and ensures accuracy over a large set of influences.

3.3.5 Fob Calibration ProcessThe calibration cycle must be performed for each fob separately. The following steps are used to performthe Calibration Fob cycle:

1. If not done so already, follow procedure detailed in Section 2.2 PC Application Software.

ATAK51004-V2


Figure 3-6.Fob Calibration

2. Select the fob to be calibrated in the Selected Fob field within the PEPS Fob Actions section ofthe System Configuration window as shown in Figure 3-6.

3. Click the Fob ID button.4. Click the Calibrate Fob button as shown in Figure 3-6.5. Click the Next button within the Fob EOL Configuration window, as shown in Figure 3-7.

ATAK51004-V2


Figure 3-7.Fob EOL Configuration Window

6. Position the LF antenna module and the fob (as shown in the Fob EOL Configuration window) toalign the X-axis of the fob with the LF antenna module axis, and click the Measure button. Thismeasures the current X-axis RSSI signal amplitude and updates the result to the Peak RSSI fieldfor the X-axis. Click the Measure button several times to ensure the peak value is stable.

7. Click the Next button.8. Position the fob, as shown, to align the Y-axis and click the Measure button. This measures the

current Y-axis signal amplitude and updates the result to the Peak RSSI field for the Y-axis. Clickthe Measure button several times to ensure the peak value is stable.

9. Click the Next button.10. Position the fob, as shown, to align the Z-axis and click the Measure button. This measures the

current Y-axis signal amplitude and updates the result to the Peak RSSI field for the Y-axis. Clickthe Measure button several times to ensure the peak value is stable.

ATAK51004-V2


11. Click the Next button.12. Click the Measure button to have the fob perform an internal RSSI measurement and display the

results in the Measured Int. RSSI field. This measurement is performed by an internal currentsource, which drives each of the fobs 3-axis LF antenna coil circuits.

13. Selecting the Update EEPROM checkbox updates the RSSI values currently stored in EEPROMwith the newly measured values after the Next button is clicked.Note: This is recommended when the Measured Int. RSSI field is significantly different from theEEPROM Int. RSSI field, which can occur when the fobs components age over time or if achange in the circuit has occurred (e.g., evaluating different 3D coil). Otherwise, leave the NoChange checkbox selected.

14. Click the Next button.15. Click the Configure button to store the compensation constants into the fob EEPROM. Be aware

that it will take a few seconds to complete this action, and you must wait until the lights stop blinkingon the ATAB0001A interface board before you can close the Fob EOL Configuration window.

16. To check, click the LF Test button in the System Configuration window, as shown in Figure 3-6, torequest the RSSI values and display them in the respective fields within the PEPS Fob Actionsection of the System Configuration window.

3.3.5.1 PEPS Wake-Up FunctionalityThe PEPS wake-up functionality can be tested using the PC GUI running on the host PC as follows:

1. If not done so already, follow procedure detailed in Section 2.2 PC Application Software.2. If not done so already, perform the fob calibration (see Section 3.3.5 Fob Calibration Process).

ATAK51004-V2


Figure 3-8.PEPS Wake-Up Functionality Test

3. Select the desired LF antenna channel from which to send the LF message as shown in Figure 3-8.Note: When antenna channel 1 is used, ensure the J1 jumper on the antenna module is set to theinductor ONLY ( ) option. When channels 2 through 6 are used, ensure the J1jumper on the antenna module is set to the LCR option.

4. Select the desired LF antenna current.5. Enter the polling interval value in milliseconds (e.g., 1000, meaning the LF wake-up signal is

transmitted every one second) as shown in Figure 3-8.Note: 500 ms is the smallest allowable interval.

6. Select the Polling checkbox to enable polling and confirm the LEDs on the fob blinks each time thenew wake-up signal is received.Note: If RKE learn (See Section 3.2.1 "RF Learn Mode") was used then Bilateral Authenticationwill not work for that particular fob.

7. Type in a new vehicle ID (e.g., 887766) as shown in Figure 3-7, click on any other field within thewindow, and confirm that the LEDs on the fob no longer blink. This demonstrates that the fob willonly wake up for the vehicle to which it was paired.

8. Type in the original vehicle ID: 667788.9. Deselect the Polling checkbox to disable polling.

3.3.6 PEPS CommunicationThe PEPS communication functionality can be tested using the PC GUI running on the host PC asfollows:

ATAK51004-V2


1. If not done so already, follow procedure detailed in Section 2.2 PC Application Software.2. If not done so already, perform the fob calibration (see Section 3.3.5 Fob Calibration Process).3. If not done so already, use the pull-down menu (View>PEPS Messaging) to open the PEPS

Message Status window as shown in Figure 3-4.4. Position the fob at an arbitrary distance from the LF antenna module.5. Press the SW2 (RSSI) push button switch on the ATAB0001A interface board to set the in/out

threshold field, within the PEPS features section of the System Configuration window, based on thefobs current location.

Note: Successful update of the in/out threshold is, also, indicated by a steady illumination of LED7(PEPS) and a momentary blink of LED5 (Learn) on the ATAB0001A interface board.

6. Move the fob closer to the LF antenna module.7. Click the PEPS UA button within the PEPS Message Status window to execute the unilateral

authentication sequence.Note: The LF Encrypted Challenge' field is not populated since this data is not transmitted to thefob.

Example: The results of a PEPS unilateral authentication sequence are shown in Figure 3-9. Withthe in/out threshold = 321.3 and the measured value distance scale = 399.5, the fob is identified asinside the vehicle and highlighted in blue due to the distance scale value being greater than thethreshold value.

ATAK51004-V2


Figure 3-9.PEPS Unilateral Authentication with Inside Localization

8. Move the fob further away from the LF antenna module, beyond the location used in step 4, but stillwithin PEPS operating range.

9. Click the PEPS BA button within the PEPS Message Status window to execute the bilateralauthentication sequence. Confirm that the LF Encrypted Challenge' field is now populated.Note: If RKE learn (See section 3.2.1 "RF Learn Mode") was used then PEPS BA will not work forthat particular fob.

Example: The results of a PEPS bilateral authentication sequence are shown in Figure 3-10. Withthe in/out threshold = 321.3 and the measured value distance scale = 298.1, the fob is identified asoutside the vehicle and highlighted in pink due to the distance scale value being less than thethreshold value.

ATAK51004-V2


Figure 3-10.PEPS Bilateral Authentication with Outside Localization

Note:1. The PEPS UA and PEPS BA buttons can be used for either inside or outside localization.2. Each time the PEPS UA or PEPS BA button is clicked, a new PEPS wake-up signal is generated.

Once the fob receives the wake-up signal, the LED on the fob blinks and the PEPS MessageStatus window information is updated.

3. A continuous polling sequence can be achieved by selecting the Polling checkbox in the PEPSfeatures section of the System Configuration window. This polling feature can be used todynamically determine the PEPS fob area coverage in real-time with the PEPS results being shownin the PEPS Message Status window.

3.3.7 PEPS Normal OperationThe PEPS sequence typically begins with the vehicle in a LOCKED state. If necessary, press the RKElock button to ensure that the system is in the LOCKED state. To achieve best results, it may benecessary to adjust the in/out boundary (see Section 3.3.7 "PEPS Communication").

ATAK51004-V2


3.3.7.1 PEPS UnlockA PEPS vehicle typically has sensors or buttons in the door-handles, which trigger the PEPS system tounlock the door once the handle is pulled. This is demonstrated by placing the fob beyond the in/outthreshold boundary and pressing the SW7 (Unlock) push button switch on the ATAB0001A interfaceboard. Even if multiple fobs are present, the system uses the first received response as the basis for allactions.

The PEPS unlock action is indicated by a quick blink of LED7 (PEPS) followed by a steady illumination, aquick blink of LED4 (In/out) followed by a steady illumination (indicating that the fob location is outsidethe vehicle), and the fob index used (LED0 LED3) being illuminated on the ATAB0001A interface board.The fob index LED also indicates that AES authentication has been successfully completed.

The PC GUI shows the trigger location; the location of the key fob (outside or inside) and the status of theaction (color of the fob and lock status of the vehicle). The GUI response can be viewed in detail in Figure3-11 . If the fob were within the in/out threshold boundary (i.e. inside the vehicle), the fob would be red toindicate the function could not be performed and the vehicle would remain locked.

Figure 3-11.PEPS Unlock

3.3.7.2 PEPS StartThe driver presses the START button to start the vehicle in a PEPS system. This is demonstrated byplacing the fob within the in/out threshold boundary and pressing the SW0 (PEPS) push button switchon the ATAB0001A interface board. Even if multiple fobs are present, the system uses the first responseas the basis for all actions.

The PEPS start action is indicated by a quick blink of LED7 (PEPS) followed by a steady illumination,LED4 (In/out) is not illuminated (indicating that the fob location is inside the vehicle), and the fob indexused (LED0 LED3) being illuminated on the ATAB0001A interface board. The fob index LED alsoindicates AES authentication has been successfully completed.

ATAK51004-V2


The PC GUI shows the trigger location; the location of the key fob (outside or inside) and the status of theaction (color of the fob and engine status of vehicle). The GUI response can be viewed in detail in Figure312. If the fob were beyond the in/out threshold boundary (i.e. outside the vehicle), the fob would be redto indicate the function could not be performed and the vehicle engine would remain unstarted.

Figure 3-12.PEPS Start Function

Note: If the fob battery is dead (demonstrated by removing the battery), pressing the SW0 (PEPS)push button switch on the ATAB0001A interface board initially attempts to carry out a PEPS start, butthen tries the immobilizer as a backup method. Follow the instructions in Section 3.1 ImmobilizerOperation, but press the SW0 (PEPS) push button switch on the ATAB0001A interface board instead ofthe SW1 (IMMO) push button switch in step 5.

3.3.7.3 PEPS Lock (Fob Left in Vehicle)A very important feature for PEPS is the ability to prevent accidentally locking the fob inside the vehicle.This is demonstrated by placing the fob within the in/out threshold boundary and pressing the SW6(Lock) push button switch on the ATAB0001A interface board. Even if multiple fobs are present, thesystem uses the first response as the basis for all actions.

The PEPS action is indicated by a quick blink of LED7 (PEPS) followed by a steady illumination, LED4(In/out) is not illuminated (indicating that the fob location is inside the vehicle), and the fob index used(LED0 LED3) being illuminated on the ATAB0001A interface board. The fob index LED also indicatesAES authentication has been successfully completed.

The PC GUI shows the trigger location; the location of the key fob (outside or inside) and the status of theaction (color of the fob and lock status of vehicle). The GUI response can be viewed in detail in Figure3-13. Since the fob is within the in/out threshold boundary (i.e. inside the vehicle), the fob is red toindicate the function could not be performed and the vehicle remains unlocked.

ATAK51004-V2


Figure 3-13.PEPS Lock (Fob Inside)

3.3.7.4 PEPS Lock (Fob Removed from Vehicle)To lock the vehicle the fob must first be removed and taken away by the owner. This is demonstrated byplacing the fob beyond the in/out threshold boundary and pressing the SW6 (Lock) push button switchon the ATAB0001A interface board. Even if multiple fobs are present, the system uses the first responseas the basis for all actions.

The PEPS lock action is indicated by a quick blink of LED7 (PEPS) followed by a steady illumination, aquick blink of LED4 (In/out) followed by a steady illumination (indicating that the fob location is outsidethe vehicle), and the fob index used (LED0 LED3) being illuminated on the ATAB0001A interface board.The fob index LED also indicates AES authentication has been successfully completed.

The PC GUI shows the trigger location; the location of the key fob (outside or inside) and the status of theaction (color of the fob and lock status of vehicle). The GUI response can be viewed in detail in Figure3-14. Since the fob is now outside the vehicle, the fob is green and the vehicle locked.

ATAK51004-V2


Figure 3-14.PEPS Lock (Fob Outside)

ATAK51004-V2


4. Programming InstructionsSpecific firmware (Flash) and configuration settings (EEPROM) are required to operate the system.These are found in the MCU (ATmega2560) and the RF receiver (ATA5782) on the vehicle side. The fobcomes with its own PEPS, IMMO and RKE firmware and configuration files. The list below details exactlywhat type of file is needed for each device:

Car Side: ATmega2560: PEPS, IMMO and RKE firmware in Flash and configuration in the EEPROM ATA5782. PEPS and RKE configuration in the EEPROM

Fob Side: ATA5702: PEPS, IMMO and RKE firmware in Flash and configuration in the EEPROM

Note: All devices within the system are shipped fully programmed and it is normally notnecessary to perform the steps described in sections that follow; except in circumstanceswhen revised ATAK51004-V2 Tool Package software is available for download from http://www.microchip.com/ or where the source code has been modified or when a device becomeserratic or unresponsive in behavior.

4.1 Programming the ATmega2560 on ATAB0001A Interface BoardIf it is necessary to reprogram the ATmega2560 on the ATAB0001A interface board, connect theprogrammer (e.g., Atmel-ICE, JTAGICE3, etc.) either to the JTAG or to the ISP header placed on the leftperimeter of the board (see Figure 4-1).

Figure 4-1.ATAB0001A Programming Header Locations

ATmega2560 ISP Header

ATmega2560 JTAG Header

The following programming steps are used with the Atmel-ICE programmer and the JTAG interface:

1. Using Studio 7, program the ATmega2560 by selecting Device Programming in the Tools menu(see Figure 4-2).Figure 4-2.Device Programming

2. Select the programmer, device, interface as shown in Figure 4-3, and press Apply:

Figure 4-3.Programmer Configuration

3. Click the Read Signature button to be sure the signature matches the selected device (see Figure4-4).

ATAK51004-V2



Figure 4-4.Device Signature

4. Select the Fuses tab and verify the proper fuse settings exist. If not, change them to match Figure4-5 and press the Program button.Figure 4-5.ATmega2560 Fuse Settings

5. Select the Memories tab and click the Erase now button (see Figure 4-6).6. Browse to locate the CARS_ATmega2560_flash.hex file for the flash memory image (see Figure

4-6).7. Click the Program button and wait for completion.

Note: LEDs 0 through 7 on the ATAB0001A CARS interface board will blink rapidly indicating thatthe EEPROM within the ATmega2560 still is needed. These LEDs will stop blinking upon theinitiation of step 9.

8. Browse to locate the CARS_ATMega2560_EEPROM.eep file for the EEPROM memory image (see Figure 4-6).

9. Click the Program button and wait for completion.

ATAK51004-V2


Figure 4-6.ATmega2560 Memory Programming

Note:When using an ISP programmer connected to the ISP header, follow the exact same procedure asdescribed above. However, be sure to select the ISP interface in Step 2 and set the ISPprogramming frequency to 100 kHz or lower prior to Step 4 (see Figure 4-7).

Figure 4-7.ISP Clock Frequency

4.2 Programming the ATA5702 on the ATAB5702A PEPS Fob BoardIf it is necessary to reprogram the ATA5702 on the ATAB5702A PEPS transmitter board, connect theprogrammer (e.g., Atmel-ICE, JTAGICE3, etc.) to the ISP header located near the center of the board.

The following programming steps are used with the ICE programmer and the ISP interface:

1. Using Studio 7, program the ATA5702 by selecting Device Programming in the Tools menu (see Figure 4-8).Figure 4-8.Device Programming

2. Select the programmer, device, interface as shown in Figure 4-9, and press Apply:

ATAK51004-V2


Figure 4-9.Programmer Configuration

3. Be sure to Set the ISP frequency to less than 100 kHz (see Figure 4-10).Figure 4-10.ISP Clock Frequency

4. Click the Read Signature button to be sure the signature matches the selected device (see Figure4-11).Figure 4-11.Device Signature

5. Select the Fuses tab and verify the proper fuse settings exist. If not, change them to match Figure412 and press the Program button.Figure 4-12.ATA5702 Fuse Settings

6. Select the Memories tab and click the Erase now button (see Figure 4-13).7. Browse to locate the ATA5702_flash.hex file for the flash memory image (see Figure 4-13).8. Click the Program button and wait for completion.9. Browse to locate the ATA5702_eeprom.eep file for the EEPROM memory image (see Figure


ATAK51004-V2


Figure 4-13.ATA5702 Memory Programming

Note: Should the EEPROM verification step fail (similar to what is shown in Figure 4-14) repeatsteps 1 10 to ensure everything is properly configured. If the error still occurs, then the ATA5702 ICversion is outdated and you must contact your local sales representative for an upgrade.Figure 4-14.ATA5702 EEPROM Verification Failure

4.3 Programming the ATA5782 on the ATAB0003A RF Receiver BoardIf it is necessary to reprogram the ATA5782 on the ATAB0003A RF receiver board, begin by first removingthe board from the UHF_X1 and UHF_X2 sockets of the ATAB0001A CARS interface board. Thenconnect the programmer (e.g., Atmel-ICE, JTAGICE3, etc.) to the ISP header located near the center ofthe board. Finally, provide +3V across the Vs and Ground test points, as well as, connect the TRPB testpoint to ground as shown in Figure 4-15.

Note: To avoid potentially shorting Vs and Ground, it is recommended to make the connections onopposite sides of the board.

ATAK51004-V2


Figure 4-15.ATA5782 Programming Header and Test Point Locations

The following programming steps are used with the Atmel-ICE programmer and the ISP interface:

1. Using Studio 7, program the ATA5782 by selecting Device Programming in the Tools menu (see Figure 4-16).Figure 4-16.Device Programming

2. Select the programmer, device, interface as shown in Figure 4-17, and press Apply.Figure 4-17.Programmer Configuration

3. Be sure to Set the ISP frequency to less than 100 kHz (see Figure 4-18).Figure 4-18.ISP Clock Frequency

4. Click the Read Signature button to be sure the signature matches the selected device (see Figure4-19).

ATAK51004-V2


Figure 4-19.Device Signature

5. Select the Fuses tab and verify the proper fuse settings exist. If not, change them to match Figure4-20 and click the Program button.Figure 4-20.ATA5782 Fuse Settings

6. Select the Memories tab and click the Erase now button (see Figure 4-21).7. Browse to locate the ATA5781_eeprom.eep file for the EEPROM memory image (see Figure


Figure 4-21. ATA5782 Memory Programming

9. Remount the ATAB0003A RF receiver board onto the UHF_X1 and UHF_X2 sockets of theATAB0001A CARS interface board.

ATAK51004-V2


5. Installing Virtual COM Port

5.1 USB Driver Setup for Windows 71. Connect the mini-USB plug to the USB connector (J12) on the ATAB0001A CARS interface board

as shown in Figure 21.2. Connect the USB cable to your PC and right-mouse click on the Computer entry in the

Computer>Manage dialog as shown in Figure 51.Figure 5-1.Manage Dialog in Windows 7

3. Open the Add legacy hardware dialog by selecting Device Manager and right-mouse click thecomputer name as shown in Figure 52.Figure 5-2.Add Legacy Hardware Dialog

4. Select the Install the hardware dialog from the Add Hardware wizard and press Next as shownin Figure 5-3.

ATAK51004-V2


Figure 5-3.Add Hardware Wizard - Install Selection Dialog

5. Choose Show All Devices and in the next prompt select the Have Disk button as shown in Figure 54.Figure 5-4.Show All Devices - Have Disk... Dialog

ATAK51004-V2


6. Choose the Browse button, select the directory for the USB driver(atmel_devices_cdc.inf), and open the file as shown in Figure 55.Figure 5-5.Locate File Dialog

7. In the next menu, select the EVK1XXX Virtual Com Port entry and press Next to install the driveras shown in Figure 56.

ATAK51004-V2


Figure 5-6.Select Device Driver Dialog

8. When the Windows Security prompt appears, select Install this driver software anyway as shownin Figure 57.Figure 5-7.Windows Security Dialog

9. Click Finish in the Add Hardware dialog to close the wizard as shown in Figure 58.

ATAK51004-V2


Figure 5-8.Complete Dialog

10. Now connect the USB cable to your PC and verify the successful installation by checking the COMport number in Device Manager. There should be a type EVK11xx Virtual COM Port deviceavailable that identifies the COM port number as shown in Figure 59.Figure 5-9.Device Manager with Port Settings

ATAK51004-V2


6. Errata (Version3_Rev3 Software Version)The following is a list of known errata issues found on the current release of software:

1. Section 3.2.1:1.1. The RF learn feature only works when the fob has been previously learned to the system

using LF learn.2. Section 3.3.2:

2.1. The PEPS Message Status window does not consistently display multiple fobs as beingauthenticated. However, the ATAB0001A CARS interface board fob index LEDs (LED0 LED3) properly indicate multiple fobs as being authenticated.

ATAK51004-V2


7. Revision History

Revision A (September 2017)Original release of the document.

ATAK51004-V2


8. Object of DeclarationEU Declaration of Conformity for ATAK51004-V2 Car Access Reference System (CARS) Kit

This declaration of conformity is issued by the manufacturer.

The development/evaluation tool is designed to be used for research and development in a laboratoryenvironment. This development/evaluation tool is not a Finished Appliance, nor is it intended forincorporation into Finished Appliances that are made commercially available as single functional units toend users under EU EMC Directive 2004/108/EC and as supported by the European Commission's Guidefor the EMC Directive 2004/108/EC (8th February 2010).

This development/evaluation tool complies with EU RoHS2 Directive 2011/65/EU.

This development/evaluation tool, when incorporating wireless and radio-telecom functionality, is incompliance with the essential requirement and other relevant provisions of the R&TTE Directive1999/5/EC and the FCC rules as stated in the declaration of conformity provided in the module datasheetand the module product page available at www.microchip.com.

For information regarding the exclusive, limited warranties applicable to Microchip products, please seeMicrochips standard terms and conditions of sale, which are printed on our sales documentation andavailable at www.microchip.com.

Signed for and on behalf of Microchip Technology Inc. at Chandler, Arizona, USA.

ATAK51004-V2



The Microchip Web Site

Microchip provides online support via our web site at http://www.microchip.com/. This web site is used asa means to make files and information easily available to customers. Accessible by using your favoriteInternet browser, the web site contains the following information:

Product Support Data sheets and errata, application notes and sample programs, designresources, users guides and hardware support documents, latest software releases and archivedsoftware

General Technical Support Frequently Asked Questions (FAQ), technical support requests,online discussion groups, Microchip consultant program member listing

Business of Microchip Product selector and ordering guides, latest Microchip press releases,listing of seminars and events, listings of Microchip sales offices, distributors and factoryrepresentatives

Customer Change Notification Service

Microchips customer notification service helps keep customers current on Microchip products.Subscribers will receive e-mail notification whenever there are changes, updates, revisions or erratarelated to a specified product family or development tool of interest.

To register, access the Microchip web site at http://www.microchip.com/. Under Support, click onCustomer Change Notification and follow the registration instructions.

Customer Support

Users of Microchip products can receive assistance through several channels:

Distributor or Representative Local Sales Office Field Application Engineer (FAE) Technical Support

Customers should contact their distributor, representative or Field Application Engineer (FAE) for support.Local sales offices are also available to help customers. A listing of sales offices and locations is includedin the back of this document.

Technical support is available through the web site at: http://www.microchip.com/support

Microchip Devices Code Protection Feature

Note the following details of the code protection feature on Microchip devices:

Microchip products meet the specification contained in their particular Microchip Data Sheet. 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 theoperating specifications contained in Microchips Data Sheets. Most likely, the person doing so isengaged in theft of intellectual property.

Microchip is willing to work with the customer who is concerned about the integrity of their code.

ATAK51004-V2


http://www.microchip.com/http://www.microchip.com/http://www.microchip.com/support

Neither Microchip nor any other semiconductor manufacturer can guarantee the security of theircode. 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 thecode protection features of our products. Attempts to break Microchips code protection feature may be aviolation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your softwareor other copyrighted work, you may have a right to sue for relief under that Act.

Legal NoticeInformation contained in this publication regarding device applications and the like is provided only foryour convenience and may be superseded by updates. It is your responsibility to ensure that yourapplication meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORYOR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITSCONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE.Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in lifesupport and/or safety applications is entirely at the buyers risk, and the buyer agrees to defend,indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resultingfrom such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectualproperty rights unless otherwise stated.

TrademarksThe Microchip name and logo, the Microchip logo, AnyRate, AVR, AVR logo, AVR Freaks, BeaconThings,BitCloud, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq, KeeLoq logo,Kleer, LANCheck, LINK MD, maXStylus, maXTouch, MediaLB, megaAVR, MOST, MOST logo, MPLAB,OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch, RightTouch, SAM-BA,SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O, and XMEGA are registered trademarks ofMicrochip Technology Incorporated in the U.S.A. and other countries.

ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLightLoad, IntelliMOS, mTouch, Precision Edge, and Quiet-Wire are registered trademarks of MicrochipTechnology Incorporated in the U.S.A.

Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BodyCom,chipKIT, chipKIT logo, CodeGuard, CryptoAuthentication, CryptoCompanion, CryptoController,dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit SerialProgramming, ICSP, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, Mindi, MiWi,motorBench, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, OmniscientCode Generation, PICDEM, PICDEM.net, PICkit, PICtail, PureSilicon, QMatrix, RightTouch logo, REALICE, Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, TotalEndurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA aretrademarks of Microchip Technology Incorporated in the U.S.A. and other countries.

SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.

Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries.

GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary ofMicrochip Technology Inc., in other countries.

All other trademarks mentioned herein are property of their respective companies. 2017, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.

ATAK51004-V2


ISBN: 978-1-5224-2181-8

Quality Management System Certified by DNV

ISO/TS 16949Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and waferfabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in Californiaand India. The Companys quality system processes and procedures are for its PIC MCUs and dsPIC

DSCs, KEELOQ code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory andanalog products. In addition, Microchips quality system for the design and manufacture of developmentsystems is ISO 9001:2000 certified.

ATAK51004-V2


AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPECorporate Office2355 West Chandler Blvd.Chandler, AZ 85224-6199Tel: 480-792-7200Fax: 480-792-7277Technical Support:http://www.microchip.com/supportWeb Address:www.microchip.comAtlantaDuluth, GATel: 678-957-9614Fax: 678-957-1455Austin, TXTel: 512-257-3370BostonWestborough, MATel: 774-760-0087Fax: 774-760-0088ChicagoItasca, ILTel: 630-285-0071Fax: 630-285-0075DallasAddison, TXTel: 972-818-7423Fax: 972-818-2924DetroitNovi, MITel: 248-848-4000Houston, TXTel: 281-894-5983IndianapolisNoblesville, INTel: 317-773-8323Fax: 317-773-5453Tel: 317-536-2380Los AngelesMission Viejo, CATel: 949-462-9523Fax: 949-462-9608Tel: 951-273-7800Raleigh, NCTel: 919-844-7510New York, NYTel: 631-435-6000San Jose, CATel: 408-735-9110Tel: 408-436-4270Canada - TorontoTel: 905-695-1980Fax: 905-695-2078

Asia Pacific OfficeSuites 3707-14, 37th FloorTower 6, The GatewayHarbour City, KowloonHong KongTel: 852-2943-5100Fax: 852-2401-3431Australia - SydneyTel: 61-2-9868-6733Fax: 61-2-9868-6755China - BeijingTel: 86-10-8569-7000Fax: 86-10-8528-2104China - ChengduTel: 86-28-8665-5511Fax: 86-28-8665-7889China - ChongqingTel: 86-23-8980-9588Fax: 86-23-8980-9500China - DongguanTel: 86-769-8702-9880China - GuangzhouTel: 86-20-8755-8029China - HangzhouTel: 86-571-8792-8115Fax: 86-571-8792-8116China - Hong Kong SARTel: 852-2943-5100Fax: 852-2401-3431China - NanjingTel: 86-25-8473-2460Fax: 86-25-8473-2470China - QingdaoTel: 86-532-8502-7355Fax: 86-532-8502-7205China - ShanghaiTel: 86-21-3326-8000Fax: 86-21-3326-8021China - ShenyangTel: 86-24-2334-2829Fax: 86-24-2334-2393China - ShenzhenTel: 86-755-8864-2200Fax: 86-755-8203-1760China - WuhanTel: 86-27-5980-5300Fax: 86-27-5980-5118China - XianTel: 86-29-8833-7252Fax: 86-29-8833-7256

China - XiamenTel: 86-592-2388138Fax: 86-592-2388130China - ZhuhaiTel: 86-756-3210040Fax: 86-756-3210049India - BangaloreTel: 91-80-3090-4444Fax: 91-80-3090-4123India - New DelhiTel: 91-11-4160-8631Fax: 91-11-4160-8632India - PuneTel: 91-20-3019-1500Japan - OsakaTel: 81-6-6152-7160Fax: 81-6-6152-9310Japan - TokyoTel: 81-3-6880- 3770Fax: 81-3-6880-3771Korea - DaeguTel: 82-53-744-4301Fax: 82-53-744-4302Korea - SeoulTel: 82-2-554-7200Fax: 82-2-558-5932 or82-2-558-5934Malaysia - Kuala LumpurTel: 60-3-6201-9857Fax: 60-3-6201-9859Malaysia - PenangTel: 60-4-227-8870Fax: 60-4-227-4068Philippines - ManilaTel: 63-2-634-9065Fax: 63-2-634-9069SingaporeTel: 65-6334-8870Fax: 65-6334-8850Taiwan - Hsin ChuTel: 886-3-5778-366Fax: 886-3-5770-955Taiwan - KaohsiungTel: 886-7-213-7830Taiwan - TaipeiTel: 886-2-2508-8600Fax: 886-2-2508-0102Thailand - BangkokTel: 66-2-694-1351Fax: 66-2-694-1350

Austria - WelsTel: 43-7242-2244-39Fax: 43-7242-2244-393Denmark - CopenhagenTel: 45-4450-2828Fax: 45-4485-2829Finland - EspooTel: 358-9-4520-820France - ParisTel: 33-1-69-53-63-20Fax: 33-1-69-30-90-79France - Saint CloudTel: 33-1-30-60-70-00Germany - GarchingTel: 49-8931-9700Germany - HaanTel: 49-2129-3766400Germany - HeilbronnTel: 49-7131-67-3636Germany - KarlsruheTel: 49-721-625370Germany - MunichTel: 49-89-627-144-0Fax: 49-89-627-144-44Germany - RosenheimTel: 49-8031-354-560Israel - RaananaTel: 972-9-744-7705Italy - MilanTel: 39-0331-742611Fax: 39-0331-466781Italy - PadovaTel: 39-049-7625286Netherlands - DrunenTel: 31-416-690399Fax: 31-416-690340Norway - TrondheimTel: 47-7289-7561Poland - WarsawTel: 48-22-3325737Romania - BucharestTel: 40-21-407-87-50Spain - MadridTel: 34-91-708-08-90Fax: 34-91-708-08-91Sweden - GothenbergTel: 46-31-704-60-40Sweden - StockholmTel: 46-8-5090-4654UK - WokinghamTel: 44-118-921-5800Fax: 44-118-921-5820

Worldwide Sales and Service


FeaturesKit ContentsTable of Contents1.Introduction1.1.Immobilizer Support1.2.RKE Support1.3.PEPS Support

2.Kit System Setup2.1.Hardware2.2.PC Application Software

3.System Operation3.1.Immobilizer Operation3.2.Remote Keyless Entry (RKE) Operation3.2.1.RF Learn Mode3.2.2.Normal RKE Operation3.2.3.Using the RKE System with the GUI

3.3.PEPS Operation3.3.1.System Configuration Window Overview3.3.2.PEPS Message Status Window Overview3.3.3.Identifying Fobs in Range3.3.4.Fob Calibration Overview3.3.5.Fob Calibration Process3.3.5.1.PEPS Wake-Up Functionality

3.3.6.PEPS Communication3.3.7.PEPS Normal Operation3.3.7.1.PEPS Unlock3.3.7.2.PEPS Start3.3.7.3.PEPS Lock (Fob Left in Vehicle)3.3.7.4.PEPS Lock (Fob Removed from Vehicle)

4.Programming Instructions4.1.Programming the ATmega2560 on ATAB0001A Interface Board4.2.Programming the ATA5702 on the ATAB5702A PEPS Fob Board4.3.Programming the ATA5782 on the ATAB0003A RF Receiver Board

5.Installing Virtual COM Port5.1.USB Driver Setup for Windows 7

6.Errata (Version3_Rev3 Software Version)7.Revision History8.Object of DeclarationThe Microchip Web SiteCustomer Change Notification ServiceCustomer SupportMicrochip Devices Code Protection FeatureLegal NoticeTrademarksQuality Management System Certified by DNVWorldwide Sales and Service

ATAK51004-V2 User's Guide - Microchip...

Documents

Transcript of ATAK51004-V2 User's Guide - Microchip...