util.h

Miscellaneous utility macros and procedures.

Bit Manipulation

#define BIT(shift)                     (1UL << (shift))
#define BIT_MASK_SHIFT(mask, shift)    ((mask) << (shift))
/** Gets bits m to n of x */
#define GET_BITS(x, m, n) ((((uint32)x) << (31 - (n))) >> ((31 - (n)) + (m)))
#define IS_POWER_OF_TWO(v)  (v && !(v & (v - 1)))

Failure Routines

void throb(void)

Fades the error LED on and off.

Side Effects::Sets output push-pull on ERROR_LED_PIN.

Asserts and Debug Levels

The level of libmaple’s assertion support is determined by DEBUG_LEVEL, as follows:

DEBUG_LEVEL

Controls the level of assertion checking.

The higher the debug level, the more assertions will be compiled in. This increases the amount of debugging information, but slows down (and increases the size of) the binary.

The debug levels, from lowest to highest, are DEBUG_NONE, DEBUG_FAULT, and DEBUG_ALL. The default level is DEBUG_ALL.

The current assert macros are ASSERT() and ASSERT_FAULT(). ASSERT() is checked when DEBUG_LEVEL >= DEBUG_ALL. ASSERT_FAULT() is checked whenever DEBUG_LEVEL >= DEBUG_FAULT.

As explained above, an assert macro is checked when the current DEBUG_LEVEL is high enough. If the debug level is too low, the macro expands into a no-op that gets compiled away.

If an assertion fails, execution is halted at the point of the failed assertion. When libmaple has been configured properly (Wirish performs this configuration by default), the built-in LED throbs in a smooth pattern to signal the failed assertion (using throb()), and the file and line where the assert failed are transmitted to the user as detailed in ASSERT(...).