Shulou(Shulou.com)06/01 Report--

This article mainly introduces what the image types of VxWorks in Boot are, which can be used for reference. Interested friends can refer to them. I hope you can learn a lot after reading this article.

VxWorks has several types of Image that can be used to boot, store, load, or execute scenarios. These different Image may contain different components

VxWorks

Only this type of Image (sometimes called a downloadable image) requires a bootstrap. It is most commonly used (and most practical) during the development phase because it does not need to be copied to Target's local storage device (such as rewriting Flash) every time it is modified. Because this kind of Image is usually stored in Host, or on Networks. It is downloaded to Target through the bootstrap and loaded into RAM. The symbol table can be saved in the Host file vxWorks.sym, which can be directly used by Host development tools. This method can reduce the size of Image and shorten the boot time.

Other types of Image (sometimes called stand-alone mirrors) do not require a separate bootstrap. They are usually used in the production phase and are stored in devices such as Target's Flash. You may also need to configure a stand-alone image with non-default startup parameters

VxWorks_rom

An Image stored in non-volatile devices of Target. It copies itself to RAM and then switches the processor to RAM execution. This Image does not require compression and is larger than other ROM-based Image, so its startup time is slightly slower; but its execution speed is faster than vxWorks

VxWorks_romCompress

Image stored in Target's non-volatile devices. It is almost completely compressed, and the processor executes a small amount of uncompressed parts immediately only at boot / restart. This small part is responsible for decompressing the compressed part of Image in ROM into RAM and causing the processor to jump to RAM execution. This compression makes it much smaller than other Image. However, the decompression operation increases the boot time. It takes longer to start than vxWorks_rom, but takes up less space than other ROM-based Image. Execution speed at runtime is the same as that of vxWorks_rom

VxWorks_romResident

Image stored in the ROM of Target. It only copies the data segment to the RAM at startup, while the text segment is left in the ROM, so it is described as a ROM resident type. It has the fastest startup time and uses a minimum number of RAM, but it runs more slowly than other Image types because getting instructions from ROM is much slower than getting instructions from RAM. It is obviously suitable for systems with limited memory resources. Thank you for reading this article carefully. I hope the article "what are the image types of VxWorks in Boot" shared by the editor will be helpful to you. At the same time, I also hope that you will support and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.