[Coco] CoCo 3 512k SRAM Upgrade (Renamed Thread)

[Bob Devries]

The manual of the coco 3 is available online at: 
ftp://maltedmedia.com/coco/MANUALS0/TANDY/HARDWARE/COCO3/

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: <coco at yourdvd.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Monday, April 23, 2007 4:43 PM
Subject: Re: [Coco] CoCo 3 512k SRAM Upgrade (Renamed Thread)


> We can't use a static ram to create a one-chip solution because the
> address bus has to be demultiplexed for use with static rams. The info
> provided by James D. indicates that what I thought would work yesterday
> morning probably won't. I made some assumptions that look like they
> might've been wrong. -r
> (is there a pdf of the coco 3 tech ref manual to be found on the net?) -
> r
>
>> -------- Original Message --------
>> Subject: Re: [Coco] CoCo 3 512k SRAM Upgrade (Renamed Thread)
>> From: Mike Pepe <lamune at doki-doki.net>
>> Date: Sun, April 22, 2007 11:30 pm
>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>>
>> jdaggett at gate.net wrote: > I would recommend that you not try and do a
>> 512K expansion with just a single 512K byte > SRAM. Instead I would
>> use four 128K SRAM instead. The WE0 and WE1 signals are > controlled
>> by the MPU's A0 address line. What is then on the Z-Buss is A1 through
>> A18. The > Row address is A1 through A9 and the Col Address is A10
>> through A18. This allows a byte > wide write control. You are correct
>> that the mempry map of the Coco3 is two banks of 256K > bytes. This
>> allows 512 rows for refresh purposes. > > The GIME chip during VDG
>> reads is a two byte read. During the MPU cycle the second byte > may
>> be ignored. MPU and VDG periods are determined by the state of the E
>> Clock. > > > james > James, What do you think about using something
>> like this: http://www.bsi.com.tw/product/BS616LV8016.pdf Seems like it
>> would be a cool one-chip solution, though the package may be hard for
>> DIY upgrades. -Mike > > On 22 Apr 2007 at 7:24, coco at yourdvd.net
>> wrote: > >> To Sylvain Rousseau: >> >> I've renamed this thread. I
>> have been looking into your schematic. >> Now, from a quick research
>> of the G.I.M.E. I find that a write cycle >> is as follows: The
>> G.I.M.E. writes data by BYTE via the we0* or we1* >> 256k bank
>> selects. Whilst a read cycle is as follows: The G.I.M.E. >> reads data
>> by WORD, 8 bits via cas low followed by latching the next >> 8-bits on
>> cas rise and reading it from the latch. (I am using ''WORD'' >> to
>> represent 16-bits, but it's had so many meanings over the years...) >>
>> >> This will help later on in the day as I work on this. >> >> Anyway,
>> your schematic indicates that you are using negative-edge >> triggered
>> latches to demultiplex the z-bus. If this is the case, the >>
>> inversion of the ras and cas prior to entering the latches should be
>> >> removed. However, I need to find the CoCo 3 timing diagrams, if I
>> had >> those, I could solve this in a few hours. Are they online?
>> Perhaps a >> copy of the CoCo 3 Tech Ref Manual and/or service manual
>> - if anyone >> knows of a readily available download of these, I could
>> solve this in >> a couple of hours. I work best from truth tables and
>> timing diagrams >> rather than schematics. >> >> Theoretically, during
>> a read cycle, both we0 and we1 should be high, >> but if there is the
>> slightest chance that this isn't the case, ANDing >> the two signals
>> cannot be used to generate the *we signal. But I need >> to go search
>> for the timing diagrams. >> >> Any info anyone might have would be
>> appreciated, because CoCo 3 RAM >> access is actually amazing that it
>> even works considering one byte of >> the word is latched then fed to
>> the gime and finally to the cpu - >> propagation delay from hades, I
>> would think... >> >> I'll keep digging - rob >> >>> -------- Original
>> Message -------- >>> Subject: Re: [Coco] Re : Re : FREE Services For
>> Members Of The >>> CoCoList at Malted Media From: coco at yourdvd.net
>> Date: Sun, April 22, >>> 2007 5:33 am To: CoCoList for Color Computer
>> Enthusiasts >>>  >>> >>> I see what I believe may be some potential
>> problems with the >>> schematic but before I go and make a fool of
>> myself, I am going to >>> go fetch the data sheet for the sram and
>> examine the gime memory >>> timings. I'll get back to you in a few
>> hours. -rob > -------- >>> Original Message -------- >>>> Subject:
>> [Coco] Re : Re : FREE Services For Members Of The >>>> CoCoList >>> at
>> > Malted Media > From: Sylvain Rousseau > Date: Sat, April 21, >>>
>> 2007 4:22 pm > To: CoCoList for Color Computer Enthusiasts > > Yes,
>> >>> Mr. Merchberger host it for we at this address: > >>>
>> http://zmerch.30below.com/coco/coco3sram.pdf Thank you again Mr. > >>>
>> Merchberger. Sylvain ----- Message initial ---- De : Mark Marlette ?
>> >>>> : coco at maltedmedia.com Envoy? le : vendredi 20 avril 2007, 13 h
>> 16 >>> min >>>> 11 s Objet : Re: [Coco] Re : FREE Services For Members
>> Of The >>> CoCoList > at Malted Media IIRC there were some level
>> problems in >>> your circuit. I > think you posted a .jpg of it. I
>> looked at it >>> quickly. Don't totally > remember. Working other
>> designs and >>> sometimes they all run together. > Heck maybe it was
>> my levels that >>> were off.... :) Mark Quoting > coco at yourdvd.net: >
>> What 512k static >>> ram are you using? the first to > hit the scene
>> were > semistatic >>> requiring something like an 8ms? > refresh or so
>> (these were > >>> hitachi). The current ones are fully > static. The
>> 4464 used in the >>> 128k > machine use a bidirectional i/o > line
>> like the static rams. >>> The 41256 > has a seperate din and dout >
>> line but these are shorted >>> together in the > coco 3 memory
>> circuit. > did you account for the >>> 256k bank switch? > > if all
>> else fails you > can make one of these: >>>
>> ftp://ftp.maltedmedia.com/coco/TUTORIALS/How_To_Upgrade_To_512k_With
>> >>> out_A_Commercial_Memory_Board.zip >>>>> D?couvrez ce qui fait
>> jaser les gens ! Visitez les groupes de > >>> l'heure sur Yahoo!
>> Qu?bec Groupes. http://cf.groups.yahoo.com/ -- >>> Coco >>>> mailing
>> list Coco at maltedmedia.com > >>>
>> http://five.pairlist.net/mailman/listinfo/coco-- Coco mailing >>> list
>> Coco at maltedmedia.com >>>
>> http://five.pairlist.net/mailman/listinfo/coco >> >> -- >> Coco
>> mailing list >> Coco at maltedmedia.com >>
>> http://five.pairlist.net/mailman/listinfo/coco >> >> >> -- >> No virus
>> found in this incoming message. >> Checked by AVG Free Edition. >>
>> Version: 7.5.463 / Virus Database: 269.5.7/771 - Release Date: >>
>> 4/21/2007 11:56 AM >> > > > > -- > Coco mailing list >
>> Coco at maltedmedia.com > http://five.pairlist.net/mailman/listinfo/coco
>> -- Coco mailing list Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco