SEC1110/SEC1210 Linux Setup - Microchip...

AN1962SEC1110/SEC1210 Linux Setup

INTRODUCTIONThis document explains the installation of SEC1110/SEC1210 CCID reader in Linux on different platforms.

Smartcard reader installation under Linux x86The below described setup was done using Fedora 14 with kernel version 2.6.35.6-45

REQUIRED LIBRARIESThe following libraries are prerequisite to install a USB smartcard reader under Linux x86.

1. libusb 1.0.82. pcsc-tools3. libpcsc-lite4. libccid

Following are the dependencies for the installation of above libraries:

1. gnu gcc,make2. libudev3. libtool4. perl-Gtk2

LIBUSB-1.0.8Obtain the libusb package from sourceforge.net/projects/libusb/ % tar xvjf libusb-1.0.8.tar.bz2 % cd libusb-1.0.8%su #As ROOT perform % ./configure % make % make install

LIBUDEV-DEVIn case of a Fedora system Install libudev development files as:%yum install libudev-devel

Or in case of Ubuntu, use:%sudo apt-get install libudev-dev

Note 1: There is a limitation in using Microchip’s Dual Slot Reader with libusb where the slot with card always pres-ent is not accessible or simply stated, the second interface of the reader is not accessible. The limitation is not noticed when tested with pcsclite-1.7.4 compiled using libudev enabled and libusb disabled.

2: The author has added support for libudev since pcsclite -1.6.8, while removing libhal. http://ludovicrous-seau.blogspot.com/2011/02/pcscd-now-uses-libudev-instead-of.html

Author: VishnuPriya Padmanabhan Microchip Technology Inc.

2015 Microchip Technology Inc. DS00001962A-page 1

http://sourceforge.net/projects/libusb/

http://ludovicrousseau.blogspot.com/2011/02/pcscd-now-uses-libudev-instead-of.html

http://ludovicrousseau.blogspot.com/2011/02/pcscd-now-uses-libudev-instead-of.html

AN1962
PCSC-LITEObtain tar file for the pcsc-lite version 1.7.4 from https://alioth.debian.org/frs/?group_id=30105% tar xvjf pcsc-lite-1.7.4.tar.bz2 % cd pcsc-lite-1.7.4
%su #As ROOT perform % ./configure –enable-libusb –disable-libudev --enable-debugatr % make % make install

In case of following with section 2.1.3 use below configuration:% ./configure –enable-libudev –disable-libusb --enable-debugatr % make % make install

PCSC-TOOLSObtain tar file for pcsc-tools from http://ludovic.rousseau.free.fr/softwares/pcsc-tools/% tar xvf pcsc-tools-1.4.17.tar.gz % cd pcsc-tools-1.4.17

%su #As ROOT perform % ./configure % make % make install

CCID FREE SOFTWARE DRIVERObtain a copy of the free driver ccid-1.4.4.tar.bz2 from http://pcsclite.alioth.debian.org/ccid.html% tar xvjf ccid-1.4.4.tar.bz2 % cd ccid-1.4.4 % cd readers

Here is present a file “supported_readers.txt” containing the list of supported readers. Microchip's smart card reader SEC1110/SEC1210 needs to be added to this list along with its VID and PID. Add the following at the end of the “sup-ported_readers.txt” for Microchip device to be detected as smartcard reader.

For Single Slot device# SMSC 0x0424:0x1011:SEC1x10 SmartCard Reader

For Dual Slot device# SMSC 0x0424:0x1200:SEC1x10 Dual Slot SmartCard Reader

Where 0x0424 Stands for Microchip’s VID and following value corresponds to the PID of the Device.

Now as ROOT do:% ./configure % make % make install

PERL-GTK2This dependency will be required to run the tools obtained using pcsc-tools.

In Fedora use:%su %yum install perl-Gtk2

OTHER DEPENDENCIESFor other dependency library installation follow the general steps% tar xvf library.tar.gz

Or:% tar xvjf library.tar.bz2 % cd library

DS00001962A-page 2 2015 Microchip Technology Inc.

http://ludovic.rousseau.free.fr/softwares/pcsc-tools/

https://alioth.debian.org/frs/?group_id=30105

http://pcsclite.alioth.debian.org/ccid.html

