VxWorks 7: VxWorks Memory
Welcome to the VxWorks Memory Course!
In this course, the configuration of both physical and virtual memory is discussed and the methods available to access and allocate each. Available functions to examine memory and their respective outputs are explained. We also look at the ability to create user defined partitions which could be used as a user heap.
Learning Objectives
Welcome to the VxWorks Memory Courses
In this introduction video, I am going to give you an overview of VxWorks® memory. I’ll describe the memory management and how virtual and physical memory are related. We will also go over the memory partition manager.
VxWorks® Memory
VxWorks uses the same memory model for both 32-bit and 64-bit CPUs. Only these data models are supported. VxWorks 7 does not require identity mapping—that is, the virtual and physical addresses must not be the same.
Full MMU support is always required. VxWorks cannot function without the CPU’s MMU. This means that RAM need not be presented in a single contiguous block of addresses. The mapping of the memory and I/O space is implemented dynamically.
Course Syllabus:
Choose a training offering that's right for you
Interested in Private Live Training Events?
