QDK PIC24/dsPIC-XC16 - Quantum Leaps

QDK
PIC24/dsPIC-XC16
www.state-machine.com/pic
6.5 Assertion Handling Policy in Q_onAssert()
As described in Chapter 6 of [PSiCC2], all QP components use internally assertions to detect errors in the
way application is using the QP services. You need to define how the application reacts in case of
assertion failure by providing the callback function Q_onAssert(). Typically, you would put the system in
a fail-safe state and try to reset. It is also a good idea to log some information as to where the assertion
failed.
The following code fragment shows the Q_onAssert() callback for PIC24/dsPIC. The function keeps
locking interrupts in an endless loop. You can then break into the code with the debugger and inspect the
cause of the assertion by backtracking the call stack.
NOTE: This policy is only adequate for testing, but is not adequate for production release.
void Q_onAssert(char const Q_ROM * const Q_ROM_VAR file, int line) {
(void)file; /* avoid compiler warning */
(void)line; /* avoid compiler warning */
QF_INT_DISABLE(); /* make sure that interrupts are disabled */
for (;;) {
}
}
Copyright © Quantum Leaps, LLC. All Rights Reserved.
29 of 35