Possible usage scenarios include for example preparation of hardware for debugging, collection of various information while debugging or simulating peripherals and interrupts. Whether you are connected to the target hardware or simulating your embedded project, C-SPY macros offer a very useful and flexible way to customize your debugging session. Once that counter is 2, the macro sets a code breakpoint at the entry of the fast timer interrupt handler: SetBreakpoint().82.1',0,'WriteMemory2File()','TRUE','') It contains a counter as a macro variable, which is incremented every time the slow timer is executed. If so, the macro sets a breakpoint in the faster event.īelow is one possible solution for that macro. This breakpoint calls a macro that checks whether it is the second time it has been called.

Imagine that you want to know what happens the first time that the faster event triggers after the slower has triggered twice. This is really useful when debugging an event-driven system where you wish to debug a nested series of events, but want the system to keep running until this happens. As an example, you can have a system with two timer interrupts, one at 10s and one at 0.1s. This breakpoint can be set by another macro depending on the conditions when executing this macro. Executing macrosĪ macro can be executed at other times too, either manually or by using a breakpoint. Instead of waiting for the developers working on the boot application so that you can test your application, just throw in a macro that loads the memory, perhaps from a file, before the application is loaded and continue testing, without changing the code to be tested. One example where this might be useful is a system where the boot process is not developed yet, but you need to have some specific data in place for the application to work correctly. These macros can be used for preparing the device before the next step in debugging, such as clearing or filling an area of the memory before downloading your application software. Setup macrosĪ setup macro is a macro with a predefined name that is called during a predefined phase of the debugging, such as each time the target is reset. Macro strings, which you can manipulate using predefined system macros.Ĭ-SPY macros can be called at specific times or executed manually or by breakpoints.Macro variables, which can be global or local, and can be used in C-SPY expressions.Predefined built-in system macros, similar to C library functions, which perform useful tasks such as opening and closing files, setting breakpoints, and defining simulated interrupts.

Macro functions, which you can define with or without parameters and return values.Macro statements, which are similar to C statements.The syntax of the macro language is actually very similar to the C language.

C for macro