MPU for RTOS task isolation in ARM Architecture - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does an MPU help in RTOS task isolation?

In an RTOS running on an ARM processor, what is the primary role of the Memory Protection Unit (MPU) in task isolation?

A It restricts each task's access to only its assigned memory regions to prevent interference.

B It increases the processor clock speed to improve task switching performance.

C It manages the scheduling order of tasks based on priority levels.

D It encrypts the memory contents of each task to secure data.

💡 Hint

Think about how memory access control can prevent tasks from affecting each other.

The MPU sets memory access permissions so each task can only read or write to its own memory areas. This prevents tasks from accidentally or maliciously accessing others' memory, ensuring isolation.

📋 Factual

intermediate

MPU region configuration limits

What is a typical limitation of the number of memory regions that an ARM MPU can configure for task isolation?

A MPU can configure unlimited regions dynamically.

B MPU can configure only 1 region per task.

C MPU can configure exactly 16 regions per task.

D MPU can configure up to 8 regions per task.

💡 Hint

Consider the hardware constraints of MPU region registers.

Most ARM MPUs support up to 8 configurable regions. This limit means tasks must share these regions carefully for isolation.

🔍 Analysis

advanced

Effect of incorrect MPU configuration on RTOS tasks

What is the most likely outcome if an RTOS task's MPU region is configured with read-write access to another task's memory?

A The task can corrupt or read data from the other task, breaking isolation.

B The MPU will automatically block the access and raise an exception.

C The RTOS scheduler will prevent the task from running.

D The task will run slower due to extra MPU checks.

💡 Hint

Think about what happens when access permissions are too permissive.

If the MPU allows read-write access to another task's memory, that task can modify or read data it shouldn't, causing data corruption and security risks.

❓ Comparison

advanced

MPU vs MMU in task isolation

Which statement correctly compares the MPU and MMU regarding task isolation in embedded systems?

A Both MPU and MMU provide identical memory protection features.

B MPU supports virtual memory, MMU only supports fixed physical regions.

C MPU provides simple fixed regions for protection, while MMU supports complex virtual memory mapping.

D MMU is only used in microcontrollers, MPU in desktop CPUs.

💡 Hint

Consider the difference between physical and virtual memory management.

MPU uses fixed physical memory regions with simple access control, suitable for microcontrollers. MMU supports virtual memory with complex page tables, common in full operating systems.

❓ Reasoning

expert

Designing MPU regions for a multi-task RTOS

You have an RTOS with 4 tasks, each needing isolated memory. The MPU supports 8 regions total. Which design approach best ensures isolation and efficient use of MPU regions?

A Use 8 regions for all tasks' data only, ignoring code protection.

B Assign 2 MPU regions per task: one for code (read-only) and one for data (read-write).

C Assign 4 MPU regions to one task and share the rest among others.

D Assign 1 MPU region per task covering both code and data with read-write access.

💡 Hint

Think about separating code and data permissions for security and how to use limited regions.

Separating code (read-only) and data (read-write) per task improves security by preventing code modification. Using 2 regions per task fits the 8-region limit for 4 tasks.

Practice

1. What is the main purpose of the Memory Protection Unit (MPU) in an RTOS environment?

easy

A. To isolate tasks by controlling their memory access

B. To increase the CPU clock speed

C. To manage power consumption of the processor

D. To handle input/output operations

Solution

1. Step 1: Understand MPU role in RTOS

   The MPU is designed to control which memory areas a task can access, preventing interference between tasks.

2. Step 2: Compare MPU functions with other options

   Increasing CPU speed, managing power, or handling I/O are not MPU functions.

3. Final Answer:

   To isolate tasks by controlling their memory access -> Option A

4. Quick Check:

   MPU isolates tasks = To isolate tasks by controlling their memory access [OK]

Hint: MPU controls memory access to keep tasks separate [OK]

Common Mistakes:

• Confusing MPU with CPU speed control
• Thinking MPU manages power or I/O
• Assuming MPU schedules tasks

2. Which of the following is the correct way to define an MPU region for a task's stack in ARM architecture?

easy

A. Set region base address and size, then enable read/write access

B. Only set the region size without base address

C. Enable execute-only access for the stack region

D. Disable the MPU for the stack region

Solution

1. Step 1: Identify MPU region setup requirements

   MPU regions require a base address and size to define memory boundaries.

2. Step 2: Determine correct access permissions for stack

   The stack needs read/write access, not execute-only or disabled MPU.

3. Final Answer:

   Set region base address and size, then enable read/write access -> Option A

4. Quick Check:

   Stack needs base, size, read/write access = Set region base address and size, then enable read/write access [OK]

Hint: Stack needs base, size, and read/write enabled [OK]

Common Mistakes:

• Omitting base address when defining region
• Setting execute-only for stack
• Disabling MPU for stack memory

3. Consider this simplified MPU configuration code snippet for two RTOS tasks:

Task1: MPU region base=0x20000000, size=32KB, RW access
Task2: MPU region base=0x20008000, size=32KB, RW access

What happens if Task1 tries to access address 0x20009000?

medium

A. Access allowed because address is within Task1's region

B. Access allowed because MPU ignores overlapping regions

C. Access denied because MPU is disabled

D. Access denied because address is outside Task1's region

Solution

1. Step 1: Calculate Task1's memory range

   Task1's region starts at 0x20000000 and covers 32KB (0x8000 bytes), so it ends at 0x20007FFF.

2. Step 2: Check if 0x20009000 is inside Task1's region

   Address 0x20009000 is greater than 0x20007FFF, so it is outside Task1's allowed memory.

3. Final Answer:

   Access denied because address is outside Task1's region -> Option D

4. Quick Check:

   Address outside region = Access denied = Access denied because address is outside Task1's region [OK]

Hint: Check address range carefully for access permission [OK]

Common Mistakes:

• Assuming overlapping regions allow access
• Miscalculating region size boundaries
• Ignoring MPU enforcement

4. A developer configures an MPU region for a task's data with execute permission enabled. What is the likely problem with this setup?

medium

A. The MPU will disable the task completely

B. The task will not be able to read its data

C. It may allow code execution from data memory, risking security

D. The stack size will automatically increase

Solution

1. Step 1: Understand MPU execute permission

   Enabling execute permission on data memory allows instructions to run from that area.

2. Step 2: Identify security risk

   This can lead to security risks like code injection or unintended execution.

3. Final Answer:

   It may allow code execution from data memory, risking security -> Option C

4. Quick Check:

   Execute permission on data = security risk = It may allow code execution from data memory, risking security [OK]

Hint: Data regions should not have execute permission [OK]

Common Mistakes:

• Thinking execute permission affects reading data
• Assuming MPU disables task on wrong permissions
• Confusing stack size with MPU permissions

5. In an RTOS using MPU for task isolation, how can you ensure that a shared peripheral register is safely accessed by multiple tasks?

hard

A. Disable MPU for all tasks accessing the peripheral

B. Create an MPU region for the peripheral with read/write access and share it among tasks

C. Assign execute-only permission to the peripheral region

D. Map the peripheral region as no-access in all tasks

Solution

1. Step 1: Understand shared peripheral access

   Peripheral registers must be accessible by tasks that use them, typically with read/write permissions.

2. Step 2: Configure MPU regions for safe sharing

   Creating an MPU region with read/write access for the peripheral and sharing it among tasks allows controlled access without disabling MPU.

3. Final Answer:

   Create an MPU region for the peripheral with read/write access and share it among tasks -> Option B

4. Quick Check:

   Shared peripheral needs shared RW MPU region = Create an MPU region for the peripheral with read/write access and share it among tasks [OK]

Hint: Share peripheral region with RW access in MPU for tasks [OK]

Common Mistakes:

• Disabling MPU instead of configuring regions
• Setting execute-only permission on peripherals
• Blocking access by setting no-access