IC DSPIC MCU/DSP 144K 64TQFP

 

DSPIC30F6012A-20E/PT

Manufacturer Part NumberDSPIC30F6012A-20E/PT
DescriptionIC DSPIC MCU/DSP 144K 64TQFP
ManufacturerMicrochip Technology
SeriesdsPIC™ 30F
DSPIC30F6012A-20E/PT datasheets

Availability: In stock

International delivery:

Warranty: 60 days

Shipping & payment terms

Added to cart

 

Specifications of DSPIC30F6012A-20E/PT

Program Memory TypeFLASHProgram Memory Size144KB (48K x 24)
Package / Case64-TFQFPCore ProcessordsPIC
Core Size16-BitSpeed20 MIPS
ConnectivityCAN, I²C, SPI, UART/USARTPeripheralsAC'97, Brown-out Detect/Reset, I²S, LVD, POR, PWM, WDT
Number Of I /o52Eeprom Size4K x 8
Ram Size8K x 8Voltage - Supply (vcc/vdd)2.5 V ~ 5.5 V
Data ConvertersA/D 16x12bOscillator TypeInternal
Operating Temperature-40°C ~ 125°CProductDSCs
Data Bus Width16 bitProcessor SeriesDSPIC30F
CoredsPICMaximum Clock Frequency20 MHz
Number Of Programmable I/os52Data Ram Size8 KB
Maximum Operating Temperature+ 125 CMounting StyleSMD/SMT
3rd Party Development Tools52713-733, 52714-737, 53276-922, EWDSPICDevelopment Tools By SupplierPG164130, DV164035, DV244005, DV164005, PG164120, ICE4000, DM240002, DM330011
Minimum Operating Temperature- 40 CPackage64TQFP
Device CoredsPICFamily NamedsPIC30
Maximum Speed20 MHzOperating Supply Voltage3.3|5 V
Interface TypeCAN/I2C/SPI/UARTOn-chip Adc16-chx12-bit
Number Of Timers5Lead Free Status / RoHS StatusLead free / RoHS Compliant
For Use WithAC30F008 - MODULE SKT FOR DSPIC30F 64TQFP  
1
Page 1
2
Page 2
3
Page 3
4
Page 4
5
Page 5
6
Page 6
7
Page 7
8
Page 8
9
Page 9
10
Page 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
Page 6/66

Download datasheet (2Mb)Embed
PrevNext
5.2
Entering Enhanced ICSP Mode
The Enhanced ICSP mode is entered by holding PGC
and PGD high, and then raising MCLR/V
(high voltage), as illustrated in
Figure
5-2. In this mode,
the code memory, data EEPROM and Configuration
bits can be efficiently programmed using the program-
ming executive commands that are serially transferred
using PGC and PGD.
FIGURE 5-2:
ENTERING ENHANCED
ICSP™ MODE
P6
P7
V
IHH
MCLR/V
PP
V
DD
PGD
PGC
PGD = Input
Note 1: The sequence that places the device into
Enhanced ICSP mode places all unused
I/Os in the high-impedance state.
2: Before entering Enhanced ICSP mode,
clock switching must be disabled using
ICSP, by programming the FCKSM<1:0>
bits in the FOSC Configuration register to
‘11’ or ‘10’.
3: When in Enhanced ICSP mode, the SPI
output pin (SDO1) will toggle while the
device is being programmed.
DS70102K-page 6
5.3
Chip Erase
Before a chip can be programmed, it must be erased.
to V
The Bulk Erase command (ERASEB) is used to perform
PP
IHH
this task. Executing this command with the MS
command field set to 0x3 erases all code memory, data
EEPROM and code-protect Configuration bits. The
Chip Erase process sets all bits in these three memory
regions to ‘1’.
Since non-code-protect Configuration bits cannot be
erased, they must be manually set to ‘1’ using multiple
PROGC commands. One PROGC command must be
sent for each Configuration register (see
“Configuration Bits
If Advanced Security features are enabled, then indi-
vidual Segment Erase operations would need to be
performed, depending on which segment needs to be
programmed at a given stage of system programming.
The user should have the flexibility to select specific
segments for programming.
Note:
The Device ID registers cannot be erased.
These registers remain intact after a Chip
Erase is performed.
5.4
Blank Check
The term “Blank Check” means to verify that the device
has been successfully erased and has no programmed
memory cells. A blank or erased memory cell reads as
‘1’. The following memories must be blank checked:
• All implemented code memory
• All implemented data EEPROM
• All Configuration bits (for their default value)
The Device ID registers (0xFF0000:0xFF0002) can be
ignored by the Blank Check since this region stores
device information that cannot be erased. Additionally,
all unimplemented memory space should be ignored
from the Blank Check.
The QBLANK command is used for the Blank Check. It
determines if the code memory and data EEPROM are
erased by testing these memory regions. A ‘BLANK’ or
‘NOT BLANK’ response is returned. The READD
command is used to read the Configuration registers. If
it is determined that the device is not blank, it must be
erased (see
Section 5.3 “Chip
attempting to program the chip.
Section 5.7
Programming”).
Erase”) before
© 2010 Microchip Technology Inc.