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)
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.
To read the full article, click here
Related Semiconductor IP
- USB 4.0 V2 PHY - 4TX/2RX, TSMC N3P , North/South Poly Orientation
- FH-OFDM Modem
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- PQC CRYSTALS core for accelerating NIST FIPS 202 FIPS 203 and FIPS 204
- USB Full Speed Transceiver
Related White Papers
- How to write DSP device drivers
- Customized DSP -> Applications take the driver's seat
- IP Integration - Size Matters! - Reducing the size of a USB 2.0 device core
- FPGAs: Embedded Apps : Designing an FPGA-based network communications device
Latest White Papers
- FastPath: A Hybrid Approach for Efficient Hardware Security Verification
- Automotive IP-Cores: Evolution and Future Perspectives
- TROJAN-GUARD: Hardware Trojans Detection Using GNN in RTL Designs
- How a Standardized Approach Can Accelerate Development of Safety and Security in Automotive Imaging Systems
- SV-LLM: An Agentic Approach for SoC Security Verification using Large Language Models