SIMM72 on scorpion
ZXNet echo conference «hardware.zx»
Hello, All
I decided to hang it on SIMM72 for my memory scorpion (after all, 4 rulers of 4 meters each
in each) and encountered the following: all the necessary legs are soldered as necessary, but the computer
does not want to accept it, although it is known that the SIMM is working.
Either my document is burned out, or what I heard about hyper-secret methods of protection
on the scorpion - the truth. Regarding the first one, please check with knowledgeable people:
┌─- code ───
1 GND 19 MA10 (GND) 50 D0
10 +5V 28 MA7 52 D1
12 MA0 30 +5V 54 D2
13 MA1 31 MA8 56 D3
14 MA2 32 MA9 (GND) 58 D4
15 MA3 39 GND 60 D5
16 MA4 42 CAS0/ 62 D6
17 MA5 45 RAS/ 64 D7
18 MA6 47 WE/ 72 GND
└── code ───
There was also +5V on the 59th leg, but because of this everything was short-circuited, which is why it crept in
I doubt that the document is blatantly lying to me.
Regarding the second - what if SIMM is organized as memory above 256K, i.e. native
Leave the memory, only CAS/share?
Hello jtn
jtn> Block unused races and races.
jtn> also, if the sim is >4mb then tricky addressing begins there, to be honest
jtn> I forgot what the salt is...
The effect is the same - at first there is a black screen, then something flashes on it and at the end
stops at the “mattress” (it’s different all the time).
jtn> p.s. Buffer ir22 I hope I didn’t forget? =)
And if I send the data not immediately to the bus, but to MD0..7 (for 14 legs of all RU7,
which are currently sleeping due to the lack of CAS on them) - a buffer is also needed
or will we get by?
PS: 5 volts on the 59th leg short to ground when the SIMM is inserted.
Hello, SAM style
* │Pin │ Name │Pin │ Name │Pin │ Name
│
* │ 1 │ GND │ 25 │ DB22 │ 49 │ DB8
│
* │ 2 │ DB0 │ 26 │ DB7 │ 50 │ DB24
│
* │ 3 │ DB16 │ 27 │ DB23 │ 51 │ DB9
│
* │ 4 │ DB1 │ 28 │ MA7 │ 52 │ DB25
│
* │ 5 │ DB17 │ 29 │ BS0 │ 53 │ DB10
│
* │ 6 │ DB2 │ 30 │ +5é │ 54 │ DB26
│
* │ 7 │ DB18 │ 31 │ MA8 │ 55 │ DB11
│
* │ 8 │ DB3 │ 32 │ MA9 │ 56 │ DB27
│
* │ 9 │ DB19 │ 33 │ RAS3 │ 57 │ DB12
│
* │ 10 │ +5é │ 34 │ RAS2 │ 58 │ DB28
│
* │ 11 │ CASp │ 35 │ DP2 │ 59 │ +5é
│
* │ 12 │ MA0 │ 36 │ DP0 │ 60 │ DB29
│
* │ 13 │ MA1 │ 37 │ DP1 │ 61 │ DB13
│
* │ 14 │ MA2 │ 38 │ DP3 │ 62 │ DB30
│
* │ 15 │ MA3 │ 39 │ GND │ 63 │ DB14
│
* │ 16 │ MA4 │ 40 │ CAS0 │ 64 │ DB31
│
* │ 17 │ MA5 │ 41 │ CAS2 │ 65 │ DB15
│
* │ 18 │ MA6 │ 42 │ CAS3 │ 66 │ BS2
│
* │ 19 │ Rsv. │ 43 │ CAS1 │ 67 │ PD0
│
* │ 20 │ DB4 │ 44 │ RAS0 │ 68 │ PD1
│
* │ 21 │ DB20 │ 45 │ RAS1 │ 69 │ PD2
│
* │ 22 │ DB5 │ 46 │ BS1 │ 70 │ PD3
│
* │ 23 │ DB21 │ 47 │ WE │ 71 │ BS3
│
* │ 24 │ DB6 │ 48 │ Rsv. │ 72 │ GND
│
Block unused casas and races.
also, if the sim is >4mb, then tricky addressing begins there, to be honest, I forgot in
what's the salt...
p.s. Buffer ir22 I hope I didn’t forget? =)
Hello jtn
jtn> I have both GND and 5V connected this way. Are you sure the simm is alive?
jtn> anyway, why all these troubles? 30 pin sims are easier to solder.
I tried 4 pieces, and all with the same result. By the way, it was the same on SIMM30
the most (not short-circuited, of course)...
Hello, SAM style
ITIC power, solder the buffer directly to the same IR22 that is the same on the board
ir22, the current legs are the opposite:
2 and 3, 4 and 5, etc... on the 1st leg GND, on the 11th /WE with ru7
Hello, SAM style
Well, if there is no buffer, who will write to the sim? SD doesn't care about him
started
SAM> PS: 5 volts on the 59th leg short to ground when the SIMM is inserted.
I have both GND and 5V connected this way. Are you sure the sim is alive?
In general, why all these troubles? It’s easier to solder 30 pin sims.
Hello Orionsoft
Ori> I only have 16MB Sims, what's the problem with addressing?
No ambushes, MA11 is also added there (on SIMM30 too).
HERE [http://www.radiomaster.ru/spravka/hwb/connector/index5.php] I found two
different simm72 pinouts. And how to determine which one based on external signs?
mine?
Hello, SAM style
SAM> No ambushes, MA11 is also added there (on SIMM30 too).
SAM> HERE [http://www.radiomaster.ru/spravka/hwb/connector/index5.php]
SAM> found two different simm72 pinouts. And according to external signs
SAM> determine which one is mine?
By pin N48. If it is not connected to anything on your module, then you have
module without ECC, if connected, then accordingly with ECC. Take the diagram accordingly
inclusions.
Hello, SAM style
in short, I don’t remember exactly, but it seems like if you put together the right circuit, then there’s no difference
The data is going there normally (D0 D1 D2 D3 ...) or mixed up (D0 D16 D1 D17 ...)
although what confuses me is that when in one type of SIM cards on some contacts
parity, and in the second on the same data.
search on aminet (www.aminet.net) for connecting FAST memory to the A500.
it seems like it was perpendicular to that diagram which SIM cards to poke (lvd will correct if
I'm wrong)
Hello, lvd
As a last resort, you can use the memory as 32-bit, and allocate the required 8 bits
handles multiplexers. really funny ^_~
Well, or if such troubles start, then look for normal memory ^_~
Hello, SAM style
SAM> As for the second - what if SIMM is organized as memory above 256K
SAM> that is, leave the native memory, only CAS / share?
I expanded my scorpion to 1 meter, though not with sims, but with hands (41256
some). He soldered himself with sandwiches on top, KAS gave it to ID4 and distributed it to 4
rulers. Well, there’s the management of this ID, that’s all. The only thing I had to
cheat with the RC chain, which makes the RAS so that it works stably in the turbo.
Since then I've been running tests - everything is OK.
Hello Sinus
Sin> in short, I don’t remember exactly, but it seems like if you put together the right circuit, then
Sin> it makes no difference whether the data goes there normally (D0 D1 D2 D3 ...) or
Sin> mixed up (D0 D16 D1 D17 ...)
Sin>
Sin> although what confuses me is that when in one type of SIM cards on some
Sin> contacts with parity, and in the second with the same data.
Sin>
Sin> search on aminet (www.aminet.net) for connecting FAST memory
Sin> to A500.
Sin> it seems like it was perpendicular to that diagram which SIM cards to poke (lvd
Sin> correct me if I'm wrong)
There are problems with sims. Which do not affect operation in 32-bit mode, but
are reflected in operation in 16 and 8 bit modes when data pins are parallelized.
Smoking here:
http://groups.google.com/group/fido7.ru.amiga/browse_thread/thread/5f268fa04e31
23f3/3db50277ba36fa35?lnk=st&q=zx.spectrum+vadik+akimoff+SIMM&rnum=5#3db50277ba
36fa35
I came across this when I soldered 2 meters of chipram to an Amiga600 - it needs to go there
16-bit drama, well, I stupidly parallelized D0-D15 with D16-D31. What happened - there
written. I had to trace the data to m/sx and resolder it.
Hello, serg.ne@
ser> Has anyone tried a separate megabyte sdram chip
ser> use instead of sims, etc. ???
No. SDRAM and DRAM are very different things (kuri datye shyty). Combine together
It just doesn't make sense.