This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
PIC18F1XK22/LF1XK22
Flash Memory Programming Specification
1.0 DEVICE OVERVIEWThis document includes the programmingspecifications for the following devices:
2.0 PROGRAMMING OVERVIEWThe PIC18F1XK22/LF1XK22 devices can beprogrammed using either the high-voltage In-CircuitSerial Programming™ (ICSP™) method or the low-voltage ICSP method. Both methods can be done withthe device in the users’ system. The low-voltage ICSPmethod is slightly different than the high-voltagemethod and these differences are noted whereapplicable. The PIC18F1XK22 devices operate from1.8 to 5.5 volts and the PIC18LF1XK22 devicesoperate from 1.8 to 3.6 volts. All other aspects of thePIC18F1XK22 with regards to the PIC18LF1XK22devices are identical.
2.1 Hardware RequirementsIn High-Voltage ICSP mode, the PIC18F1XK22/LF1XK22 devices require two programmable powersupplies: one for VDD and one for MCLR/VPP/RA3.Both supplies should have a minimum resolution of0.25V. Refer to Section 8.0 “AC/DC CharacteristicsTiming Requirements for Program/Verify TestMode” for additional hardware parameters.
2.1.1 LOW-VOLTAGE ICSP PROGRAMMING
In Low-Voltage ICSP mode, the PIC18F1XK22/LF1XK22 devices can be programmed using a singleVDD source in the operating range. The MCLR/VPP/RA3 does not have to be brought to a different voltage,but can instead be left at the normal operating voltage.Refer to Section 8.0 “AC/DC Characteristics TimingRequirements for Program/Verify Test Mode” foradditional hardware parameters.
2.1.1.1 Single-Supply ICSP ProgrammingThe LVP bit in Configuration register, CONFIG4L,enables single-supply (low-voltage) ICSPprogramming. The LVP bit defaults to a ‘1’ (enabled)from the factory.
If Single-Supply Programming mode is not used, theLVP bit can be programmed to a ‘0’ and RC3/PGMbecomes a digital I/O pin. However, the LVP bit mayonly be programmed by entering the High-VoltageICSP mode, where MCLR/VPP/RA3 is raised to VIHH.Once the LVP bit is programmed to a ‘0’, only theHigh-Voltage ICSP mode is available and only theHigh-Voltage ICSP mode can be used to program thedevice.
MCLR/VPP/RA3 VPP P Programming EnableVDD(2) VDD P Power SupplyVSS(2) VSS P GroundRC3 PGM I Low-Voltage ICSP™ input when LVP Configuration bit equals ‘1’(1)
RA1 PGC I Serial ClockRA0 PGD I/O Serial DataLegend: I = Input, O = Output, P = PowerNote 1: See Figure 6-1 for more information.
2: All power supply (VDD) and ground (VSS) pins must be connected.
3.0 MEMORY MAPSFor the PIC18F14K22/LF14K22 device, the programFlash space extends from 0000h to 03FFFh(16 Kbytes) in two 8-Kbyte blocks. For thePIC18F13K22/LF13K22 device, the program Flashspace extends from 0000h to 01FFFh (8 Kbytes) in two4-Kbyte blocks.
For the PIC18F14K22/LF14K22 addresses 0000hthrough 0FFFh, however, define a “Boot Block” regionthat is treated separately from Block 0. For thePIC18F13K22/LF13K22 addresses 0000h through07FFh, define the “Boot Block” region. All of theseblocks define code protection boundaries within theprogram Flash space. The size of the Boot Block in thePIC18F14K22/LF14K22 devices can be configured as2K, or 4 Kbyte (see Figure 3-1). The size of the Boot
Block in the PIC18F13K22/LF13K22 devices can beconfigured as 1K, or 2 Kbytes (see Figure 3-1). This isdone through the BBSIZ bit in the Configuration regis-ter, CONFIG4L. It is important to note that increasingthe size of the Boot Block decreases the size of theBlock 0.
TABLE 3-1: IMPLEMENTATION OF PROGRAM FLASH
FIGURE 3-1: MEMORY MAP AND THE PROGRAM FLASH SPACE FOR PIC18F14K22/LF14K22 DEVICES(1)
Device Program Flash Size (Bytes)
PIC18F13K22/LF13K22 000000h-001FFFh (8K)
PIC18F14K22/LF14K22 000000h-003FFFh (16K)
000000h
200000h
3FFFFFh
01FFFFh
Note 1: Sizes of memory areas are not to scale.2: Boot Block size is determined by the BBSIZ bit in the CONFIG4L register.
In addition to the program Flash space, there are threeblocks in the Configuration and ID space that areaccessible to the user through table reads and tablewrites. Their locations in the memory map are shown inFigure 3-3.
Users may store identification information (ID) in eightID registers. These ID registers are mapped inaddresses 200000h through 200007h. The ID locationsread out normally, even after code protection is applied.
Locations 300001h through 30000Dh are reserved forthe Configuration bits. These bits select various deviceoptions and are described in Section 6.0 “Configura-tion Word”. These Configuration bits read outnormally, even after code protection.
Locations 3FFFFEh and 3FFFFFh are reserved for thedevice ID bits. These bits may be used by theprogrammer to identify what device type is beingprogrammed and are described in Section 6.0“Configuration Word”. These device ID bits read outnormally, even after code protection.
3.0.1 MEMORY ADDRESS POINTERMemory in the address space, 0000000h to 3FFFFFh,is addressed via the Table Pointer register, which iscomprised of three Pointer registers:
• TBLPTRU, at RAM address 0FF8h• TBLPTRH, at RAM address 0FF7h• TBLPTRL, at RAM address 0FF6h
The 4-bit command, ‘0000’ (core instruction), is used toload the Table Pointer prior to using any read or writeoperations.
FIGURE 3-3: CONFIGURATION AND ID LOCATIONS FOR PIC18F1XK22/LF1XK22 DEVICES
Programming ProcessFigure 3-4 shows the high-level overview of theprogramming process. First, a Bulk Erase is performed.Next, the program Flash, ID locations and dataEEPROM are programmed. These memories are thenverified to ensure that programming was successful. Ifno errors are detected, the Configuration bits are thenprogrammed and verified.
FIGURE 3-4: HIGH-LEVEL PROGRAMMING FLOW
3.2 Entering and Exiting High-Voltage ICSP Program/Verify Mode
As shown in Figure 3-6, the High-Voltage ICSPProgram/Verify mode is entered by holding PGC andPGD low and then raising MCLR/VPP/RA3 to VIHH(high voltage). Once in this mode, the program Flash,data EEPROM, ID locations and Configuration bits canbe accessed and programmed in serial fashion.Figure 3-7 shows the exit sequence.
The sequence that enters the device into the Program/Verify mode places all unused I/Os in the high-impedancestate.
FIGURE 3-5: VPP-FIRST PROGRAM/VERIFY MODE ENTRY
FIGURE 3-6: VDD-FIRST PROGRAM/VERIFY MODE ENTRY
Start
Program Memory
Program IDs
Program Data EE
Verify Program
Verify IDs
Verify Data
ProgramConfiguration Bits
Verify Configuration Bits
Done
Perform BulkErase
MCLR/VPP/RA3
P12
PGD
PGD = Input
PGC
VDD
D110
P13
P1
Note: This method of entry is valid, regardlessof Configuration Word selected.
3.3 Entering and Exiting Low-Voltage ICSP Program/Verify Mode
When the LVP Configuration bit is ‘1’ (seeSection 2.1.1.1 “Single-Supply ICSP Programming”),the Low-Voltage ICSP mode is enabled. As shown inFigure 3-8, Low-Voltage ICSP Program/Verify mode isentered by holding PGC and PGD low, placing a logichigh on PGM and then raising MCLR/VPP/RA3 to VIH. Inthis mode, the RC3/PGM pin is dedicated to theprogramming function and ceases to be a generalpurpose I/O pin. Figure 3-9 shows the exit sequence.
The sequence that enters the device into the Program/Verify mode places all unused I/Os in the high-impedancestate.
3.4 Serial Program/Verify OperationThe PGC pin is used as a clock input pin and the PGDpin is used for entering command bits and data input/output during serial operation. Commands and data aretransmitted on the rising edge of PGC, latched on thefalling edge of PGC and are Least Significant bit (LSb)first.
3.4.1 4-BIT COMMANDSAll instructions are 20 bits, consisting of a leading 4-bitcommand followed by a 16-bit operand, which dependson the type of command being executed. To input acommand, PGC is cycled four times. The commandsneeded for programming and verification are shown inTable 3-2.
Depending on the 4-bit command, the 16-bit operandrepresents 16 bits of input data or 8 bits of input dataand 8 bits of output data.
Throughout this specification, commands and data arepresented as illustrated in Table 3-3. The 4-bitcommand, Most Significant bit (MSb), is shown first.The command operand, or “Data Payload”, is shown<MSB><LSB>. Figure 3-10 demonstrates how toserially present a 20-bit command/operand to thedevice.
3.4.2 CORE INSTRUCTIONThe core instruction passes a 16-bit instruction to theCPU core for execution. This is needed to set upregisters as appropriate for use with other commands.
TABLE 3-2: COMMANDS FOR PROGRAMMING
Description 4-Bit Command
Core Instruction (Shift in16-bit instruction)
0000
Shift out TABLAT register 0010
Table Read 1000
Table Read, post-increment 1001
Table Read, post-decrement 1010
Table Read, pre-increment 1011
Table Write 1100
Table Write, post-increment by 2 1101
Table Write, start programming, post-increment by 2
4.0 DEVICE PROGRAMMINGProgramming includes the ability to erase or write thevarious memory regions within the device.
In all cases, except high-voltage ICSP Bulk Erase, theEECON1 register must be configured in order tooperate on a particular memory region.
When using the EECON1 register to act on programFlash, the EEPGD bit must be set (EECON1<7> = 1)and the CFGS bit must be cleared (EECON1<6> = 0).The WREN bit must be set (EECON1<2> = 1) toenable writes of any sort (e.g., erases) and this must bedone prior to initiating a write sequence. The FREE bitmust be set (EECON1<4> = 1) in order to erase theprogram space being pointed to by the Table Pointer.The erase or write sequence is initiated by setting theWR bit (EECON1<1> = 1). It is strongly recommendedthat the WREN bit only be set immediately prior to aprogram or erase.
4.1 ICSP Erase
4.1.1 HIGH-VOLTAGE ICSP BULK ERASEErasing program Flash or data EEPROM isaccomplished by configuring two Bulk Erase Controlregisters located at 3C0004h and 3C0005h. ProgramFlash may be erased portions at a time, or the user mayerase the entire device in one action. Bulk Eraseoperations will also clear any code-protect settingsassociated with the memory block erased. Eraseoptions are detailed in Table 4-1. If data EEPROM iscode-protected (CPD = 0), the user must request anerase of data EEPROM (e.g., 0084h as shown inTable 4-1).
TABLE 4-1: BULK ERASE OPTIONS
The actual Bulk Erase function is a self-timedoperation. Once the erase has started (falling edge ofthe 4th PGC after the NOP command), serial executionwill cease until the erase completes (parameter P11).During this time, PGC may continue to toggle but PGDmust be held low.
The code sequence to erase the entire device is shownin Table 4-2 and the flowchart is shown in Figure 4-1.
4.1.2 LOW-VOLTAGE ICSP BULK ERASEWhen using low-voltage ICSP, the part must besupplied by the voltage specified in parameter D111 if aBulk Erase is to be executed. All other Bulk Erasedetails as described above apply.
If it is determined that a program memory erase mustbe performed at a supply voltage below the Bulk Eraselimit, refer to the erase methodology described inSection 4.1.3 “ICSP Row Erase” and Section 4.2.1“Modifying Program Flash”.
If it is determined that a data EEPROM erase must beperformed at a supply voltage below the Bulk Eraselimit, follow the methodology described in Section 4.3“Data EEPROM Programming” and write ‘1’s to thearray.
4.1.3 ICSP ROW ERASERegardless of whether high or low-voltage ICSP isused, it is possible to erase one row (64 bytes of data),provided the block is not code or write-protected. Rowsare located at static boundaries beginning at programmemory address 000000h, extending to the internalprogram memory limit (see Section 3.0 “MemoryMaps”).
The Row Erase duration is self-timed. After the WR bitin EECON1 is set, two NOPs are issued. Erase startsupon the 4th PGC of the second NOP. It ends when theWR bit is cleared by hardware.
The code sequence to Row Erase a PIC18F1XK22/LF1XK22 device is shown in Table 4-3. The flowchartshown in Figure 4-3 depicts the logic necessary to com-pletely erase the PIC18F1XK22/LF1XK22 devices. Thetiming diagram for Row Erase is identical to the dataEEPROM write timing shown in Figure 4-7.
Note 1: The TBLPTR register can point at anybyte within the row intended for erase.
2: ICSP row erase of the User ID locationsis also possible using the techniquedescribed in Section 4.1.3 “ICSP RowErase”. The address argument usedshould be 0x200000. A row erase of theUser ID locations is required when VDD isbelow the Bulk Erase threshold.
4.2 Program Flash ProgrammingProgramming program Flash is accomplished by firstloading data into the write buffer and then initiating aprogramming sequence. The write and erase buffersizes shown in Table 4-4 can be mapped to anylocation of the same size beginning at 000000h. Theactual memory write sequence takes the contents ofthis buffer and programs the proper amount of programFlash that contains the Table Pointer.
The programming duration is externally timed and iscontrolled by PGC. After a Start Programmingcommand is issued (4-bit command, ‘1111’), a NOP isissued, where the 4th PGC is held high for the durationof the programming time, P9.
After PGC is brought low, the programming sequenceis terminated. PGC must be held low for the timespecified by parameter P10 to allow high-voltagedischarge of the memory array.
The code sequence to program a PIC18F1XK22/LF1XK22 device is shown in Table 4-5. The flowchartshown in Figure 4-4 depicts the logic necessary tocompletely write a PIC18F1XK22/LF1XK22 device.The timing diagram that details the Start Programmingcommand and parameters P9 and P10 is shown inFigure 4-5.
TABLE 4-4: WRITE AND ERASE BUFFER SIZES
TABLE 4-5: WRITE PROGRAM FLASH CODE SEQUENCE
Note: The TBLPTR register must point to thesame region when initiating the program-ming sequence as it did when the writebuffers were loaded.
4.2.1 MODIFYING PROGRAM FLASHThe previous programming example assumed that thedevice has been Bulk Erased prior to programming(see Section 4.1.1 “High-Voltage ICSP Bulk Erase”).It may be the case, however, that the user wishes tomodify only a section of an already programmeddevice.
The appropriate number of bytes required for the erasebuffer must be read out of program Flash (as describedin Section 5.2 “Verify Program Flash and ID Loca-tions”) and buffered. Modifications can be made onthis buffer. Then, the block of program Flash that wasread out must be erased and rewritten with themodified data.
The WREN bit must be set if the WR bit in EECON1 isused to initiate a write sequence.
TABLE 4-6: MODIFYING PROGRAM FLASH4-bit
Command Data Payload Core Instruction
Step 1: Direct access to program Flash.00000000
8E A69C A6
BSF EECON1, EEPGDBCF EECON1, CFGS
Step 2: Read program Flash into buffer (Section 5.1 “Read Program Flash, ID Locations and Configuration Bits”).
Step 3: Set the Table Pointer for the block to be erased.000000000000000000000000
Step 4: Enable memory writes and setup an erase.00000000
84 A688 A6
BSF EECON1, WRENBSF EECON1, FREE
Step 5: Initiate erase. 0000000000000000
88 A682 A600 0000 00
BSF EECON1, FREEBSF EECON1, WRNOPNOP Erase starts on the 4th clock of this instruction
Step 6: Poll WR bit. Repeat until bit is clear. 0000000000000000
50 A66E F500 00
<MSB><LSB>
MOVF EECON1, W, 0MOVWF TABLATNOPShift out data(1)
Step 7: Load write buffer. The correct bytes will be selected based on the Table Pointer.0000000000000000000000001101•••
11110000
0E <Addr[21:16]>6E F8
0E <Addr[8:15]>6E F7
0E <Addr[7:0]>6E F6
<MSB><LSB>•••
<MSB><LSB>00 00
MOVLW <Addr[21:16]>MOVWF TBLPTRUMOVLW <Addr[8:15]>MOVWF TBLPTRHMOVLW <Addr[7:0]>MOVWF TBLPTRLWrite 2 bytes and post-increment address by 2.
Repeat as many times as necessary to fill the write bufferWrite 2 bytes and start programming.NOP - hold PGC high for time P9 and low for time P10.
To continue modifying data, repeat Steps 2 through 6, where the Address Pointer is incremented by the appropriate number of bytes (see Table 4-4) at each iteration of the loop. The write cycle must be repeated enough times to completely rewrite the contents of the erase buffer.Step 8: Disable writes.
Data EEPROM is accessed one byte at a time via anAddress Pointer (register EEADR) and a data latch(EEDATA). Data EEPROM is written by loadingEEADR with the desired memory location, EEDATAwith the data to be written and initiating a memory writeby appropriately configuring the EECON1 register. Abyte write automatically erases the location and writesthe new data (erase-before-write).
When using the EECON1 register to perform a dataEEPROM write, both the EEPGD and CFGS bits mustbe cleared (EECON1<7:6> = 00). The WREN bit mustbe set (EECON1<2> = 1) to enable writes of any sortand this must be done prior to initiating a writesequence. The write sequence is initiated by setting theWR bit (EECON1<1> = 1).
The write begins on the falling edge of the 24th PGCafter the WR bit is set. It ends when the WR bit iscleared by hardware.
After the programming sequence terminates, PGCmust be held low for the time specified by parameterP10 to allow high-voltage discharge of the memoryarray.
FIGURE 4-6: PROGRAM DATA FLOW
FIGURE 4-7: DATA EEPROM WRITE TIMING DIAGRAM
Start
Start Write
Set Data
Done
No
Yes
done?
Enable Write
Sequence
Set Address
WR bitclear?
No
Yes
n
PGC
PGD
PGD = Input
0 0 0 0
BSF EECON1, WR4-bit Command
1 2 3 4 1 2 15 16
P5 P5A
P101 2
n
Poll WR bit, Repeat until Clear 16-bit DataPayload
4.4 ID Location ProgrammingThe ID locations are programmed much like theprogram Flash. The ID registers are mapped inaddresses 200000h through 200007h. These locationsread out normally even after code protection.
Table 4-8 demonstrates the code sequence required towrite the ID locations.
In order to modify the ID locations, refer to themethodology described in Section 4.2.1 “ModifyingProgram Flash”. As with program Flash, the IDlocations must be erased before being modified.
TABLE 4-8: WRITE ID SEQUENCE
Note: The user only needs to fill the first 8 bytesof the write buffer in order to write the IDlocations.
4-bitCommand Data Payload Core Instruction
Step 1: Direct access to program Flash.000000000000
8E A69C A684 A6
BSF EECON1, EEPGDBCF EECON1, CFGSBSF EECON1, WREN
Step 2: Set Table Pointer to ID. Load write buffer with 8 bytes and write.00000000000000000000000011011101110111110000
0E 206E F80E 006E F70E 006E F6
<MSB><LSB><MSB><LSB><MSB><LSB><MSB><LSB>
00 00
MOVLW 20hMOVWF TBLPTRUMOVLW 00hMOVWF TBLPTRHMOVLW 00hMOVWF TBLPTRLWrite 2 bytes and post-increment address by 2.Write 2 bytes and post-increment address by 2.Write 2 bytes and post-increment address by 2.Write 2 bytes and start programming.NOP - hold PGC high for time P9 and low for time P10.
4.5 Boot Block ProgrammingThe code sequence detailed in Table 4-5 should beused, except that the address used in “Step 2” will be inthe following ranges:
If BBSIZ = 0:
000000h-0003FFh for PIC18F13K22/LF13K22
000000h-0007FFh for PIC18F14K22/LF14K22
If BBSIZ = 1:
000000h-0007FFh for PIC18F13K22/LF13K22
000000h-000FFFh for PIC18F14K22/LF14K22
4.6 Configuration Bits ProgrammingUnlike program Flash, the Configuration bits areprogrammed a byte at a time. The Table Write, BeginProgramming 4-bit command (‘1111’) is used, but only8 bits of the following 16-bit payload will be written. TheLSB of the payload will be written to even addressesand the MSB will be written to odd addresses. Thecode sequence to program two consecutiveconfiguration locations is shown in Table 4-9. SeeFigure 4-5 for the timing diagram.
TABLE 4-9: SET ADDRESS POINTER TO CONFIGURATION LOCATION
FIGURE 4-8: CONFIGURATION PROGRAMMING FLOW
Note: The address must be explicitly written foreach byte programmed. The addressescan not be incremented in this mode.
4-bitCommand Data Payload Core Instruction
Step 1: Direct access to configuration memory.000000000000
8E A68C A684 A6
BSF EECON1, EEPGDBSF EECON1, CFGSBSF EECON1, WREN
Step 2(1): Set Table Pointer for configuration byte to be written. Write even/odd addresses.000000000000000000000000111100000000000011110000
0E 306E F80E 006E F70E 006E F6
<MSB ignored><LSB>00 000E 016E F6
<MSB><LSB ignored>00 00
MOVLW 30hMOVWF TBLPTRUMOVLW 00hMOVWF TBLPRTHMOVLW 00hMOVWF TBLPTRLLoad 2 bytes and start programming.NOP - hold PGC high for time P9 and low for time P10.MOVLW 01hMOVWF TBLPTRLLoad 2 bytes and start programming.NOP - hold PGC high for time P9A and low for time P10.
Note 1: Enabling the write protection of Configuration bits (WRTC = 0 in CONFIG6H) will prevent further writing of Configura-tion bits. Always write all the Configuration bits before enabling the write protection for Configuration bits.
5.1 Read Program Flash, ID Locations and Configuration Bits
Program Flash is accessed one byte at a time via the4-bit command, ‘1001’ (table read, post-increment).The contents of memory pointed to by the Table Pointer(TBLPTRU:TBLPTRH:TBLPTRL) are serially output onPGD.
The 4-bit command is shifted in LSb first. The read isexecuted during the next 8 clocks, then shifted out onPGD during the last 8 clocks, LSb to MSb. A delay ofP6 must be introduced after the falling edge of the 8thPGC of the operand to allow PGD to transition from aninput to an output. During this time, PGC must be heldlow (see Figure 5-1). This operation also incrementsthe Table Pointer by one, pointing to the next byte inprogram Flash for the next read.
This technique will work to read any memory in the000000h to 3FFFFFh address space, so it also appliesto the reading of the ID and Configuration registers.
LocationsThe verify step involves reading back the programFlash space and comparing it against the copy held inthe programmer’s buffer. Memory reads occur a singlebyte at a time, so two bytes must be read to compareagainst the word in the programmer’s buffer. Refer toSection 5.1 “Read Program Flash, ID Locations andConfiguration Bits” for implementation details ofreading program Flash.
The Table Pointer must be manually set to 200000h(base address of the ID locations) once the programFlash has been verified. The post-increment feature ofthe table read 4-bit command can not be used toincrement the Table Pointer beyond the program Flashspace. In a 64-Kbyte device, for example, a post-increment read of address FFFFh will wrap the TablePointer back to 000000h, rather than point tounimplemented address, 010000h.
5.3 Verify Configuration BitsA Configuration address may be read and output onPGD via the 4-bit command, ‘1001’. Configuration datais read and written in a byte-wise fashion, so it is notnecessary to merge two bytes into a word prior to acompare. The result may then be immediatelycompared to the appropriate configuration data in theprogrammer’s memory for verification. Refer toSection 5.1 “Read Program Flash, ID Locations andConfiguration Bits” for implementation details ofreading Configuration data.
5.4 Read Data EEPROM MemoryData EEPROM is accessed one byte at a time via anAddress Pointer (register EEADR) and a data latch(EEDATA). Data EEPROM is read by loading EEADRwith the desired memory location and initiating amemory read by appropriately configuring theEECON1 register. The data will be loaded intoEEDATA, where it may be serially output on PGD viathe 4-bit command, ‘0010’ (Shift Out Data Holdingregister). A delay of P6 must be introduced after thefalling edge of the 8th PGC of the operand to allowPGD to transition from an input to an output. During thistime, PGC must be held low (see Figure 5-4).
The command sequence to read a single byte of datais shown in Table 5-2.
FIGURE 5-3: READ DATA EEPROM FLOW
TABLE 5-2: READ DATA EEPROM MEMORY
Start
SetAddress
ReadByte
Done
No
Yes
done?
Move to TABLAT
Shift Out Data
4-bitCommand Data Payload Core Instruction
Step 1: Direct access to data EEPROM.00000000
9E A69C A6
BCF EECON1, EEPGDBCF EECON1, CFGS
Step 2: Set the data EEPROM Address Pointer.00000000
FIGURE 5-4: SHIFT OUT DATA HOLDING REGISTER TIMING DIAGRAM (0010)
FIGURE 5-5: HIGH-IMPEDANCE DELAY
5.5 Verify Data EEPROMA data EEPROM address may be read via a sequenceof core instructions (4-bit command, ‘0000’) and thenoutput on PGD via the 4-bit command, ‘0010’ (TABLATregister). The result may then be immediatelycompared to the appropriate data in the programmer’smemory for verification. Refer to Section 5.4 “ReadData EEPROM Memory” for implementation details ofreading data EEPROM.
5.6 Blank CheckThe term “Blank Check” means to verify that the devicehas no programmed memory cells. All memories mustbe verified: program Flash, data EEPROM, ID locationsand Configuration bits. The device ID registers(3FFFFEh:3FFFFFh) should be ignored.
A “blank” or “erased” memory cell will read as a ‘1’.Therefore, Blank Checking a device merely means toverify that all bytes read as FFh except theConfiguration bits. Unused (reserved) Configurationbits will read ‘0’ (programmed). Refer to Table 6-1 forblank configuration expect data for the variousPIC18F1XK22/LF1XK22 devices.
Given that Blank Checking is merely code and dataEEPROM verification with FFh expect data, refer toSection 5.4 “Read Data EEPROM Memory” andSection 5.2 “Verify Program Flash and ID Locations”for implementation details.
FIGURE 5-6: BLANK CHECK FLOW
1 2 3 4PGC
P5
PGD
PGD = Input
Shift Data Out
P6
PGD = Output
5 6 7 8 1 2 3 4
P5A
9 10 11 13 15 161412
Fetch Next 4-bit Command
0 1 0 0
PGD = Input
LSb MSb1 2 3 4 5 6
1 2 3 4
n n n n
P14
(Note 1)
Note 1: Magnification of the high-impedance delay between PGC and PGD is shown in Figure 5-5.
6.0 CONFIGURATION WORDThe PIC18F1XK22/LF1XK22 devices have severalConfiguration Words. These bits can be set or clearedto select various device configurations. All other mem-ory areas should be programmed and verified prior tosetting Configuration Words. These bits may be readout normally, even after read or code protection. SeeTable 6-1 for a list of Configuration bits and device IDsand Table 6-3 for the Configuration bit descriptions.
6.1 ID Locations A user may store identification information (ID) in eightID locations mapped in 200000h:200007h. It is recom-mended that the Most Significant nibble of each ID beFh. In doing so, if the user code inadvertently tries toexecute from the ID space, the ID data will execute asa NOP.
6.2 Device ID Word The device ID word for the PIC18F1XK22/LF1XK22devices is located at 3FFFFEh:3FFFFFh. These bitsmay be used by the programmer to identify what devicetype is being programmed and read out normally, evenafter code or read protection. See Table 6-2 for acomplete list of device ID values.
FIGURE 6-1: READ DEVICE ID WORD FLOW
TABLE 6-1: CONFIGURATION BITS AND DEVICE IDs
Start
Set TBLPTR = 3FFFFE
Done
Read Low Byte
Read High Byte
with Post-Increment
with Post-Increment
File Name Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0Default/
Legend: x = unknown, u = unchanged, – = unimplemented. Shaded cells are unimplemented, read as ‘0’.Note 1: These bits are only implemented on specific devices. Refer to Section 3.0 “Memory Maps” to determine which bits apply based on
available memory.2: DEVID registers are read-only and cannot be programmed by the user.
PLL_EN CONFIG1H 4 X PLL Enable bit1 = Oscillator multiplied by 40 = Oscillator used directly
FOSC<3:0> CONFIG1H Oscillator Selection bits1111 = External RC oscillator, CLKOUT function on OSC21110 = External RC oscillator, CLKOUT function on OSC21101 = EC oscillator (low)1100 = EC oscillator, CLKOUT function on OSC2 (low)1011 = EC oscillator (medium)1010 = EC oscillator, CLKOUT function on OSC2 (medium)1001 = Internal RC oscillator, CLKOUT function on OSC21000 = Internal RC oscillator0111 = External RC oscillator0110 = External RC oscillator, CLKOUT function on OSC20101 = EC oscillator (high)0100 = EC oscillator, CLKOUT function on OSC2 (high)0011 = External RC oscillator, CLKOUT function on OSC20010 = HS oscillator0001 = XT oscillator0000 = LP oscillator
BORV<1:0> CONFIG2L Brown-out Reset Voltage bits11 = VBOR set to 1.9V10 = VBOR set to 2.2V01 = VBOR set to 2.7V00 = VBOR set to 3.0V
BOREN<1:0> CONFIG2L Brown-out Reset Enable bits11 = Brown-out Reset enabled in hardware only (SBOREN is disabled)10 = Brown-out Reset enabled in hardware only and disabled in Sleep
modeSBOREN is disabled)
01 = Brown-out Reset enabled and controlled by software (SBOREN isenabled)
00 = Brown-out Reset disabled in hardware and software
CPB CONFIG5H Code Protection bits (Boot Block memory area)1 = Boot Block is not code-protected0 = Boot Block is code-protected
WRT1 CONFIG6L Write Protection bits (Block 1 program Flash area)1 = Block 1 is not write-protected0 = Block 1 is write-protected
WRT0 CONFIG6L Write Protection bits (Block 0 program Flash area)1 = Block 0 is not write-protected0 = Block 0 is write-protected
WRTD CONFIG6H Write Protection bit (Data EEPROM)1 = Data EEPROM is not write-protected0 = Data EEPROM is write-protected
WRTB CONFIG6H Write Protection bit (Boot Block memory area)1 = Boot Block is not write-protected0 = Boot Block is write-protected
WRTC CONFIG6H Write Protection bit (Configuration registers)1 = Configuration registers are not write-protected0 = Configuration registers are write-protected
EBTR1 CONFIG7L Table Read Protection bit (Block 1 program Flash area)1 = Block 1 is not protected from table reads executed in other blocks0 = Block 1 is protected from table reads executed in other blocks
EBTR0 CONFIG7L Table Read Protection bit (Block 0 program Flash area)1 = Block 0 is not protected from table reads executed in other blocks0 = Block 0 is protected from table reads executed in other blocks
EBTRB CONFIG7H Table Read Protection bit (Boot Block memory area)1 = Boot Block is not protected from table reads executed in other blocks0 = Boot Block is protected from table reads executed in other blocks
DEV<10:3> DEVID2 Device ID bitsThese bits are used with the DEV<2:0> bits in the DEVID1 register to identify part number.
DEV<2:0> DEVID1 Device ID bitsThese bits are used with the DEV<10:3> bits in the DEVID2 register to identify part number.
REV<4:0> DEVID1 Revision ID bitsThese bits are used to indicate the revision of the device.
TABLE 6-3: PIC18F1XK22/LF1XK22 BIT DESCRIPTIONS (CONTINUED)
7.0 EMBEDDING CONFIGURATION WORD INFORMATION IN THE HEX FILE
To allow portability of code, a PIC18F1XK22/LF1XK22programmer is required to read the Configuration Wordlocations from the hex file. If Configuration Word infor-mation is not present in the hex file, then a simple warn-ing message should be issued. Similarly, while savinga hex file, all Configuration Word information must beincluded. An option to not include the ConfigurationWord information may be provided. When embeddingConfiguration Word information in the hex file, it shouldstart at address 300000h.
Microchip Technology Inc. feels strongly that thisfeature is important for the benefit of the end customer.
7.1 Embedding Data EEPROM Information In the HEX File
To allow portability of code, a PIC18F1XK22/LF1XK22programmer is required to read the data EEPROMinformation from the hex file. If data EEPROMinformation is not present, a simple warning messageshould be issued. Similarly, when saving a hex file, alldata EEPROM information must be included. An optionto not include the data EEPROM information may beprovided. When embedding data EEPROM informationin the hex file, it should start at address F00000h.
Microchip Technology Inc. believes that this feature isimportant for the benefit of the end customer.
7.2 Checksum ComputationThe checksum is calculated by summing the following:
• The contents of all program Flash locations• The Configuration Word, appropriately masked• ID locations (Only if any portion of program
memory is code-protected)
The Least Significant 16 bits of this sum are thechecksum.
Code protection limits access to program memory byboth external programmer (code-protect) and codeexecution (table read protect). The ID locations, whenincluded in a code protected checksum, contain thechecksum of an unprotected part. The unprotectedchecksum is distributed: one nibble per ID location.Each nibble is right justified.
Table 7-1 describes how to calculate the checksum foreach device.
Note: The checksum calculation differsdepending on the code-protect setting.Since the program Flash locations readout differently depending on the code-protect setting, the table describes how tomanipulate the actual program Flashvalues to simulate the values that wouldbe read from a protected device. Whencalculating a checksum by reading adevice, the entire program Flash cansimply be read and summed. TheConfiguration Word and ID locations canalways be read.
Legend: Item DescriptionCONFIGx = Configuration Word SUM[a:b] = Sum of locations, a to b inclusive SUM_ID = Byte-wise sum of lower four bits of all customer ID locations + = Addition & = Bit-wise AND
D112 IPP Programming Current on MCLR/VPP/RA3 — 5 mAD113 IDDP Supply Current During Programming — 5 mAD031 VIL Input Low Voltage VSS 0.2 VDD VD041 VIH Input High Voltage 0.8 VDD VDD VD080 VOL Output Low Voltage — 0.6 V IOL = 3.0 mA @ 2.7VD090 VOH Output High Voltage VDD – 0.7 — V IOH = -2.0 mA @ 2.7VD012 CIO Capacitive Loading on I/O pin (PGD) — 50 pF To meet AC specifica-
tions
P1 TR MCLR/VPP/RA3 Rise Time to enter Program/Verify mode
— 1.0 μs (Note 1)
P2 TPGC Serial Clock (PGC) Period 100 — ns VDD = 3.6V1 — μs VDD = 1.8V
P2A TPGCL Serial Clock (PGC) Low Time 40 — ns VDD = 3.6V400 — ns VDD = 1.8V
P2B TPGCH Serial Clock (PGC) High Time 40 — ns VDD = 3.6V400 — ns VDD = 1.8V
P3 TSET1 Input Data Setup Time to Serial Clock ↓ 15 — nsP4 THLD1 Input Data Hold Time from PGC ↓ 15 — nsP5 TDLY1 Delay between 4-bit Command and Command
Operand40 — ns
P5A TDLY1A Delay between 4-bit Command Operand and next 4-bit Command
40 — ns
P6 TDLY2 Delay between Last PGC ↓ of Command Byte to First PGC ↑ of Read of Data Word
20 — ns
P9 TDLY5 PGC High Time (minimum programming time) 1 — ms Externally TimedP9A TDLY5
APGC High Time 5 ms Configuration Word
programming timeP10 TDLY6 PGC Low Time after Programming
(high-voltage discharge time)100 — μs
P11 TDLY7 Delay to allow Self-Timed Data Write or Bulk Erase to occur
5 — ms
P11A TDRWT Data Write Polling Time 4 — msNote 1: Do not allow excess time when transitioning MCLR between VIL and VIHH; this can cause spurious program
executions to occur. The maximum transition time is:1 TCY + TPWRT (if enabled) + 1024 TOSC (for LP, HS, HS/PLL and XT modes only) + 2 ms (for HS/PLL mode only) + 1.5 μs (for EC mode only) where TCY is the instruction cycle time, TPWRT is the Power-up Timer period and TOSC is the oscillator period. For specific values, refer to the Electrical Characteristics section of the device data sheet for the particular device.
P12 THLD2 Input Data Hold Time from MCLR/VPP/RA3 ↑ 2 — μs
P12A THLD2A
Input Data Hold Time from MCLR/VPP/RA3 ↑ 70 — μs PIC18F1XK22 Only. Refer to Figure 2.1.1.
P13 TSET2 VDD ↑ Setup Time to MCLR/VPP/RA3 ↑ 100 — ns
P13A TSET2A
VDD ↑ Setup Time to MCLR/VPP/RA3 ↑ 70 — μs PIC18F1XK22 Only. Refer to Figure 2.1.1.
P14 TVALID Data Out Valid from PGC ↑ 10 — ns
P15 TSET3 PGM ↑ Setup Time to MCLR/VPP/RA3 ↑ 2 — μs
P16 TDLY8 Delay between Last PGC ↓ and MCLR/VPP/RA3 ↓
0 — s
P17 THLD3 MCLR/VPP/RA3 ↓ to VDD ↓ — 100 ns
P18 THLD4 MCLR/VPP/RA3 ↓ to PGM ↓ 0 — s
P19 THIZ Delay from PGC ↑ to PGD High-Z 3 10 nS
P20 TPPDP Hold time after VPP changes 5 — μs
8.0 AC/DC CHARACTERISTICS TIMING REQUIREMENTS FOR PROGRAM/VERIFY TEST MODE (CONTINUED)
Standard Operating ConditionsOperating Temperature: 25°C is recommended
Param No. Sym. Characteristic Min. Max. Units Conditions
Note 1: Do not allow excess time when transitioning MCLR between VIL and VIHH; this can cause spurious program executions to occur. The maximum transition time is:1 TCY + TPWRT (if enabled) + 1024 TOSC (for LP, HS, HS/PLL and XT modes only) + 2 ms (for HS/PLL mode only) + 1.5 μs (for EC mode only) where TCY is the instruction cycle time, TPWRT is the Power-up Timer period and TOSC is the oscillator period. For specific values, refer to the Electrical Characteristics section of the device data sheet for the particular device.
Note the following details of the code protection feature on Microchip devices:• Microchip products meet the specification contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of ourproducts. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such actsallow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
Information contained in this publication regarding deviceapplications and the like is provided only for your convenienceand may be superseded by updates. It is your responsibility toensure that your application meets with your specifications.MICROCHIP MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WHETHER EXPRESS ORIMPLIED, WRITTEN OR ORAL, STATUTORY OROTHERWISE, RELATED TO THE INFORMATION,INCLUDING BUT NOT LIMITED TO ITS CONDITION,QUALITY, PERFORMANCE, MERCHANTABILITY ORFITNESS FOR PURPOSE. Microchip disclaims all liabilityarising from this information and its use. Use of Microchipdevices in life support and/or safety applications is entirely atthe buyer’s risk, and the buyer agrees to defend, indemnify andhold harmless Microchip from any and all damages, claims,suits, or expenses resulting from such use. No licenses areconveyed, implicitly or otherwise, under any Microchipintellectual property rights.
The Microchip name and logo, the Microchip logo, Accuron, dsPIC, KEELOQ, KEELOQ logo, MPLAB, PIC, PICmicro, PICSTART, rfPIC, SmartShunt and UNI/O are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
FilterLab, Hampshire, Linear Active Thermistor, MXDEV, MXLAB, SEEVAL, SmartSensor and The Embedded Control Solutions Company are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Analog-for-the-Digital Age, Application Maestro, CodeGuard, dsPICDEM, dsPICDEM.net, dsPICworks, dsSPEAK, ECAN, ECONOMONITOR, FanSense, In-Circuit Serial Programming, ICSP, ICEPIC, Mindi, MiWi, MPASM, MPLAB Certified logo, MPLIB, MPLINK, mTouch, nanoWatt XLP, PICkit, PICDEM, PICDEM.net, PICtail, PIC32 logo, PowerCal, PowerInfo, PowerMate, PowerTool, REAL ICE, rfLAB, Select Mode, Total Endurance, TSHARC, WiperLock and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.
All other trademarks mentioned herein are property of their respective companies.
Microchip received ISO/TS-16949:2002 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition, Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified.