🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: sci.electronics.design
Article #2378

Re: Interfacing a PIC to SRAM - OE / W question

#2378
From: Troy Schultz
Date: Thu, 25 Jul 2002 12:58
45 lines
2952 bytes
Richard wrote:
> Al Borowski wrote:
> 
>>Just 2 quick questions. I'm hooking a 32kb X 8 chunk of SRAM up to a
>>pic. PIC I/O pins are running short, so is it OK to connect pin X
>>directly to the output enable Pin on the SRAM, and connect a NOT gate
>>from output enable to write enable? If so, I can us pin X as a read /
>>write pin on the SRAM.
> 
> 
> New turf for me too, but I've been studying Samsung's SRAM with similar
> questions.  I don't know if Samsung's SRAM works uniquely, but here's
> what I'm gathering:
> 
> Per their data sheet, /OE is Don't Care (or overridden by /CS) for all
> operations except /WE.  So it would seem that /OE could be hardwired,
> leaving /CS to control whether the chip is selected and /WE to toggle
> the read/write behavior.  Timing would be:
> 
> To read:
> * Set the address on the bus
> * Clear /WE and enable /CS
> * Read byte
> * Clear /CS
> 
> To write:
> * Set the address and data on the bus
> * Enable /WE and /CS
> * Clear /WE and /CS
> 
> If /CS and /WE pins are on the same port, it would seem possible to set
> them in one operation, followed by the next step without a wait cycle,
> depending on the CPU clock.
> 
> As I said, something I'm only just exploring myself, so commentary is
> welcome...
> 
> http://www.samsungusa.com/download/semiconductors/sram/k6t0808c1d.pdf

You may want to check out the http://www.ramtron.com/ product line. 
They offer I2C and SPI serial FRAM chips, which allow 1E10 or more 
read/write cycles, are fast and non-volatile as well.  They interface 
very nicely to a PIC or other micro.

- Troy
Technical Details
Message-ID: <3D3FF54B.3050102@canada.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!newsfeed.telusplanet.net!peer1-sjc1.usenetserver.com.MISMATCH!ps01-sjc1!news.webusenet.com!news03.bloor.is.net.cable.rogers.com!news01.bloor.is.net.cable.rogers.com.POSTED!not-for-mail
References: <27bf520c.0207231544.77e822f9@posting.google.com> <3D3E43B1.A2E96DDB@azglobal.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 112d1e,8593f5a81176e283
X-Google-Attributes: gid112d1e,public
X-Google-Thread: 103407,8593f5a81176e283
X-Google-Attributes: gid103407,public
X-Google-ArrivalTime: 2002-07-25 06:04:32 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!newsfeed.telusplanet.net!peer1-sjc1.usenetserver.com.MISMATCH!ps01-sjc1!news.webusenet.com!news03.bloor.is.net.cable.rogers.com!news01.bloor.is.net.cable.rogers.com.POSTED!not-for-mail
Message-ID: <3D3FF54B.3050102@canada.com>
From: Troy Schultz <tschultz@canada.com>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.17-acpi i686; en-US; m18) Gecko/20010110 Netscape6/6.5
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sci.electronics.design,aus.electronics
Subject: Re: Interfacing a PIC to SRAM - OE / W question
References: <27bf520c.0207231544.77e822f9@posting.google.com> <3D3E43B1.A2E96DDB@azglobal.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 46
Date: Thu, 25 Jul 2002 12:58:20 GMT
NNTP-Posting-Host: 24.156.160.101
X-Complaints-To: abuse@rogers.com
X-Trace: news01.bloor.is.net.cable.rogers.com 1027601900 24.156.160.101 (Thu, 25 Jul 2002 08:58:20 EDT)
NNTP-Posting-Date: Thu, 25 Jul 2002 08:58:20 EDT