AN1962
As ROOT perform:% ./configure % make % make install
OPENSCOpenSC is a tool that can be used to list the smartcard readers installed in a system. This tool can be installed manually as:% tar xvf opensc-0.12.0.tar.gz % cd opensc-0.12.0

%su #As ROOT perform % ./configure % make % make install

SMART CARD READER INSTALLATION UNDER ARM PLATFORMTo Setup the SmartCard Reader on an embedded ARM platform we will be using a HOST Linux PC to Cross Compile the required libraries and then copy the compiled libraries and resources to the ARM device. In this Setup:HOST DEVICE:Ubuntu Linux 11.04TARGET DEVICE: OpenRD Tasman System

Required Libraries and ToolsCreate a directory to copy the libraries required for the cross compilation Toolchain.% cd /home/smsc/Desktop/ % mkdir toolchain

Obtain the source tar bals for the libraries from their online repositories

1. libusb-1.0.8.tar.bz22. pcsc-lite 1.7.4.tar.bz23. ccid-1.4.4.tar.bz2

Copy these source files to our toolchain directory (/home/smsc/Desktop/toolchain/) from the place of Download.

Copy OpenRD’s gcc compiler for their ARM platform from the given media to the toolchain directory% cp /home/openrd/openrd-tasman-devkit-v1.0/openrd-tasman_host_swsupportpackage/linux/gcc.tar.bz2 /home/smsc/Desktop/toolchain/% cd /home/smsc/Desktop/toolchain/% tar -xjvf /home/smsc/Desktop/toolchain/gcc.tar.bz2

Add this gcc location to the PATH environment variable% export PATH=/home/smsc/Desktop/toolchain/gcc/bin:$PATH

Now Set the compiler variables to utilize the OpenRD compiler.% export CC=arm-none-linux-gnueabi-gcc AR= arm-none-linux-gnueabi -ar LD= arm-none-linux-gnueabi -ld STRIP= arm-none-linux-gnueabi-strip

The above variables CC, AR, LD, STRIP and the corresponding names will be present as executables in the declared PATH variable.

Extract Libraries Libusb,Pcsclite,CcidCreate a Separate Directory to install the cross-compiled toolchain.% mkdir –p /home/smsc/Desktop/Target % cd /home/smsc/Desktop/Target

Note: A possible issue while running OpenSC after manual installation would be with accessing libpcsclite.so.In that case, follow the solution mentioned in OpenSC website http://www.opensc-project.org/opensc/wiki/FrequentlyAskedQuestions


http://www.opensc-project.org/opensc/wiki/FrequentlyAskedQuestions

http://www.opensc-project.org/opensc/wiki/FrequentlyAskedQuestions

AN1962
LIBUSB-1.0.8Obtain the libusb package from sourceforge.net/projects/libusb/ % tar xvjf libusb-1.0.8.tar.bz2 % cd libusb-1.0.8 %./configure --host=arm-none-linux-gnueabi --prefix=/usr % make %su #As ROOT perform % make install prefix=/home/smsc/Desktop/Target/
Now just make sure that the compiled library files support the ARM platform and not the host architecture i.e X86Cd =/home/smsc/Desktop/Target/lib/ File lib*

The command output should show that the file is supported for ARM.

PCSC-LITE% tar xvjf pcsc-lite-1.7.4.tar.bz2 % cd pcsc-lite-1.7.4 % ./configure --host=arm-none-linux-gnueabi --prefix=/usr –enable-libusb –disable-libudev --enable-debugatr PKG_CONFIG_PATH==/home/smsc/Desktop/toolchain/OpenRD/lib/pkg-config LIBUSB_CFLAGS=-I/home/smsc/Desktop/Target/include/libusb-1.0/ LIBUSB_LIBS=/home/smsc/Desktop/Target/lib/libusb-1.0.so % make % make install prefix=/home/smsc/Desktop/Target/

Check the compatibility for ARM as done before.

CCID FREE SOFTWARE DRIVERObtain a copy of the free driver ccid-1.4.4.tar.bz2 from http://pcsclite.alioth.debian.org/ccid.html% tar xvjf ccid-1.4.4.tar.bz2 % cd ccid-1.4.4 % cd readers

Here is present a file “supported_readers.txt” containing the list of supported readers. Microchip's smart card reader SEC1x10 needs to be added to this list along with its VID and PID. Add the following at the end of the “supported_read-ers.txt” for Microchip device to be detected as smartcard reader.

