English
Use Pre-Configured Device Drivers (PCD) to reduce embedded system memory footprint
By Ashutosh Sharma, STMicroelectronics
Embedded.com (10/22/08, 12:15:00 AM EDT)
In embedded systems, the predominant bottle-neck is the size of the binaries and the RAM used. The large memory size results in an increase in the cost of the final system due to the large FLASH and RAM.
However, by using preconfigured device (PCD) driver techniques developers can significantly reduce the usage of memory to minimize the cost of the final product with only slight changes in the conventional development method/technique.
PCD does not require any extra hardware or critical software development. At present, the developed code is rewritten, such that the final binary is smaller in size. Moreover, the start-up of the device driver is faster compared to the original one.
Embedded.com (10/22/08, 12:15:00 AM EDT)
In embedded systems, the predominant bottle-neck is the size of the binaries and the RAM used. The large memory size results in an increase in the cost of the final system due to the large FLASH and RAM.
However, by using preconfigured device (PCD) driver techniques developers can significantly reduce the usage of memory to minimize the cost of the final product with only slight changes in the conventional development method/technique.
PCD does not require any extra hardware or critical software development. At present, the developed code is rewritten, such that the final binary is smaller in size. Moreover, the start-up of the device driver is faster compared to the original one.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Reusable Device Simulation Models for Embedded System Virtual Platforms
- Memory system tradeoffs: embedded DRAM in SoCs, Chip-on-Board, multichip packages or memory modules
- A new era for embedded memory
- Emerging Trends and Challenges in Embedded System Design
- Automating C test cases for embedded system verification