topic K20 Interrupts in Kinetis Microcontrollers

K20 Interrupts

gerryk — Wed, 21 Jan 2015 19:31:27 GMT

I am trying to get a K20 chip up and running using Code Warrier.

When I set up a basic project with Code Warrier both with and without program expert, the interrupt vector table gets populated with a common interrupt vector which generates a breakpoint.

The chip is generating an interrupt when I try to run even the simplest piece of code and when running in debug mode I am ending up in the common interrupt handler.

Is there a way to determine what the interrupt source is without having to write a separate vector for each source?

Is there a way to disable all interrupts?

Re: K20 Interrupts

adriancano — Wed, 21 Jan 2015 20:36:10 GMT

Hi,

Please check these posts form colleague Erich Styger they might be useful:

A Processor Expert Component to Help with Hard Faults | MCU on Eclipse

Debugging Hard Faults on ARM Cortex-M | MCU on Eclipse

Oh my! An Interrupt… | MCU on Eclipse

Hope this information can help you

Best Regards,
Adrian Sanchez Cano
Technical Support Engineer
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: K20 Interrupts

yasuhikokoumoto — Thu, 22 Jan 2015 02:14:01 GMT

Hi Gerry,

you can know the interrupt source from NVIC_IABR, NVIC_ISPR or NVIC_ICPR. If it was the hard fault, the possible reason was because the clock for the correspondent module had not been supplied.

Best regards,

Yasuhiko Koumoto.

Re: K20 Interrupts

mjbcswitzerland — Thu, 22 Jan 2015 03:50:09 GMT

To avoid starting complications you can also use a complete project framework for the K20 boards:

http://www.utasker.com/kinetis/FRDM-K20D50M.html

http://www.utasker.com/kinetis/TWR-K20D50M.html

µTasker Kinetis TWR-K20D72M support

Includes CW support and allows development and debugging a simulated K20 with VisualStudio.

When debugging, make sure that you never try stepping the watchdog initialisation code as decribed in http://www.utasker.com/docs/KINETIS/uTaskerV1.4_Kinetis_demo.pdf

Also verify that you have loaded the code correctly to Flash (check in a memory view) otherwise the code will also jump straight to an error handler.

Regards

Mark

µTasker Kinetis support