delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/09/23/04:45:28

From: danspam2000 AT my-deja DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: fast access to parallel port
Date: Sat, 23 Sep 2000 08:08:39 GMT
Organization: Deja.com - Before you buy.
Lines: 27
Message-ID: <8qhoe0$6rt$1@nnrp1.deja.com>
NNTP-Posting-Host: 152.163.204.201
X-Article-Creation-Date: Fri Sep 22 22:24:42 2000 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; MSN 2.5; AOL 4.0; Windows 95)
X-Http-Proxy: 1.0 x73.deja.com:80 (Squid/1.1.22) for client 152.163.204.201
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I am working on a project that requires accessing
the parallel port as a means to generating a data
stream according to a pre defined standard. That
standard dictates that the length of any one bit
of data within the packet should be four micro
seconds long. This means that i have to write to
the parallel port and hold it high or low for
four microseconds at a time. This is not a
problem, as one cycle of the bus, running at 1.3
MHz gives me plenty of time. Also, the uclock
function in DJGPP is accurate to less than 1
microsecond, so i should be able to use that for
the timings. The problem is, that by the time
i've called uclock, written to the port and
called uclock again, even using register
variables takes about eighteen uclock ticks,
which is about three times longer than i can
allow. Does anyone know of a way around this?
Perhaps coding in assembler would speed the whole
process up enough to work? Any help or pointers
in the right direction would be appreciated.
Thanks,
Dan


Sent via Deja.com http://www.deja.com/
Before you buy.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019