Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site okstate.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!okstate!kermit From: kermit@okstate.UUCP Newsgroups: net.micro.ti Subject: Re: PIO ADDRESS... Message-ID: <26500003@okstate.UUCP> Date: Sat, 8-Dec-84 23:47:00 EST Article-I.D.: okstate.26500003 Posted: Sat Dec 8 23:47:00 1984 Date-Received: Wed, 12-Dec-84 03:22:58 EST References: <893@vax135.UUCP> Lines: 17 Nf-ID: #R:vax135:-89300:okstate:26500003:000:819 Nf-From: okstate!kermit Dec 8 22:47:00 1984 [munch...munch...munch...] Make it easy on yourself and use DSRLNK. If you must use direct port addressing than you will have to experiment to find the right 8 bits to write to. Try turning your printer or whatever paralel device you are using and load the TI-BUG (or you favorite monitor that gives access to the the CRU bits), and write to consecutive bytes until you get a reaction from the device. Although this is primative at best, it will probably solve your problem. By the way, if you have not heard of The BUGOUT Machine Language Monitor which I wrote for the 99/4A, you should look into getting one. It gives you window editing features (By the bit in the case of CRU memory) that would allow you to watch the status of the RS232 card as you tested the device. Gregg Wonderly