Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

AN247 Datasheet(PDF) 9 Page - Microchip Technology

Part # AN247
Description  A CAN Bootloader for PIC18F CAN Microcontrollers
PDF  32 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  MICROCHIP [Microchip Technology]
Direct Link  http://www.microchip.com
Logo MICROCHIP - Microchip Technology

AN247 Datasheet(HTML) 9 Page - Microchip Technology

Back Button AN247 Datasheet HTML 5Page - Microchip Technology AN247 Datasheet HTML 6Page - Microchip Technology AN247 Datasheet HTML 7Page - Microchip Technology AN247 Datasheet HTML 8Page - Microchip Technology AN247 Datasheet HTML 9Page - Microchip Technology AN247 Datasheet HTML 10Page - Microchip Technology AN247 Datasheet HTML 11Page - Microchip Technology AN247 Datasheet HTML 12Page - Microchip Technology AN247 Datasheet HTML 13Page - Microchip Technology Next Button
Zoom Inzoom in Zoom Outzoom out
 9 / 32 page
background image
 2003 Microchip Technology Inc.
DS00247A-page 9
AN247
TIPS FOR SUCCESSFUL FIELD
PROGRAMMING
Successful programming can take several forms,
depending on which compile time options are selected.
In P-Mode with self-verification enabled, the pro-
grammed target keeps a running 16-bit sum of all the
data written to memory. In addition, every write opera-
tion is verified by reading back and comparing the data,
providing some assurance that all data was received
and that all data was correctly written.
In PG mode without self-verification, the programming
source can read as well as write data. Thus, verification
is provided directly by the source.
EXAMPLE PROGRAMMING SEQUENCE
(P MODE)
1.
Put the programming target in Boot mode.
2.
Send a control packet. Load the address with
the beginning memory. Unlock write operations.
Enable auto erase. Disable erase only. Issue a
Self-Verify Reset.
3.
Send Program Memory data. The data must be
8 bytes and aligned on an even 8-byte address.
4.
Wait an appropriate amount of time.
5.
Repeat steps 3 and 4 until all Program Memory
is written.
6.
Send EEPROM Data Memory data.
7.
Wait an appropriate amount of time.
8.
Repeat steps 6 and 7 until all EEPROM Data
Memory is written except for the last location.
9.
Send one byte of Configuration Memory data.
10. Wait an appropriate amount of time.
11. Repeat steps 9 and 10 until all the desired con-
figuration settings are written. If setting memory
protection, write these last.
12. Send a control packet. Send a check and run
command. Also, send the two’s compliment of
the sum of all data written in the Data registers
in the same packet.
13. Send a RESET command. If self-verification suc-
ceeded, then the node should be running the new
application. This could be verified at the applica-
tion level by the programming source, or any
other node in the network that communicates
with the target.
EXAMPLE PROGRAMMING SEQUENCE
(PG MODE)
1.
Put the programming target in Boot mode.
2.
Send a control packet. Load the address with
the beginning memory. Unlock write operations.
Enable auto erase. Disable erase only.
3.
Send Program Memory data. The data must be
8 bytes and aligned on an even 8-byte address.
4.
Wait an appropriate amount of time.
5.
Read back the data written and compare. If fail,
then reset the pointer and try again, steps 3
and 4.
6.
Repeat steps 3, 4, and 5 until all Program
Memory is written.
7.
Send EEPROM Data Memory data.
8.
Wait an appropriate amount of time.
9.
Read back the data written and compare. If fail,
then reset the pointer and try again, steps 7
and 8.
10. Repeat steps 7, 8, and 9 until all EEPROM Data
Memory is written except for the last location.
11. Send one byte of Configuration Memory data.
12. Wait an appropriate amount of time.
13. Read back the data written and compare. If fail,
then reset the pointer and try again, steps 11
and 12.
14. Repeat steps 11, 12, and 13 until all the desired
configuration settings are written. If setting
memory protection, write these last.
15. Write 00h to the last location of EEPROM Data
Memory.
16. Send a RESET command. Functionality should
be verified at the application level by the
programming source, or any other node in the
network that communicates with the target.



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com