From 6e3f238df7d36e32180793b0422d5d08625804f7 Mon Sep 17 00:00:00 2001 From: Quantum Leaps Date: Fri, 4 Sep 2015 12:08:22 -0400 Subject: [PATCH] 5.5.0 --- 3rd_party/CMSIS-RTX/SRC/GCC/ArInp.Scr | 19 + 3rd_party/CMSIS-RTX/SRC/GCC/ArInp.bat | 1 + .../CMSIS-RTX/SRC/GCC/RTX_Lib_CM.uvprojx | 2 +- 3rd_party/ek-lm3s6965/arm/startup_LM3S6965.s | 69 +- 3rd_party/ek-lm3s6965/gnu/startup_LM3S6965.c | 63 +- 3rd_party/ek-lm3s6965/iar/startup_LM3S6965.s | 45 +- 3rd_party/ek-lm3s811/arm/startup_LM3S811.s | 63 +- 3rd_party/ek-lm3s811/gnu/startup_LM3S811.c | 63 +- 3rd_party/ek-lm3s811/iar/startup_LM3S811.s | 43 +- .../ek-tm4c123gxl/arm/startup_TM4C123GH6PM.s | 55 +- .../ek-tm4c123gxl/gnu/startup_TM4C123GH6PM.c | 63 +- .../ek-tm4c123gxl/iar/startup_TM4C123GH6PM.s | 323 +- 3rd_party/mbed-lpc1768/arm/startup_LPC17xx.s | 56 +- 3rd_party/mbed-lpc1768/gnu/startup_LPC17xx.c | 52 +- 3rd_party/mbed-lpc1768/iar/startup_LPC17xx.s | 46 +- .../nucleo-l053r8/arm/startup_stm32l053xx.s | 42 +- .../nucleo-l053r8/gnu/startup_stm32l053xx.c | 63 +- .../nucleo-l053r8/iar/startup_stm32l053xx.s | 43 +- .../nucleo-l152re/arm/startup_stm32l1xx.s | 42 +- .../nucleo-l152re/gnu/startup_stm32l1xx.c | 63 +- .../nucleo-l152re/iar/startup_stm32l1xx.s | 43 +- .../stm32f4-discovery/arm/startup_stm32f4xx.s | 66 +- .../stm32f4-discovery/gnu/startup_stm32f4xx.c | 72 +- .../stm32f4-discovery/iar/startup_stm32f4xx.s | 49 +- GPL.txt => GPLv3.txt | 0 COPYING => LICENSE.txt | 0 doxygen/Doxyfile | 2143 +----------- doxygen/Doxyfile-CHM | 2141 +----------- doxygen/{about.dox => about.cc} | 27 +- doxygen/{design.dox => design.cc} | 9 +- doxygen/{exa.dox => exa.cc} | 28 + doxygen/{exa_apps.dox => exa_apps.cc} | 26 +- doxygen/{exa_mware.dox => exa_mware.cc} | 0 doxygen/{exa_native.dox => exa_native.cc} | 0 doxygen/{exa_os.dox => exa_os.cc} | 4 +- doxygen/{exa_rtos.dox => exa_rtos.cc} | 0 doxygen/{history.dox => history.cc} | 91 +- .../{images => img}/AN_Coding_Standard.jpg | Bin .../AN_Getting_Started_with_QPC.jpg | Bin doxygen/{images => img}/AN_MISRA-QPC.jpg | Bin .../{images => img}/AN_Simple_OOP_in_C.jpg | Bin doxygen/img/img.htm | 4 + doxygen/{lint.dox => lint.cc} | 0 doxygen/make.bat | 22 +- doxygen/{metrics.dox => metrics.cc} | 498 ++- doxygen/{modules.dox => modules.cc} | 0 doxygen/{ports.dox => ports.cc} | 0 doxygen/{ports_native.dox => ports_native.cc} | 0 doxygen/{ports_os.dox => ports_os.cc} | 0 doxygen/{ports_rtos.dox => ports_rtos.cc} | 0 doxygen/qpc_metrics.txt | 2930 +++++++++++++++++ doxygen/rsm.bat | 13 +- doxygen/scripts/jquery.plugins.min.js | 228 -- doxygen/scripts/ql.js | 20 - doxygen/snippets/qmp_init.c | 15 + doxygen/snippets/qmp_use.c | 12 + examples/arm-cm/blinky_ek-tm4c123gxl/blinky.c | 15 +- .../qk/arm/blinky-qk.uvoptx | 79 +- .../qk/arm/blinky-qk.uvprojx | 73 +- examples/arm-cm/blinky_ek-tm4c123gxl/qk/bsp.c | 33 +- .../blinky_ek-tm4c123gxl/qk/gnu/Makefile | 16 +- .../blinky_ek-tm4c123gxl/qk/iar/blinky-qk.ewp | 159 +- .../qv/arm/blinky-qv.uvoptx | 76 +- .../qv/arm/blinky-qv.uvprojx | 44 +- examples/arm-cm/blinky_ek-tm4c123gxl/qv/bsp.c | 35 +- .../blinky_ek-tm4c123gxl/qv/gnu/Makefile | 14 +- .../blinky_ek-tm4c123gxl/qv/iar/blinky-qv.ewp | 159 +- .../blinky_ek-tm4c123gxl/win32-qv/Makefile | 7 +- .../blinky_ek-tm4c123gxl/win32/Makefile | 11 +- examples/arm-cm/dpp_ek-tm4c123gxl/.dpp | 58 + .../dpp_ek-tm4c123gxl/lint/lint_out.txt | 320 +- .../dpp_ek-tm4c123gxl/qk/arm/dpp-qk.uvoptx | 85 +- .../dpp_ek-tm4c123gxl/qk/arm/dpp-qk.uvprojx | 73 +- examples/arm-cm/dpp_ek-tm4c123gxl/qk/bsp.c | 209 +- .../arm-cm/dpp_ek-tm4c123gxl/qk/gnu/Makefile | 14 +- .../dpp_ek-tm4c123gxl/qk/iar/dpp-qk.ewp | 159 +- .../arm-cm/dpp_ek-tm4c123gxl/qspy/dpp.tcl | 375 +++ .../dpp_ek-tm4c123gxl/qspy/img/BTN_DWN.gif | Bin 0 -> 2071 bytes .../dpp_ek-tm4c123gxl/qspy/img/BTN_UP.gif | Bin 0 -> 1987 bytes .../dpp_ek-tm4c123gxl/qspy/img/eating.gif | Bin 0 -> 3169 bytes .../dpp_ek-tm4c123gxl/qspy/img/hungry.gif | Bin 0 -> 2428 bytes .../dpp_ek-tm4c123gxl/qspy/img/thinking.gif | Bin 0 -> 2378 bytes .../dpp_ek-tm4c123gxl/qspy/qspyview.bat | 1 + .../dpp_ek-tm4c123gxl/qspy/qspyview.lnk | Bin 0 -> 884 bytes .../dpp_ek-tm4c123gxl/qv/arm/dpp-qv.uvoptx | 77 +- .../dpp_ek-tm4c123gxl/qv/arm/dpp-qv.uvprojx | 74 +- examples/arm-cm/dpp_ek-tm4c123gxl/qv/bsp.c | 222 +- .../arm-cm/dpp_ek-tm4c123gxl/qv/gnu/Makefile | 14 +- .../dpp_ek-tm4c123gxl/qv/iar/dpp-qv.ewp | 163 +- .../dpp_ek-tm4c123gxl/win32-qv/Makefile | 11 +- .../arm-cm/dpp_ek-tm4c123gxl/win32-qv/bsp.c | 75 +- .../win32-qv/dpp-gui.vcxproj | 46 +- .../win32-qv/dpp-gui.vcxproj.filters | 23 +- .../arm-cm/dpp_ek-tm4c123gxl/win32/Makefile | 11 +- examples/arm-cm/dpp_ek-tm4c123gxl/win32/bsp.c | 75 +- .../dpp_ek-tm4c123gxl/win32/dpp-gui.vcxproj | 38 +- .../win32/dpp-gui.vcxproj.filters | 23 +- .../dpp_mbed-lpc1768/qk/arm/dpp-qk.uvoptx | 88 +- .../dpp_mbed-lpc1768/qk/arm/dpp-qk.uvprojx | 65 +- examples/arm-cm/dpp_mbed-lpc1768/qk/bsp.c | 85 +- .../arm-cm/dpp_mbed-lpc1768/qk/gnu/Makefile | 12 +- .../arm-cm/dpp_mbed-lpc1768/qk/iar/dpp-qk.ewp | 186 +- .../dpp_mbed-lpc1768/qv/arm/dpp-qv.uvoptx | 80 +- .../dpp_mbed-lpc1768/qv/arm/dpp-qv.uvprojx | 65 +- examples/arm-cm/dpp_mbed-lpc1768/qv/bsp.c | 85 +- .../arm-cm/dpp_mbed-lpc1768/qv/gnu/Makefile | 12 +- .../arm-cm/dpp_mbed-lpc1768/qv/iar/dpp-qv.ewp | 156 +- .../dpp_nucleo-l053r8/qk/arm/dpp-qk.uvoptx | 153 +- .../dpp_nucleo-l053r8/qk/arm/dpp-qk.uvprojx | 59 +- examples/arm-cm/dpp_nucleo-l053r8/qk/bsp.c | 84 +- .../arm-cm/dpp_nucleo-l053r8/qk/gnu/Makefile | 12 +- .../dpp_nucleo-l053r8/qk/iar/dpp-qk.ewp | 192 +- .../dpp_nucleo-l053r8/qv/arm/dpp-qv.uvoptx | 133 +- .../dpp_nucleo-l053r8/qv/arm/dpp-qv.uvprojx | 59 +- examples/arm-cm/dpp_nucleo-l053r8/qv/bsp.c | 84 +- .../arm-cm/dpp_nucleo-l053r8/qv/gnu/Makefile | 12 +- .../dpp_nucleo-l053r8/qv/iar/dpp-qv.ewp | 156 +- .../dpp_nucleo-l152re/qk/arm/dpp-qk.uvoptx | 168 +- .../dpp_nucleo-l152re/qk/arm/dpp-qk.uvprojx | 59 +- examples/arm-cm/dpp_nucleo-l152re/qk/bsp.c | 84 +- .../arm-cm/dpp_nucleo-l152re/qk/gnu/Makefile | 12 +- .../dpp_nucleo-l152re/qk/iar/dpp-qk.ewp | 157 +- .../dpp_nucleo-l152re/qv/arm/dpp-qv.uvoptx | 121 +- .../dpp_nucleo-l152re/qv/arm/dpp-qv.uvprojx | 59 +- examples/arm-cm/dpp_nucleo-l152re/qv/bsp.c | 84 +- .../arm-cm/dpp_nucleo-l152re/qv/gnu/Makefile | 12 +- .../dpp_nucleo-l152re/qv/iar/dpp-qv.ewp | 157 +- .../game_ek-lm3s811/qk/arm/game-qk.uvoptx | 82 +- .../game_ek-lm3s811/qk/arm/game-qk.uvprojx | 59 +- examples/arm-cm/game_ek-lm3s811/qk/bsp.c | 87 +- .../arm-cm/game_ek-lm3s811/qk/gnu/Makefile | 12 +- .../arm-cm/game_ek-lm3s811/qk/iar/game-qk.ewp | 156 +- .../game_ek-lm3s811/qv/arm/game-qv.uvoptx | 78 +- .../game_ek-lm3s811/qv/arm/game-qv.uvprojx | 59 +- examples/arm-cm/game_ek-lm3s811/qv/bsp.c | 83 +- .../arm-cm/game_ek-lm3s811/qv/gnu/Makefile | 14 +- .../arm-cm/game_ek-lm3s811/qv/iar/game-qv.ewp | 156 +- .../arm-cm/game_ek-lm3s811/win32-qv/Makefile | 17 +- .../arm-cm/game_ek-lm3s811/win32-qv/bsp.c | 75 +- .../game_ek-lm3s811/win32-qv/game-gui.vcxproj | 39 +- .../win32-qv/game-gui.vcxproj.filters | 23 +- .../arm-cm/game_ek-lm3s811/win32/Makefile | 17 +- examples/arm-cm/game_ek-lm3s811/win32/bsp.c | 75 +- .../game_ek-lm3s811/win32/game-gui.vcxproj | 37 +- .../win32/game-gui.vcxproj.filters | 23 +- examples/arm7-9/dpp_at91sam7s-ek/qk/iar/bsp.c | 83 +- .../arm7-9/dpp_at91sam7s-ek/qk/iar/dpp-qk.ewp | 159 +- examples/arm7-9/dpp_at91sam7s-ek/qv/iar/bsp.c | 85 +- .../arm7-9/dpp_at91sam7s-ek/qv/iar/dpp-qv.ewp | 159 +- .../avr/blinky_arduino-uno/qk/gnu/Makefile | 12 +- examples/avr/blinky_arduino-uno/qk/gnu/bsp.c | 19 +- .../blinky_arduino-uno/qk/iar/blinky-qk.ewp | 168 +- examples/avr/blinky_arduino-uno/qk/iar/bsp.c | 19 +- .../avr/blinky_arduino-uno/qv/gnu/Makefile | 12 +- examples/avr/blinky_arduino-uno/qv/gnu/bsp.c | 19 +- .../blinky_arduino-uno/qv/iar/blinky-qv.ewp | 168 +- examples/avr/blinky_arduino-uno/qv/iar/bsp.c | 19 +- examples/avr/dpp_arduino-uno/qk/gnu/Makefile | 12 +- examples/avr/dpp_arduino-uno/qk/gnu/bsp.c | 83 +- examples/avr/dpp_arduino-uno/qk/iar/bsp.c | 84 +- .../avr/dpp_arduino-uno/qk/iar/dpp-qk.ewp | 166 +- examples/avr/dpp_arduino-uno/qv/gnu/Makefile | 12 +- examples/avr/dpp_arduino-uno/qv/gnu/bsp.c | 84 +- examples/avr/dpp_arduino-uno/qv/iar/bsp.c | 84 +- .../avr/dpp_arduino-uno/qv/iar/dpp-qv.ewp | 166 +- .../blinky_ek-tm4c123gxl/arm/blinky.uvoptx | 78 +- .../blinky_ek-tm4c123gxl/arm/blinky.uvprojx | 74 +- examples/cmsis-rtx/blinky_ek-tm4c123gxl/bsp.c | 27 +- .../blinky_ek-tm4c123gxl/gnu/.cproject | 64 - .../blinky_ek-tm4c123gxl/gnu/.project | 32 - .../blinky_ek-tm4c123gxl/gnu/Makefile | 14 +- .../blinky_ek-tm4c123gxl/iar/blinky.ewp | 156 +- .../dpp_ek-tm4c123gxl/arm/dpp.uvoptx | 64 +- .../dpp_ek-tm4c123gxl/arm/dpp.uvprojx | 72 +- examples/cmsis-rtx/dpp_ek-tm4c123gxl/bsp.c | 119 +- .../cmsis-rtx/dpp_ek-tm4c123gxl/gnu/Makefile | 14 +- .../cmsis-rtx/dpp_ek-tm4c123gxl/iar/dpp.ewp | 156 +- .../dpp_nucleo-l053r8/arm/dpp.uvoptx | 133 +- .../dpp_nucleo-l053r8/arm/dpp.uvprojx | 59 +- examples/cmsis-rtx/dpp_nucleo-l053r8/bsp.c | 82 +- .../cmsis-rtx/dpp_nucleo-l053r8/gnu/Makefile | 12 +- .../cmsis-rtx/dpp_nucleo-l053r8/iar/dpp.ewp | 156 +- .../dpp_nucleo-l152re/arm/dpp.uvoptx | 119 +- .../dpp_nucleo-l152re/arm/dpp.uvprojx | 59 +- examples/cmsis-rtx/dpp_nucleo-l152re/bsp.c | 85 +- .../cmsis-rtx/dpp_nucleo-l152re/gnu/Makefile | 12 +- .../cmsis-rtx/dpp_nucleo-l152re/iar/dpp.ewp | 156 +- .../arm-cm/dpp_stm32f429-discovery/bsp.c | 70 +- .../dpp_stm32f429-discovery/iar/dpp.ewp | 158 +- .../arm-cm/blinky_ek-tm4c123gxl/bsp.c | 28 +- .../arm-cm/blinky_ek-tm4c123gxl/gnu/Makefile | 14 +- .../blinky_ek-tm4c123gxl/iar/blinky.ewp | 156 +- .../freertos/arm-cm/dpp_ek-tm4c123gxl/bsp.c | 123 +- .../arm-cm/dpp_ek-tm4c123gxl/gnu/Makefile | 14 +- .../arm-cm/dpp_ek-tm4c123gxl/iar/dpp.ewp | 156 +- .../lwip/arm-cm/lwip_ek-lm3s6965/qk/bsp.c | 98 +- .../arm-cm/lwip_ek-lm3s6965/qk/gnu/Makefile | 12 +- .../lwip_ek-lm3s6965/qk/iar/lwip-qk.ewp | 156 +- .../lwip/arm-cm/lwip_ek-lm3s6965/qv/bsp.c | 84 +- .../arm-cm/lwip_ek-lm3s6965/qv/gnu/Makefile | 12 +- .../lwip_ek-lm3s6965/qv/iar/lwip-qv.ewp | 158 +- .../msp430/blinky_msp-exp430f5529lp/qk/bsp.c | 20 +- .../blinky_msp-exp430f5529lp/qk/ccs/.cproject | 10 +- .../blinky_msp-exp430f5529lp/qk/ccs/.project | 9 +- .../qk/iar/blinky-qk.ewp | 12 +- .../msp430/blinky_msp-exp430f5529lp/qv/bsp.c | 22 +- .../blinky_msp-exp430f5529lp/qv/ccs/.cproject | 25 +- .../blinky-qv_msp-exp430f5529lp.launch | 14 +- .../blinky_msp-exp430f5529lp/qv/ccs/.project | 9 +- .../qv/iar/blinky-qv.ewp | 12 +- examples/msp430/blinky_msp-exp430g2/qk/bsp.c | 22 +- .../blinky_msp-exp430g2/qk/ccs/.cproject | 25 +- .../.launches/blinky-qk_msp-exp430g2.launch | 14 +- .../blinky_msp-exp430g2/qk/ccs/.project | 9 +- .../blinky_msp-exp430g2/qk/iar/blinky-qk.ewp | 12 +- examples/msp430/blinky_msp-exp430g2/qv/bsp.c | 20 +- .../blinky_msp-exp430g2/qv/ccs/.cproject | 10 +- .../blinky_msp-exp430g2/qv/ccs/.project | 9 +- .../blinky_msp-exp430g2/qv/iar/blinky-qv.ewp | 12 +- examples/msp430/dpp_msp-exp430g2/qk/bsp.c | 85 +- .../msp430/dpp_msp-exp430g2/qk/ccs/.cproject | 25 +- .../ccs/.launches/dpp-qk_msp-exp430g2.launch | 14 +- .../msp430/dpp_msp-exp430g2/qk/ccs/.project | 9 +- .../msp430/dpp_msp-exp430g2/qk/iar/dpp-qk.ewp | 12 +- examples/msp430/dpp_msp-exp430g2/qv/bsp.c | 85 +- .../msp430/dpp_msp-exp430g2/qv/ccs/.cproject | 25 +- .../ccs/.launches/dpp-qv_msp-exp430g2.launch | 2 +- .../msp430/dpp_msp-exp430g2/qv/ccs/.project | 9 +- .../msp430/dpp_msp-exp430g2/qv/iar/dpp-qv.ewp | 12 +- examples/posix/blinky/Makefile | 156 +- examples/posix/blinky/bsp.c | 18 +- examples/posix/dpp/Makefile | 157 +- examples/posix/dpp/bsp.c | 108 +- examples/posix/dpp/make.tcl | 194 -- examples/posix/qhsmtst/Makefile | 155 +- examples/posix/qmsmtst/Makefile | 155 +- examples/posix/qmsmtst/log.txt | 23 + examples/threadx/dpp_visual-studio/bsp.c | 91 +- .../threadx/dpp_visual-studio/dpp.vcxproj | 4 + .../dpp_visual-studio/dpp.vcxproj.filters | 1 + .../arm-cm/dpp_ek-tm4c123gxl/arm/dpp.uvoptx | 90 +- .../arm-cm/dpp_ek-tm4c123gxl/arm/dpp.uvprojx | 72 +- .../ucos-ii/arm-cm/dpp_ek-tm4c123gxl/bsp.c | 117 +- .../arm-cm/dpp_ek-tm4c123gxl/iar/dpp.ewp | 159 +- .../arm-cm/dpp_nucleo-l152re/arm/dpp.uvoptx | 143 +- .../arm-cm/dpp_nucleo-l152re/arm/dpp.uvprojx | 59 +- .../ucos-ii/arm-cm/dpp_nucleo-l152re/bsp.c | 85 +- .../arm-cm/dpp_nucleo-l152re/iar/dpp.ewp | 186 +- examples/win32-qv/dpp/Makefile | 24 +- examples/win32-qv/dpp/bsp.c | 304 +- examples/win32-qv/dpp/bsp.h | 2 +- examples/win32-qv/dpp/dpp.vcxproj | 22 +- examples/win32-qv/dpp/dpp.vcxproj.filters | 30 + examples/win32-qv/dpp/main.c | 4 +- examples/win32-qv/reminder2/Makefile | 7 +- examples/win32-qv/reminder2/reminder2.c | 12 +- examples/win32/calc/Makefile | 7 +- examples/win32/calc2/Makefile | 7 +- examples/win32/comp/Makefile | 7 +- examples/win32/comp_qm/Makefile | 9 +- examples/win32/defer/Makefile | 7 +- examples/win32/defer/defer.c | 53 +- examples/win32/dpp/Makefile | 24 +- examples/win32/dpp/bsp.c | 269 +- examples/win32/dpp/bsp.h | 21 +- examples/win32/dpp/dpp.vcxproj | 18 +- examples/win32/dpp/dpp.vcxproj.filters | 31 + examples/win32/dpp/main.c | 39 +- examples/win32/history_qhsm/Makefile | 7 +- examples/win32/history_qhsm/history.c | 5 + examples/win32/history_qhsm/history.qm | 9 +- examples/win32/history_qmsm/Makefile | 7 +- examples/win32/history_qmsm/history.c | 18 +- examples/win32/history_qmsm/history.qm | 9 +- examples/win32/history_qmsm/history.sln | 25 + examples/win32/qhsmtst/.qhsmtst | 58 + examples/win32/qhsmtst/Makefile | 7 +- examples/win32/qhsmtst/qhsmtst.sln | 25 + examples/win32/qhsmtst/qhsmtst.vcxproj | 174 + .../win32/qhsmtst/qhsmtst.vcxproj.filters | 28 + examples/win32/qmsmtst/Makefile | 7 +- examples/win32/reminder/Makefile | 7 +- examples/win32/reminder2/Makefile | 7 +- examples/win32/reminder2/reminder2.c | 12 +- include/qassert.h | 6 +- include/qep.h | 34 +- include/qf.h | 57 +- include/qpc.h | 20 +- include/qpc.lnt | 16 +- include/qs.h | 144 +- include/qs_dummy.h | 14 +- include/qstamp.c | 55 + ports/freertos/arm-cm/gnu/qf_port.c | 19 +- ports/freertos/arm-cm/gnu/qf_port.h | 7 +- ports/freertos/arm-cm/iar/qf_port.c | 19 +- ports/freertos/arm-cm/iar/qf_port.h | 7 +- ports/lint/lin.bat | 14 +- ports/lint/lint_qep.txt | 502 --- ports/lint/lint_qf.txt | 509 --- ports/lint/lint_qk.txt | 551 ---- ports/lint/lint_qs.txt | 554 ---- ports/lint/lint_qv.txt | 522 --- ports/lint/options.lnt | 15 +- ports/posix/Makefile | 46 +- ports/win32-qv/Makefile | 27 +- ports/win32-qv/qp.vcxproj | 5 + ports/win32-qv/qp.vcxproj.filters | 3 + ports/win32/Makefile | 25 +- ports/win32/qp.vcxproj | 5 + ports/win32/qp.vcxproj.filters | 3 + source/qep_hsm.c | 58 +- source/qep_msm.c | 50 +- source/qf_dyn.c | 37 +- source/qf_mem.c | 18 +- source/qk.c | 58 +- source/qs.c | 226 +- source/qs_pkg.h | 16 +- source/qs_rx.c | 730 ++++ source/qv.c | 33 +- version-5.4.2 | 2 - version-5.5.0 | 2 + 321 files changed, 14277 insertions(+), 14853 deletions(-) create mode 100644 3rd_party/CMSIS-RTX/SRC/GCC/ArInp.Scr create mode 100644 3rd_party/CMSIS-RTX/SRC/GCC/ArInp.bat rename GPL.txt => GPLv3.txt (100%) rename COPYING => LICENSE.txt (100%) rename doxygen/{about.dox => about.cc} (91%) rename doxygen/{design.dox => design.cc} (96%) rename doxygen/{exa.dox => exa.cc} (90%) rename doxygen/{exa_apps.dox => exa_apps.cc} (68%) rename doxygen/{exa_mware.dox => exa_mware.cc} (100%) rename doxygen/{exa_native.dox => exa_native.cc} (100%) rename doxygen/{exa_os.dox => exa_os.cc} (92%) rename doxygen/{exa_rtos.dox => exa_rtos.cc} (100%) rename doxygen/{history.dox => history.cc} (95%) rename doxygen/{images => img}/AN_Coding_Standard.jpg (100%) rename doxygen/{images => img}/AN_Getting_Started_with_QPC.jpg (100%) rename doxygen/{images => img}/AN_MISRA-QPC.jpg (100%) rename doxygen/{images => img}/AN_Simple_OOP_in_C.jpg (100%) rename doxygen/{lint.dox => lint.cc} (100%) rename doxygen/{metrics.dox => metrics.cc} (80%) rename doxygen/{modules.dox => modules.cc} (100%) rename doxygen/{ports.dox => ports.cc} (100%) rename doxygen/{ports_native.dox => ports_native.cc} (100%) rename doxygen/{ports_os.dox => ports_os.cc} (100%) rename doxygen/{ports_rtos.dox => ports_rtos.cc} (100%) create mode 100644 doxygen/qpc_metrics.txt delete mode 100644 doxygen/scripts/jquery.plugins.min.js delete mode 100644 doxygen/scripts/ql.js create mode 100644 doxygen/snippets/qmp_init.c create mode 100644 doxygen/snippets/qmp_use.c create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/.dpp create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/dpp.tcl create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/img/BTN_DWN.gif create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/img/BTN_UP.gif create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/img/eating.gif create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/img/hungry.gif create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/img/thinking.gif create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/qspyview.bat create mode 100644 examples/arm-cm/dpp_ek-tm4c123gxl/qspy/qspyview.lnk delete mode 100644 examples/cmsis-rtx/blinky_ek-tm4c123gxl/gnu/.cproject delete mode 100644 examples/cmsis-rtx/blinky_ek-tm4c123gxl/gnu/.project delete mode 100644 examples/posix/dpp/make.tcl create mode 100644 examples/posix/qmsmtst/log.txt create mode 100644 examples/win32-qv/dpp/dpp.vcxproj.filters create mode 100644 examples/win32/dpp/dpp.vcxproj.filters create mode 100644 examples/win32/history_qmsm/history.sln create mode 100644 examples/win32/qhsmtst/.qhsmtst create mode 100644 examples/win32/qhsmtst/qhsmtst.sln create mode 100644 examples/win32/qhsmtst/qhsmtst.vcxproj create mode 100644 examples/win32/qhsmtst/qhsmtst.vcxproj.filters create mode 100644 include/qstamp.c delete mode 100644 ports/lint/lint_qep.txt delete mode 100644 ports/lint/lint_qf.txt delete mode 100644 ports/lint/lint_qk.txt delete mode 100644 ports/lint/lint_qs.txt delete mode 100644 ports/lint/lint_qv.txt create mode 100644 source/qs_rx.c delete mode 100644 version-5.4.2 create mode 100644 version-5.5.0 diff --git a/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.Scr b/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.Scr new file mode 100644 index 00000000..205e45fd --- /dev/null +++ b/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.Scr @@ -0,0 +1,19 @@ +CREATE ./CM4F_LE/libRTX_CM4.a +ADDMOD ./cm4f_le/rt_cmsis.o +ADDMOD ./cm4f_le/rt_task.o +ADDMOD ./cm4f_le/rt_system.o +ADDMOD ./cm4f_le/rt_event.o +ADDMOD ./cm4f_le/rt_list.o +ADDMOD ./cm4f_le/rt_mailbox.o +ADDMOD ./cm4f_le/rt_semaphore.o +ADDMOD ./cm4f_le/rt_time.o +ADDMOD ./cm4f_le/rt_timer.o +ADDMOD ./cm4f_le/rt_mutex.o +ADDMOD ./cm4f_le/rt_robin.o +ADDMOD ./cm4f_le/rt_membox.o +ADDMOD ./cm4f_le/rt_memory.o +ADDMOD ./cm4f_le/svc_table.o +ADDMOD ./cm4f_le/hal_cm.o +ADDMOD ./cm4f_le/hal_cm4.o +SAVE +END diff --git a/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.bat b/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.bat new file mode 100644 index 00000000..21bf52d3 --- /dev/null +++ b/3rd_party/CMSIS-RTX/SRC/GCC/ArInp.bat @@ -0,0 +1 @@ +"C:\tools\gnu_arm-eabi\bin\arm-eabi-ar" -M 2 1 - -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -ffunction-sections + -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections __CORTEX_M4F __FPU_PRESENT=1 __CMSIS_RTOS DBG_MSG ..\..\..\CMSIS\Include diff --git a/3rd_party/ek-lm3s6965/arm/startup_LM3S6965.s b/3rd_party/ek-lm3s6965/arm/startup_LM3S6965.s index 850cc77f..de6d8f0a 100644 --- a/3rd_party/ek-lm3s6965/arm/startup_LM3S6965.s +++ b/3rd_party/ek-lm3s6965/arm/startup_LM3S6965.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_LM3S6965.s for ARM-KEIL ARM assembler ; * @brief CMSIS Cortex-M3 Core Device Startup File for LM3S6965 -; * @version CMSIS v4.2.0 -; * @date 07 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -14,11 +14,11 @@ ; * --pd "Stack_Size SETA 512" --pd "Heap_Size SETA 0" ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * determine the error/assertion handling policy for the application and -; * might need to be customized for each project. This function is defined -; * in assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -85,7 +85,7 @@ __heap_limit ; Place code into the reset code section. ; ;****************************************************************************** - AREA RESET, DATA, READONLY + AREA RESET, DATA, READONLY EXPORT __Vectors EXPORT __Vectors_End EXPORT __Vectors_Size @@ -182,15 +182,20 @@ Reset_Handler PROC IMPORT SystemInit IMPORT __main - BL SystemInit ; CMSIS system initialization + LDR r0, =SystemInit ; CMSIS system initialization + BLX r0 - ; Call the C library enty point that handles startup. This will copy + ; Call the C library enty point that handles startup. This will copy ; the .data section initializers from flash to SRAM and zero fill the ; .bss section. - BL __main + LDR r0, =__main + BX r0 + + ; __main calls the main() function, which should not return, + ; but just in case jump to assert_failed() if main returns. MOVS r0,#0 MOVS r1,#0 ; error number - B assert_failed ; __main should not return, but assert if it does + B assert_failed ENDP ;****************************************************************************** @@ -432,40 +437,28 @@ __user_initial_stackheap PROC ;****************************************************************************** ; -; The weak functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** - EXPORT assert_failed [WEAK] - EXPORT Q_onAssert [WEAK] + EXPORT assert_failed + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm3.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP - ALIGN ; make sure the end of this section is aligned + ALIGN ; make sure the end of this section is aligned - END ; end of module + END ; end of module diff --git a/3rd_party/ek-lm3s6965/gnu/startup_LM3S6965.c b/3rd_party/ek-lm3s6965/gnu/startup_LM3S6965.c index 799319d0..e28ba4e8 100644 --- a/3rd_party/ek-lm3s6965/gnu/startup_LM3S6965.c +++ b/3rd_party/ek-lm3s6965/gnu/startup_LM3S6965.c @@ -1,17 +1,18 @@ /* File: startup_LM3S6965.c for GCC-ARM * Purpose: startup file for LM3S6965 Cortex-M3 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 07 March 2015 + * Version: CMSIS 4.3.0 + * Date: 06 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -309,31 +309,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/ek-lm3s6965/iar/startup_LM3S6965.s b/3rd_party/ek-lm3s6965/iar/startup_LM3S6965.s index 9c512708..49203c21 100644 --- a/3rd_party/ek-lm3s6965/iar/startup_LM3S6965.s +++ b/3rd_party/ek-lm3s6965/iar/startup_LM3S6965.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_LM3S6965.s for IAR ARM assembler ; * @brief CMSIS Cortex-M# Core Device Startup File for LM3S6965 -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -303,36 +303,23 @@ Hibernate_IRQHandler ;****************************************************************************** ; -; The weak functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** - PUBWEAK assert_failed - PUBWEAK Q_onAssert -Q_onAssert + PUBLIC assert_failed + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + + END ; end of module diff --git a/3rd_party/ek-lm3s811/arm/startup_LM3S811.s b/3rd_party/ek-lm3s811/arm/startup_LM3S811.s index 577fea00..996fc12a 100644 --- a/3rd_party/ek-lm3s811/arm/startup_LM3S811.s +++ b/3rd_party/ek-lm3s811/arm/startup_LM3S811.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_LM3S811.s for ARM-KEIL ARM assembler ; * @brief CMSIS Cortex-M3 Core Device Startup File for LM3S811 -; * @version CMSIS v4.2.0 -; * @date 07 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -14,11 +14,11 @@ ; * --pd "Stack_Size SETA 512" --pd "Heap_Size SETA 0" ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * determine the error/assertion handling policy for the application and -; * might need to be customized for each project. This function is defined -; * in assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -169,15 +169,20 @@ Reset_Handler PROC IMPORT SystemInit IMPORT __main - BL SystemInit ; CMSIS system initialization + LDR r0, =SystemInit ; CMSIS system initialization + BLX r0 - ; Call the C library enty point that handles startup. This will copy + ; Call the C library enty point that handles startup. This will copy ; the .data section initializers from flash to SRAM and zero fill the ; .bss section. - BL __main + LDR r0, =__main + BX r0 + + ; __main calls the main() function, which should not return, + ; but just in case jump to assert_failed() if main returns. MOVS r0,#0 MOVS r1,#0 ; error number - B assert_failed ; __main should not return, but assert if it does + B assert_failed ENDP ;****************************************************************************** @@ -384,37 +389,25 @@ __user_initial_stackheap PROC ;****************************************************************************** ; -; The weak functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** - EXPORT assert_failed [WEAK] - EXPORT Q_onAssert [WEAK] + EXPORT assert_failed + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm3.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP diff --git a/3rd_party/ek-lm3s811/gnu/startup_LM3S811.c b/3rd_party/ek-lm3s811/gnu/startup_LM3S811.c index 4b4ecb03..42321d2e 100644 --- a/3rd_party/ek-lm3s811/gnu/startup_LM3S811.c +++ b/3rd_party/ek-lm3s811/gnu/startup_LM3S811.c @@ -1,17 +1,18 @@ /* File: startup_LM3S811.c for GNU-ARM * Purpose: startup file for TM4C123GH6PM Cortex-M4 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 07 March 2015 + * Version: CMSIS 4.3.0 + * Date: 20 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -276,31 +276,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/ek-lm3s811/iar/startup_LM3S811.s b/3rd_party/ek-lm3s811/iar/startup_LM3S811.s index f70ce57c..b84000b4 100644 --- a/3rd_party/ek-lm3s811/iar/startup_LM3S811.s +++ b/3rd_party/ek-lm3s811/iar/startup_LM3S811.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_LM3S811.s for IAR ARM assembler ; * @brief CMSIS Cortex-M# Core Device Startup File for LM3S811 -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -253,36 +253,23 @@ FlashCtrl_IRQHandler ;****************************************************************************** ; -; The weak functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** - PUBWEAK assert_failed - PUBWEAK Q_onAssert + PUBLIC assert_failed + EXTERN Q_onAssert assert_failed -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm3.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs END ; end of module diff --git a/3rd_party/ek-tm4c123gxl/arm/startup_TM4C123GH6PM.s b/3rd_party/ek-tm4c123gxl/arm/startup_TM4C123GH6PM.s index 9641171c..eb113ab7 100644 --- a/3rd_party/ek-tm4c123gxl/arm/startup_TM4C123GH6PM.s +++ b/3rd_party/ek-tm4c123gxl/arm/startup_TM4C123GH6PM.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_TM4C123GH6PM.s for ARM-KEIL ARM assembler -; * @brief CMSIS Cortex-M# Core Device Startup File for TM4C123GH6PM -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @brief CMSIS Cortex-M4F Core Device Startup File for TM4C123GH6PM +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -14,11 +14,11 @@ ; * --pd "Stack_Size SETA 512" --pd "Heap_Size SETA 0" ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * determine the error/assertion handling policy for the application and -; * might need to be customized for each project. This function is defined -; * in assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -660,40 +660,27 @@ __user_initial_stackheap PROC ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** EXPORT assert_failed - EXPORT Q_onAssert + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP + ALIGN ; make sure the end of this section is aligned - ALIGN ; make sure the end of this section is aligned - - END ; end of module + END ; end of module diff --git a/3rd_party/ek-tm4c123gxl/gnu/startup_TM4C123GH6PM.c b/3rd_party/ek-tm4c123gxl/gnu/startup_TM4C123GH6PM.c index 4236979f..13515a38 100644 --- a/3rd_party/ek-tm4c123gxl/gnu/startup_TM4C123GH6PM.c +++ b/3rd_party/ek-tm4c123gxl/gnu/startup_TM4C123GH6PM.c @@ -1,17 +1,18 @@ /* File: startup_TM4C123GH6PM.c * Purpose: startup file for TM4C123GH6PM Cortex-M4 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 07 March 2015 + * Version: CMSIS 4.3.0 + * Date: 20 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -467,31 +467,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/ek-tm4c123gxl/iar/startup_TM4C123GH6PM.s b/3rd_party/ek-tm4c123gxl/iar/startup_TM4C123GH6PM.s index f203d06c..ede44805 100644 --- a/3rd_party/ek-tm4c123gxl/iar/startup_TM4C123GH6PM.s +++ b/3rd_party/ek-tm4c123gxl/iar/startup_TM4C123GH6PM.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_TM4C123GH6PM.s for IAR ARM assembler -; * @brief CMSIS Cortex-M# Core Device Startup File for TM4C123GH6PM -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @brief CMSIS Cortex-M4F Core Device Startup File for TM4C123GH6PM +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -78,145 +78,145 @@ __vector_table DCD SysTick_Handler ; The SysTick handler ; IRQ handlers... - DCD GPIOPortA_IRQHandler ; GPIO Port A - DCD GPIOPortB_IRQHandler ; GPIO Port B - DCD GPIOPortC_IRQHandler ; GPIO Port C - DCD GPIOPortD_IRQHandler ; GPIO Port D - DCD GPIOPortE_IRQHandler ; GPIO Port E - DCD UART0_IRQHandler ; UART0 Rx and Tx - DCD UART1_IRQHandler ; UART1 Rx and Tx - DCD SSI0_IRQHandler ; SSI0 Rx and Tx - DCD I2C0_IRQHandler ; I2C0 Master and Slave - DCD PWMFault_IRQHandler ; PWM Fault - DCD PWMGen0_IRQHandler ; PWM Generator 0 - DCD PWMGen1_IRQHandler ; PWM Generator 1 - DCD PWMGen2_IRQHandler ; PWM Generator 2 - DCD QEI0_IRQHandler ; Quadrature Encoder 0 - DCD ADCSeq0_IRQHandler ; ADC Sequence 0 - DCD ADCSeq1_IRQHandler ; ADC Sequence 1 - DCD ADCSeq2_IRQHandler ; ADC Sequence 2 - DCD ADCSeq3_IRQHandler ; ADC Sequence 3 - DCD Watchdog_IRQHandler ; Watchdog timer - DCD Timer0A_IRQHandler ; Timer 0 subtimer A - DCD Timer0B_IRQHandler ; Timer 0 subtimer B - DCD Timer1A_IRQHandler ; Timer 1 subtimer A - DCD Timer1B_IRQHandler ; Timer 1 subtimer B - DCD Timer2A_IRQHandler ; Timer 2 subtimer A - DCD Timer2B_IRQHandler ; Timer 2 subtimer B - DCD Comp0_IRQHandler ; Analog Comparator 0 - DCD Comp1_IRQHandler ; Analog Comparator 1 - DCD Comp2_IRQHandler ; Analog Comparator 2 - DCD SysCtrl_IRQHandler ; System Control (PLL, OSC, BO) - DCD FlashCtrl_IRQHandler ; FLASH Control - DCD GPIOPortF_IRQHandler ; GPIO Port F - DCD GPIOPortG_IRQHandler ; GPIO Port G - DCD GPIOPortH_IRQHandler ; GPIO Port H - DCD UART2_IRQHandler ; UART2 Rx and Tx - DCD SSI1_IRQHandler ; SSI1 Rx and Tx - DCD Timer3A_IRQHandler ; Timer 3 subtimer A - DCD Timer3B_IRQHandler ; Timer 3 subtimer B - DCD I2C1_IRQHandler ; I2C1 Master and Slave - DCD QEI1_IRQHandler ; Quadrature Encoder 1 - DCD CAN0_IRQHandler ; CAN0 - DCD CAN1_IRQHandler ; CAN1 - DCD CAN2_IRQHandler ; CAN2 - DCD 0 ; Reserved - DCD Hibernate_IRQHandler ; Hibernate - DCD USB0_IRQHandler ; USB0 - DCD PWMGen3_IRQHandler ; PWM Generator 3 - DCD uDMAST_IRQHandler ; uDMA Software Transfer - DCD uDMAError_IRQHandler ; uDMA Error - DCD ADC1Seq0_IRQHandler ; ADC1 Sequence 0 - DCD ADC1Seq1_IRQHandler ; ADC1 Sequence 1 - DCD ADC1Seq2_IRQHandler ; ADC1 Sequence 2 - DCD ADC1Seq3_IRQHandler ; ADC1 Sequence 3 - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD GPIOPortJ_IRQHandler ; GPIO Port J - DCD GPIOPortK_IRQHandler ; GPIO Port K - DCD GPIOPortL_IRQHandler ; GPIO Port L - DCD SSI2_IRQHandler ; SSI2 Rx and Tx - DCD SSI3_IRQHandler ; SSI3 Rx and Tx - DCD UART3_IRQHandler ; UART3 Rx and Tx - DCD UART4_IRQHandler ; UART4 Rx and Tx - DCD UART5_IRQHandler ; UART5 Rx and Tx - DCD UART6_IRQHandler ; UART6 Rx and Tx - DCD UART7_IRQHandler ; UART7 Rx and Tx - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD I2C2_IRQHandler ; I2C2 Master and Slave - DCD I2C3_IRQHandler ; I2C3 Master and Slave - DCD Timer4A_IRQHandler ; Timer 4 subtimer A - DCD Timer4B_IRQHandler ; Timer 4 subtimer B - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD Timer5A_IRQHandler ; Timer 5 subtimer A - DCD Timer5B_IRQHandler ; Timer 5 subtimer B - DCD WideTimer0A_IRQHandler ; Wide Timer 0 subtimer A - DCD WideTimer0B_IRQHandler ; Wide Timer 0 subtimer B - DCD WideTimer1A_IRQHandler ; Wide Timer 1 subtimer A - DCD WideTimer1B_IRQHandler ; Wide Timer 1 subtimer B - DCD WideTimer2A_IRQHandler ; Wide Timer 2 subtimer A - DCD WideTimer2B_IRQHandler ; Wide Timer 2 subtimer B - DCD WideTimer3A_IRQHandler ; Wide Timer 3 subtimer A - DCD WideTimer3B_IRQHandler ; Wide Timer 3 subtimer B - DCD WideTimer4A_IRQHandler ; Wide Timer 4 subtimer A - DCD WideTimer4B_IRQHandler ; Wide Timer 4 subtimer B - DCD WideTimer5A_IRQHandler ; Wide Timer 5 subtimer A - DCD WideTimer5B_IRQHandler ; Wide Timer 5 subtimer B - DCD FPU_IRQHandler ; FPU - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD I2C4_IRQHandler ; I2C4 Master and Slave - DCD I2C5_IRQHandler ; I2C5 Master and Slave - DCD GPIOPortM_IRQHandler ; GPIO Port M - DCD GPIOPortN_IRQHandler ; GPIO Port N - DCD QEI2_IRQHandler ; Quadrature Encoder 2 - DCD 0 ; Reserved - DCD 0 ; Reserved - DCD GPIOPortP0_IRQHandler ; GPIO Port P (Summary or P0) - DCD GPIOPortP1_IRQHandler ; GPIO Port P1 - DCD GPIOPortP2_IRQHandler ; GPIO Port P2 - DCD GPIOPortP3_IRQHandler ; GPIO Port P3 - DCD GPIOPortP4_IRQHandler ; GPIO Port P4 - DCD GPIOPortP5_IRQHandler ; GPIO Port P5 - DCD GPIOPortP6_IRQHandler ; GPIO Port P6 - DCD GPIOPortP7_IRQHandler ; GPIO Port P7 - DCD GPIOPortQ0_IRQHandler ; GPIO Port Q (Summary or Q0) - DCD GPIOPortQ1_IRQHandler ; GPIO Port Q1 - DCD GPIOPortQ2_IRQHandler ; GPIO Port Q2 - DCD GPIOPortQ3_IRQHandler ; GPIO Port Q3 - DCD GPIOPortQ4_IRQHandler ; GPIO Port Q4 - DCD GPIOPortQ5_IRQHandler ; GPIO Port Q5 - DCD GPIOPortQ6_IRQHandler ; GPIO Port Q6 - DCD GPIOPortQ7_IRQHandler ; GPIO Port Q7 - DCD GPIOPortR_IRQHandler ; GPIO Port R - DCD GPIOPortS_IRQHandler ; GPIO Port S - DCD PWM1Gen0_IRQHandler ; PWM 1 Generator 0 - DCD PWM1Gen1_IRQHandler ; PWM 1 Generator 1 - DCD PWM1Gen2_IRQHandler ; PWM 1 Generator 2 - DCD PWM1Gen3_IRQHandler ; PWM 1 Generator 3 - DCD PWM1Fault_IRQHandler ; PWM 1 Fault + DCD GPIOPortA_IRQHandler ; GPIO Port A + DCD GPIOPortB_IRQHandler ; GPIO Port B + DCD GPIOPortC_IRQHandler ; GPIO Port C + DCD GPIOPortD_IRQHandler ; GPIO Port D + DCD GPIOPortE_IRQHandler ; GPIO Port E + DCD UART0_IRQHandler ; UART0 Rx and Tx + DCD UART1_IRQHandler ; UART1 Rx and Tx + DCD SSI0_IRQHandler ; SSI0 Rx and Tx + DCD I2C0_IRQHandler ; I2C0 Master and Slave + DCD PWMFault_IRQHandler ; PWM Fault + DCD PWMGen0_IRQHandler ; PWM Generator 0 + DCD PWMGen1_IRQHandler ; PWM Generator 1 + DCD PWMGen2_IRQHandler ; PWM Generator 2 + DCD QEI0_IRQHandler ; Quadrature Encoder 0 + DCD ADCSeq0_IRQHandler ; ADC Sequence 0 + DCD ADCSeq1_IRQHandler ; ADC Sequence 1 + DCD ADCSeq2_IRQHandler ; ADC Sequence 2 + DCD ADCSeq3_IRQHandler ; ADC Sequence 3 + DCD Watchdog_IRQHandler ; Watchdog timer + DCD Timer0A_IRQHandler ; Timer 0 subtimer A + DCD Timer0B_IRQHandler ; Timer 0 subtimer B + DCD Timer1A_IRQHandler ; Timer 1 subtimer A + DCD Timer1B_IRQHandler ; Timer 1 subtimer B + DCD Timer2A_IRQHandler ; Timer 2 subtimer A + DCD Timer2B_IRQHandler ; Timer 2 subtimer B + DCD Comp0_IRQHandler ; Analog Comparator 0 + DCD Comp1_IRQHandler ; Analog Comparator 1 + DCD Comp2_IRQHandler ; Analog Comparator 2 + DCD SysCtrl_IRQHandler ; System Control (PLL, OSC, BO) + DCD FlashCtrl_IRQHandler ; FLASH Control + DCD GPIOPortF_IRQHandler ; GPIO Port F + DCD GPIOPortG_IRQHandler ; GPIO Port G + DCD GPIOPortH_IRQHandler ; GPIO Port H + DCD UART2_IRQHandler ; UART2 Rx and Tx + DCD SSI1_IRQHandler ; SSI1 Rx and Tx + DCD Timer3A_IRQHandler ; Timer 3 subtimer A + DCD Timer3B_IRQHandler ; Timer 3 subtimer B + DCD I2C1_IRQHandler ; I2C1 Master and Slave + DCD QEI1_IRQHandler ; Quadrature Encoder 1 + DCD CAN0_IRQHandler ; CAN0 + DCD CAN1_IRQHandler ; CAN1 + DCD CAN2_IRQHandler ; CAN2 + DCD 0 ; Reserved + DCD Hibernate_IRQHandler ; Hibernate + DCD USB0_IRQHandler ; USB0 + DCD PWMGen3_IRQHandler ; PWM Generator 3 + DCD uDMAST_IRQHandler ; uDMA Software Transfer + DCD uDMAError_IRQHandler ; uDMA Error + DCD ADC1Seq0_IRQHandler ; ADC1 Sequence 0 + DCD ADC1Seq1_IRQHandler ; ADC1 Sequence 1 + DCD ADC1Seq2_IRQHandler ; ADC1 Sequence 2 + DCD ADC1Seq3_IRQHandler ; ADC1 Sequence 3 + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD GPIOPortJ_IRQHandler ; GPIO Port J + DCD GPIOPortK_IRQHandler ; GPIO Port K + DCD GPIOPortL_IRQHandler ; GPIO Port L + DCD SSI2_IRQHandler ; SSI2 Rx and Tx + DCD SSI3_IRQHandler ; SSI3 Rx and Tx + DCD UART3_IRQHandler ; UART3 Rx and Tx + DCD UART4_IRQHandler ; UART4 Rx and Tx + DCD UART5_IRQHandler ; UART5 Rx and Tx + DCD UART6_IRQHandler ; UART6 Rx and Tx + DCD UART7_IRQHandler ; UART7 Rx and Tx + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD I2C2_IRQHandler ; I2C2 Master and Slave + DCD I2C3_IRQHandler ; I2C3 Master and Slave + DCD Timer4A_IRQHandler ; Timer 4 subtimer A + DCD Timer4B_IRQHandler ; Timer 4 subtimer B + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD Timer5A_IRQHandler ; Timer 5 subtimer A + DCD Timer5B_IRQHandler ; Timer 5 subtimer B + DCD WideTimer0A_IRQHandler ; Wide Timer 0 subtimer A + DCD WideTimer0B_IRQHandler ; Wide Timer 0 subtimer B + DCD WideTimer1A_IRQHandler ; Wide Timer 1 subtimer A + DCD WideTimer1B_IRQHandler ; Wide Timer 1 subtimer B + DCD WideTimer2A_IRQHandler ; Wide Timer 2 subtimer A + DCD WideTimer2B_IRQHandler ; Wide Timer 2 subtimer B + DCD WideTimer3A_IRQHandler ; Wide Timer 3 subtimer A + DCD WideTimer3B_IRQHandler ; Wide Timer 3 subtimer B + DCD WideTimer4A_IRQHandler ; Wide Timer 4 subtimer A + DCD WideTimer4B_IRQHandler ; Wide Timer 4 subtimer B + DCD WideTimer5A_IRQHandler ; Wide Timer 5 subtimer A + DCD WideTimer5B_IRQHandler ; Wide Timer 5 subtimer B + DCD FPU_IRQHandler ; FPU + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD I2C4_IRQHandler ; I2C4 Master and Slave + DCD I2C5_IRQHandler ; I2C5 Master and Slave + DCD GPIOPortM_IRQHandler ; GPIO Port M + DCD GPIOPortN_IRQHandler ; GPIO Port N + DCD QEI2_IRQHandler ; Quadrature Encoder 2 + DCD 0 ; Reserved + DCD 0 ; Reserved + DCD GPIOPortP0_IRQHandler ; GPIO Port P (Summary or P0) + DCD GPIOPortP1_IRQHandler ; GPIO Port P1 + DCD GPIOPortP2_IRQHandler ; GPIO Port P2 + DCD GPIOPortP3_IRQHandler ; GPIO Port P3 + DCD GPIOPortP4_IRQHandler ; GPIO Port P4 + DCD GPIOPortP5_IRQHandler ; GPIO Port P5 + DCD GPIOPortP6_IRQHandler ; GPIO Port P6 + DCD GPIOPortP7_IRQHandler ; GPIO Port P7 + DCD GPIOPortQ0_IRQHandler ; GPIO Port Q (Summary or Q0) + DCD GPIOPortQ1_IRQHandler ; GPIO Port Q1 + DCD GPIOPortQ2_IRQHandler ; GPIO Port Q2 + DCD GPIOPortQ3_IRQHandler ; GPIO Port Q3 + DCD GPIOPortQ4_IRQHandler ; GPIO Port Q4 + DCD GPIOPortQ5_IRQHandler ; GPIO Port Q5 + DCD GPIOPortQ6_IRQHandler ; GPIO Port Q6 + DCD GPIOPortQ7_IRQHandler ; GPIO Port Q7 + DCD GPIOPortR_IRQHandler ; GPIO Port R + DCD GPIOPortS_IRQHandler ; GPIO Port S + DCD PWM1Gen0_IRQHandler ; PWM 1 Generator 0 + DCD PWM1Gen1_IRQHandler ; PWM 1 Generator 1 + DCD PWM1Gen2_IRQHandler ; PWM 1 Generator 2 + DCD PWM1Gen3_IRQHandler ; PWM 1 Generator 3 + DCD PWM1Fault_IRQHandler ; PWM 1 Fault __Vectors_End @@ -526,37 +526,24 @@ PWM1Fault_IRQHandler ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** PUBLIC assert_failed - PUBLIC Q_onAssert -Q_onAssert + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + END ; end of module + diff --git a/3rd_party/mbed-lpc1768/arm/startup_LPC17xx.s b/3rd_party/mbed-lpc1768/arm/startup_LPC17xx.s index 6b70ab1d..f843be7a 100644 --- a/3rd_party/mbed-lpc1768/arm/startup_LPC17xx.s +++ b/3rd_party/mbed-lpc1768/arm/startup_LPC17xx.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ -; * @file startup_LPC17xx.s for ARM-KEIL ARM assembler -; * @brief CMSIS Cortex-M3 Core Device Startup File for LPC17xx -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @file startup_TM4C123GH6PM.s for ARM-KEIL ARM assembler +; * @brief CMSIS Cortex-M4F Core Device Startup File for TM4C123GH6PM +; * @version CMSIS 4.3.0 +; * @date 06 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -14,11 +14,11 @@ ; * --pd "Stack_Size SETA 512" --pd "Heap_Size SETA 0" ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * determine the error/assertion handling policy for the application and -; * might need to be customized for each project. This function is defined -; * in assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -410,40 +410,28 @@ __user_initial_stackheap PROC ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** EXPORT assert_failed - EXPORT Q_onAssert + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP - ALIGN ; make sure the end of this section is aligned + ALIGN ; make sure the end of this section is aligned - END ; end of module + END ; end of module diff --git a/3rd_party/mbed-lpc1768/gnu/startup_LPC17xx.c b/3rd_party/mbed-lpc1768/gnu/startup_LPC17xx.c index f3e0587a..25734bfb 100644 --- a/3rd_party/mbed-lpc1768/gnu/startup_LPC17xx.c +++ b/3rd_party/mbed-lpc1768/gnu/startup_LPC17xx.c @@ -1,8 +1,8 @@ /* File: startup_LPC17xx.c * Purpose: startup file for LPC17xx Cortex-M3 devices. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 30 March 2015 + * Version: CMSIS 4.3.0 + * Date: 06 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com @@ -47,20 +47,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -290,31 +289,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/mbed-lpc1768/iar/startup_LPC17xx.s b/3rd_party/mbed-lpc1768/iar/startup_LPC17xx.s index 4e07750d..7033d0f1 100644 --- a/3rd_party/mbed-lpc1768/iar/startup_LPC17xx.s +++ b/3rd_party/mbed-lpc1768/iar/startup_LPC17xx.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ -; * @file startup_LPC17xx.s for IAR ARM assembler -; * @brief CMSIS Cortex-M# Core Device Startup File for LPC17xx -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @file startup_TM4C123GH6PM.s for IAR ARM assembler +; * @brief CMSIS Cortex-M4F Core Device Startup File for TM4C123GH6PM +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -276,37 +276,23 @@ CANActivity_IRQHandler ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** PUBLIC assert_failed - PUBLIC Q_onAssert -Q_onAssert + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + END ; end of module diff --git a/3rd_party/nucleo-l053r8/arm/startup_stm32l053xx.s b/3rd_party/nucleo-l053r8/arm/startup_stm32l053xx.s index a3af3a20..db4b69c0 100644 --- a/3rd_party/nucleo-l053r8/arm/startup_stm32l053xx.s +++ b/3rd_party/nucleo-l053r8/arm/startup_stm32l053xx.s @@ -9,7 +9,7 @@ ; ; ; Quantum Leaps, LLC; www.state-machine.com -; 2015-03-24 +; 2015-08-27 ;******************** (C) COPYRIGHT 2014 STMicroelectronics ******************** ;* File Name : startup_stm32l053xx.s ;* Author : MCD Application Team @@ -304,39 +304,29 @@ __user_initial_stackheap ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** EXPORT assert_failed - EXPORT Q_onAssert + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR R2,=__initial_sp ; load the original top of stack + MOV SP,R2 ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP - END -;************************ (C) COPYRIGHT STMicroelectronics *****END OF FILE***** + ALIGN ; make sure the end of this section is aligned + + END ; end of module diff --git a/3rd_party/nucleo-l053r8/gnu/startup_stm32l053xx.c b/3rd_party/nucleo-l053r8/gnu/startup_stm32l053xx.c index 16c9e05a..171ef4f5 100644 --- a/3rd_party/nucleo-l053r8/gnu/startup_stm32l053xx.c +++ b/3rd_party/nucleo-l053r8/gnu/startup_stm32l053xx.c @@ -1,17 +1,18 @@ /* File: startup_stm32l053xx.c for GNU-ARM * Purpose: startup file for LM3S6965 Cortex-M3 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 07 March 2015 +* Version: CMSIS 4.3.0 + * Date: 20 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -279,31 +279,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/nucleo-l053r8/iar/startup_stm32l053xx.s b/3rd_party/nucleo-l053r8/iar/startup_stm32l053xx.s index 5c3efff3..2a7490c4 100644 --- a/3rd_party/nucleo-l053r8/iar/startup_stm32l053xx.s +++ b/3rd_party/nucleo-l053r8/iar/startup_stm32l053xx.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_startup_stm32l053xx.s for IAR ARM assembler ; * @brief CMSIS Cortex-M0+ Core Device Startup File for STM32L053xx.s -; * @version CMSIS v4.1 -; * @date 27 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -258,37 +258,24 @@ USB_IRQHandler ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** PUBLIC assert_failed - PUBLIC Q_onAssert -Q_onAssert + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR r2,=sfe(CSTACK) ; load the original top of stack + MOV sp,r2 ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + END ; end of module diff --git a/3rd_party/nucleo-l152re/arm/startup_stm32l1xx.s b/3rd_party/nucleo-l152re/arm/startup_stm32l1xx.s index 52036f42..3c7e97b9 100644 --- a/3rd_party/nucleo-l152re/arm/startup_stm32l1xx.s +++ b/3rd_party/nucleo-l152re/arm/startup_stm32l1xx.s @@ -9,7 +9,7 @@ ; ; ; Quantum Leaps, LLC; www.state-machine.com -; 2015-03-25 +; 2015-08-26 ;******************** (C) COPYRIGHT 2014 STMicroelectronics ******************** ;* File Name : startup_stm32l1xx_hd.s ;* Author : MCD Application Team @@ -443,41 +443,27 @@ __user_initial_stackheap ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** EXPORT assert_failed - EXPORT Q_onAssert + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP - ALIGN ; make sure the end of this section is aligned + ALIGN ; make sure the end of this section is aligned - END - -;************************ (C) COPYRIGHT STMicroelectronics *****END OF FILE***** + END ; end of module diff --git a/3rd_party/nucleo-l152re/gnu/startup_stm32l1xx.c b/3rd_party/nucleo-l152re/gnu/startup_stm32l1xx.c index b5e0ab8c..2579d3f3 100644 --- a/3rd_party/nucleo-l152re/gnu/startup_stm32l1xx.c +++ b/3rd_party/nucleo-l152re/gnu/startup_stm32l1xx.c @@ -1,17 +1,18 @@ /* File: startup_stm32l1xx.c for GNU-ARM * Purpose: startup file for STM32L1xx Cortex-M3 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 27 March 2015 + * Version: CMSIS 4.3.0 + * Date: 20 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -334,31 +334,22 @@ void _fini(void) { /* dummy */ /***************************************************************************** * The function assert_failed defines the error/assertion handling policy -* for the application and might need to be customized for each project. -* This function is defined as "naked" and specifically avoids accessing the -* stack, which might be corrupted by the time assert_failed is called. +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ __attribute__ ((naked)) -void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/nucleo-l152re/iar/startup_stm32l1xx.s b/3rd_party/nucleo-l152re/iar/startup_stm32l1xx.s index 6f026c52..4df4fbad 100644 --- a/3rd_party/nucleo-l152re/iar/startup_stm32l1xx.s +++ b/3rd_party/nucleo-l152re/iar/startup_stm32l1xx.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_stm32l1xx for IAR ARM assembler ; * @brief CMSIS Cortex-M3 Core Device Startup File for STM32L1xx.s -; * @version CMSIS v4.1 -; * @date 27 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -12,8 +12,8 @@ ; * The function assert_failed defined at the end of this file defines ; * the error/assertion handling policy for the application and might ; * need to be customized for each project. This function is defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed is called. +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -343,37 +343,24 @@ COMP_ACQ_IRQHandler ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** PUBLIC assert_failed - PUBLIC Q_onAssert -Q_onAssert + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + END ; end of module + diff --git a/3rd_party/stm32f4-discovery/arm/startup_stm32f4xx.s b/3rd_party/stm32f4-discovery/arm/startup_stm32f4xx.s index 6d10ccab..85f6b008 100644 --- a/3rd_party/stm32f4-discovery/arm/startup_stm32f4xx.s +++ b/3rd_party/stm32f4-discovery/arm/startup_stm32f4xx.s @@ -1,8 +1,8 @@ ;/***************************************************************************/ ; * @file startup_stm32f4xx.s for ARM-KEIL ARM assembler ; * @brief CMSIS Cortex-M# Core Device Startup File for STM32F40xx devices -; * @version CMSIS v4.1 -; * @date 07 March 2015 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device @@ -14,11 +14,11 @@ ; * --pd "Stack_Size SETA 512" --pd "Heap_Size SETA 0" ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * determine the error/assertion handling policy for the application and -; * might need to be customized for each project. This function is defined -; * in assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -221,15 +221,20 @@ Reset_Handler PROC IMPORT SystemInit IMPORT __main - BL SystemInit ; CMSIS system initialization + LDR r0, =SystemInit ; CMSIS system initialization + BLX r0 - ; Call the C library enty point that handles startup. This will copy + ; Call the C library enty point that handles startup. This will copy ; the .data section initializers from flash to SRAM and zero fill the ; .bss section. - BL __main + LDR r0, =__main + BX r0 + + ; __main calls the main() function, which should not return, + ; but just in case jump to assert_failed() if main returns. MOVS r0,#0 MOVS r1,#0 ; error number - B assert_failed ; __main should not return, but assert if it does + B assert_failed ENDP ;****************************************************************************** @@ -547,40 +552,27 @@ __user_initial_stackheap PROC ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** EXPORT assert_failed - EXPORT Q_onAssert + IMPORT Q_onAssert assert_failed PROC -Q_onAssert - ; - ; NOTE: add here your application-specific error handling - ; - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + LDR sp,=__initial_sp ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler + + B . ; should not be reached, but just in case... + ENDP + ALIGN ; make sure the end of this section is aligned - ALIGN ; make sure the end of this section is aligned - - END ; end of module + END ; end of module diff --git a/3rd_party/stm32f4-discovery/gnu/startup_stm32f4xx.c b/3rd_party/stm32f4-discovery/gnu/startup_stm32f4xx.c index 8a6134ea..2afb6857 100644 --- a/3rd_party/stm32f4-discovery/gnu/startup_stm32f4xx.c +++ b/3rd_party/stm32f4-discovery/gnu/startup_stm32f4xx.c @@ -1,17 +1,18 @@ /* File: startup_stm32f4xx.c * Purpose: startup file for stm32f4xx Cortex-M4 device. * Should be used with GCC 'GNU Tools ARM Embedded' - * Version: CMSIS v4.2.0 - * Date: 07 March 2015 + * Version: CMSIS 4.3.0 + * Date: 20 August 2015 * * Created from the CMSIS template for the specified device * Quantum Leaps, www.state-machine.com * - * NOTE: The function assert_failed defined at the end of this file - * determines the error/assertion handling policy for the application and - * might need to be customized for each project. This function is defined - * using the GNU-ARM language extensions to avoid accessing the stack, - * which might be corrupted by the time assert_failed is called. + * NOTE: + * The function assert_failed defined at the end of this file defines + * the error/assertion handling policy for the application and might + * need to be customized for each project. This function is defined in + * assembly to re-set the stack pointer, in case it is corrupted by the + * time assert_failed is called. */ /* Copyright (c) 2011 - 2014 ARM LIMITED @@ -47,20 +48,19 @@ extern int __stack_end__; /* Weak prototypes for error handlers --------------------------------------*/ /** * \note -* The functions assert_failed/Q_onAssert defined at the end of this file -* determine the error/assertion handling policy for the application and -* might need to be customized for each project. These functions are defined -* as "naked" to avoid accessing the stack, which might be corrupted by -* the time assert_failed/Q_onAssert are called. +* The function assert_failed defined at the end of this file defines +* the error/assertion handling policy for the application and might +* need to be customized for each project. This function is defined in +* assembly to avoid accessing the stack, which might be corrupted by +* the time assert_failed is called. */ -__attribute__ ((naked)) void assert_failed(char const *file, int line); -__attribute__ ((alias("assert_failed"))) -void Q_onAssert(char const *file, int line); +__attribute__ ((naked)) void assert_failed(char const *module, int loc); /* Function prototypes -----------------------------------------------------*/ void Default_Handler(void); /* Default empty handler */ void Reset_Handler(void); /* Reset Handler */ void SystemInit(void); /* CMSIS system initialization */ +void Q_onAssert(char const *module, int loc); /* QP assertion handler */ /*---------------------------------------------------------------------------- * weak aliases for each Exception handler to the Default_Handler. @@ -366,37 +366,31 @@ void Default_Handler(void) { ); } /*..........................................................................*/ -void _init() { +void _init(void) { /* dummy */ +} +/*..........................................................................*/ +void _fini(void) { /* dummy */ } /***************************************************************************** -* The function assert_failed defines the error/assertion -* handling policy for the application and might need to be customized -* for each project. This function is defined as "naked" and specifically -* avoids accessing the stack, which might be corrupted by the time -* assert_failed is called. +* The function assert_failed defines the error/assertion handling policy +* for the application. After making sure that the stack is OK, this function +* calls Q_onAssert, which should NOT return (typically reset the CPU). * -* NOTE: the functions assert_failed/Q_onAssert should NOT return. +* NOTE: the function Q_onAssert should NOT return. *****************************************************************************/ -__attribute__ ((naked)) void assert_failed(char const *file, int line) { - - /* NOTE: add here your application-specific error handling... */ - - /* the following assembly implements the CMIS function - * NVIC_SystemReset() from core_cm4.h - * Leave this code if you wish to reset the system after an error. - */ +__attribute__ ((naked)) +void assert_failed(char const *module, int loc) { + /* re-set the SP in case of stack overflow */ __asm volatile ( - " DSB\n\t" /* ensure all memory access complete */ - " LDR r0,=0x05FA0004\n\t" /* (0x5FA << SCB_AIRCR_VECTKEY_Pos) - * | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - * | SCB_AIRCR_SYSRESETREQ_Msk */ - " LDR r1,=0xE000ED0C\n\t" /* address of SCB->AIRCR */ - " STR r0,[r1]\n\t" /* r0 -> SCB->AIRCR */ - " DSB\n\t" /* ensure all memory access complete */ - " B .\n\t" /* wait until reset occurs */ - ); + " MOV sp,%0\n\t" + : : "r" (&__stack_end__)); + + Q_onAssert(module, loc); /* call the application-specific QP handler */ + + for (;;) { /* should not be reached, but just in case loop forever... */ + } } /****** End Of File *********************************************************/ diff --git a/3rd_party/stm32f4-discovery/iar/startup_stm32f4xx.s b/3rd_party/stm32f4-discovery/iar/startup_stm32f4xx.s index 0ecd08bf..96a1ea88 100644 --- a/3rd_party/stm32f4-discovery/iar/startup_stm32f4xx.s +++ b/3rd_party/stm32f4-discovery/iar/startup_stm32f4xx.s @@ -1,19 +1,19 @@ ;/***************************************************************************/ ; * @file startup_stm32f4xx.s for IAR ARM assembler ; * @brief CMSIS Cortex-M4F Core Device Startup File for STM32F40xx devices -; * @version CMSIS v4.2.0 -; * @date 2015-03-16 +; * @version CMSIS 4.3.0 +; * @date 20 August 2015 ; * ; * @description ; * Created from the CMSIS template for the specified device ; * Quantum Leaps, www.state-machine.com ; * ; * @note -; * The functions assert_failed/Q_onAssert defined at the end of this file -; * define the error/assertion handling policy for the application and might -; * need to be customized for each project. These functions are defined in -; * assembly to avoid accessing the stack, which might be corrupted by -; * the time assert_failed/Q_onAssert are called. +; * The function assert_failed defined at the end of this file defines +; * the error/assertion handling policy for the application and might +; * need to be customized for each project. This function is defined in +; * assembly to re-set the stack pointer, in case it is corrupted by the +; * time assert_failed is called. ; * ; ***************************************************************************/ ;/* Copyright (c) 2012 ARM LIMITED @@ -416,37 +416,24 @@ FPU_IRQHandler ;****************************************************************************** ; -; The functions assert_failed/Q_onAssert define the error/assertion -; handling policy for the application and might need to be customized -; for each project. These functions are defined in assembly to avoid -; accessing the stack, which might be corrupted by the time assert_failed -; is called. For now the function just resets the CPU. +; The function assert_failed defines the error/assertion handling policy +; for the application. After making sure that the stack is OK, this function +; calls Q_onAssert, which should NOT return (typically reset the CPU). ; -; NOTE: the functions assert_failed/Q_onAssert should NOT return. +; NOTE: the function Q_onAssert should NOT return. ; -; The C proptotypes of these functions are as follows: +; The C proptotype of the assert_failed() and Q_onAssert() functions are: ; void assert_failed(char const *file, int line); ; void Q_onAssert (char const *file, int line); ;****************************************************************************** PUBLIC assert_failed - PUBLIC Q_onAssert -Q_onAssert + EXTERN Q_onAssert assert_failed - ; - ; NOTE: add here your application-specific error handling - ; + LDR sp,=sfe(CSTACK) ; re-set the SP in case of stack overflow + BL Q_onAssert ; call the application-specific handler - ; the following code implements the CMIS function - ; NVIC_SystemReset() from core_cm4.h - ; Leave this code if you wish to reset the system after an error. - DSB ; ensure all memory access complete - LDR r0,=0x05FA0004 ; (0x5FA << SCB_AIRCR_VECTKEY_Pos) - ; | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) - ; | SCB_AIRCR_SYSRESETREQ_Msk - LDR r1,=0xE000ED0C ; address of SCB->AIRCR - STR r0,[r1] ; r0 -> SCB->AIRCR - DSB ; ensure all memory access complete - B . ; wait until reset occurs + B . ; should not be reached, but just in case... - END + END ; end of module + diff --git a/GPL.txt b/GPLv3.txt similarity index 100% rename from GPL.txt rename to GPLv3.txt diff --git a/COPYING b/LICENSE.txt similarity index 100% rename from COPYING rename to LICENSE.txt diff --git a/doxygen/Doxyfile b/doxygen/Doxyfile index 28c4f329..21f6f04f 100644 --- a/doxygen/Doxyfile +++ b/doxygen/Doxyfile @@ -1,2419 +1,360 @@ -# Doxyfile 1.8.9.1 - -# This file describes the settings to be used by the documentation system -# doxygen (www.doxygen.org) for a project. -# -# All text after a double hash (##) is considered a comment and is placed in -# front of the TAG it is preceding. -# -# All text after a single hash (#) is considered a comment and will be ignored. -# The format is: -# TAG = value [value, ...] -# For lists, items can also be appended using: -# TAG += value [value, ...] -# Values that contain spaces should be placed between quotes (\" \"). +# Doxyfile 1.8.10 #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- - -# This tag specifies the encoding used for all characters in the config file -# that follow. The default is UTF-8 which is also the encoding used for all text -# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv -# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv -# for the list of possible encodings. -# The default value is: UTF-8. - DOXYFILE_ENCODING = UTF-8 - -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by -# double-quotes, unless you are using Doxywizard) that should identify the -# project for which the documentation is generated. This name is used in the -# title of most generated pages and in a few other places. -# The default value is: My Project. - PROJECT_NAME = "QP/C" - -# The PROJECT_NUMBER tag can be used to enter a project or revision number. This -# could be handy for archiving the generated documentation or if some version -# control system is used. - -PROJECT_NUMBER = "5.4.2" - -# Using the PROJECT_BRIEF tag one can provide an optional one line description -# for a project that appears at the top of each page and should give viewer a -# quick idea about the purpose of the project. Keep the description short. - +PROJECT_NUMBER = "5.5.0" PROJECT_BRIEF = - -# With the PROJECT_LOGO tag one can specify a logo or an icon that is included -# in the documentation. The maximum height of the logo should not exceed 55 -# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy -# the logo to the output directory. - PROJECT_LOGO = images/header_logo_ql.png - -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path -# into which the generated documentation will be written. If a relative path is -# entered, it will be relative to the location where doxygen was started. If -# left blank the current directory will be used. - OUTPUT_DIRECTORY = - -# If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub- -# directories (in 2 levels) under the output directory of each output format and -# will distribute the generated files over these directories. Enabling this -# option can be useful when feeding doxygen a huge amount of source files, where -# putting all generated files in the same directory would otherwise causes -# performance problems for the file system. -# The default value is: NO. - CREATE_SUBDIRS = NO - -# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII -# characters to appear in the names of generated files. If set to NO, non-ASCII -# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode -# U+3044. -# The default value is: NO. - ALLOW_UNICODE_NAMES = NO - -# The OUTPUT_LANGUAGE tag is used to specify the language in which all -# documentation generated by doxygen is written. Doxygen will use this -# information to generate all constant output in the proper language. -# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, -# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), -# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, -# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), -# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, -# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, -# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, -# Ukrainian and Vietnamese. -# The default value is: English. - OUTPUT_LANGUAGE = English - -# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member -# descriptions after the members that are listed in the file and class -# documentation (similar to Javadoc). Set to NO to disable this. -# The default value is: YES. - BRIEF_MEMBER_DESC = YES - -# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief -# description of a member or function before the detailed description -# -# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the -# brief descriptions will be completely suppressed. -# The default value is: YES. - REPEAT_BRIEF = YES - -# This tag implements a quasi-intelligent brief description abbreviator that is -# used to form the text in various listings. Each string in this list, if found -# as the leading text of the brief description, will be stripped from the text -# and the result, after processing the whole list, is used as the annotated -# text. Otherwise, the brief description is used as-is. If left blank, the -# following values are used ($name is automatically replaced with the name of -# the entity):The $name class, The $name widget, The $name file, is, provides, -# specifies, contains, represents, a, an and the. - ABBREVIATE_BRIEF = - -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then -# doxygen will generate a detailed section even if there is only a brief -# description. -# The default value is: NO. - ALWAYS_DETAILED_SEC = NO - -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all -# inherited members of a class in the documentation of that class as if those -# members were ordinary class members. Constructors, destructors and assignment -# operators of the base classes will not be shown. -# The default value is: NO. - -INLINE_INHERITED_MEMB = YES - -# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path -# before files name in the file list and in the header files. If set to NO the -# shortest path that makes the file name unique will be used -# The default value is: YES. - +INLINE_INHERITED_MEMB = NO FULL_PATH_NAMES = YES - -# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. -# Stripping is only done if one of the specified strings matches the left-hand -# part of the path. The tag can be used to show relative paths in the file list. -# If left blank the directory from which doxygen is run is used as the path to -# strip. -# -# Note that you can specify absolute paths here, but also relative paths, which -# will be relative from the directory where doxygen is started. -# This tag requires that the tag FULL_PATH_NAMES is set to YES. - STRIP_FROM_PATH = - -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the -# path mentioned in the documentation of a class, which tells the reader which -# header file to include in order to use a class. If left blank only the name of -# the header file containing the class definition is used. Otherwise one should -# specify the list of include paths that are normally passed to the compiler -# using the -I flag. - STRIP_FROM_INC_PATH = - -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but -# less readable) file names. This can be useful is your file systems doesn't -# support long names like on DOS, Mac, or CD-ROM. -# The default value is: NO. - SHORT_NAMES = NO - -# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the -# first line (until the first dot) of a Javadoc-style comment as the brief -# description. If set to NO, the Javadoc-style will behave just like regular Qt- -# style comments (thus requiring an explicit @brief command for a brief -# description.) -# The default value is: NO. - JAVADOC_AUTOBRIEF = NO - -# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first -# line (until the first dot) of a Qt-style comment as the brief description. If -# set to NO, the Qt-style will behave just like regular Qt-style comments (thus -# requiring an explicit \brief command for a brief description.) -# The default value is: NO. - QT_AUTOBRIEF = YES - -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a -# multi-line C++ special comment block (i.e. a block of //! or /// comments) as -# a brief description. This used to be the default behavior. The new default is -# to treat a multi-line C++ comment block as a detailed description. Set this -# tag to YES if you prefer the old behavior instead. -# -# Note that setting this tag to YES also means that rational rose comments are -# not recognized any more. -# The default value is: NO. - MULTILINE_CPP_IS_BRIEF = YES - -# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the -# documentation from any documented member that it re-implements. -# The default value is: YES. - INHERIT_DOCS = YES - -# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new -# page for each member. If set to NO, the documentation of a member will be part -# of the file/class/namespace that contains it. -# The default value is: NO. - SEPARATE_MEMBER_PAGES = NO - -# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen -# uses this value to replace tabs by spaces in code fragments. -# Minimum value: 1, maximum value: 16, default value: 4. - TAB_SIZE = 4 - -# This tag can be used to specify a number of aliases that act as commands in -# the documentation. An alias has the form: -# name=value -# For example adding -# "sideeffect=@par Side Effects:\n" -# will allow you to put the command \sideeffect (or @sideeffect) in the -# documentation, which will result in a user-defined paragraph with heading -# "Side Effects:". You can put \n's in the value part of an alias to insert -# newlines. - -ALIASES = \ +ALIASES = \ "next{1}=
Next: \ref \1

