M TB025 Downloading HEX Files to PIC16F87X PICmicro® Microcontrollers Author: ACCESSING MEMORY Rodger Richey Microchip Technology Inc. The read and write operations are controlled by a set of Special Function Registers (SFRs). There are six SFRs required to access the FLASH program memory: • • • • • • INTRODUCTION The release of the PIC16F87X devices introduces the first mid-range family of devices from Microchip Technology that has the capability to read and write to internal program memory. This family has FLASH-based program memory, SRAM data memory and EEPROM data memory. The FLASH program memory allows for a truly reprogrammable system. Table 1 shows the features of the PIC16F87X family of devices. EECON1 EECON2 EEDATA EEDATH EEADR EEADRH The registers EEADRH:EEADR holds the 12-bit address required to access a location in the 8K words of program memory. The registers EEDATH:EEDATA are used to hold the data values. When reading program memory, the EEPGD bit (EECON1<7>) must be set to indicate to the microcontroller that the operation is going to be on program memory. If the bit is cleared, the operation will be performed on data memory at the address pointed to by EEADR. The EEDATA register will hold the data. The EECON1 register also has bits for write enable and to initiate the read or write operation. There is also a bit to indicate a write error has occurred, possibly due to a reset condition happening while a write operation is in progress. Figure 1 shows the register map for EECON1. The EECON2 register is not a physical register. Reading it will result in all '0's. This register is used exclusively in the EEPROM and FLASH write sequences. Listing 1 shows the code snippet to initiate a write operation on the PIC16F87X devices. TABLE 1 PIC16F87X FAMILY FEATURES Key Features PIC16F873 PIC16F874 PIC16F876 PIC16F877 Operating Frequency DC - 20 MHz DC - 20 MHz DC - 20 MHz DC - 20 MHz Resets POR, BOR POR, BOR POR, BOR POR, BOR Flash Prog Memory (14-bit words) 4K 4K 8K 8K Data Memory (bytes) 192 192 368 368 EEPROM Data Memory 128 128 256 256 Interrupts 13 14 13 14 I/O Ports Ports A,B,C Ports A,B,C,D,E Ports A,B,C Ports A,B,C,D,E Timers 3 3 3 3 Capture/Compare/PWM modules 2 2 2 2 Serial Communications MSSP, USART MSSP, USART MSSP, USART MSSP, USART Parallel Communications — PSP — PSP 10-bit Analog-to-Digital Module 5 input channels 8 input channels 5 input channels 8 input channels 1998 Microchip Technology Inc. DS91025A-page 1 TB025 FIGURE 1: R/W-x U-0 EEPGD — bit7 bit 7: EECON1 REGISTER U-0 — U-0 — R/W-x R/W-0 WRERR WREN R/S-0 WR R/S-0 RD bit0 R= Readable bit W= Writable bit S= Settable bit U= Unimplemented bit, read as ‘0’ - n= Value at POR reset EEPGD: Program / Data EEPROM Select bit 1 = Accesses Program memory 0 = Accesses data memory Note: This bit cannot be changed while a write operation is in progress. bit 6:4: Unimplemented: Read as '0' bit 3: WRERR: EEPROM Error Flag bit 1 = A write operation is prematurely terminated (any MCLR reset or any WDT reset during normal operation) 0 = The write operation completed bit 2: WREN: EEPROM Write Enable bit 1 = Allows write cycles 0 = Inhibits write to the EEPROM bit 1: WR: Write Control bit 1 = initiates a write cycle. The bit is cleared by hardware once write is complete. The WR bit can only be set (not cleared) in software. 0 = Write cycle to the EEPROM is complete bit 0: RD: Read Control bit 1 = Initiates an EEPROM read (read takes one cycle) RD is cleared in hardware. The RD bit can only be set (not cleared) in software. 0 = Does not initiate an EEPROM read HEX FILE FORMAT The data to be programmed into program memory will be read into the microcontroller using one of its standard interface modules: SPI, I2C™, USART, or PSP. Probably the simplest format to send the data to the microcontroller is in the standard HEX format used by the Microchip development tools. The formats supported are the Intel HEX Format (INHX8M), Intel Split HEX Format (INHX8S), and the Intel HEX 32 Format (INHX32). The most commonly used formats are the INHX8M and INHX32 and therefore are the only formats discussed in this document. Please refer to Appendix A in the MPASM User's Guide (DS33014) for more information about HEX file formats. The difference between INHX8M and INHX32 is that INHX32 supports 32-bit addresses using a linear address record. The basic format of the hex file is the same between both formats as shown below: :BBAAAATTHHHH...HHHHCC Each data record begins with a 9 character prefix and always ends with a 2 character checksum. All records begin with a ':' regardless of the format. The individual elements are described below. • BB - is a two digit hexadecimal byte count representing the number of data bytes that will appear DS91025A-page 2 • • • • on the line. Divide this number by two to get the number of words per line. AAAA - is a four digit hexadecimal address representing the starting address of the data record. Format is high byte first followed by low byte. The address is doubled because this format only supports 8-bits (to find the real PICmicro address, simply divide the value AAAA by 2). TT - is a two digit record type that will be '00' for data records, '01' for end of file records and '04' for extended address record (INHX32 only). HHHH - is a four digit hexadecimal data word. Format is low byte followed by high byte. There will be BB/2 data words following TT. CC - is a two digit hexadecimal checksum that is the two's complement of the sum of all the preceding bytes in the line record. Since the PIC16F87X devices only have a maximum of 8K words, the linear address record '04' is ignored by the routine. The HEX file is composed of ASCII characters 0 thorough 9 and A to F and the end of each line has a carriage return and linefeed. The downloader code in the PICmicro microcontrollers must convert the ASCII characters to binary numbers to be used for programming. 1998 Microchip Technology Inc. TB025 PICmicro Code The sample downloader code does not specifically use one of the interface modules on the PIC16F87X device. Instead, a routine called GetByte retrieves a single character from the HEX file over the desired interface. It is up to the engineer to write this routine around the desired interface. Another routine GetHEX8 calls GetByte twice to form a two digit hexadecimal number. One issue that arises is how many times to reprogram a location that does not program correctly. The sample code provided simply exits the downloader routine and stores a value of 0xFF in the WREG if a program memory location does not properly program on the first attempt. The engineer may optionally add code to loop several times if this event occurs. Still another issue that is not specifically addressed in the sample code is to prevent the downloader from overwriting its own program memory address locations. The designer must add an address check to prevent this situation from happening. Finally, the designer must account for situations where the download of new code into the microcontroller is interrupted by an external event such as power failure or reset. The system must be able to recover from such an event. This is not a trivial task, is very system dependent, and is therefore left up to the designer to provide the safeguards and recovery mechanisms. Another error that could happen is a line checksum error. If the calculated line checksum does not match the line checksum from the HEX file, a value of 1 is returned in WREG. The part of the routine that calls the downloader should check for the errors 0xFF (could not program a memory location) and 1. If program memory is programmed correctly and no errors have been encountered, the downloader routine returns a 0 in WREG to indicate success to the calling routine. Figure 2 shows the flowchart for the downloader routines. Listing 2 shows the complete listing for the downloader code. 1998 Microchip Technology Inc. The routine ASCII2HEX converts the input character to a binary number. The routine does not provide any out of range error checking for incoming characters. Since the only valid characters in a HEX file are the colon (:), the numbers 0 through 9 and the letters A through F, the routine can be highly optimized. It first subtracts 48 from the character value. For the ASCII numbers 0 through 9, this results in a value from 0 to 9. If the character is A through F, the result is a number greater than 15. The routine checks to see if the upper nibble of the result is 0. If not 0, then the original value was A through F and the routine now subtracts an additional 43 from the character resulting in the binary values 10 through 15. The colon is not accounted for in this routine because the main part of the downloader code uses it as a line sync. LISTING 1: bsfSTATUS,RP1 bcfSTATUS,RP0 movfAddrH,W movwfEEADRH movfAddrL,W movwfEEADR bsfSTATUS,RP0 bsfEECON1,EEPGD bsfEECON1,RD bcfSTATUS,RP0 nop movfEEDATA,W … movfEEDATH,W … FLASH WRITE SEQUENCE ; Bank2 ; Load address into ; EEADRH:EEADR ; ; ; ; Bank3 Set for Prog Mem read operation Bank2 ; Data is read ; user can now ; access memory DS91025A-page 3 TB025 LISTING 2: HEX DOWNLOAD CODE WRITTEN FOR MPASM list p=16f877 #include "c:\progra~1\mplab\p16f877.inc" DownloadCode banksel DCStart call movlw subwf btfss goto ;Uses USART to receive data from PC RCREG GetByte ':' RCREG,W STATUS,Z DCStart ;Wait for colon call movwf movwf bcf rrf GetHex8 ByteCount LineChecksum STATUS,C ByteCount,F ;Read byte count ;Store in register ;Store in line checksum call movwf addwf call movwf addwf GetHex8 AddrH LineChecksum,F GetHex8 AddrL LineChecksum,F ;Read high byte of 16-bit address call movwf addwf GetHex8 RecType LineChecksum,F ;Read record type movf btfss goto RecType,F STATUS,Z EndOfFileRec movf btfsc goto call movwf addwf call movwf addwf ByteCount,F STATUS,Z DRCkChecksum GetHex8 HexDataL LineChecksum,F GetHex8 HexDataH LineChecksum,F DataRec ;Divide byte counter by 2 to get words ;Add high byte to line checksum ;Read low byte of 16-bit address ;Add low byte to line checksum ;Add to line checksum ;Data reception ;Check for data record (0h) ;Otherwise check for EOF DRLoop WriteDataSequence banksel movf movwf movf movwf movf movwf movf movwf banksel bsf bsf bcf movlw movwf movlw movwf bsf nop DS91025A-page 4 ;Check for bytecount = 0 ;If zero, goto checksum validation ;Read lower byte of data (2 characters) ;Add received data to checksum ;Read upper byte of data (2 characters) ;Add received data to checksum ;Write sequence to internal prog. mem FLASH EEADRH AddrH,W EEADRH AddrL,W EEADR HexDataH,W EEDATH HexDataL,W EEDATA EECON1 EECON1,EEPGD EECON1,WREN INTCON,GIE 0x55 EECON2 0xaa EECON2 EECON1,WR ;Write address to EEADRH:EEADR registers ;Write data to EEDATH:EEDATA registers ;Write sequence ;Set EEPGD to indicate program memory ;Enable writes to memory ;Make sure interrupts are disabled ;Required write sequence ;Start internal write cycle 1998 Microchip Technology Inc. TB025 nop bcf EECON1,WREN ;Disable writes banksel bsf bsf bcf nop movf subwf btfss retlw movf subwf btfss retlw EECON1 EECON1,EEPGD EECON1,RD STATUS,RP0 ;Read sequence ;Set EEPGD to indicate program memory ;Enable reads from memory EEDATH,W HexDataH,W STATUS,Z 0xff EEDATA,W HexDataL,W STATUS,Z 0xff ;Compare memory value to HexDataH:HexDataL incf btfsc incf decf goto AddrL,F STATUS,Z AddrH,F ByteCount,F DRLoop DRCkChecksum call addwf btfss retlw goto GetHex8 LineChecksum,W STATUS,Z 1 DCStart EndOfFileRec decf btfss goto call addwf btfss retlw retlw RecType,W STATUS,Z DCStart GetHex8 LineChecksum,W STATUS,Z 1 0 ;If upper byte not equal, return FFh ; to indicate programming failure ;If lower byte not equal, return FFh ; to indicate programming failure ;Increment address for next iteration ;Decrement byte count ;Go back to check for ByteCount = 0 ;Checksum verification ;Read in checksum ;Add to calculated checksum ;Result should be 0 ; If not return 1 to indicate checksum fail ;Do it again ;End of File record (01h) ;If EOF record, decrement should = 0 ;Not valid record type, wait for next : ;Read in checksum ;Add to calculated checksum ;Result should be 0 ; If not return 1 to indicate checksum fail ;Otherwise return 0 to indicate success GetByte ; Insert your code here to retrieve a byte of data from ; the desired interface. In this case it is the USART on F877. ;clear CTS ; banksel PIR1 ;GH4Waitbtfss PIR1,RCIF ; goto GH4Wait ;set CTS nop banksel RCREG movf RCREG,W return GetHex8 call call movwf swapf GetByte ASCII2Hex Temp Temp,F call call iorwf movf return GetByte ASCII2Hex Temp,F Temp,W 1998 Microchip Technology Inc. ;This function uses the USART ;Read a character from the USART ;Convert the character to binary ;Store result in high nibble ;Read a character from the USART ;Convert the character to binary ;Store result in low nibble ;Move result into WREG DS91025A-page 5 TB025 ASCII2Hex movwf movlw subwf movlw andwf btfsc goto movlw subwf ASCIIOut movf return Temp1 '0' Temp1,F 0xf0 Temp1,W STATUS,Z ASCIIOut 'A'-'0'-0x0a Temp1,F Temp1,W ;Convert value to binary ;Subtract ASCII 0 from number ;If number is 0-9 result, upper nibble ; should be zero ;Otherwise, number is A - F, so ;subtract off additional amount ;Value should be 0 - 15 end DS91025A-page 6 1998 Microchip Technology Inc. TB025 FIGURE 2: FLOWCHART Download Code 2 3 1 No Get a single byte GetByte Move AddrH:AddrL into EEADRH:EEADR 1 RecType = 1? Yes Move HexDataH:HexDataL into EEDATH:EEDATA Read Checksum and add to LineChecksum No Character = :? Set EEPGD and WREN bits Result = 0? Yes Yes No Write 55h to EECON2 Read ByteCount and store in LineChecksum Return with W = 0 Return with W = 1 Write AAh to EECON2 Divide by 2 to get # of words Set WR bit Read AddrH and add to LineChecksum Wait for EE Write complete Read AddrL and add to LineChecksum Set RD bit Read RecType and add to LineChecksum No Return with W = FFh No Record RecType type==0? 0? Yes 2 No Yes ByteCount = 0? Return with W = FFh Yes Read DataL and add to LineChecksum EEDATA = HexDataL? Yes Continue with program No Read DataH and add to LineChecksum EEDATH = HexDataH? Read Checksum and add to LineChecksum Result = 0? Yes 1 No 3 Return with W = 1 Decrement ByteCount 1998 Microchip Technology Inc. DS91025A-page 7 M WORLDWIDE SALES AND SERVICE AMERICAS AMERICAS (continued) ASIA/PACIFIC (continued) Corporate Office Toronto Singapore Microchip Technology Inc. 2355 West Chandler Blvd. Chandler, AZ 85224-6199 Tel: 602-786-7200 Fax: 602-786-7277 Technical Support: 602 786-7627 Web: http://www.microchip.com Microchip Technology Inc. 5925 Airport Road, Suite 200 Mississauga, Ontario L4V 1W1, Canada Tel: 905-405-6279 Fax: 905-405-6253 Microchip Technology Singapore Pte Ltd. 200 Middle Road #07-02 Prime Centre Singapore 188980 Tel: 65-334-8870 Fax: 65-334-8850 Atlanta Hong Kong Microchip Technology Inc. 500 Sugar Mill Road, Suite 200B Atlanta, GA 30350 Tel: 770-640-0034 Fax: 770-640-0307 Microchip Asia Pacific RM 3801B, Tower Two Metroplaza 223 Hing Fong Road Kwai Fong, N.T., Hong Kong Tel: 852-2-401-1200 Fax: 852-2-401-3431 Boston Microchip Technology Inc. 5 Mount Royal Avenue Marlborough, MA 01752 Tel: 508-480-9990 Fax: 508-480-8575 Chicago Microchip Technology Inc. 333 Pierce Road, Suite 180 Itasca, IL 60143 Tel: 630-285-0071 Fax: 630-285-0075 Dallas Microchip Technology Inc. 14651 Dallas Parkway, Suite 816 Dallas, TX 75240-8809 Tel: 972-991-7177 Fax: 972-991-8588 Dayton Microchip Technology Inc. Two Prestige Place, Suite 150 Miamisburg, OH 45342 Tel: 937-291-1654 Fax: 937-291-9175 Detroit Microchip Technology Inc. 42705 Grand River, Suite 201 Novi, MI 48375-1727 Tel: 248-374-1888 Fax: 248-374-2874 Los Angeles ASIA/PACIFIC Taiwan, R.O.C Microchip Technology Taiwan 10F-1C 207 Tung Hua North Road Taipei, Taiwan, ROC Tel: 886-2-2717-7175 Fax: 886-2-2545-0139 EUROPE India United Kingdom Microchip Technology Inc. India Liaison Office No. 6, Legacy, Convent Road Bangalore 560 025, India Tel: 91-80-229-0061 Fax: 91-80-229-0062 Arizona Microchip Technology Ltd. 505 Eskdale Road Winnersh Triangle Wokingham Berkshire, England RG41 5TU Tel: 44-1189-21-5858 Fax: 44-1189-21-5835 Japan Microchip Technology Intl. Inc. Benex S-1 6F 3-18-20, Shinyokohama Kohoku-Ku, Yokohama-shi Kanagawa 222-0033 Japan Tel: 81-45-471- 6166 Fax: 81-45-471-6122 France Korea Germany Microchip Technology Korea 168-1, Youngbo Bldg. 3 Floor Samsung-Dong, Kangnam-Ku Seoul, Korea Tel: 82-2-554-7200 Fax: 82-2-558-5934 Arizona Microchip Technology GmbH Gustav-Heinemann-Ring 125 D-81739 Müchen, Germany Tel: 49-89-627-144 0 Fax: 49-89-627-144-44 Shanghai Arizona Microchip Technology SRL Centro Direzionale Colleoni Palazzo Taurus 1 V. Le Colleoni 1 20041 Agrate Brianza Milan, Italy Tel: 39-39-6899939 Fax: 39-39-6899883 Microchip Technology RM 406 Shanghai Golden Bridge Bldg. 2077 Yan’an Road West, Hong Qiao District Shanghai, PRC 200335 Tel: 86-21-6275-5700 Fax: 86 21-6275-5060 Arizona Microchip Technology SARL Zone Industrielle de la Bonde 2 Rue du Buisson aux Fraises 91300 Massy, France Tel: 33-1-69-53-63-20 Fax: 33-1-69-30-90-79 Italy Microchip Technology Inc. 18201 Von Karman, Suite 1090 Irvine, CA 92612 Tel: 714-263-1888 Fax: 714-263-1338 New York Microchip Technology Inc. 150 Motor Parkway, Suite 202 Hauppauge, NY 11788 Tel: 516-273-5305 Fax: 516-273-5335 San Jose Microchip Technology Inc. 2107 North First Street, Suite 590 San Jose, CA 95131 Tel: 408-436-7950 Fax: 408-436-7955 All rights reserved. © 1998 Microchip Technology Incorporated. Printed in the USA. 10/98 9/29/98 Microchip received ISO 9001 Quality System certification for its worldwide headquarters, design, and wafer fabrication facilities in January, 1997. Our field-programmable PICmicro® 8-bit MCUs, Serial EEPROMs, related specialty memory products and development systems conform to the stringent quality standards of the International Standard Organization (ISO). Printed on recycled paper. Information contained in this publication regarding device applications and the like is intended for suggestion only and may be superseded by updates. No representation or warranty is given and no liability is assumed by Microchip Technology Incorporated with respect to the accuracy or use of such information, or infringement of patents or other intellectual property rights arising from such use or otherwise. Use of Microchip’s products as critical components in life support systems is not authorized except with express written approval by Microchip. No licenses are conveyed, implicitly or otherwise, under any intellectual property rights. The Microchip logo and name are registered trademarks of Microchip Technology Inc. in the U.S.A. and other countries. All rights reserved. All other trademarks mentioned herein are the property of their respective companies. DS91025A-page 8 1998 Microchip Technology Inc.