On Sat, Jul 13, 2019 at 06:56:24PM +0200, Gerrit Heitsch wrote: > On 7/12/19 10:28 PM, smf wrote: > >On 11/07/2019 16:14, Gerrit Heitsch wrote: > >>SRAM doesn't care what you do with the address lines during a read, > > > >It doesn't? AFAIK the memory is still organised in rows and columns, a > >read still opens a line and connects it to something that reads the line. > > Yes, but reading doesn't change the state of a cell, you just read the > state of the flipflop representing the cell. So, if VIC changes the > adress lines mid cycle (which is what happens with the VSP bug), the > SRAM doesn't care. It will supply VIC with the data the address lines > select. If those change then different data will be supplied. VIC might > read garbage, but the contents of the SRAM won't change. If two addresses are (for a moment) selected at the same time, it depends on the SRAM implementation. For the 2114 the timing diagram shows you can change the address whenever you want; but anything that has rows and columns will need to make sure rows do not interfere, usually via an #OE or some other timing/sequencing stuff, which makes sure at most one row in the array is selected at any time. SegherReceived on 2020-05-29 22:22:44
Archive generated by hypermail 2.3.0.