topic Doubt in CodeWarrior for MCU

Doubt

admin — Wed, 24 Feb 2010 17:58:12 GMT

Hi,

I am working on Code warrior Development Studio version 5.0 for MC9S12XDP512 MCU on SK-S12XDP512A demo kit. I want to check the status of the pushbutton on led connected to the PortB Pins. Can the pushbutton be given as an interrupt? If so, what interrupt type would it be? a Hardware Trigger? a Real time Interrupt? or what?

Re: Doubt

CrasyCat — Wed, 24 Feb 2010 21:32:16 GMT

Hello

You cannot generate an interrupt clicking on a push button in the visualization tool window.

CrasyCat

Re: Doubt

admin — Thu, 25 Feb 2010 01:25:53 GMT

hello, thank you.

n we make it work onRe: Doubt

admin — Thu, 25 Feb 2010 12:26:19 GMT

But can we make it work on a Demo Kit? The input will be the push button the status of which can be seen on an led...

SK-S12XDP512A is the demo kit I am using.

Re: n we make it work onRe: Doubt

vivek31be — Thu, 25 Feb 2010 14:53:26 GMT

Hi, checkout the processor expert help "Tutorial for Freescale HCS12 Project 2 Step 4" . I think it will solve your problem. It has given how to generate interrupt on button, since you are using a hardware demo kit it should work. Thanks, Vivek

Re: n we make it work onRe: Doubt

admin — Fri, 26 Feb 2010 15:14:12 GMT

Hello Vivek,

I have just tried it the way u suggested, but I am advised not to use the processor Expert as the code is generated within.... As a newbie this will not help me understand the programming of my microcontroller..

If u have any other idea of doing it.. just let me know..

Re: Doubt

Lundin — Fri, 26 Feb 2010 18:26:58 GMT

All pushbuttons have something called "contact bounce". When you press down a button, the mechanical parts bounce up and down and generate an electrical disturbance for a short time. Connect an oscilloscope to any button and check, you will see a short sine wave when it is pressed.

Another issue is electro-magnetical interference (EMI), "glitches" that are caused by noisy electronics. Such glitches can be removed through hardware with decoupling capacitors etc, but a serious embedded software designer will still have glitches in mind when writing the program.

Because of the two issues above, you must "debounce" a button whenever you read its status.

This is typically done this way:

1) Set an interrupt on the port where the button is connected, or alternatively read ("poll") the port from the main program.
2) When the port goes active, you have either found a user pressing the button, or a contact bounce from a previous button press, or an EMI glitch. You don't know which.

3) Start a timer. 5ms is a good timer value. During this time, ignore the button port.
3) When the timer has elapsed, read the port again.
4) Make sure that the values are the same during the 1st and the 2nd read. If they aren't, disregard the whole keypress - it was likely caused by EMI.
5) If the values were the same, light the LED etc.

Re: Doubt

admin — Wed, 03 Mar 2010 21:44:23 GMT

hello, thank you so much. that was very informative... i will try it.thank u agn