AnsweredAssumed Answered

Problems porting from KL27Z64 to KL17Z128 - cannot see interrupts

Question asked by Katie Elliott on Jun 7, 2017
Latest reply on Jun 7, 2017 by Kerry Zhou

I'm in the middle of HW bring up on a custom board using the KL17Z128. We did initial development on the FRDM-KL27Z development kit and had everything working fine. Now that we've ported to the KL17Z, we've run into a problem where interrupts are not firing.

 

Even when we force a hard fault by dereferencing a null pointer, we cannot break in the hardfault ISR. When we halt execution, the code is indeed in the weeds, which is expected if we had a hardfault but didn't go to the ISR. We have also tried other interrupts and so far have not been able to get ANY interrupt to go to its ISR. The vector table and map file appear to be correct, with the vector table address pointing to the correct interrupt handler.

 

Any suggestions on what could be wrong?

 

Dev environment: Using IAR v7.70.2 with jlink debugger on Windows 10 and Windows7.

Outcomes