Yahoo Groups archive

68300

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

Message

Re: [68300] Does anybody have a TPU solution for this?

2003-03-20 by Robert Smith

The straight forward way is to program one channel for the input pulse and
one for the output pulse.

The communicate between the two in the interrupt handlers.

If you want to do it entirely within the TPU, find a copy of the TPU
assembler and have at it.

    Good luck, Bob Smith


---   Avoid computer viruses, Practice safe hex  ---

-- Specializing in small, cost effective
    embedded control systems --

http://www.smithmachineworks.com/embedprod.html


Robert L. (Bob) Smith
Smith Machine Works, Inc.
9900 Lumlay Road
Richmond, VA 23236   804/745-1065

  bobsmith5@...

----- Original Message -----
From: "Alwin Lutz" <ALutz@...>
To: "68300 Group (E-mail)" <68300@yahoogroups.com>
Sent: Wednesday, March 19, 2003 7:30 PM
Subject: [68300] Does anybody have a TPU solution for this?


> Hello group,
>
> does anybody of you guys know of some nifty
> way to solve the following problem:
>
> I have an incoming signal (low pulse with a period T1)
> at one TPU channel and need to generate a new signal
> at another TPU channel with the following period:
> T2 = (T1 * X) + Y,
> where X would be a multiplier from 1.0 to 2.0
> and Y some additional time.
>
> It would be great to have this done automatically
> with two TPU functions that are linked.  The CPU would
> have to update the terms X and Y at whatever time
> interval is desired.
>
> If anybody had to deal with something similar,
> I would be interested in any suggestions.
>
> Thanks,
> Alwin
>
>
> ---------------------------------------------------
> 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/
>
>
>

Attachments

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.