6502.org Forum  Projects  Code  Documents  Tools  Forum
It is currently Sun Nov 10, 2024 9:40 pm

All times are UTC




Post new topic Reply to topic  [ 4 posts ] 
Author Message
PostPosted: Mon May 27, 2024 5:58 pm 
Offline

Joined: Wed Nov 16, 2011 9:39 am
Posts: 68
How well does SRAM cope with floating address pins when it's enabled (/CE, CE2) but neither outputting (/OE) nor storing (/WE)?

I am designing a read/write-round-robin-algorithm for SRAM in a VGA circuit and was thinking about how strict I need to be about always having some kind of data on the address bus.


Top
 Profile  
Reply with quote  
PostPosted: Mon May 27, 2024 6:09 pm 
Offline
User avatar

Joined: Fri Aug 30, 2002 1:09 am
Posts: 8539
Location: Southern California
If CMOS inputs are left floating, power-supply current may increase a lot.  They go to a totem pole arrangement of MOS transistors, and the one and the top should be totally off while the one at the bottom is on, and vice-versa.  If the input is not connected, they could both be at least partially on.  However, if there's nothing driving the line in either direction and all loads are CMOS, the capacitance will hold the last driven voltage a surprisingly long time, not just nanoseconds, or even microseconds, but milliseconds.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?


Top
 Profile  
Reply with quote  
PostPosted: Mon May 27, 2024 6:31 pm 
Offline

Joined: Wed Nov 16, 2011 9:39 am
Posts: 68
I forgot to mention, I am not talking about the 6502 bus, as it's a completely separate design that I want to interface using address and data-latches, in a first incarnation connected to the 6522 in some way, then if successful, later on integrated in the SBC (with the latches connected using memory mapped I/O).

What I have in mind is to have something like a 74AHC138 cycle through the lowest 3 bits of a column value, and one of the '138 outputs will trigger a write to RAM from the above mentioned latches, and 2-4 of the other will do various reads from memory for a simple state machine to form the next 8 pixels to be displayed. Kind of. Then there might be a few outputs from the '138 left unconnected where nothing is driving the address bus (I don't think I need to do 7 memory accesses per 8 pixels and I am thinking of leaving some "padding" around the write to avoid bus contention).

Sounds like, while not ideal, it will be kind of OK to leave the address bus floating for a few ~80ns periods (a 12.5 MHz pixel clock).

(FWIW the RAM in question is an Alliance Memory AS7C164A-15PCN and I am using all CMOS ICs, some HC, some AHC)


Top
 Profile  
Reply with quote  
PostPosted: Mon May 27, 2024 6:55 pm 
Offline

Joined: Wed Nov 16, 2011 9:39 am
Posts: 68
Actually when I think about it, it might be better to let the "write-latch" drive the address bus for half of those 8 steps (say using bit 2 of the x-coordinate as latch output enable instead of an output from the '138) and then put the /WE trigger from the '138 somewhere in the middle of those 4 steps to be sure memory corruption is not an issue. That also leaves less steps to fill and reduces floating bus time that could possibly cause some ruckus. Sorry for the sudden rubberducking :D


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 23 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: