Note the following details of the code protection feature on Microchip devices:
YSTEM
CERTIFIE DBYDNV
== ISO/TS16949==
•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.
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 T O THE INFORMATION, INCLUDING B UT 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 Microchip 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, AnyRate, AVR, AVR logo, AVR Freaks, BeaconThings, BitCloud, CryptoMemory, CryptoRF,
dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KEELOQ, KEELOQ logo, Kleer, LANCheck, LINK MD, maXStylus , maXT ouch, Med iaLB, megaA VR,
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 of Microchip Technology Incorporated in the U.S.A. and
other countries.
ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight Load, IntelliMOS, mTouch, Precision
Edge, and Quiet-Wire are registered trademarks of Microchip Technology 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 Serial Programming, ICSP, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, Mindi, MiWi, motorBench,
MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit,
PICtail, PureSilicon, QMatrix, RightTouch logo, REAL ICE, Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher,
SuperSwitcher II, 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
DS50002604A-page 2 2017 Microchip Technology Inc.
Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
T empe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’ s q uality syst em for th e de si gn
and manufacture of development systems is ISO 9001:2000 certified.
®
MCUs and dsPIC® DSCs, KEELOQ
®
code hopping
EU Declaration of Conformity
This declaration of conformity is issued by the manufacturer.
The development/evaluation tool is designed to be used for research and development in a laboratory environment. This
development/evaluation tool is not a Finished Appliance, nor is it intended for incorporation into Finished Appliances that are made
commercially available as single functional units to end users under EU EMC Directive 2004/108/EC and as supported by the European
Commission's Guide for 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 in compliance with the essential
requirement and other relevant provisions of the R&TTE Directive 1999/5/EC and the FCC rules as stated in the declaration of conformity
provided in the module datasheet and the module product page available at www.microchip.com.
For information regarding the exclusive, limited warranties applicable to Microchip products, please see Microchip’s standard terms and
conditions of sale, which are printed on our sales documentation and available at www.microchip.com.
Signed for and on behalf of Microchip Technology Inc. at Chandler, Arizona, USA.
DS50002604A-page 6 2017 Microchip Technology Inc.
EVB-LAN9252-SPI
QUICK START
GUIDE
Preface
NOTICE TO CUSTOMERS
All documentation becomes dated, and this manual is no exception. Microchip tools and
documentation are constantly evolving to meet customer needs, so some actual dialogs
and/or tool descriptions may differ from those in this document. Please refer to our web site
(www.microchip.com) to obtain the latest documentation available.
Documents are identified with a “DS” number. This number is located on the bottom of each
page, in front of the page number. The numbering convention for the DS number is
“DSXXXXXA”, where “XXXXX” is the document number and “A” is the revision level of the
document.
For the most up-to-date information on development tools, see the MPLAB
Select the Help menu, and then Topics to open a list of available online help files.
®
IDE online help.
INTRODUCTION
This chapter contains general information that will be useful to know before using and
configuring the EVB-LAN9252-SPI. Items discussed in this chapter include:
• Document Layout
• Conventions Used in this Guide
• The Microchip Web Site
• Development Systems Customer Change Notification Service
• Customer Support
• Document Revision History
DOCUMENT LAYOUT
This document describes how to configure the EVB-LAN9252-SPI, such as the DIGIO
and SPI, as well as various setup options, scanning, and programming. The manual
layout is as follows:
• Chapter 1. “Overview” – Shows a brief description of the EVB-LAN9252-SPI
board quick setup.
• Chapter 2. “EVB-LAN9252-SPI” – Provides instructions in configuring SPI.
• Appendix A. “EVB-LAN9252-SPI Evaluation Board Schematics” – This
appendix shows how to set up Master in Windows.
Choice of mutually exclusive
arguments; an OR selection
Represents code supplied by
user
errorlevel {0|1}
var_name...]
void main (void)
{ ...
}
DS50002604A-page 8 2017 Microchip Technology Inc.
Preface
THE MICROCHIP WEB SITE
Microchip provides online support via our web 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 contains 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 (FAQs), 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 factory representatives
DEVELOPMENT SYSTEMS CUSTOMER CHANGE NOTIFICATION SERVICE
Microchip’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 de velopment tool of
interest.
To register, access the Microchip web site at www.microchip.com, click on Customer
Change Notification and follow the registration instructions.
The Development Systems product group categories are:
• Compilers – The latest information on Microchip C compilers, assemblers, linkers
and other language tools. These include all MPLAB C compilers; all MPLAB
assemblers (including MPASM assembler); all MPLAB linkers (including MPLINK
object linker); and all MPLAB librarians (including MPLIB object librarian).
• Emulators – The latest information on Microchip in-circuit emulators.This
includes the MPLAB REAL ICE and MPLAB ICE 2000 in-circuit emulators.
• In-Circuit Debuggers – The latest information on the Microchip in-circuit
debuggers. This includes MPLAB ICD 3 in-circuit debuggers and PICkit 3 debug
express.
• MPLAB IDE – The latest information on Microchip MPLAB IDE, the Windows
Integrated Development Environment for development systems tools. This list is
focused on the MPLAB IDE, MPLAB IDE Project Manager, MPLAB Editor and
MPLAB SIM simulator, as well as general editing and debugging features.
• Programmers – The latest information on Microchip programmers. These include
production programmers such as MPLAB REAL ICE in-circuit emulator, MPLAB
ICD 3 in-circuit debugger and MPLAB PM3 device programmers. Also included
are nonproduction development programmers such as PICSTART Plus and
PIC-kit 2 and 3.
CUSTOMER SUPPORT
Users of Microchip products can receive assistance through several channels:
Customers should contact their distributor , representative or field application e ngineer
(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 document.
Technical support is available through the web site at:
http://www.microchip.com/support
DOCUMENT REVISION HISTORY
RevisionsSection/Figure/EntryCorrection
DS50002604A (05-30-17)Initial release of document
DS50002604A-page 10 2017 Microchip Technology Inc.
1.1INTRODUCTION
The EVB-LAN9252-SPI board is intended to be a generic interface to many third party
processors used in EtherCA T Slave applications. The EVB-LAN9252-SPI is designed
to be a simple interface to the SPI port, with test points for power and ground. The evaluation board uses standard RJ45 connectors to connect to the EtherCAT system and
can be used to begin software developmen t of th e Eth er CAT Slave code before the
final hardware is completed.
1.1.1References
The following documents should be referenced when using this quick start g uide. See
your Microchip representative for availability.
DS50002604A-page 12 2017 Microchip Technology Inc.
Chapter 2. EVB-LAN9252-SPI
2.1EVB-LAN9252-SPI BOARD DESIGN
This section is an overview of the EVB-LAN9252-SPI board design and interface. The
board is intended to provide an interface to the SPI port of a microcontroller development platform.
FIGURE 2-1:EVB-LAN9252-SPI TOP VIEW
EVB-LAN9252-SPI
QUICK START
GUIDE
2.1.1SPI Headers
The four signals used for SPI communication with LAN9252 are exposed via he ade rs
(J4-J7). These can direct the signals to the conne ctor J3 as HBI or SPI, or be u sed to
fly-wire SPI between boards.
• J4 is connected to pin 19 of LAN9252. Connect a jumper between pi ns 1 and 2 to
route the signal to the D9 pin of J3. Jump er p ins 2 an d 3 to conn ect the signal to
pin SCK of J3. Altern atively, remove the jumper and wire the SPI Clock directly to
pin 2 of this header.
• J5 is connected to pin 50 of the LAN9252. Connect a jumper between pins 1 and
2 to route the signal to the D5 pin of J3. Jumper pins 2 and 3 to connect the signal
to pin SCS# of J3. Alternatively, remove the jumper and wire the SPI Chip Select
directly to pin 2 of this header.
• J6 is connected to pin 13 of the LAN9252. Connect a jumper between pins 1 and
2 to route the signal to the D1 pin of J3. Jumper pins 2 and 3 to connect the signal
to pin S0 of J3. Alternatively, remove the jumper and wire the SPI Slave Data Out
(SPI Master In) directly to pin 2 of this header.
• J7 is connected to pin 17 of the LAN9252. Connect a jumper between pins 1 and
2 to route the signal to the D0 pin of J3. Jumper pins 2 and 3 to connect the signal
to pin SI of J3. Alternatively, remove the jumper and wire the SPI Slave Data In
(SPI Master Out) directly to pin 2 of this header.
When connected to a compatible development system through J3, the power test
points are to be used to confirm a proper voltage is present on the boa rd. When wiring
the board to an external development board, the p ower test points are used to connect
an external power supply to the board.
• TP2 is tied to the 3.3V supply for the LAN9252 and the EEPROM for configuration.
• TP3 is tied to the GND plane of the board. Additional GND access can be found
on J8 and J9.
2.1.3Digital Interface Connector
EVB-LAN9252-SPI also has a mass interface connector on the bottom of the board.
This interface is used to connect many of the LAN9252 signals to third party development platforms. These pins enable evaluation of HBI and SPI abstraction using
LAN9252. LAN9252 must also be configured with the correct ESI (EtherCAT Slave
Information) via EEPROM for these signals to be active.
FIGURE 2-2:EVB-LAN9252-SPI BOTTOM VIEW
2.2INTERFACING WITH A THIRD PARTY PROCESSOR VIA SPI
The EVB-LAN9252-SPI can be connected to any microprocessor development platform with exposed SPI pins. Once the pins have been connected properly, software
development can begin. The process can be broken down into three steps:
2.2.1Connect pins
1. Connect the SPI pins to J4-J7.
2. Connect to Power T e st Points to a bench supply , or 3.3V supply on the processor
board. Connect GND to TP3 and 3.3V to TP2.
DS50002604A-page 14 2017 Microchip Technology Inc.
EVB-LAN9252-SPI
2.2.2Configure Slave Software
There are four ways to program the processor to act as an EtherCA T Slave Device. The
different methods have different degrees of development needed to get to a solution
ready for the next stage in the process.
• When using an existing EtherCAT Slave solution, refer to the LAN9252 Migration
guide for details on how to replace the existing ET1100 interface libraries with the
LAN9252 equivalent. All other code can remain the same.
• When using a processor with a LAN9252 SDK, the Slave Source Code (SSC) tool
from Beckhoff can be used to automatically generate Ethe rCAT Slave code. In the
SDK are template files that are used to speed the process along. Refer to the
LAN9252 product page for the latest SDKs in the software library section.
•The EVB-LAN9252_HBIPLUS_SDK_V1.3 is an example of an SDK that has tem-
plate libraries to help with development.
• When using a processor that only has LAN9252 drivers, the Slave Source Code
tool can still be used. There will not be template files for faster development, and
the developer will need to manually add the LAN9252 driver files into the SSC and
develop the processor specific interface code to the necessary peripherals used.
-The LAN9252_C2000_Drivers_V1.0 is an example of the drivers provided
for the LAN9252.
• When using a processor without any drivers, the developer will need to develop
both the LAN9252 SPI interface libraries as well as the processor specific interface code to the peripherals used.
2.2.3Configure System from EtherCAT Master
Once the Slave Source Code has been developed and programmed onto the processor, the LAN9252 can be connected to an EtherCAT Master. Use the ESI files and
EEPROM configuration settings to properly set up the LAN9252 for the desired digital
communication. Debug and test the Slave code in the full EtherCAT development environment.
Note:
Capacitors C23 through C26 are optional for
EMI purposes and are not populated in this
board. These capacitors are required for
p
Note:
Capacitors C29 through C32 are optional for
EMI purposes and are not populated in this
board. These capacitors are required for
operation in an EMI constrained environment.
p
0R
1210
5%
R13
0R
1210
5%
R23
Copper Port-A(IN)
Copper Port-B(OUT)
"RUN"
A0
1
SDA
5
A2
3
A1
2
WP
7
VSS
4
SCL
6
VCC
8
24FC512
U2
XMIT
RCV
75
7575
1000pF2kV
RJ45
1
4&5
2
3
7&8
6
75
GRN
YEL
RCV
75
75
75
1000
F
2
V
RJ
45
4 & 5
675G
RN
L
RD+
3
RXCT
5
RD-
6
TD+
1
TXCT
4
TD-
2
CHS GND
8
GND13GND114MTG15MTG1
16
NC
7
C
10
A
9
C1
11
A1
12
J1
XMIT
RCV
75
7575
1000pF2kV
RJ45
1
4&5
2
3
7&8
6
75
GRN
YEL
RCV
75
75
75
F
RJ
4
4 & 5
2
6
75
G
RNYEL
RD+
3
RXCT
5
RD-
6
TD+
1
TXCT
4
TD-
2
CHS GND
8
GND13GND114MTG15MTG1
16
NC
7
C
10
A
9
C1
11
A1
12
J2
FIGURE A-2:LAN CONNECTORS, STRAP & EEPROM
operation in an EMI constrained environment.
MI
3
7 & 8
k
YE
5
1
3
7 & 8
k
p
1000 p
DS50002604A-page 20 2017 Microchip Technology Inc.