DSPIC30F6010A-20E/PT Microchip Technology, DSPIC30F6010A-20E/PT Datasheet - Page 125

• Manufacturer Part Number: DSPIC30F6010A-20E/PT
• Description: IC,DSP,16-BIT,CMOS,TQFP,80PIN,PLASTIC
• Manufacturer: Microchip Technology
• Series: dsPIC™ 30Fr

Specifications of DSPIC30F6010A-20E/PT

• Rohs Compliant: YES
• Core Processor: dsPIC
• Core Size: 16-Bit
• Speed: 20 MIPS
• Connectivity: CAN, I²C, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, LVD, Motor Control PWM, QEI, POR, PWM, WDT
• Number Of I /o: 68
• Program Memory Size: 144KB (48K x 24)
• Program Memory Type: FLASH
• Eeprom Size: 4K x 8
• Ram Size: 8K x 8
• Voltage - Supply (vcc/vdd): 2.5 V ~ 5.5 V
• Data Converters: A/D 16x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 125°C
• Package / Case: 80-TFQFP
• Package: 80TQFP
• Device Core: dsPIC
• Family Name: dsPIC30
• Maximum Speed: 20 MHz
• Operating Supply Voltage: 3.3|5 V
• Data Bus Width: 16 Bit
• Number Of Programmable I/os: 68
• Interface Type: CAN/I2C/SPI/UART
• On-chip Adc: 16-chx10-bit
• Number Of Timers: 5
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: DM300019 - BOARD DEMO DSPICDEM 80L STARTERXLT80PT3 - SOCKET TRAN ICE 80MQFP/TQFPAC164320 - MODULE SKT MPLAB PM3 80TQFPAC30F007 - MODULE SKT FOR DSPIC30F 80TQFPDM300020 - BOARD DEV DSPICDEM MC1 MOTORCTRL
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

19.0
19.1
The Controller Area Network (CAN) module is a serial
interface, useful for communicating with other CAN
modules
interface/protocol was designed to allow communica-
tions within noisy environments. The dsPIC30F6010A
has two CAN modules. The dsPIC30F6015 has only
one.
The CAN module is a communication controller
implementing the CAN 2.0 A/B protocol, as defined in
the BOSCH specification. The module will support
CAN 1.2, CAN 2.0A, CAN2.0B Passive and CAN 2.0B
Active
implementation is a full CAN system. The CAN
specification is not covered within this data sheet. The
reader may refer to the BOSCH CAN specification for
further details.
The module features are as follows:
• Implementation of the CAN protocol CAN 1.2,
• Standard and extended data frames
• 0-8 bytes data length
• Programmable bit rate up to 1 Mbit/sec
• Support for remote frames
• Double-buffered receiver with two prioritized
• 6 full (standard/extended identifier) acceptance
• 2 full acceptance filter masks, one each associ-
• Three transmit buffers with application specified
• Programmable wake-up functionality with
• Programmable Loopback mode supports self-test
• Signaling via interrupt capabilities for all CAN
• Programmable clock source
• Programmable link to timer module for
© 2008 Microchip Technology Inc.
Note:
CAN 2.0A and CAN 2.0B
received message storage buffers (each buffer
may contain up to 8 bytes of data)
filters, 2 associated with the high priority receive
buffer, and 4 associated with the low priority
receive buffer
ated with the high and low priority receive buffers
prioritization and abort capability (each buffer may
contain up to 8 bytes of data)
integrated low-pass filter
operation
receiver and transmitter error states
time-stamping and network synchronization
versions
CAN MODULE
Overview
This data sheet summarizes features of
this group of dsPIC30F devices and is not
intended to be a complete reference
source. For more information on the CPU,
peripherals, register descriptions and
general device functionality, refer to the
“dsPIC30F Family Reference Manual”
(DS70046).
or
microcontroller
of
the
protocol.
devices.
The
module
This
dsPIC30F6010A/6015
• Low-Power Sleep and Idle mode
The CAN bus module consists of a protocol engine,
and message buffering/control. The CAN protocol
engine handles all functions for receiving and
transmitting messages on the CAN bus. Messages are
transmitted by first loading the appropriate data
registers. Status and errors can be checked by reading
the appropriate registers. Any message detected on
the CAN bus is checked for errors and then matched
against filters to see if it should be received and stored
in one of the receive registers.
19.2
The CAN module transmits various types of frames,
which include data messages or remote transmission
requests initiated by the user as other frames that are
automatically generated for control purposes. The
following frame types are supported:
• Standard Data Frame
A Standard Data Frame is generated by a node when
the node wishes to transmit data. It includes a 11-bit
Standard Identifier (SID), but not an 18-bit Extended
Identifier (EID).
• Extended Data Frame
An Extended Data Frame is similar to a Standard Data
Frame, but includes an Extended Identifier as well.
• Remote Frame
It is possible for a destination node to request the data
from the source. For this purpose, the destination node
sends a Remote Frame with an identifier that matches
the identifier of the required Data Frame. The
appropriate data source node will then send a Data
Frame as a response to this remote request.
• Error Frame
An Error Frame is generated by any node that detects
a bus error. An error frame consists of 2 fields: an Error
Flag field and an Error Delimiter field.
• Overload Frame
An Overload Frame can be generated by a node as a
result of 2 conditions. First, the node detects a
dominant bit during lnterframe Space, which is an
illegal condition. Second, due to internal conditions, the
node is not yet able to start reception of the next
message. A node may generate a maximum of 2
sequential Overload Frames to delay the start of the
next message.
• Interframe Space
Interframe Space separates a proceeding frame (of
whatever type) from a following Data or Remote
Frame.
Frame Types
DS70150D-page 125