Книга: Embedded Linux Primer: A Practical, Real-World Approach
7.2.2. Flash Versus RAM
7.2.2. Flash Versus RAM
Another complexity inherent in bootloaders is that they are required to be stored in nonvolatile storage but are usually loaded into RAM for execution. Again, the complexity arises from the level of resources available for the bootloader to rely on. In a fully operational computer system running an operating system such as Linux, it is relatively easy to compile a program and invoke it from nonvolatile storage. The runtime libraries, operating system, and compiler work together to create the infrastructure necessary to load a program from nonvolatile storage into memory and pass control to it. The aforementioned "Hello World" program is a perfect example. When compiled, it can be loaded into memory and executed simply by typing the name of the executable (hello) on the command line (assuming, of course, that the executable exists somewhere on your PATH).
This infrastructure does not exist when a bootloader gains control upon power-on. Instead, the bootloader must create its own operational context and move itself, if required, to a suitable location in RAM. Furthermore, additional complexity is introduced by the requirement to execute from a read-only medium.
Оглавление книги
- 1.2.6 Flash EEPROM
- Рабочая среда Flash
- Private versus Shared Assemblies
- Parameter problem
- 2. How to Apply These Terms to Your New Programs
- The Programmers
- Flash-накопители
- Instagram как платформа для реализации.
- Специфика .NET Compact Framework: ADO.NET
- Для чего нужны папки Windows, Documents and Settings, Program Files и Temp?
- Можно ли указать использование по умолчанию вместо C:Program Files другого каталога для установки программ?
- Можно ли удалять из папки Program Files папки деинсталлированных программ?