DV164101 Microchip Technology, DV164101 Datasheet - Page 12

• Manufacturer Part Number: DV164101
• Description: KIT DEV PICKIT1 FLASH 8/14PIN
• Manufacturer: Microchip Technology
• Series: PICkit™ 1r
• Type: MCUr

Specifications of DV164101

• Contents: PIC Kit 1 Circuit Board, CD-ROMs, USB Interface Cable and Booklet
• Processor To Be Evaluated: PIC12F675
• Interface Type: USB
• Silicon Manufacturer: Microchip
• Core Architecture: PIC
• Core Sub-architecture: PIC12, PIC16
• Silicon Core Number: PIC12F, PIC16F
• Silicon Family Name: PIC12F6xx, PIC16F6xx
• Rohs Compliant: NA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With/related Products: Microchip's 8-14 Pin FLASH Microcontrollers
• For Use With: AC164122 - BOARD DAUGHT PICTAIL SD/MMC CARDAC164120 - BOARD SIGNAL ANALYSIS PICKIT
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: DV164101R; DV164101R

PICkit
DS40051D-page 8
™
1 Flash Starter Kit User’s Guide
2.2.1
To import a compiled program (hex file), select File > Import HEX , as shown in
Figure 2-2. Browse for the hex file and click Open.
FIGURE 2-2:
The code is displayed in the Program Memory and EEDATA Memory windows. (For
more information on Program and EEDATA memory, see Lesson 5 and Lesson 6 in
Appendix C. “PIC12F675 Programming Projects”.)
After the hex file is imported, write the program to the device by clicking the
Write Device button. The existing program will be erased and replaced with the new
one. The status of the program write is displayed in the status bar located at the bottom
of the interface window.
If the write is successful, the status bar turns green and displays “Write Successful”, as
shown in Figure 2-3.
FIGURE 2-3:
If the write fails, the status bar turns red and displays “Checksum verify failed”, as
shown in Figure 2-4. This error indicates the data was corrupted during the
programming sequence. If this error is displayed, try writing the program to the device
again. If this error continues, see Chapter 5. “Troubleshooting” for assistance.
FIGURE 2-4:
2.2.2
Prior to each write, the imported hex file time stamp is compared to the version on the
disk. If the version on the disk is newer, it is reloaded. This occurs only when a hex file
has been read from the disk.
In the normal mode of operation, the hex file is updated with every build in MPLAB IDE.
This ensures that the latest version built by MPLAB IDE will be written to the device.
Import HEX File
Automatic File Reload
IMPORT HEX FILE
WRITE SUCCESSFUL STATUS BAR
WRITE ERROR STATUS BAR
 2004 Microchip Technology Inc.