Xilinx is providing this product documentation, hereinafter “Information,” to you “AS IS” with no warranty of any kind, express or implied.
Xilinx makes no representation that the Information, or any particular implementation thereof, is free from any claims of infringement. You
are responsible for obtaining any rights you may require for any implementation based on the Information. All specifications are subject to
change without notice.
XILINX EXPRESSLY DISCLAIMS ANY WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF THE INFORMATION OR
ANY IMPLEMENTATION BASED THEREON, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR REPRESENTATIONS THAT
THIS IMPLEMENTATION IS FREE FROM CLAIMS OF INFRINGEMENT AND ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Except as stated herein, none of the Information may be copied, reproduced, distributed, republished, downloaded, displayed, posted, or
transmitted in any form or by any means including, but not limited to, electronic, mechanical, photocopying, recording, or otherwise, without
the prior written consent of Xilinx.
The CAN v3.2 Getting Started Guide provides information about generating the
LogiCORE™ IP CAN core, customizing and simulating the core with the provided
example design, and running the design files through implementation using the Xilinx
tools.
Guide Contents
The following chapters are included in this guide:
•Preface, “About This Guide” introduces the organization and purpose of this Getting
Started Guide and the conventions used in this document.
•Chapter 1, “Introduction” describes the core and related information, including
recommended design experience, additional resources, technical support, and
submitting feedback to Xilinx.
•Chapter 2, “Licensing the Core” provides information about licensing the core.
•Chapter 3, “Quick Start Example Design” provides instructions to quickly generate
the core and run the example design through implementation and simulation.
•Chapter 4, “Detailed Example Design”describes the demonstration test bench in
detail and provides instructions for how to customize the demonstration test bench
for use in an application.
Preface
Conventions
This document uses the following conventions. An example illustrates each convention.
Typographical
The following typographical conventions are used in this document:
ConventionMeaning or UseExample
Messages, prompts, and
Courier font
Courier bold
Helvetica bold
CAN Getting Started Guidewww.xilinx.com7
UG186 April 19, 2010
program files that the system
displays. Signal names also.
Literal commands you enter in a
syntactical statement
Commands that you select from
a menu
Keyboard shortcutsCtrl+C
speed grade: - 100
ngdbuilddesign_name
File → Open
Preface: About This Guide
ConventionMeaning or UseExample
Variables in a syntax statement
for which you must supply
values
ngdbuild design_name
Italic font
Dark Shading
Square brackets [ ]
Braces { }
Vertical bar |
Angle brackets < >
Vertical ellipsis
.
.
.
References to other manualsSee the User Guide for details.
If a wire is drawn so that it
Emphasis in text
Items that are not supported or
reserved
An optional entry or parameter.
However, in bus specifications,
such as bus[7:0], they are
required.
A list of items from which you
must choose one or more
Separates items in a list of
choices
User-defined variable or in code
samples
Repetitive material that has
been omitted
overlaps the pin of a symbol, the
two nets are not connected.
This feature is not supported
ngdbuild [option_name]
design_name
lowpwr ={on|off}
lowpwr ={on|off}
<directory name>
IOB #1: Name = QOUT’
IOB #2: Name = CLKIN’
.
.
.
Horizontal ellipsis . . .Omitted repetitive material
Notations
Online Document
The following linking conventions are used in this document:
ConventionMeaning or UseExample
Blue text
Blue, underlined text
The prefix ‘0x’ or the suffix ‘h’
indicate hexadecimal notation
An ‘_n’ means the signal is
active low
Cross-reference link to a
location in the current
document
Hyperlink to a website (URL)
allow block block_name loc1
loc2 ... locn;
A read of address 0x00112975
returned 45524943h.
usr_teof_n is active low.
See the section “Guide
Contents” for details.
See “Title Formats” in Chapter 1
for details.
Go to www.xilinx.com
latest speed files.
for the
8www.xilinx.comCAN Getting Started Guide
UG186 April 19, 2010
Introduction
The LogiCORE™ IP CAN v3.2 core is a compact, full-featured targeted design platform
that conforms to ISO 11898-1, CAN2.0A and CAN2.0B standards. Bit rates of up to 1 Mbps
are supported. The core size can be optimized using parameterized configurations for
acceptance filtering and FIFO depth. The example design in this guide is provided in both
Ver il o g a nd VH DL .
This chapter introduces the CAN core and provides related information, including system
requirements, recommended design experience, additional resources, technical support,
and submitting feedback to Xilinx.
About the Core
The CAN core is a Xilinx CORE Generator™ IP core, included in the latest IP Update on the
Xilinx IP Center. For detailed information about the core, see