# SMSC 0x0424:0x1011:SEC1x10 SmartCard Reader 0x0424:0x1200:SEC1x10 Dual Slot SmartCard Reader

Where 0x0424 Stands for Microchip’s VID and following value corresponds to the PID of the Device.%cd /home/smsc/Desktop/toolchain/ccid-1.4.4% ./configure --host=arm-none-linux-gnueabi –prefix=/usr PCSC_CFLAGS=-I/home/smsc/Desktop/Target/include/PCSC/ LIBUSB_CFLAGS=-I/home/smsc/Desktop/Target/include/libusb-1.0/ LIBUSB_LIBS=/home/smsc/Desktop/Target/lib/libusb-1.0.so --enable-usbdropdir=/home/smsc/Desktop/Target/lib/drivers PCSC_LIBS=/home/smsc/Desktop/Target/lib/libpcsclite.so.1.0.0

//(Kindly check NOTE: in section2.3 method1)% make % make install prefix=/home/smsc/Desktop/Target/

Check the compatibility for ARM as done before. Also check for the driver file at /home/smsc/Desktop/Target//lib/driv-ers/ifd-ccid.bundle/Contents/Linux/libccid.so

Copying the Installed Libraries to the ARM Device:The Directory used as prefix in the library configuration will now hold the following cross-compiled Resources:/home/smsc/Desktop/Target/lib /home/smsc/Desktop/Target/include /home/smsc/Desktop/Target/sbin /home/smsc/Desktop/Target/share

The contents of these directories now need to be copied to their corresponding directories in the ARM device as follows:




AN1962
/usr/include /usr/lib /usr/share /usr/sbin
To copy the compiled libraries from the host to OpenRD, two methods can be followed:

Method 1:Tar the folder containing the libraries in the host and copy to the OpenRD using a USB storage device and untar the file

To create a tar file of the location /home/smsc/Desktop/Target type:%tar cvjf tools.bzip2 /home/smsc/Desktop/Target%cp –f /home/smsc/Desktop/Target/tools.bzip2 /media/pendrive

Move the pendrive to the OpenRD system and mount it.%cp –f /media/pendrive/tools.bzip2 /home/openrd/Desktop%cd /home/openrd/Desktop%tar xvjf tools.bzip2%cd Target %cp –fr include/ /usr/ %cp –fr /lib/usr/ %cp –fr /sbin /usr/

The current method of setup requires a copy of the driver “libccid.so” to be copied in the same directory structure as in the host.

So Create the below directory:%mkdir -p /home/smsc/Desktop/Target/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/

Now make a copy of the libccid.so file created in section3.2.3 to the new directory

Method 2:If tar is not possible, simply copy the directory:/home/smsc/Desktop/Target

While doing so an error like “the filesystem does not support copying symbolic links”, may be posted if the pendrive is in FAT filesystem. This can be resolved later.

Now copy the libraries to the corresponding directory structure in OpenRD%cd Target %cp –fr include/ /usr/ %cp –fr /lib/usr/ %cp –fr /sbin /usr/

Now to resolve the missing symbolic links:%cd /usr/lib

%ln -s libusb-1.0.so.0.0.0 libusb-1.0.so.0%ln -s libusb-1.0.so.0.0.0 libusb-1.0.so

Setup In ARM Summary1. Setup a Host Linux System for Cross Compilation using gcc provided by OpenRD.2. Obtain the source tars for the Libraries required to setup a smart reader.3. Configure using –host=arm-none-linux-gnueabi and Cross Compile the Libraries to a separate directory.4. Move the cross compiled resources from the created directory to the target ARM device.

CROSS COMPILATION FOR MAKING FILESYSTEM IMAGE%mkdir –p /home/openrd/Debian_Lenny_OpenRD-Tasman

Obtain the FileSystem source Tar file to /home/openrd

Note: This can be overcome while cross-compiling ccid-1.4.4, by changing the flag--enable-usbdropdir=/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/

and copy the libccid.so to the OpenRD


AN1962
%cd /home/openrd/Debian_Lenny_OpenRD-Tasman
Extract the FileSystem source tar Debian_Lenny_OpenRD-Tasman.tar.gz here%tar xvf /home/openrd/Debian_Lenny_OpenRD-Tasman.tar.gz /home/openrd/Debian_Lenny_OpenRD-Tasman%export INSTALL_PATH=/home/openrd/Debian_Lenny_OpenRD-Tasman/

Follow Section 3.1 to setup gcc cross compiler

LIBUSB-1.0.8Obtain the libusb package from sourceforge.net/projects/libusb/ % tar xvjf libusb-1.0.8.tar.bz2 % cd libusb-1.0.8 % . /configure --host=arm-none-linux-gnueabi --prefix=/usr % make %su #As ROOT perform % make install DESTDIR=$( INSTALL_PATH)

PCSC-LITE% tar xvjf pcsc-lite-1.7.4.tar.bz2 % cd pcsc-lite-1.7.4 %./configure --host=arm-none-linux-gnueabi --prefix=/usr --enable-libusb --disable-libudev --enable-debugatr LIBUSB_CFLAGS=-I$( INSTALL_PATH)/usr/include/libusb-1.0 LDFLAGS=-L$( INSTALL_PATH)/usr/lib/ LIBUSB_LIBS=-lusb-1.0 % make %make install DESTDIR=$( INSTALL_PATH)

CCID FREE SOFTWARE DRIVERObtain a copy of the free driver ccid-1.4.4.tar.bz2 from http://pcsclite.alioth.debian.org/ccid.html

% tar xvjf ccid-1.4.4.tar.bz2 % cd ccid-1.4.4%./configure --host=arm-none-linux-gnueabi --prefix=/usr LIBUSB_CFLAGS=-I$( INSTALL_PATH)/usr/include/libusb-1.0 LDFLAGS=-L$( INSTALL_PATH)/usr/lib/ LIBUSB_LIBS=-lusb-1.0 PCSC_CFLAGS=-I$( INSTALL_PATH)/usr/include/PCSC/ --enable-usbdropdir=/usr/lib/pcsc/drivers PCSC_LIBS=-lpcsclite% make %make install DESTDIR=$( INSTALL_PATH)

BUILDING THE UBI FILESYSTEM IMAGEOnce the above libraries have been installed in the filesystem directory, follow the steps to build the Filesystem image using MTD-Utils as documented by OpenRD.

The resulting build image will need to be flashed onto the OpenRD Flash memory, the steps for which are provided by OpenRD documentation.

DEBUGGING IN LINUX

USB TracesSometimes getting a USB bus trace is required to debug field issues.

Some of the manufacturers of USB analyzers have been listed below:

Ellisys, LeCroy

PCSCD debug log1. Check whether pcscd is running or not. Use command:

ps –ef | grep pcscd




AN1962
If it lists any running pcscd, stop the process using the command service pcscd stop
2. Start logging using the command:tail –f /var/log/messages > debuglog.txt

3. Open a new command terminal and run pcscd in debug mode using command:pcscd –df

All debug messages will be available in a text file named debuglog.txt in current directory.

4. After the issue scenario has been simulated, stop the logging by pressing ctrl+c in the terminal where “tail -...” is running.

APPENDIX

SIM explorer for Linux-FedoraInstall the following packages using yum install in Fedora:%yum install gtk-sharp2 libmono-system-runtime2.0-cil%yum install monosim

Use a Smartcard to SIM adapter and insert a SIM card in it.Launch monoSIM % monosimSelect Sim -> Connect to Sim Select SMSC smart card reader.


AN1962

FIGURE 1: VIEW OF SMARTCARD READER


AN1962
The contacts stored in the SIM card can be viewed as shown below.
Scriptor - Perl script to send commands to a smart cardscriptor is a program that sends commands to a smart card using a batch file or stdin.

USAGE: scriptor [-h] [-r reader] [-p protocol] [file]

APDU Commands can be given from command line or a file can also be given instead of stdin to read commands (APDUs)

The commands are of the form: CLA INS P1 P2 Lc [data] [le].Commands need to be sent according to the type of the smart card.

Example: The below sequence of commands can be used on a Airtel SIM card.

Method 1: From Command promptStep 1:

FIGURE 2: VIEW OF CONTACTS IN SIM CARD


AN1962
[root@localhost Desktop]# scriptor –r “SMSC USX1011 Smart Card Reader (0123456789AF) 00 00 “ -p “T=0”.
.

Step 2:# reset the card reset

Step 3:# Select MF 3F00 A0 A4 00 00 02 3F 00

Step 4:# Get Reponse # 16 is the value of second SW from the previous command A0 C0 00 00 16

Step 5:# Select DF Telecom (7F10) A0 A4 00 00 02 7F 10

Method 2: Using Batch-file as inputCreate a file having contents like below.# reset the card reset # Select MF 3F00 A0 A4 00 00 02 3F 00 # Get Reponse # 16 is the expected value of second SW from the previous command A0 C0 00 00 16 # Select DF Telecom (7F10) A0 A4 00 00 02 7F 10

Save the file as file.txt (any file name).

Step1:

[root@localhost Desktop]# scriptor –r “SMSC USX1011 Smart Card Reader (0123456789AF) 00 00 “ -p “T=0” file.txt

This is the output from the Airtel simcard.

FIGURE 3: COMMAND PROMPT

Note: If you get a response as shown below just re-run it. It is a utility issue.

FIGURE 4: UTILITY ISSUE ERROR MESSAGE

Note: The error messages below are ignorable as they are not the proper commands to the card.


AN1962

CCID driver fix for Dual Slot Reader using LibusbAs mentioned in section 2.1.2, The Dual Slot reader does not enumerate properly with PCSC lite compiled using libusb.

This issue can be overcome by compiling the ccid driver with a type of hack in its source file CCID_USB.c

Locate the following code:r = libusb_claim_interface(dev_handle, interface);if (r < 0){

(void)libusb_close(dev_handle);DEBUG_CRITICAL4("Can't claim interface %d/%d: %d",

bus_number, device_address, r);claim_failed = TRUE;interface_number = -1;continue;

}

And make the change as

r = libusb_claim_interface(dev_handle, interface);if (r < 0){

interface=interface+1;r = libusb_claim_interface(dev_handle, interface);

if(r<0){

(void)libusb_close(dev_handle);DEBUG_CRITICAL4("Can't claim interface %d/%d: %d",

bus_number, device_address, r);claim_failed = TRUE;interface_number = -2;continue;

}}

FIGURE 5: IGNORABLE ERROR MESSAGES


AN1962
This code shall try to access the second interface which doesn’t happen in the actual driver.

AN1962
APPENDIX A: APPLICATION NOTE REVISION HISTORY
TABLE A-1: REVISION HISTORY

Revision Level & Date Section/Figure/Entry Correction

Note: AN1962, Revision A replaces the previous SMSC version, AN004.


AN1962


THE MICROCHIP WEB SITEMicrochip provides online support via our WWW site at www.microchip.com. This web site is used as a means to make files and information easily available to customers. Accessible by using your favorite Internet browser, the web site con-tains the following information:

• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software

• 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 semi-nars and events, listings of Microchip sales offices, distributors and factory representatives

CUSTOMER CHANGE NOTIFICATION SERVICEMicrochip’s customer notification service helps keep customers current on Microchip products. Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.

To register, access the Microchip web site at www.microchip.com. Under “Support”, click on “Customer Change Notifi-cation” and follow the registration instructions.

CUSTOMER SUPPORTUsers 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 included in the back of this docu-ment.

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

http://www.microchip.com




AN1962

Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Micro-chip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.

Trademarks

The Microchip name and logo, the Microchip logo, dsPIC, FlashFlex, flexPWR, JukeBlox, KEELOQ, KEELOQ logo, Kleer, LANCheck, MediaLB, MOST, MOST logo, MPLAB, OptoLyzer, PIC, PICSTART, PIC32 logo, RightTouch, SpyNIC, SST, SST Logo, SuperFlash and UNI/O are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.

The Embedded Control Solutions Company and mTouch are registered trademarks of Microchip Technology Incorporated in the U.S.A.

Analog-for-the-Digital Age, BodyCom, chipKIT, chipKIT logo, CodeGuard, dsPICDEM, dsPICDEM.net, ECAN, In-Circuit Serial Programming, ICSP, Inter-Chip Connectivity, KleerNet, KleerNet logo, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, RightTouch logo, REAL ICE, SQI, Serial Quad I/O, Total Endurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA are trademarks 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 of Microchip Technology Inc., in other countries.

All other trademarks mentioned herein are property of their respective companies.

© 2015, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.

