PIC18F25J50-I/SO Microchip Technology, PIC18F25J50-I/SO Datasheet - Page 13

• Manufacturer Part Number: PIC18F25J50-I/SO
• Description: IC PIC MCU FLASH 32K 2V 28-SOIC
• Manufacturer: Microchip Technology
• Series: PIC® XLP™ 18Fr

Specifications of PIC18F25J50-I/SO

• Program Memory Type: FLASH
• Program Memory Size: 32KB (16K x 16)
• Package / Case: 28-SOIC (7.5mm Width)
• Core Processor: PIC
• Core Size: 8-Bit
• Speed: 48MHz
• Connectivity: I²C, SPI, UART/USART, USB
• Peripherals: Brown-out Detect/Reset, DMA, POR, PWM, WDT
• Number Of I /o: 16
• Ram Size: 3.8K x 8
• Voltage - Supply (vcc/vdd): 2.15 V ~ 3.6 V
• Data Converters: A/D 10x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Processor Series: PIC18F
• Core: PIC
• Data Bus Width: 8 bit
• Data Ram Size: 3776 B
• Interface Type: EUSART, I2C, SPI
• Maximum Clock Frequency: 48 MHz
• Number Of Timers: 5
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• 3rd Party Development Tools: 52715-96, 52716-328, 52717-734, 52712-325, EWPIC18
• Development Tools By Supplier: PG164130, DV164035, DV244005, DV164005, PG164120, DM183022, DM183032, DV164136, MA180024
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 10 bit, 10 Channel
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: AC164322 - MODULE SOCKET MPLAB PM3 28/44QFN
• Eeprom Size: -
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

Microchip USB Device Firmware Framework User’s Guide
DS51679B-page 9
• USB_PING_PONG_MODE defines the Ping-Pong Buffer mode to be used during
• USB_USE_CLASS is used to indicate which USB classes should be included in
• USE_USB_BUS_SENSE_IO indicates that the firmware will use the pin defined in
• USE_SELF_POWER_SENSE_IO indicates that the microcontroller is sensing the
• USB_MAX_EP_NUMBER must equal the highest endpoint number used in the proj-
• USB_DEVICE_DESCRIPTOR is the name of the ROM variable that contains the
• USB_CONFIG_DESCRIPTOR is the name of the ROM variable that contains the
In addition to the options listed above, there may be additional definitions required in
usb_config.h in order to run certain USB class code with the Framework. Please refer
to the documentation for each class in order to determine the definitions that are required.
run time. The function of each mode is explained in the USB chapter of the device
data sheet. The options for this setting are:
USB_PING_PONG__NO_PING_PONG
USB_PING_PONG__EP0_OUT_ONLY
USB_PING_PONG__FULL_PING_PONG
USB_PING_PONG__ALL_BUT_EP0
Not all of these settings may be available for every device. Please check with the
appropriate device data sheet.
the code project. The options for this setting are the USB classes with class-spe-
cific header files implemented in the Framework, including (among others):
UBS_USE_CDC
USB_USE_GEN
USB_USE_HID
USB_USE_MSD
When one or more of these are defined, it tells the USB global header file, usb.h,
which class-specific header files to include. The usb.h header is used globally as
the necessary include file when using the USB library. If the HID class is used,
then hid.c and hid.h should also be added to the MPLAB IDE project. If the
CDC class is used, then cdc.c and cdc.h should also be added to the MPLAB
IDE project.
HardwareProfile.h to determine when to enable the USB module. If the target
board design does not use an I/O pin to detect the presence of the USB bus, this
definition must be commented out.
When USE_USB_BUS_SENSE_IO is undefined, the USB module will always be
enabled. Using this feature helps to improve the power efficiency of the system
because the USB module is only enabled when the bus is present. Additionally, in
order for the device to pass USB compliance certification, all self-powered
devices are required to support a bus sense feature. Self-powered devices which
do not implement this feature will fail the back drive voltage tests. The USB speci-
fications require that devices should not source current on D+ or D- (and never
V
will not know when the host is actively powering V
to enable the D+ or D- pull-up resistor) unless a bus sense feature is
implemented. Purely bus-powered devices do not need to implement this feature
and this feature may be commented out.
presence of on-board power through an I/O pin. If the target board design does
not use an I/O pin to detect the presence of self-power, this definition must be
commented out.
ect. For example, if the highest endpoint number used is Endpoint 5, then
USB_MAX_EP_NUMBER should equal five. This definition is used mainly in the
usbmmap.c to allocate the buffer descriptor registers.
device descriptor information.
configuration descriptor information.
BUS
) unless the host is actively powering the V
BUS
BUS
line. A self-powered device
(and when it is acceptable
© 2008 Microchip Technology Inc.