Skip to content

Fixed image links in MISRA C compliance appendix #16

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.

Sign up for GitHub

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

Merged
fdesbiens merged 1 commit into from
Feb 4, 2026
Merged

Fixed image links in MISRA C compliance appendix #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 6 additions & 6 deletions rtos-docs/threadx/appendix-e.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ source code. However, to enable the reuse, macros are used to replace
data structures specific to each core with function calls or an array
indexed by core, like the following:

image::misra-Compliance/image1.png[Image that shows an array indexed by core.]
image::media/misra-Compliance/image1.png[Image that shows an array indexed by core.]

Technically, this isn't replacing a reserved identifier, but the
MISRA-C:2004 specification indicates that anything with an underscore
Expand Down Expand Up @@ -248,13 +248,13 @@ C-STAT 1.4.4 MISRA-C:2004 and MISRA C:2012. The following figures show
the MISRA C rules checked by C-STAT (and should also serve as a
compliance matrix):

image::misra-Compliance/image2.png[Image that shows IAR EWARM 8.11.1.]
image::media/misra-Compliance/image2.png[Image that shows IAR EWARM 8.11.1.]

image::misra-Compliance/image3.png[Image that shows C-STAT 1.4.4.]
image::media/misra-Compliance/image3.png[Image that shows C-STAT 1.4.4.]

image::misra-Compliance/image4.png[Image that shows MISRA-C:2004.]
image::media/misra-Compliance/image4.png[Image that shows MISRA-C:2004.]

image::misra-Compliance/image5.png[Image that shows MISRA C:2012.]
image::media/misra-Compliance/image5.png[Image that shows MISRA C:2012.]

*Figure 1: MISRA-C:2004/MISRA C:2012 Compliance Matrix*

Expand All @@ -276,7 +276,7 @@ achieve full MISRA compliance. In addition to building ThreadX SMP with
*_TX_MISRA_ENABLE_*, the ThreadX project should have the C dialect C89
specified and strict language conformance selected, as follows:

image::misra-Compliance/image6.png[Screenshot that shows strict language conformance.]
image::media/misra-Compliance/image6.png[Screenshot that shows strict language conformance.]

Next, if the version of ThreadX does not have a pre-built
*_tx_misra.s_* assembly file, the *_tx_misra.c_* file should be
Expand Down