RE: TI-H: I2C status - now it's the TI-Bus!
[Prev][Next][Index][Thread]
RE: TI-H: I2C status - now it's the TI-Bus!
As soon as I dig out my Mouser catalog, I'll tell you. the deal is that the density is pathetic. 16 Kilobytes grand total (128K chips), so it isn't as good as the expanders that we're used to hearing about.
Christopher Kalos
raptorone@stuytech.com
Executive Director/Administrator
Virtual Technologies Developer's Group
----------
From: Jeff Rapp[SMTP:jrapp@geocities.com]
Sent: Monday, January 12, 1998 9:41 PM
To: ti-hardware@lists.ticalc.org
Subject: Re: TI-H: I2C status - now it's the TI-Bus!
Whats the part number on the I2C Chips your using? Thanks!
Jeff Rapp
jrapp@geocities.com
+--------------------------------------------
|http://qbplace.home.ml.org
|http://qble.home.ml.org
-----Original Message-----
From: Christopher Kalos <raptorone@stuytech.com>
To: 'ti-hardware@lists.ticalc.org' <ti-hardware@lists.ticalc.org>
Date: Monday, January 12, 1998 4:57 PM
Subject: RE: TI-H: I2C status - now it's the TI-Bus!
Thanks a million, man. I think that I can get it all to work now. The
actual communications layer was far beyond simple to figure out. as soon as
I can finalize the VAT editing, I think I can build the Expander.
As for the SPinterface, I'd rather do it for the link port and then make a
SPinterface version later, since that way everyone can access it.
Christopher Kalos
raptorone@stuytech.com
Executive Director/Administrator
Virtual Technologies Developer's Group
- Warning
- Could not process part with given Content-Type:
application/ms-tnef
Follow-Ups: