MPU for RTOS task isolation in ARM Architecture - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable the MPU for task isolation in an RTOS.

ARM Architecture

MPU->CTRL = [1] | MPU_CTRL_PRIVDEFENA_Msk;

Drag options to blanks, or click blank then click option'

AMPU_CTRL_HFNMIENA_Msk

BMPU_CTRL_DISABLE_Msk

CMPU_CTRL_PRIVDEFENA_Msk

DMPU_CTRL_ENABLE_Msk

Attempts:

3 left

💡 Hint

Common Mistakes

Using the disable flag instead of enable.

Confusing privilege default enable with MPU enable.

The MPU must be enabled using the MPU_CTRL_ENABLE_Msk flag to activate memory protection for tasks.

2fill in blank

medium

Complete the code to configure an MPU region base address for a task.

ARM Architecture

MPU->RNR = [1];  // Select region number
MPU->RBAR = task_base_address;

Drag options to blanks, or click blank then click option'

A0

B1

CMPU_REGION_NUMBER0

DMPU_REGION_NUMBER1

Attempts:

3 left

💡 Hint

Common Mistakes

Using symbolic constants that may not be defined.

Starting region numbering at 1 instead of 0.

Region number 0 is commonly used for the first MPU region configuration.

3fill in blank

hard

Fix the error in setting the MPU region size for task isolation.

ARM Architecture

MPU->RASR = ([1] << MPU_RASR_SIZE_Pos) | MPU_RASR_ENABLE_Msk;

Drag options to blanks, or click blank then click option'

A7

B5

C4

D6

Attempts:

3 left

💡 Hint

Common Mistakes

Using the actual size in bytes instead of the encoded value.

Off-by-one errors in size encoding.

The size field in the MPU_RASR register uses the value 7 to represent a 256-byte region (2^(7+1) = 256 bytes).

4fill in blank

hard

Fill both blanks to set the MPU region attributes for privileged read/write (unprivileged no-access) and execute never.

ARM Architecture

MPU->RASR = ([1] << MPU_RASR_AP_Pos) | ([2] << MPU_RASR_XN_Pos) | MPU_RASR_ENABLE_Msk;

Drag options to blanks, or click blank then click option'

A5

B1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing access permission values.

Forgetting to set the execute never bit.

Access permission 1 (AP=001) allows read/write access from privileged mode and no access from unprivileged mode. Execute never (XN) bit set to 1 disables execution.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps task names to their MPU region sizes if the size is greater than 128 bytes.

ARM Architecture

region_sizes = {{'{'}}[1]: [2] for [1], [2] in tasks.items() if [2] > 128{{'}}'}}

Drag options to blanks, or click blank then click option'

Atask

Bsize

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up keys and values in the comprehension.

Using inconsistent variable names.

The comprehension iterates over task and size from the dictionary. It maps each task to its size if the size is greater than 128 bytes.

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