ISBN: 978-1-63277-514-6

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 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.

Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures 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.


AMERICASCorporate Office2355 West Chandler Blvd.Chandler, AZ 85224-6199Tel: 480-792-7200 Fax: 480-792-7277Technical Support: http://www.microchip.com/supportWeb Address: www.microchip.comAtlantaDuluth, GA Tel: 678-957-9614 Fax: 678-957-1455Austin, TXTel: 512-257-3370 BostonWestborough, MA Tel: 774-760-0087 Fax: 774-760-0088ChicagoItasca, IL Tel: 630-285-0071 Fax: 630-285-0075ClevelandIndependence, OH Tel: 216-447-0464 Fax: 216-447-0643DallasAddison, TX Tel: 972-818-7423 Fax: 972-818-2924DetroitNovi, MI Tel: 248-848-4000Houston, TX Tel: 281-894-5983IndianapolisNoblesville, IN Tel: 317-773-8323Fax: 317-773-5453Los AngelesMission Viejo, CA Tel: 949-462-9523 Fax: 949-462-9608New York, NY Tel: 631-435-6000San Jose, CA Tel: 408-735-9110Canada - TorontoTel: 905-673-0699 Fax: 905-673-6509

ASIA/PACIFICAsia 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-7000 Fax: 86-10-8528-2104China - ChengduTel: 86-28-8665-5511Fax: 86-28-8665-7889China - ChongqingTel: 86-23-8980-9588Fax: 86-23-8980-9500China - HangzhouTel: 86-571-8792-8115 Fax: 86-571-8792-8116China - Hong Kong SARTel: 852-2943-5100 Fax: 852-2401-3431China - NanjingTel: 86-25-8473-2460Fax: 86-25-8473-2470China - QingdaoTel: 86-532-8502-7355Fax: 86-532-8502-7205China - ShanghaiTel: 86-21-5407-5533 Fax: 86-21-5407-5066China - ShenyangTel: 86-24-2334-2829Fax: 86-24-2334-2393China - ShenzhenTel: 86-755-8864-2200 Fax: 86-755-8203-1760China - WuhanTel: 86-27-5980-5300Fax: 86-27-5980-5118China - XianTel: 86-29-8833-7252Fax: 86-29-8833-7256China - XiamenTel: 86-592-2388138 Fax: 86-592-2388130China - ZhuhaiTel: 86-756-3210040 Fax: 86-756-3210049

ASIA/PACIFICIndia - BangaloreTel: 91-80-3090-4444 Fax: 91-80-3090-4123India - New DelhiTel: 91-11-4160-8631Fax: 91-11-4160-8632India - PuneTel: 91-20-3019-1500Japan - OsakaTel: 81-6-6152-7160 Fax: 81-6-6152-9310Japan - TokyoTel: 81-3-6880- 3770 Fax: 81-3-6880-3771Korea - DaeguTel: 82-53-744-4301Fax: 82-53-744-4302Korea - SeoulTel: 82-2-554-7200Fax: 82-2-558-5932 or 82-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-8600 Fax: 886-2-2508-0102Thailand - BangkokTel: 66-2-694-1351Fax: 66-2-694-1350

EUROPEAustria - WelsTel: 43-7242-2244-39Fax: 43-7242-2244-393Denmark - CopenhagenTel: 45-4450-2828 Fax: 45-4485-2829France - ParisTel: 33-1-69-53-63-20 Fax: 33-1-69-30-90-79Germany - DusseldorfTel: 49-2129-3766400Germany - MunichTel: 49-89-627-144-0 Fax: 49-89-627-144-44Germany - PforzheimTel: 49-7231-424750Italy - Milan Tel: 39-0331-742611 Fax: 39-0331-466781Italy - VeniceTel: 39-049-7625286 Netherlands - DrunenTel: 31-416-690399 Fax: 31-416-690340Poland - WarsawTel: 48-22-3325737 Spain - MadridTel: 34-91-708-08-90Fax: 34-91-708-08-91Sweden - StockholmTel: 46-8-5090-4654UK - WokinghamTel: 44-118-921-5800Fax: 44-118-921-5820

Worldwide Sales and Service

01/30/15

http://support.microchip.com


SEC1110/SEC1210 Linux Setup - Microchip...

Documents

Transcript of SEC1110/SEC1210 Linux Setup - Microchip...