" \ "description=\par Description\n" \ "hint=\par Hint\n" \ "usage=@par Usage\n" -# This tag can be used to specify a number of word-keyword mappings (TCL only). -# A mapping has the form "name=value". For example adding "class=itcl::class" -# will allow you to use the command class in the itcl::class meaning. - TCL_SUBST = - -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources -# only. Doxygen will then generate output that is more tailored for C. For -# instance, some of the names that are used will be different. The list of all -# members will be omitted, etc. -# The default value is: NO. - OPTIMIZE_OUTPUT_FOR_C = YES - -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or -# Python sources only. Doxygen will then generate output that is more tailored -# for that language. For instance, namespaces will be presented as packages, -# qualified scopes will look different, etc. -# The default value is: NO. - OPTIMIZE_OUTPUT_JAVA = NO - -# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran -# sources. Doxygen will then generate output that is tailored for Fortran. -# The default value is: NO. - OPTIMIZE_FOR_FORTRAN = NO - -# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL -# sources. Doxygen will then generate output that is tailored for VHDL. -# The default value is: NO. - OPTIMIZE_OUTPUT_VHDL = NO - -# Doxygen selects the parser to use depending on the extension of the files it -# parses. With this tag you can assign which parser to use for a given -# extension. Doxygen has a built-in mapping, but you can override or extend it -# using this tag. The format is ext=language, where ext is a file extension, and -# language is one of the parsers supported by doxygen: IDL, Java, Javascript, -# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: -# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: -# Fortran. In the later case the parser tries to guess whether the code is fixed -# or free formatted code, this is the default for Fortran type files), VHDL. For -# instance to make doxygen treat .inc files as Fortran files (default is PHP), -# and .f files as C (default is Fortran), use: inc=Fortran f=C. -# -# Note: For files without extension you can use no_extension as a placeholder. -# -# Note that for custom extensions you also need to set FILE_PATTERNS otherwise -# the files are not read by doxygen. - EXTENSION_MAPPING = - -# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments -# according to the Markdown format, which allows for more readable -# documentation. See http://daringfireball.net/projects/markdown/ for details. -# The output of markdown processing is further processed by doxygen, so you can -# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in -# case of backward compatibilities issues. -# The default value is: YES. - MARKDOWN_SUPPORT = YES - -# When enabled doxygen tries to link words that correspond to documented -# classes, or namespaces to their corresponding documentation. Such a link can -# be prevented in individual cases by putting a % sign in front of the word or -# globally by setting AUTOLINK_SUPPORT to NO. -# The default value is: YES. - AUTOLINK_SUPPORT = YES - -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want -# to include (a tag file for) the STL sources as input, then you should set this -# tag to YES in order to let doxygen match functions declarations and -# definitions whose arguments contain STL classes (e.g. func(std::string); -# versus func(std::string) {}). This also make the inheritance and collaboration -# diagrams that involve STL classes more complete and accurate. -# The default value is: NO. - BUILTIN_STL_SUPPORT = NO - -# If you use Microsoft's C++/CLI language, you should set this option to YES to -# enable parsing support. -# The default value is: NO. - CPP_CLI_SUPPORT = NO - -# Set the SIP_SUPPORT tag to YES if your project consists of sip (see: -# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen -# will parse them like normal C++ but will assume all classes use public instead -# of private inheritance when no explicit protection keyword is present. -# The default value is: NO. - SIP_SUPPORT = NO - -# For Microsoft's IDL there are propget and propput attributes to indicate -# getter and setter methods for a property. Setting this option to YES will make -# doxygen to replace the get and set methods by a property in the documentation. -# This will only work if the methods are indeed getting or setting a simple -# type. If this is not the case, or you want to show the methods anyway, you -# should set this option to NO. -# The default value is: YES. - IDL_PROPERTY_SUPPORT = YES - -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC -# tag is set to YES then doxygen will reuse the documentation of the first -# member in the group (if any) for the other members of the group. By default -# all members of a group must be documented explicitly. -# The default value is: NO. - DISTRIBUTE_GROUP_DOC = NO - -# Set the SUBGROUPING tag to YES to allow class member groups of the same type -# (for instance a group of public functions) to be put as a subgroup of that -# type (e.g. under the Public Functions section). Set it to NO to prevent -# subgrouping. Alternatively, this can be done per class using the -# \nosubgrouping command. -# The default value is: YES. - +GROUP_NESTED_COMPOUNDS = NO SUBGROUPING = YES - -# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions -# are shown inside the group in which they are included (e.g. using \ingroup) -# instead of on a separate page (for HTML and Man pages) or section (for LaTeX -# and RTF). -# -# Note that this feature does not work in combination with -# SEPARATE_MEMBER_PAGES. -# The default value is: NO. - -INLINE_GROUPED_CLASSES = NO - -# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions -# with only public data fields or simple typedef fields will be shown inline in -# the documentation of the scope in which they are defined (i.e. file, -# namespace, or group documentation), provided this scope is documented. If set -# to NO, structs, classes, and unions are shown on a separate page (for HTML and -# Man pages) or section (for LaTeX and RTF). -# The default value is: NO. - -INLINE_SIMPLE_STRUCTS = NO - -# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or -# enum is documented as struct, union, or enum with the name of the typedef. So -# typedef struct TypeS {} TypeT, will appear in the documentation as a struct -# with name TypeT. When disabled the typedef will appear as a member of a file, -# namespace, or class. And the struct will be named TypeS. This can typically be -# useful for C code in case the coding convention dictates that all compound -# types are typedef'ed and only the typedef is referenced, never the tag name. -# The default value is: NO. - -TYPEDEF_HIDES_STRUCT = NO - -# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This -# cache is used to resolve symbols given their name and scope. Since this can be -# an expensive process and often the same symbol appears multiple times in the -# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small -# doxygen will become slower. If the cache is too large, memory is wasted. The -# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range -# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 -# symbols. At the end of a run doxygen will report the cache usage and suggest -# the optimal cache size from a speed point of view. -# Minimum value: 0, maximum value: 9, default value: 0. - +INLINE_GROUPED_CLASSES = YES +INLINE_SIMPLE_STRUCTS = YES +TYPEDEF_HIDES_STRUCT = YES LOOKUP_CACHE_SIZE = 0 - #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- - -# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in -# documentation are documented, even if no documentation was available. Private -# class members and static file members will be hidden unless the -# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. -# Note: This will also disable the warnings about undocumented members that are -# normally produced when WARNINGS is set to YES. -# The default value is: NO. - EXTRACT_ALL = NO - -# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will -# be included in the documentation. -# The default value is: NO. - EXTRACT_PRIVATE = NO - -# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal -# scope will be included in the documentation. -# The default value is: NO. - EXTRACT_PACKAGE = NO - -# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be -# included in the documentation. -# The default value is: NO. - EXTRACT_STATIC = YES - -# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined -# locally in source files will be included in the documentation. If set to NO, -# only classes defined in header files are included. Does not have any effect -# for Java sources. -# The default value is: YES. - EXTRACT_LOCAL_CLASSES = YES - -# This flag is only useful for Objective-C code. If set to YES, local methods, -# which are defined in the implementation section but not in the interface are -# included in the documentation. If set to NO, only methods in the interface are -# included. -# The default value is: NO. - EXTRACT_LOCAL_METHODS = NO - -# If this flag is set to YES, the members of anonymous namespaces will be -# extracted and appear in the documentation as a namespace called -# 'anonymous_namespace{file}', where file will be replaced with the base name of -# the file that contains the anonymous namespace. By default anonymous namespace -# are hidden. -# The default value is: NO. - EXTRACT_ANON_NSPACES = NO - -# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all -# undocumented members inside documented classes or files. If set to NO these -# members will be included in the various overviews, but no documentation -# section is generated. This option has no effect if EXTRACT_ALL is enabled. -# The default value is: NO. - HIDE_UNDOC_MEMBERS = NO - -# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all -# undocumented classes that are normally visible in the class hierarchy. If set -# to NO, these classes will be included in the various overviews. This option -# has no effect if EXTRACT_ALL is enabled. -# The default value is: NO. - HIDE_UNDOC_CLASSES = NO - -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend -# (class|struct|union) declarations. If set to NO, these declarations will be -# included in the documentation. -# The default value is: NO. - HIDE_FRIEND_COMPOUNDS = NO - -# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any -# documentation blocks found inside the body of a function. If set to NO, these -# blocks will be appended to the function's detailed documentation block. -# The default value is: NO. - HIDE_IN_BODY_DOCS = NO - -# The INTERNAL_DOCS tag determines if documentation that is typed after a -# \internal command is included. If the tag is set to NO then the documentation -# will be excluded. Set it to YES to include the internal documentation. -# The default value is: NO. - INTERNAL_DOCS = NO - -# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file -# names in lower-case letters. If set to YES, upper-case letters are also -# allowed. This is useful if you have classes or files whose names only differ -# in case and if your file system supports case sensitive file names. Windows -# and Mac users are advised to set this option to NO. -# The default value is: system dependent. - CASE_SENSE_NAMES = NO - -# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with -# their full class and namespace scopes in the documentation. If set to YES, the -# scope will be hidden. -# The default value is: NO. - HIDE_SCOPE_NAMES = NO - -# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will -# append additional text to a page's title, such as Class Reference. If set to -# YES the compound reference will be hidden. -# The default value is: NO. - HIDE_COMPOUND_REFERENCE= NO - -# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of -# the files that are included by a file in the documentation of that file. -# The default value is: YES. - SHOW_INCLUDE_FILES = YES - -# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each -# grouped member an include statement to the documentation, telling the reader -# which file to include in order to use the member. -# The default value is: NO. - SHOW_GROUPED_MEMB_INC = NO - -# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include -# files with double quotes in the documentation rather than with sharp brackets. -# The default value is: NO. - FORCE_LOCAL_INCLUDES = NO - -# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the -# documentation for inline members. -# The default value is: YES. - INLINE_INFO = YES - -# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the -# (detailed) documentation of file and class members alphabetically by member -# name. If set to NO, the members will appear in declaration order. -# The default value is: YES. - SORT_MEMBER_DOCS = YES - -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief -# descriptions of file, namespace and class members alphabetically by member -# name. If set to NO, the members will appear in declaration order. Note that -# this will also influence the order of the classes in the class list. -# The default value is: NO. - SORT_BRIEF_DOCS = NO - -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the -# (brief and detailed) documentation of class members so that constructors and -# destructors are listed first. If set to NO the constructors will appear in the -# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. -# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief -# member documentation. -# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting -# detailed member documentation. -# The default value is: NO. - SORT_MEMBERS_CTORS_1ST = NO - -# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy -# of group names into alphabetical order. If set to NO the group names will -# appear in their defined order. -# The default value is: NO. - SORT_GROUP_NAMES = NO - -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by -# fully-qualified names, including namespaces. If set to NO, the class list will -# be sorted only by class name, not including the namespace part. -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. -# Note: This option applies only to the class list, not to the alphabetical -# list. -# The default value is: NO. - SORT_BY_SCOPE_NAME = NO - -# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper -# type resolution of all parameters of a function it will reject a match between -# the prototype and the implementation of a member function even if there is -# only one candidate or it is obvious which candidate to choose by doing a -# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still -# accept a match between prototype and implementation in such cases. -# The default value is: NO. - STRICT_PROTO_MATCHING = NO - -# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo -# list. This list is created by putting \todo commands in the documentation. -# The default value is: YES. - GENERATE_TODOLIST = YES - -# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test -# list. This list is created by putting \test commands in the documentation. -# The default value is: YES. - GENERATE_TESTLIST = YES - -# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug -# list. This list is created by putting \bug commands in the documentation. -# The default value is: YES. - GENERATE_BUGLIST = YES - -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) -# the deprecated list. This list is created by putting \deprecated commands in -# the documentation. -# The default value is: YES. - GENERATE_DEPRECATEDLIST= YES - -# The ENABLED_SECTIONS tag can be used to enable conditional documentation -# sections, marked by \if ... \endif and \cond -# ... \endcond blocks. - ENABLED_SECTIONS = - -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the -# initial value of a variable or macro / define can have for it to appear in the -# documentation. If the initializer consists of more lines than specified here -# it will be hidden. Use a value of 0 to hide initializers completely. The -# appearance of the value of individual variables and macros / defines can be -# controlled using \showinitializer or \hideinitializer command in the -# documentation regardless of this setting. -# Minimum value: 0, maximum value: 10000, default value: 30. - MAX_INITIALIZER_LINES = 30 - -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at -# the bottom of the documentation of classes and structs. If set to YES, the -# list will mention the files that were used to generate the documentation. -# The default value is: YES. - SHOW_USED_FILES = YES - -# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This -# will remove the Files entry from the Quick Index and from the Folder Tree View -# (if specified). -# The default value is: YES. - SHOW_FILES = YES - -# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces -# page. This will remove the Namespaces entry from the Quick Index and from the -# Folder Tree View (if specified). -# The default value is: YES. - -SHOW_NAMESPACES = NO - -# The FILE_VERSION_FILTER tag can be used to specify a program or script that -# doxygen should invoke to get the current version for each file (typically from -# the version control system). Doxygen will invoke the program by executing (via -# popen()) the command command input-file, where command is the value of the -# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided -# by doxygen. Whatever the program writes to standard output is used as the file -# version. For an example see the documentation. - +SHOW_NAMESPACES = YES FILE_VERSION_FILTER = - -# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed -# by doxygen. The layout file controls the global structure of the generated -# output files in an output format independent way. To create the layout file -# that represents doxygen's defaults, run doxygen with the -l option. You can -# optionally specify a file name after the option, if omitted DoxygenLayout.xml -# will be used as the name of the layout file. -# -# Note that if you run doxygen from a directory containing a file called -# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE -# tag is left empty. - LAYOUT_FILE = - -# The CITE_BIB_FILES tag can be used to specify one or more bib files containing -# the reference definitions. This must be a list of .bib files. The .bib -# extension is automatically appended if omitted. This requires the bibtex tool -# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. -# For LaTeX the style of the bibliography can be controlled using -# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the -# search path. See also \cite for info how to create references. - CITE_BIB_FILES = - #--------------------------------------------------------------------------- # Configuration options related to warning and progress messages #--------------------------------------------------------------------------- - -# The QUIET tag can be used to turn on/off the messages that are generated to -# standard output by doxygen. If QUIET is set to YES this implies that the -# messages are off. -# The default value is: NO. - QUIET = NO - -# The WARNINGS tag can be used to turn on/off the warning messages that are -# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES -# this implies that the warnings are on. -# -# Tip: Turn warnings on while writing the documentation. -# The default value is: YES. - WARNINGS = YES - -# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate -# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag -# will automatically be disabled. -# The default value is: YES. - WARN_IF_UNDOCUMENTED = YES - -# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for -# potential errors in the documentation, such as not documenting some parameters -# in a documented function, or documenting parameters that don't exist or using -# markup commands wrongly. -# The default value is: YES. - WARN_IF_DOC_ERROR = YES - -# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that -# are documented, but have no documentation for their parameters or return -# value. If set to NO, doxygen will only warn about wrong or incomplete -# parameter documentation, but not about the absence of documentation. -# The default value is: NO. - WARN_NO_PARAMDOC = NO - -# The WARN_FORMAT tag determines the format of the warning messages that doxygen -# can produce. The string should contain the $file, $line, and $text tags, which -# will be replaced by the file and line number from which the warning originated -# and the warning text. Optionally the format may contain $version, which will -# be replaced by the version of the file (if it could be obtained via -# FILE_VERSION_FILTER) -# The default value is: $file:$line: $text. - WARN_FORMAT = "$file:$line: $text" - -# The WARN_LOGFILE tag can be used to specify a file to which warning and error -# messages should be written. If left blank the output is written to standard -# error (stderr). - WARN_LOGFILE = - #--------------------------------------------------------------------------- # Configuration options related to the input files #--------------------------------------------------------------------------- - -# The INPUT tag is used to specify the files and/or directories that contain -# documented source files. You may enter file names like myfile.cpp or -# directories like /usr/src/myproject. Separate the files or directories with -# spaces. -# Note: If this tag is empty the current directory is searched. - -INPUT = \ - modules.dox \ - about.dox \ - design.dox \ - exa.dox \ - exa_apps.dox \ - exa_native.dox \ - exa_rtos.dox \ - exa_os.dox \ - exa_mware.dox \ - ports.dox \ - ports_native.dox \ - ports_rtos.dox \ - ports_os.dox \ - history.dox \ +INPUT = \ + modules.cc \ + about.cc \ + design.cc \ + exa.cc \ + exa_apps.cc \ + exa_native.cc \ + exa_rtos.cc \ + exa_os.cc \ + exa_mware.cc \ + ports.cc \ + ports_native.cc \ + ports_rtos.cc \ + ports_os.cc \ + history.cc \ macros.h \ - metrics.dox \ + metrics.cc \ ../include \ ../source \ - ../ports/lint - ../ports/lint/qkn \ - ../ports/lint/qvn + ../ports/lint \ + ../ports/lint/qk \ + ../ports/lint/qv -# This tag can be used to specify the character encoding of the source files -# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses -# libiconv (or the iconv built into libc) for the transcoding. See the libiconv -# documentation (see: http://www.gnu.org/software/libiconv) for the list of -# possible encodings. -# The default value is: UTF-8. - -INPUT_ENCODING = UTF-8 - -# If the value of the INPUT tag contains directories, you can use the -# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and -# *.h) to filter out the source-files in the directories. If left blank the -# following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii, -# *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, -# *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, -# *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf, -# *.qsf, *.as and *.js. - -FILE_PATTERNS = \ - *.dox \ +INPUT_ENCODING = UTF-8 +FILE_PATTERNS = \ + *.cc \ *.h \ *.c \ *.cpp \ *.s \ *.asm -# The RECURSIVE tag can be used to specify whether or not subdirectories should -# be searched for input files as well. -# The default value is: NO. - RECURSIVE = YES - -# The EXCLUDE tag can be used to specify files and/or directories that should be -# excluded from the INPUT source files. This way you can easily exclude a -# subdirectory from a directory tree whose root is specified with the INPUT tag. -# -# Note that relative paths are relative to the directory from which doxygen is -# run. - -EXCLUDE = \ +EXCLUDE = \ ../include/qs_dummy.h \ ../ports/lint/MISRA_Exemplar_Suite_test -# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or -# directories that are symbolic links (a Unix file system feature) are excluded -# from the input. -# The default value is: NO. +EXCLUDE_SYMLINKS = NO +EXCLUDE_PATTERNS = +EXCLUDE_SYMBOLS = \ + QP_IMPL -EXCLUDE_SYMLINKS = NO - -# If the value of the INPUT tag contains directories, you can use the -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude -# certain files from those directories. -# -# Note that the wildcards are matched against the file with absolute path, so to -# exclude all test directories for example use the pattern */test/* - -EXCLUDE_PATTERNS = - -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names -# (namespaces, classes, functions, etc.) that should be excluded from the -# output. The symbol name can be a fully qualified name, a word, or if the -# wildcard * is used, a substring. Examples: ANamespace, AClass, -# AClass::ANamespace, ANamespace::*Test -# -# Note that the wildcards are matched against the file with absolute path, so to -# exclude all test directories use the pattern */test/* - -EXCLUDE_SYMBOLS = QP_IMPL - -# The EXAMPLE_PATH tag can be used to specify one or more files or directories -# that contain example code fragments that are included (see the \include -# command). - -EXAMPLE_PATH = \ +EXAMPLE_PATH = \ snippets \ ../include \ ../source \ ../ports \ ../examples -# If the value of the EXAMPLE_PATH tag contains directories, you can use the -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and -# *.h) to filter out the source-files in the directories. If left blank all -# files are included. - EXAMPLE_PATTERNS = - -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude commands -# irrespective of the value of the RECURSIVE tag. -# The default value is: NO. - EXAMPLE_RECURSIVE = NO - -# The IMAGE_PATH tag can be used to specify one or more files or directories -# that contain images that are to be included in the documentation (see the -# \image command). - IMAGE_PATH = images - -# The INPUT_FILTER tag can be used to specify a program that doxygen should -# invoke to filter for each input file. Doxygen will invoke the filter program -# by executing (via popen()) the command: -# -# -# -# where is the value of the INPUT_FILTER tag, and is the -# name of an input file. Doxygen will then use the output that the filter -# program writes to standard output. If FILTER_PATTERNS is specified, this tag -# will be ignored. -# -# Note that the filter must not add or remove lines; it is applied before the -# code is scanned, but not when the output code is generated. If lines are added -# or removed, the anchors will not be placed correctly. - INPUT_FILTER = - -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern -# basis. Doxygen will compare the file name with each pattern and apply the -# filter if there is a match. The filters are a list of the form: pattern=filter -# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how -# filters are used. If the FILTER_PATTERNS tag is empty or if none of the -# patterns match the file name, INPUT_FILTER is applied. - FILTER_PATTERNS = - -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using -# INPUT_FILTER) will also be used to filter the input files that are used for -# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). -# The default value is: NO. - FILTER_SOURCE_FILES = NO - -# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file -# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and -# it is also possible to disable source filtering for a specific pattern using -# *.ext= (so without naming a filter). -# This tag requires that the tag FILTER_SOURCE_FILES is set to YES. - FILTER_SOURCE_PATTERNS = - -# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that -# is part of the input, its contents will be placed on the main page -# (index.html). This can be useful if you have a project on for instance GitHub -# and want to reuse the introduction page also for the doxygen output. - USE_MDFILE_AS_MAINPAGE = - #--------------------------------------------------------------------------- # Configuration options related to source browsing #--------------------------------------------------------------------------- - -# If the SOURCE_BROWSER tag is set to YES then a list of source files will be -# generated. Documented entities will be cross-referenced with these sources. -# -# Note: To get rid of all source code in the generated output, make sure that -# also VERBATIM_HEADERS is set to NO. -# The default value is: NO. - SOURCE_BROWSER = YES - -# Setting the INLINE_SOURCES tag to YES will include the body of functions, -# classes and enums directly into the documentation. -# The default value is: NO. - INLINE_SOURCES = NO - -# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any -# special comment blocks from generated source code fragments. Normal C, C++ and -# Fortran comments will always remain visible. -# The default value is: YES. - STRIP_CODE_COMMENTS = YES - -# If the REFERENCED_BY_RELATION tag is set to YES then for each documented -# function all documented functions referencing it will be listed. -# The default value is: NO. - REFERENCED_BY_RELATION = NO - -# If the REFERENCES_RELATION tag is set to YES then for each documented function -# all documented entities called/used by that function will be listed. -# The default value is: NO. - REFERENCES_RELATION = NO - -# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set -# to YES then the hyperlinks from functions in REFERENCES_RELATION and -# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will -# link to the documentation. -# The default value is: YES. - REFERENCES_LINK_SOURCE = YES - -# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the -# source code will show a tooltip with additional information such as prototype, -# brief description and links to the definition and documentation. Since this -# will make the HTML file larger and loading of large files a bit slower, you -# can opt to disable this feature. -# The default value is: YES. -# This tag requires that the tag SOURCE_BROWSER is set to YES. - SOURCE_TOOLTIPS = YES - -# If the USE_HTAGS tag is set to YES then the references to source code will -# point to the HTML generated by the htags(1) tool instead of doxygen built-in -# source browser. The htags tool is part of GNU's global source tagging system -# (see http://www.gnu.org/software/global/global.html). You will need version -# 4.8.6 or higher. -# -# To use it do the following: -# - Install the latest version of global -# - Enable SOURCE_BROWSER and USE_HTAGS in the config file -# - Make sure the INPUT points to the root of the source tree -# - Run doxygen as normal -# -# Doxygen will invoke htags (and that will in turn invoke gtags), so these -# tools must be available from the command line (i.e. in the search path). -# -# The result: instead of the source browser generated by doxygen, the links to -# source code will now point to the output of htags. -# The default value is: NO. -# This tag requires that the tag SOURCE_BROWSER is set to YES. - USE_HTAGS = NO - -# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a -# verbatim copy of the header file for each class for which an include is -# specified. Set to NO to disable this. -# See also: Section \class. -# The default value is: YES. - VERBATIM_HEADERS = YES - -# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the -# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the -# cost of reduced performance. This can be particularly helpful with template -# rich C++ code for which doxygen's built-in parser lacks the necessary type -# information. -# Note: The availability of this option depends on whether or not doxygen was -# compiled with the --with-libclang option. -# The default value is: NO. - -CLANG_ASSISTED_PARSING = NO - -# If clang assisted parsing is enabled you can provide the compiler with command -# line options that you would normally use when invoking the compiler. Note that -# the include paths will already be set by doxygen for the files and directories -# specified with INPUT and INCLUDE_PATH. -# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. - -CLANG_OPTIONS = - #--------------------------------------------------------------------------- # Configuration options related to the alphabetical class index #--------------------------------------------------------------------------- - -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all -# compounds will be generated. Enable this if the project contains a lot of -# classes, structs, unions or interfaces. -# The default value is: YES. - ALPHABETICAL_INDEX = YES - -# The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in -# which the alphabetical index list will be split. -# Minimum value: 1, maximum value: 20, default value: 5. -# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. - COLS_IN_ALPHA_INDEX = 5 - -# In case all classes in a project start with a common prefix, all classes will -# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag -# can be used to specify a prefix (or a list of prefixes) that should be ignored -# while generating the index headers. -# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. - IGNORE_PREFIX = - #--------------------------------------------------------------------------- # Configuration options related to the HTML output #--------------------------------------------------------------------------- - -# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output -# The default value is: YES. - GENERATE_HTML = YES - -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a -# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of -# it. -# The default directory is: html. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_OUTPUT = ../../doc/qpc - -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each -# generated HTML page (for example: .htm, .php, .asp). -# The default value is: .html. -# This tag requires that the tag GENERATE_HTML is set to YES. - +HTML_OUTPUT = ../../html/qpc HTML_FILE_EXTENSION = .html - -# The HTML_HEADER tag can be used to specify a user-defined HTML header file for -# each generated HTML page. If the tag is left blank doxygen will generate a -# standard header. -# -# To get valid HTML the header file that includes any scripts and style sheets -# that doxygen needs, which is dependent on the configuration options used (e.g. -# the setting GENERATE_TREEVIEW). It is highly recommended to start with a -# default header using -# doxygen -w html new_header.html new_footer.html new_stylesheet.css -# YourConfigFile -# and then modify the file new_header.html. See also section "Doxygen usage" -# for information on how to generate the default header that doxygen normally -# uses. -# Note: The header is subject to change so you typically have to regenerate the -# default header when upgrading to a newer version of doxygen. For a description -# of the possible markers and block names see the documentation. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_HEADER = header.html - -# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each -# generated HTML page. If the tag is left blank doxygen will generate a standard -# footer. See HTML_HEADER for more information on how to generate a default -# footer and what special commands can be used inside the footer. See also -# section "Doxygen usage" for information on how to generate the default footer -# that doxygen normally uses. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_FOOTER = footer.html - -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style -# sheet that is used by each HTML page. It can be used to fine-tune the look of -# the HTML output. If left blank doxygen will generate a default style sheet. -# See also section "Doxygen usage" for information on how to generate the style -# sheet that doxygen normally uses. -# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as -# it is more robust and this tag (HTML_STYLESHEET) will in the future become -# obsolete. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_STYLESHEET = - -# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined -# cascading style sheets that are included after the standard style sheets -# created by doxygen. Using this option one can overrule certain style aspects. -# This is preferred over using HTML_STYLESHEET since it does not replace the -# standard style sheet and is therefore more robust against future updates. -# Doxygen will copy the style sheet files to the output directory. -# Note: The order of the extra style sheet files is of importance (e.g. the last -# style sheet in the list overrules the setting of the previous ones in the -# list). For an example see the documentation. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_EXTRA_STYLESHEET = ql.css - -# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or -# other source files which should be copied to the HTML output directory. Note -# that these files will be copied to the base HTML output directory. Use the -# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these -# files. In the HTML_STYLESHEET file, use the file name only. Also note that the -# files will be copied as-is; there are no commands or markers available. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_EXTRA_FILES = - -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen -# will adjust the colors in the style sheet and background images according to -# this color. Hue is specified as an angle on a colorwheel, see -# http://en.wikipedia.org/wiki/Hue for more information. For instance the value -# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 -# purple, and 360 is red again. -# Minimum value: 0, maximum value: 359, default value: 220. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_COLORSTYLE_HUE = 220 - -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors -# in the HTML output. For a value of 0 the output will use grayscales only. A -# value of 255 will produce the most vivid colors. -# Minimum value: 0, maximum value: 255, default value: 100. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_COLORSTYLE_SAT = 100 - -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the -# luminance component of the colors in the HTML output. Values below 100 -# gradually make the output lighter, whereas values above 100 make the output -# darker. The value divided by 100 is the actual gamma applied, so 80 represents -# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not -# change the gamma. -# Minimum value: 40, maximum value: 240, default value: 80. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_COLORSTYLE_GAMMA = 80 - -# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML -# page will contain the date and time when the page was generated. Setting this -# to NO can help when comparing the output of multiple runs. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_TIMESTAMP = NO - -# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML -# documentation will contain sections that can be hidden and shown after the -# page has loaded. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_DYNAMIC_SECTIONS = NO - -# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries -# shown in the various tree structured indices initially; the user can expand -# and collapse entries dynamically later on. Doxygen will expand the tree to -# such a level that at most the specified number of entries are visible (unless -# a fully collapsed tree already exceeds this amount). So setting the number of -# entries 1 will produce a full collapsed tree by default. 0 is a special value -# representing an infinite number of entries and will result in a full expanded -# tree by default. -# Minimum value: 0, maximum value: 9999, default value: 100. -# This tag requires that the tag GENERATE_HTML is set to YES. - HTML_INDEX_NUM_ENTRIES = 100 - -# If the GENERATE_DOCSET tag is set to YES, additional index files will be -# generated that can be used as input for Apple's Xcode 3 integrated development -# environment (see: http://developer.apple.com/tools/xcode/), introduced with -# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a -# Makefile in the HTML output directory. Running make will produce the docset in -# that directory and running make install will install the docset in -# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at -# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html -# for more information. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - GENERATE_DOCSET = NO - -# This tag determines the name of the docset feed. A documentation feed provides -# an umbrella under which multiple documentation sets from a single provider -# (such as a company or product suite) can be grouped. -# The default value is: Doxygen generated docs. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - DOCSET_FEEDNAME = "Doxygen generated docs" - -# This tag specifies a string that should uniquely identify the documentation -# set bundle. This should be a reverse domain-name style string, e.g. -# com.mycompany.MyDocSet. Doxygen will append .docset to the name. -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_BUNDLE_ID = com.state-machine.qm - -# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify -# the documentation publisher. This should be a reverse domain-name style -# string, e.g. com.mycompany.MyDocSet.documentation. -# The default value is: org.doxygen.Publisher. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_PUBLISHER_ID = org.doxygen.Publisher - -# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. -# The default value is: Publisher. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_PUBLISHER_NAME = Publisher - -# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three -# additional HTML index files: index.hhp, index.hhc, and index.hhk. The -# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop -# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on -# Windows. -# -# The HTML Help Workshop contains a compiler that can convert all HTML output -# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML -# files are now used as the Windows 98 help format, and will replace the old -# Windows help format (.hlp) on all Windows platforms in the future. Compressed -# HTML files also contain an index, a table of contents, and you can search for -# words in the documentation. The HTML workshop also contains a viewer for -# compressed HTML files. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - +DOCSET_BUNDLE_ID = com.state-machine.doc +DOCSET_PUBLISHER_ID = com.state-machine.doc +DOCSET_PUBLISHER_NAME = Quantum Leaps GENERATE_HTMLHELP = NO - -# The CHM_FILE tag can be used to specify the file name of the resulting .chm -# file. You can add a path in front of the file if the result should not be -# written to the html output directory. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -CHM_FILE = ../../doc/qpc.chm - -# The HHC_LOCATION tag can be used to specify the location (absolute path -# including file name) of the HTML help compiler (hhc.exe). If non-empty, -# doxygen will try to run the HTML help compiler on the generated index.hhp. -# The file has to be specified with full path. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - +CHM_FILE = ../../../html/qpc.chm HHC_LOCATION = - -# The GENERATE_CHI flag controls if a separate .chi index file is generated -# (YES) or that it should be included in the master .chm file (NO). -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - GENERATE_CHI = NO - -# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) -# and project file content. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - CHM_INDEX_ENCODING = - -# The BINARY_TOC flag controls whether a binary table of contents is generated -# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it -# enables the Previous and Next buttons. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - BINARY_TOC = NO - -# The TOC_EXPAND flag can be set to YES to add extra items for group members to -# the table of contents of the HTML help documentation and to the tree view. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - TOC_EXPAND = NO - -# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and -# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that -# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help -# (.qch) of the generated HTML documentation. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - GENERATE_QHP = NO - -# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify -# the file name of the resulting .qch file. The path specified is relative to -# the HTML output folder. -# This tag requires that the tag GENERATE_QHP is set to YES. - QCH_FILE = - -# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help -# Project output. For more information please see Qt Help Project / Namespace -# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_QHP is set to YES. - QHP_NAMESPACE = com.state-machine.qp - -# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt -# Help Project output. For more information please see Qt Help Project / Virtual -# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- -# folders). -# The default value is: doc. -# This tag requires that the tag GENERATE_QHP is set to YES. - QHP_VIRTUAL_FOLDER = doc - -# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom -# filter to add. For more information please see Qt Help Project / Custom -# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- -# filters). -# This tag requires that the tag GENERATE_QHP is set to YES. - QHP_CUST_FILTER_NAME = - -# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the -# custom filter to add. For more information please see Qt Help Project / Custom -# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- -# filters). -# This tag requires that the tag GENERATE_QHP is set to YES. - QHP_CUST_FILTER_ATTRS = - -# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this -# project's filter section matches. Qt Help Project / Filter Attributes (see: -# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). -# This tag requires that the tag GENERATE_QHP is set to YES. - QHP_SECT_FILTER_ATTRS = - -# The QHG_LOCATION tag can be used to specify the location of Qt's -# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the -# generated .qhp file. -# This tag requires that the tag GENERATE_QHP is set to YES. - QHG_LOCATION = - -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be -# generated, together with the HTML files, they form an Eclipse help plugin. To -# install this plugin and make it available under the help contents menu in -# Eclipse, the contents of the directory containing the HTML and XML files needs -# to be copied into the plugins directory of eclipse. The name of the directory -# within the plugins directory should be the same as the ECLIPSE_DOC_ID value. -# After copying Eclipse needs to be restarted before the help appears. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - GENERATE_ECLIPSEHELP = NO - -# A unique identifier for the Eclipse help plugin. When installing the plugin -# the directory name containing the HTML and XML files should also have this -# name. Each documentation set should have its own identifier. -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. - ECLIPSE_DOC_ID = com.state-machine.qp - -# If you want full control over the layout of the generated HTML pages it might -# be necessary to disable the index and replace it with your own. The -# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top -# of each HTML page. A value of NO enables the index and the value YES disables -# it. Since the tabs in the index contain the same information as the navigation -# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - DISABLE_INDEX = YES - -# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index -# structure should be generated to display hierarchical information. If the tag -# value is set to YES, a side panel will be generated containing a tree-like -# index structure (just like the one that is generated for HTML Help). For this -# to work a browser that supports JavaScript, DHTML, CSS and frames is required -# (i.e. any modern browser). Windows users are probably better off using the -# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can -# further fine-tune the look of the index. As an example, the default style -# sheet generated by doxygen has an example that shows how to put an image at -# the root of the tree instead of the PROJECT_NAME. Since the tree basically has -# the same information as the tab index, you could consider setting -# DISABLE_INDEX to YES when enabling this option. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - GENERATE_TREEVIEW = YES - -# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that -# doxygen will group on one line in the generated HTML documentation. -# -# Note that a value of 0 will completely suppress the enum values from appearing -# in the overview section. -# Minimum value: 0, maximum value: 20, default value: 4. -# This tag requires that the tag GENERATE_HTML is set to YES. - ENUM_VALUES_PER_LINE = 4 - -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used -# to set the initial width (in pixels) of the frame in which the tree is shown. -# Minimum value: 0, maximum value: 1500, default value: 250. -# This tag requires that the tag GENERATE_HTML is set to YES. - TREEVIEW_WIDTH = 180 - -# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to -# external symbols imported via tag files in a separate window. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - EXT_LINKS_IN_WINDOW = NO - -# Use this tag to change the font size of LaTeX formulas included as images in -# the HTML documentation. When you change the font size after a successful -# doxygen run you need to manually remove any form_*.png images from the HTML -# output directory to force them to be regenerated. -# Minimum value: 8, maximum value: 50, default value: 10. -# This tag requires that the tag GENERATE_HTML is set to YES. - FORMULA_FONTSIZE = 10 - -# Use the FORMULA_TRANPARENT tag to determine whether or not the images -# generated for formulas are transparent PNGs. Transparent PNGs are not -# supported properly for IE 6.0, but are supported on all modern browsers. -# -# Note that when changing this option you need to delete any form_*.png files in -# the HTML output directory before the changes have effect. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - FORMULA_TRANSPARENT = YES - -# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see -# http://www.mathjax.org) which uses client side Javascript for the rendering -# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX -# installed or if you want to formulas look prettier in the HTML output. When -# enabled you may also need to install MathJax separately and configure the path -# to it using the MATHJAX_RELPATH option. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - USE_MATHJAX = NO - -# When MathJax is enabled you can set the default output format to be used for -# the MathJax output. See the MathJax site (see: -# http://docs.mathjax.org/en/latest/output.html) for more details. -# Possible values are: HTML-CSS (which is slower, but has the best -# compatibility), NativeMML (i.e. MathML) and SVG. -# The default value is: HTML-CSS. -# This tag requires that the tag USE_MATHJAX is set to YES. - MATHJAX_FORMAT = HTML-CSS - -# When MathJax is enabled you need to specify the location relative to the HTML -# output directory using the MATHJAX_RELPATH option. The destination directory -# should contain the MathJax.js script. For instance, if the mathjax directory -# is located at the same level as the HTML output directory, then -# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax -# Content Delivery Network so you can quickly see the result without installing -# MathJax. However, it is strongly recommended to install a local copy of -# MathJax from http://www.mathjax.org before deployment. -# The default value is: http://cdn.mathjax.org/mathjax/latest. -# This tag requires that the tag USE_MATHJAX is set to YES. - MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest - -# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax -# extension names that should be enabled during MathJax rendering. For example -# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols -# This tag requires that the tag USE_MATHJAX is set to YES. - MATHJAX_EXTENSIONS = - -# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces -# of code that will be used on startup of the MathJax code. See the MathJax site -# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an -# example see the documentation. -# This tag requires that the tag USE_MATHJAX is set to YES. - MATHJAX_CODEFILE = - -# When the SEARCHENGINE tag is enabled doxygen will generate a search box for -# the HTML output. The underlying search engine uses javascript and DHTML and -# should work on any modern browser. Note that when using HTML help -# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) -# there is already a search function so this one should typically be disabled. -# For large projects the javascript based search engine can be slow, then -# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to -# search using the keyboard; to jump to the search box use + S -# (what the is depends on the OS and browser, but it is typically -# , /