DSPIC30F3013-30I/SO Microchip Technology, DSPIC30F3013-30I/SO Datasheet - Page 12

IC DSPIC MCU/DSP 24K 28SOIC

DSPIC30F3013-30I/SO

Manufacturer Part Number
DSPIC30F3013-30I/SO
Description
IC DSPIC MCU/DSP 24K 28SOIC
Manufacturer
Microchip Technology
Series
dsPIC™ 30Fr

Specifications of DSPIC30F3013-30I/SO

Program Memory Type
FLASH
Program Memory Size
24KB (8K x 24)
Package / Case
28-SOIC (7.5mm Width)
Core Processor
dsPIC
Core Size
16-Bit
Speed
30 MIPs
Connectivity
I²C, SPI, UART/USART
Peripherals
Brown-out Detect/Reset, POR, PWM, WDT
Number Of I /o
20
Eeprom Size
1K x 8
Ram Size
2K x 8
Voltage - Supply (vcc/vdd)
2.5 V ~ 5.5 V
Data Converters
A/D 10x12b
Oscillator Type
Internal
Operating Temperature
-40°C ~ 85°C
Product
DSCs
Data Bus Width
16 bit
Processor Series
DSPIC30F
Core
dsPIC
Maximum Clock Frequency
30 MHz
Number Of Programmable I/os
30
Data Ram Size
2 KB
Maximum Operating Temperature
+ 85 C
Mounting Style
SMD/SMT
3rd Party Development Tools
52713-733, 52714-737, 53276-922, EWDSPIC
Development Tools By Supplier
PG164130, DV164035, DV244005, DV164005, PG164120, ICE4000, DM240002, DM300018, DM330011
Minimum Operating Temperature
- 40 C
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
For Use With
XLT28SO-1 - SOCKET TRANSITION 28SOIC 300MILDV164005 - KIT ICD2 SIMPLE SUIT W/USB CABLE
Lead Free Status / Rohs Status
Lead free / RoHS Compliant
Other names
DSPIC30F301330ISO

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
DSPIC30F3013-30I/SO
Manufacturer:
NSC
Quantity:
340
Part Number:
DSPIC30F3013-30I/SO
Manufacturer:
PIC
Quantity:
20 000
dsPIC30F3012/3013
12. Module: I
DS80448D-page 12
When the I
either in single-master or multi-master mode, the
I
address is detected or not. Therefore, an I
receiver overflow condition occurs and this
condition is indicated by the I2COV flag in the
I2CSTAT register.
This overflow condition inhibits the ability to set the
I
valid data byte is received. Therefore, the I
slave Interrupt Service Routine (ISR) is not called
and the I
receiving the next data byte.
Work arounds
To avoid this issue, either of the following two work
arounds can be implemented, depending on the
application requirements.
Work around 1:
For applications in which the I
is not required, the following procedure can be
used to receive valid data bytes:
1. Wait until the RBF flag is set.
2. Poll the I
3. If SI2CF is not set in the corresponding
4. If the SI2CF is set in the corresponding
5. Read the I2CRCV buffer to recover valid data
6. Clear the I
7. Go back to step 1 to continue receiving
2
2
C receiver buffer is filled whether a valid slave
C receive interrupt flag (SI2CF) when the last
Interrupt Flag Status register (IFSx), a valid
address or data byte has not been received for
the current slave. Execute a dummy read of
the I
the RBF flag. Go back to step 1 until SI2CF is
set and then continue to Step 4.
Interrupt Flag Status register (IFSx), valid data
has been received. Check the D_A flag to
verify that an address or a data byte has been
received.
bytes. This will also clear the RBF flag.
incoming data bytes.
2
C receiver buffer, I2CRCV; this will clear
2
2
C receiver buffer is not read prior
2
2
C
C module is configured as a slave,
C receiver interrupt SI2CIF flag.
2
C receiver interrupt flag SI2CF.
2
C receiver interrupt
2
2
C
C
Work around 2:
Use this work around for applications in which the
I
the RBF and the I2COV flags in the I2CSTAT
register are set due to previous data transfers in
the I2C bus (i.e., between master and other
slaves); the following procedure can be used to
receive valid data bytes:
1. When a valid slave address byte is detected,
2. Check the status of the D_A flag and the
3. If the D_A flag is cleared and the I2COV flag
4. Clear the I2COV flag and perform a dummy
5. Verify that the recovered address byte
6. If the D_A flag and the I2COV flag are both set,
Affected Silicon Revisions
2
C receiver interrupt is required. Assuming that
B0
X
SI2CF bit is set and the I
service routine is called; however, the RBF and
I2COV bits are already set due to data
transfers between other I
I2COV flag in the I2CSTAT register when
executing the I
are set, an invalid data byte was received but a
valid address byte was received. The overflow
condition occurred because the I
buffer was overflowing with previous I
transfers between other I
condition only occurs after a valid slave
address was detected.
read of the I
clear the RBF bit and recover the valid address
byte. This action will also avoid the loss of the
next data byte due to an overflow condition.
matches the current slave address byte. If they
match, the next data to be received is a valid
data byte.
a valid data byte was received and a previous
valid data byte was lost. It will be necessary to
code for handling this overflow condition.
B1
X
2
2
C receiver buffer, I2CRCV, to
C slave service routine.
© 2010 Microchip Technology Inc.
2
C nodes.
2
C slave interrupt
2
C nodes. This
2
C receive
2
C data

Related parts for DSPIC30F3013-30I/SO