English
In-system programming of FLASH via control unit application
By Heiko Riessland, Programmierbare Logick & Systeme GmbH
edadesignline.com (August 12, 2008)
Introduction
A high level of data integrity and data security is essential when using FLASH memory in automotive control units. Indeed, to guarantee this for the entire life cycle of the control unit, attention should be given to a few rules. It is not only the harsh environmental conditions that can cause an end to this endeavor. For those that do not consider, at an early stage, how often and to which purpose a reprogramming of the FLASH content in the phases of production, operation and service takes place can sometimes experience nasty surprises.
How does in-system programming of FLASH essentially function?
On-chip FLASH memories are in vogue. At the same time, they first of all require a certain amount of rethinking by the user. To change the content of a FLASH memory certainly requires much more effort than to change the content of a random access memory (RAM). The reason: whereas for the writing of a RAM, a single machine command is sufficient; for FLASH programming a special algorithm, which typically is implemented via special registers, is required. In addition, the FLASH memory must be erased before each reprogramming.
Fundamentally, a FLASH device can be programmed via any target interface, which can read and write registers — for example, programming via JTAG. However, this possibility is in practice hardly ever used because it is simply too slow and inflexible. Nowadays, more often, the algorithm for programming the FLASH is usually downloaded direct in an on-chip RAM of the microcontroller and then also executed in it. With this method, significantly higher speeds can be achieved compared to direct programming via JTAG. This is because typical cyclical register polling by the MCU in the FLASH algorithm can be processed many times faster than via the JTAG connection. An additional advantage of this variant: because it functions independent of the respective target interface the connection can not only be achieved via JTAG, but also - for example - via the CAN bus.
The smallest structural unit of a FLASH memory is the page. It can be programmed at once. Furthermore, a typical on-chip FLASH memory is logically divided into various sectors, whereby the number and size of the sectors are dependent on the microcontroller type. Erasing can only be carried out by sector or also the entire FLASH. Attention should be paid that the execution of the programming routine can not take place in the memory, which is to be programmed.
edadesignline.com (August 12, 2008)
Introduction
A high level of data integrity and data security is essential when using FLASH memory in automotive control units. Indeed, to guarantee this for the entire life cycle of the control unit, attention should be given to a few rules. It is not only the harsh environmental conditions that can cause an end to this endeavor. For those that do not consider, at an early stage, how often and to which purpose a reprogramming of the FLASH content in the phases of production, operation and service takes place can sometimes experience nasty surprises.
How does in-system programming of FLASH essentially function?
On-chip FLASH memories are in vogue. At the same time, they first of all require a certain amount of rethinking by the user. To change the content of a FLASH memory certainly requires much more effort than to change the content of a random access memory (RAM). The reason: whereas for the writing of a RAM, a single machine command is sufficient; for FLASH programming a special algorithm, which typically is implemented via special registers, is required. In addition, the FLASH memory must be erased before each reprogramming.
Fundamentally, a FLASH device can be programmed via any target interface, which can read and write registers — for example, programming via JTAG. However, this possibility is in practice hardly ever used because it is simply too slow and inflexible. Nowadays, more often, the algorithm for programming the FLASH is usually downloaded direct in an on-chip RAM of the microcontroller and then also executed in it. With this method, significantly higher speeds can be achieved compared to direct programming via JTAG. This is because typical cyclical register polling by the MCU in the FLASH algorithm can be processed many times faster than via the JTAG connection. An additional advantage of this variant: because it functions independent of the respective target interface the connection can not only be achieved via JTAG, but also - for example - via the CAN bus.
The smallest structural unit of a FLASH memory is the page. It can be programmed at once. Furthermore, a typical on-chip FLASH memory is logically divided into various sectors, whereby the number and size of the sectors are dependent on the microcontroller type. Erasing can only be carried out by sector or also the entire FLASH. Attention should be paid that the execution of the programming routine can not take place in the memory, which is to be programmed.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
New Articles
- Quantum Readiness Considerations for Suppliers and Manufacturers
- A Rad Hard ASIC Design Approach: Triple Modular Redundancy (TMR)
- Early Interactive Short Isolation for Faster SoC Verification
- The Ideal Crypto Coprocessor with Root of Trust to Support Customer Complete Full Chip Evaluation: PUFcc gained SESIP and PSA Certified™ Level 3 RoT Component Certification
- Advanced Packaging and Chiplets Can Be for Everyone
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- UPF Constraint coding for SoC - A Case Study
- Dynamic Memory Allocation and Fragmentation in C and C++
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)