Skip to content

Commit 9c7c14d

Browse files
committed
basic-concepts: rephrasing
- add 'Cortex-A' to avoid expectations of a 64-bits Cortex-M - exemplify 'multitasking overhead'
1 parent 8b9d8cf commit 9c7c14d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pages/user-manual/basic-concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Smaller devices have much less resources, and are build around microcontrollers
2525

2626
In this case the application is monolithic and runs directly on the hardware, thus the name _bare-metal_.
2727

28-
µOS++ focuses on these [bare-metal](https://en.wikipedia.org/wiki/Bare_machine) applications, especially those running on ARM Cortex-M devices. Although µOS++ can be ported on larger ARM cores, even the 64-bits ones, there are no plans to include support for MMU, virtual memory, separate processes and other such features specific to the Unix world.
28+
µOS++ focuses on these [bare-metal](https://en.wikipedia.org/wiki/Bare_machine) applications, especially those running on ARM Cortex-M devices. Although µOS++ can be ported on larger ARM Cortex-A cores, even the 64-bits ones, there are no plans to include support for MMU, virtual memory, separate processes and other such features specific to the Unix world.
2929

3030
## Real-time systems
3131

@@ -110,7 +110,7 @@ One possible implementation is to loop until the data becomes available, but thi
110110

111111
Well behaved applications should never enter (long) busy loops waiting for conditions to occur, but instead suspend the thread and arrange for it to be resumed when the condition is met. During this waiting period the thread completely releases the CPU, so the CPU will be fully available for the other active threads.
112112

113-
For the sake of completeness, it should be noted that the only exception to the rule applies to short delays, where short means delays with durations comparable with the multitasking overhead. On most modern microcontrollers this is usually in the range of microseconds.
113+
For the sake of completeness, it should be noted that the only exception to the rule applies to short delays, where short means delays with durations comparable with the multitasking overhead required to suspend/resume threads (where the context switching time plays an important role). On most modern microcontrollers this is usually in the range of microseconds.
114114

115115
### The idle thread
116116

0 commit comments

Comments
 (0)