I love MCC, it's the best bit of software Microchip has done.
My two gripes, one minor and one major.Minor
Not all interrupt handlers generate a function placeholder. For example most timers do something like -
// clear the TMR0 interrupt flag
PIR0bits.TMR0IF = 0;
// add your TMR0 interrupt custom code
While the CLC interrupt handler is -
// Clear the CLC interrupt flag
PIR5bits.CLC2IF = 0;
It's minor has I just insert my own at this point, but consistency would be nice.Major
To generate the interrupt handling code for a peripheral one ticks the necessary box, however there is an assumption the interrupt is to be enabled there and then. Much of the time I just want the code in place and I'll enable the interrupt at a later time.
Rather than modifying the mcc generated code (I try to avoid doing this to prevent accidental changes) I have a config function which overwrites the mcc values before interrupt handling is enabled. For example:
configUvl is reverting the value set by MCC code in SYSTEM_Initialize.
So basically "Enable interrupt" should be split into two boxes; 1. Support interrupt handling. 2. Enable interrupt (where 2 is dimmed out if 1. is not selected).
post edited by acharnley - 2019/12/05 16:19:42