🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: sci.electronics.design
Article #2383

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

#2383
From: Richard
Date: Wed, 24 Jul 2002 06:04
35 lines
2412 bytes
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
Technical Details
Message-ID: <3D3E43B1.A2E96DDB@azglobal.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!west.cox.net!cox.net!p01!news2.west.cox.net.POSTED!53ab2750!not-for-mail
References: <27bf520c.0207231544.77e822f9@posting.google.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-23 23:04:26 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!west.cox.net!cox.net!p01!news2.west.cox.net.POSTED!53ab2750!not-for-mail
Message-ID: <3D3E43B1.A2E96DDB@azglobal.com>
From: Richard <rh86@azglobal.com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: 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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 35
Date: Wed, 24 Jul 2002 06:04:24 GMT
NNTP-Posting-Host: 68.2.65.245
X-Complaints-To: abuse@cox.net
X-Trace: news2.west.cox.net 1027490664 68.2.65.245 (Wed, 24 Jul 2002 02:04:24 EDT)
NNTP-Posting-Date: Wed, 24 Jul 2002 02:04:24 EDT
Organization: Cox Communications