PIC18F44J50-I/PT Microchip Technology, PIC18F44J50-I/PT Datasheet - Page 16

• Manufacturer Part Number: PIC18F44J50-I/PT
• Description: IC PIC MCU FLASH 16K 2V 44-TQFP
• Manufacturer: Microchip Technology
• Series: PIC® XLP™ 18Fr

Specifications of PIC18F44J50-I/PT

• Program Memory Type: FLASH
• Program Memory Size: 16KB (8K x 16)
• Package / Case: 44-TQFP, 44-VQFP
• 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: 34
• Ram Size: 3.8K x 8
• Voltage - Supply (vcc/vdd): 2.15 V ~ 3.6 V
• Data Converters: A/D 13x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Processor Series: PIC18F
• Core: PIC
• Data Bus Width: 8 bit
• Data Ram Size: 16 KB
• Interface Type: EUSART, I2C, SPI
• Maximum Clock Frequency: 48 MHz
• Number Of Timers: 5
• Operating Supply Voltage: 2.25 V to 2.75 V
• 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, 13 Channel
• Controller Family/series: PIC18
• No. Of I/o's: 22
• Ram Memory Size: 3776Byte
• Cpu Speed: 48MHz
• No. Of Timers: 5
• Embedded Interface Type: EUSART, I2C, SPI
• Rohs Compliant: Yes
• Package: 44TQFP
• Device Core: PIC
• Family Name: PIC18
• Maximum Speed: 48 MHz
• A/d Bit Size: 10 bit
• A/d Channels Available: 13
• Height: 1 mm
• Length: 10 mm
• Supply Voltage (max): 3.6 V
• Supply Voltage (min): 2.15 V
• Width: 10 mm
• 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

© 2008 Microchip Technology Inc.
A USB project may have multiple strings. The firmware supports the management of
multiple strings through a look-up table, which is defined as:
ROM BYTE *ROM USB_SD_Ptr[]={&sd000,&sd001,&sd002};
The above example has 3 strings (sd000, sd001 and sd002). Strings can be removed
or added as needed. The strings are managed by the look-up table, USB_SD_Ptr; the
index of the string must match the index position of the array (&sd000 must be in
position, USB_SD_Ptr[0], and so on). The look-up table, USB_SD_Ptr, is used by the
USBStdGetDscHandler function in usb9.c. The string descriptor, sd000, is a
specialized descriptor that defines the language code, which is usually US English
(0x0409).
1.3.1.2.4
A USB device may have more than one configuration descriptor (e.g.,
configDescriptor2, configDescriptor3, etc.). To add another configuration
descriptor, implement a new set of structures, similar to configDescriptor1, to the
USBDescriptors.c file. Once this is done, add the new configuration descriptor
name (configDescriptor2, configDescriptor3) to the look-up table,
USB_CD_Ptr, in the same method used for managing descriptor strings.
USB_CD_Ptr[0] is a dummy place holder for configuration 0, the unconfigured
state defined by the USB specification. The configuration handler,
USBStdSetCfgHandler, must also be modified to support the additional
configurations.
1.3.1.3
This file is used to map the various demo board hardware setups to a common defini-
tion for the code to use. This defines which port pins LEDs are located on, the clock
speed of the demo board, etc. This file will also determine which demo board is cur-
rently being used by looking at the compiler that is compiling the project and the device
selected in MPLAB IDE. If a custom board is required, or if a modification is made to
one of the demo boards, then the DEMO_BOARD definition needs to be defined at the
top of HardwareProfile.h to indicate to the compiler that it is a custom board.
Custom boards may also require the addition of code for other features used by the
framework.
1.3.2
The Application Programming Interface (API) to the Framework is available in the doc-
umentation folder of the Framework distribution. This document provides a description
and examples of the functions required in order to use the Framework
HardwareProfile.h
Framework Folders
Adding Configurations
DS51679B-page 12