I am a bit confused with some issues around RTX and would be grateful if one can help me to understand them.
1. Assume I want (or better said my boss wants ) to use RTX outside MDK, for example Atollic. I saw RTX is not distributed as a separate product, but just as a part of MDK. Does it mean I must buy MDK (assuming Lite does not fit my needs) in order to use it ?
2. What are the technical disadvantages in using RTX with other IDE, for example Atollic? What will I miss? I thought maybe I would miss the System View tool (RTOS awareness tool).Are there all the plugins for using the RTX in Atollic?
3. I understood there is a built-in feature in MDK for RTOS awareness to see for example the threads stacks and etc. Is that something basic or similar to features of the Percepio's tool?
Thank you in advance for any help!
Below are the answers to your questions:
1. RTX is available for Arm Compiler, GCC, and IAR Compiler. See here https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/RTOS2. As such, you can use it also with Atollic (as these tools are GCC based)
2. MDK offers static and dynamic event viewers for RTX. We don't know what Atollic has implemented here.
3. MDK has an event viewer that shows similar information like Percepio. Percepio has more features and statistic views. MDK offers an interface to Percepio and therefore you can get the extended features of Percepio when needed.
Let us know if you have further questions.
Thank you very much for your prompt and valuable answer.
Would you be so kind as also to explain me what are the dynamic and static events viewers you mentioned in #2?
MDK provides detailed insight into the RTX operations. See here http://www2.keil.com/mdk5/debug/ under Component Viewer and Event Recorder.
- System Viewer shows timing of interrupts, RTOS threads and user events: http://www.keil.com/support/man/docs/uv4/uv4_db_dbg_systemanalyzer.htm
- Here is a more generic description of the Event Recorder http://www.keil.com/support/man/docs/uv4/uv4_db_dbg_evr.htm
I hope this helps.
Thank you very much Reinhard for your help!