Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos in documentation #1674

Merged
merged 1 commit into from
Jul 31, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions CMSIS/DoxyGen/RTOS2/src/cmsis_os2.txt
Original file line number Diff line number Diff line change
Expand Up @@ -304,7 +304,7 @@ RTX5 offers three different memory allocation methods for objects:
- \ref StaticObjectMemory reserves memory during compile time and completely avoids that a system can be out of memory.
This is typically a required for some safety critical systems.

It possible to intermix all the memory allocation methods in the same application.
It's possible to intermix all the memory allocation methods in the same application.

\subsection GlobalMemoryPool Global Memory Pool

Expand Down Expand Up @@ -356,8 +356,8 @@ Memory Pool (osMemoryPoolAttr_t::mp_mem) | 4-Byte alignment. Size calculated
Message Queue (osMessageQueueAttr_t::mq_mem) | 4-Byte alignment. Size calculated with \ref osRtxMessageQueueMemSize.


In order to allow RTX5 aware debugging, i.e. Component Viewer, to recognize control blocks these
needs to be placed in individual memory sections, i.e. using `__attribute__((section(...)))`.
In order to allow RTX5 aware debugging, i.e. Component Viewer, to recognize control blocks,
they need to be placed in individual memory sections by using `__attribute__((section(...)))`.

RTX Object | Linker Section
--------------|------------------------
Expand Down
Loading