KBI SP register

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KBI SP register

Jump to solution
819 Views
davidsherman
Senior Contributor I

I have an interrupt responding on a KBI interrupt pin.  However, when I look at the KBI_SP register to indicate which pin caused the interrupt, all bits are always set.  This is true even afer I write to the KBI_SC RSTKBSP bit to clear it.  This a MKE06Z128VLH4. I have confirmed that the address is correct for  both the KBI0_SP and KBI1_SP registers, but they are all set and don't appear to change.  Am I missing something?

0 Kudos
1 Solution
544 Views
mjbcswitzerland
Specialist V

David

You need to set the KBSPEN bit in KBIx_SC to configure the correct flag mode.

pastedImage_1.png

Regards

Mark

http://www.utasker.com/kinetis.html

View solution in original post

0 Kudos
4 Replies
545 Views
mjbcswitzerland
Specialist V

David

You need to set the KBSPEN bit in KBIx_SC to configure the correct flag mode.

pastedImage_1.png

Regards

Mark

http://www.utasker.com/kinetis.html

0 Kudos
544 Views
mjbcswitzerland
Specialist V

David

I recently implemented a KBI module for KE02, KE04 and KE06 processors (there are two versions, whereby the KE06 has the more luxurious one).

The KBIs are simulated in the uTasker Kinetis simulator and allow individual user interrupts to be allocated to each of the pins.

I have a KE06 package including KBI operation at http://www.utasker.com/kinetis/FRDM-KE06Z.html

but haven't yet written up a module analysis. There is however some reference (for the simpler one) at

Re: Re: GPIO pin as interrupt source KEA-64

and some discussion of risk involved with individial interrupt assignement at

https://community.freescale.com/message/465329#465329

Regards

Mark

µTasker Kinetis support

0 Kudos
544 Views
davidsherman
Senior Contributor I

Ah, I feel sheepish.  That was the one thing I had overlooked in the documentation.  Thank you, Mark!  It's working now.

0 Kudos
544 Views
mjbcswitzerland
Specialist V

David

It is strange but I also missed it when I was developing and had the same issue the first time I tested.

Even after I had read all bit details, that one sort of blends into the white background of the user's manual, since it doesn't really make much sense as to what it does - initially...

Regards

Mark

0 Kudos