Yahoo Groups archive

68300

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

Message

Re: [68300] 32 bit timer on TPU on 68376

2003-12-04 by Rod.Niner@gsescales.spx.com

Eric McRae - Electro-Logic Machines, Inc.
511 Root St.,  Port Townsend WA, 98368
Phone/Fax: 360.379.0969, http://www.elmi.com
 wrote a timer32 that we use.

Rod Niner
GSE Scales
42860 Nine Mile Road
Novi, MI 48375-4122
ph: 248.596.3350
rod.niner@...

The information contained in this electronic mail transmission is intended 
by SPX Corporation for the use of the named individual or entity to which 
it is directed and may contain information that is confidential or 
privileged. If you have received this electronic mail transmission in 
error, please delete it from your system without copying or forwarding it, 
and notify the sender of the error by reply email so that the sender's 
address records can be corrected.



<aage@...> 
12/03/2003 06:40 PM
Please respond to
68300@yahoogroups.com


To
<68300@yahoogroups.com>
cc

Subject
[68300] 32 bit timer on TPU on 68376






Hello List,

I am trying to write a 32 bit timer routine in TPU microcode for the TPU 
in a 68376.

I seem to be having a timing problem when a match = $0000 (MRL = 1) and 
the micro instruction 

p:= ert;
ram p -> @LYD_TIMER_B.

For my application I need a high resolution (200nS) and measurements down 
to .1Hz.

Has anybody been able to implement a 32 bit timer on the TPU to measure 
frequency.

I would like to hear from somebody who any knowledge on the subject.

Aage Christoffersen
Lydatronic
Brisbane, QLD
Australia

aage@...

 

This message was sent through MyMail http://www.mymail.com.au




---------------------------------------------------
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/ 





[Non-text portions of this message have been removed]

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.