Editing Embedded system (section)

===Tracing===
Real-time operating systems often support [[tracing (software)|tracing]] of operating system events. A graphical view is presented by a host PC tool, based on a recording of the system behavior. The trace recording can be performed in software, by the RTOS, or by special tracing hardware. RTOS tracing allows developers to understand timing and performance issues of the software system and gives a good understanding of the high-level system behaviors. Trace recording in embedded systems can be achieved using hardware or software solutions. Software-based trace recording does not require specialized debugging hardware and can be used to record traces in deployed devices, but it can have an impact on CPU and RAM usage.<ref>{{Citation |last1=Kraft |first1=Johan |title=Trace Recording for Embedded Systems: Lessons Learned from Five Industrial Projects |date=2010 |url=http://link.springer.com/10.1007/978-3-642-16612-9_24 |work=Runtime Verification |volume=6418 |pages=315–329 |editor-last=Barringer |editor-first=Howard |place=Berlin, Heidelberg |publisher=Springer Berlin Heidelberg |language=en |doi=10.1007/978-3-642-16612-9_24 |isbn=978-3-642-16611-2 |access-date=2022-08-16 |last2=Wall |first2=Anders |last3=Kienle |first3=Holger |editor2-last=Falcone |editor2-first=Ylies |editor3-last=Finkbeiner |editor3-first=Bernd |editor4-last=Havelund |editor4-first=Klaus}}</ref> One example of a software-based tracing method used in RTOS environments is the use of empty [[Macro (computer science)|macros]] which are invoked by the operating system at strategic places in the code, and can be implemented to serve as [[Hooking|hooks]].