Yahoo Groups archive

68300

Index last updated: 2026-04-29 00:01 UTC

Thread

pwm interrupt for 68376

pwm interrupt for 68376

2003-03-19 by Erik Wise

I am having trouble setting up the interrupt that will fire after 
completion of each pwm period.  I previously posted but made a 
mistake when I said that I was using the TPU to handle the PWM 
signal.  I am actually using the PWM submodule that is part of the 
CTM4.

My question is: What is the interrupt vector that is selected if the 
PWM5SIC register is set to trigure an interrupt?  Is is user defined?

Thanks,
Erik

Re: [68300] pwm interrupt for 68376

2003-03-19 by jeffrey.tenney@gm.com

Erik,

Yes, it's user defined (within limits).  Write to the Bus Interface Unit's
MCR to set the "base" interrupt vector for the CTM4.  PWM5 would use vector
base+5.  You've probably already figured out that it can be at the IPL of
your choice using the PWMSIC register.

See Table 10-7 in the MC68376UM for the breakdown.

Jeff





"Erik Wise" <erik_wise@...> on 03/18/2003 05:08:04 PM

Please respond to 68300@yahoogroups.com

To:    68300@yahoogroups.com
cc:
Show quoted textHide quoted text
Subject:    [68300] pwm interrupt for 68376


I am having trouble setting up the interrupt that will fire after
completion of each pwm period.  I previously posted but made a
mistake when I said that I was using the TPU to handle the PWM
signal.  I am actually using the PWM submodule that is part of the
CTM4.

My question is: What is the interrupt vector that is selected if the
PWM5SIC register is set to trigure an interrupt?  Is is user defined?

Thanks,
Erik




---------------------------------------------------
To unsubscribe from this group, send an email to:
68300-unsubscribe@yahoogroups.com

To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.