RE: AlphaStation 200 NVRAM Problem

I have been setting up a MAX232CPE to try to get serial output from the serial diagnostic port. Trouble is I am not sure which signal is the data signal. The one that is marked SROMCDAT in the technical manual does not appear to do anything when I look at it with the scope. Anyone know which is

RE: AlphaStation 200 NVRAM Problem

> > On 03 May 2016 at 18:20 "Maciej W. Rozycki" wrote: > > > On Mon, 2 May 2016, Robert Jarratt wrote: > > > I decided to attempt the construction of an adapter. But it is the > > connectors which always bite me because I don't know what all the types >

RE: AlphaStation 200 NVRAM Problem

> > On 02 May 2016 at 22:56 "Maciej W. Rozycki" wrote: > > > On Mon, 2 May 2016, Robert Jarratt wrote: > > > > Other than that maybe it's NVRAM after all. But what could it be then > > that > > > did not show up in your testing? Could it be that the

RE: AlphaStation 200 NVRAM Problem

On Mon, 2 May 2016, Robert Jarratt wrote: > > Other than that maybe it's NVRAM after all. But what could it be then > that > > did not show up in your testing? Could it be that the settings and > > environment variables stored there are protected with a checksum (or a > > signature) which

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Peter > Coghlan > Sent: 02 May 2016 10:42 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > > > > &

RE: AlphaStation 200 NVRAM Problem

> I suppose I should find or construct a diagnostic port adapter. I suppose I am > slightly put off by the effort needed to make one as I don't have the > components needed to hand. I may just have to bite this bullet. > I decided to attempt the construction of an adapter. But it is the

RE: AlphaStation 200 NVRAM Problem

> > > > One possibility I have in mind is it's something peculiar about DRAM. > > As you may have been aware DROM code isn't run directly, it's loaded by > > SROM into DRAM. If it fails a specific bit pattern at a specific location > > some reason, then you might see symptoms like these. So

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Maciej > W. Rozycki > Sent: 02 May 2016 08:14 > To: Robert Jarratt <robert.jarr...@ntlworld.com> > Cc: 'General Discussion: On-Topic Posts' <cct...@classiccmp.org> &

RE: AlphaStation 200 NVRAM Problem

On Sun, 1 May 2016, Robert Jarratt wrote: > Any ideas what it might be? I can't help with the chip, except that the manual states it's a 64-Kbyte part. But something has struck me: "When the SROM code has completed its tasks, it normally loads the DROM code and turns control over to it.

RE: AlphaStation 200 NVRAM Problem

I want to read the DROM chip with my programmer, but I can't ID the chip. Does anyone know what kind it is? It is in a PLCC32 package and the label on it is: 369E7 AYOMA 49/95 I am sure at least some of that is DEC stuff, unrelated to the type of chip. However, none of those parts of the

RE: AlphaStation 200 NVRAM Problem

in touch. Thanks Rob Sent from my Windows 10 phone From: Maciej W. Rozycki Sent: 30 April 2016 18:36 To: General Discussion: On-Topic Posts Subject: RE: AlphaStation 200 NVRAM Problem On Tue, 26 Apr 2016, Robert Jarratt wrote: > It turns out that I only needed to flip the bit in the bank 8 con

RE: AlphaStation 200 NVRAM Problem

On Tue, 26 Apr 2016, Robert Jarratt wrote: > It turns out that I only needed to flip the bit in the bank 8 config > register and I can now access the flashbus. I can write to the LEDs, it > turns out that writing a 0 turns the LED on, rather than off, which is why I > thought it hadn't worked.

RE: AlphaStation 200 NVRAM Problem

Windows 10 phone From: Maciej W. Rozycki Sent: 27 April 2016 14:47 To: General Discussion: On-Topic Posts Subject: RE: AlphaStation 200 NVRAM Problem On Tue, 26 Apr 2016, Robert Jarratt wrote: > I examined the bank 8 configuration register contents using the console. It > contained 0x0136,

RE: AlphaStation 200 NVRAM Problem

On Wed, 27 Apr 2016, Maciej W. Rozycki wrote: > I've been looking for a... screw, DEC P/N 12-32249-01. Of course my > DEC 3000 can live without a screw, however some are still around I > suppose, perhaps in unusable remains heading for the scrapper, so why > not save one and have my box fully

RE: AlphaStation 200 NVRAM Problem

On Wed, 27 Apr 2016, Maciej W. Rozycki wrote: > Does he get any mechanical parts as well by any chance? I'll ask, Mighty Maciej. I have a couple of other vendors, too (partners with my $job). I'll forward your message to them. They are guys with service companies who fix the Alphas and IBM

RE: AlphaStation 200 NVRAM Problem

On Tue, 26 Apr 2016, Swift Griggs wrote: > Also, I still deal with a lot of business clients running alphas and > Tru64. There is a guy in Thornton, Colorado who I get quite a few dead, > spare, and orphaned alphas from. It's an electronics supply type business. > I'll see him this weekend and

RE: AlphaStation 200 NVRAM Problem

On Tue, 26 Apr 2016, Robert Jarratt wrote: > I examined the bank 8 configuration register contents using the console. It > contained 0x0136, which suggests the cache is not valid. The base address > register contained 0x4000. Both correct: * 0x4000 << (23 - 5) => 0x1 * 0x0136:

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Dave > Wade > Sent: 26 April 2016 23:18 > To: 'General Discussion: On-Topic and Off-Topic Posts' > <cctalk@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem &g

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Swift > Griggs > Sent: 26 April 2016 23:07 > To: General Discussion: On-Topic and Off-Topic Posts > <cctalk@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Probl

RE: AlphaStation 200 NVRAM Problem

> I can now do test code for the NVRAM, I will start with repeated reads to see if > I get different values on different occasions. Then I will save it and write > patterns etc. It may be a checksum that is failing of course. Or the DROM itself, > which I can't verify until I get the PLCC adapter

RE: AlphaStation 200 NVRAM Problem

On Tue, 26 Apr 2016, Robert Jarratt wrote: > It may be a checksum that is failing of course. Or the DROM itself, > which I can't verify until I get the PLCC adapter for my PROM programmer > and someone else to read their DROM. Could you use a pull or replacement mobo ? I notice there are some

RE: AlphaStation 200 NVRAM Problem

> I just got some very interesting results. > > I examined the bank 8 configuration register contents using the console. It > contained 0x0136, which suggests the cache is not valid. The base address > register contained 0x4000. > > So I booted VMS and modified my code to read the same

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Maciej > W. Rozycki > Sent: 26 April 2016 21:02 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > > On Tu

RE: AlphaStation 200 NVRAM Problem

On Tue, 26 Apr 2016, Robert Jarratt wrote: > > One possibility is SRM unmaps them when it takes over from SROM, for > > safety maybe -- so as not to let one corrupt flash by accident easily > (BTW, I do > > recommend write-protecting flash with its jumper for these experiments -- > > with DROM

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Maciej W. > Rozycki > Sent: 26 April 2016 00:42 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > > On Mo

RE: AlphaStation 200 NVRAM Problem

On Mon, 25 Apr 2016, Robert Jarratt wrote: > To help me work out why my program isn't working I went back to the console > command to try to write to the flashbus index register, I used the following > command: > > deposit -l pmem:1 9400 > > This should set up the flashbus

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Maciej > W. Rozycki > Sent: 25 April 2016 14:29 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > >

RE: AlphaStation 200 NVRAM Problem

On Sun, 24 Apr 2016, Maciej W. Rozycki wrote: > > The thing > > I am struggling with at the moment is getting sys$crmpsc_pfn_64 to work so I > > can use C to test the NVRAM. I seem to have a problem with the service > > writing back the address and length, but I don't yet know why. > > That's

RE: AlphaStation 200 NVRAM Problem

> > > From what I read the 3000 is a slightly earlier generation, not sure how close > it will be. Sounds like a good idea to get it going anyway. The thing I am > struggling with at the moment is getting sys$crmpsc_pfn_64 to work so I can > use C to test the NVRAM. I seem to have a problem with

RE: AlphaStation 200 NVRAM Problem

On Sun, 24 Apr 2016, Robert Jarratt wrote: > > Reminds me to revive my 3000/700, once I get the mechanical issues from > > mishandling in shipping sorted out. I hope it hasn't rotted from disuse > > -- it was alright, booted OSF/1 even, when I last powered it on ~10 years > ago. > > I should

RE: AlphaStation 200 NVRAM Problem

> This thread has been making me wonder about my two AS200’s, I’ve been > meaning to revive the one with 768MB of RAM for VMS. Nice! Mine only has 160MB. Still it works well, apart from the NVRAM problem. Regards Rob > I really should also > check out my XP1000/667 as well, though I last

Re: AlphaStation 200 NVRAM Problem

On 24/04/16 15:46, Robert Jarratt wrote: The thing I am struggling with at the moment is getting sys$crmpsc_pfn_64 to work so I can use C to test the NVRAM. I seem to have a problem with the service writing back the address and length, but I don't yet know why. Regards Rob If you post a

Re: AlphaStation 200 NVRAM Problem

> On Apr 24, 2016, at 6:33 AM, Maciej W. Rozycki wrote: > > On Sat, 23 Apr 2016, Peter Coghlan wrote: > >> (Congratulations on the progress made so far. Maybe there is hope yet >> for my two DEC 3000/600 machines which have similar symptoms.) > > Reminds me to revive my

RE: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Peter Coghlan wrote: > (Congratulations on the progress made so far. Maybe there is hope yet > for my two DEC 3000/600 machines which have similar symptoms.) Reminds me to revive my 3000/700, once I get the mechanical issues from mishandling in shipping sorted out. I

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Maciej > W. Rozycki > Sent: 24 April 2016 14:34 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > > On S

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Peter > Coghlan > Sent: 23 April 2016 21:44 > To: General Discussion: On-Topic Posts <cct...@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem > > > &g

RE: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Robert Jarratt wrote: > > or > > from the OS (can't help how to do this from VMS; under Linux you could > > mmap(2) /dev/mem at the right address and then poke at it with a little > > program doing the right dance to get the flashbus access protocol right), > to > > see if it

RE: AlphaStation 200 NVRAM Problem

> > First of all you might be able to run some SRAM diagnostics yourself, > either from the console (if it has a tool for this; at worst you could > poke at it manually with deposit/examine commands, but the complicated > flashbus access protocol will make it a tedious task unless there is a

RE: AlphaStation 200 NVRAM Problem

> First of all you might be able to run some SRAM diagnostics yourself, either > from the console (if it has a tool for this; at worst you could poke at it > manually with deposit/examine commands, but the complicated flashbus > access protocol will make it a tedious task unless there is a way

RE: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Robert Jarratt wrote: > > Second: it may also be that DROM itself is faulty, a bit may have flipped > for > > example; NB this is UV EPROM, so things happen. Maybe someone can > > share a known-good image. > > > > When I put the DROM back the failure returned. So it is

RE: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Robert Jarratt wrote: > Well! I took out the DROM and switched it on again. The machine bleeped at > me, but then it gave me a console and I was able to boot VMS! I'm glad that it worked, this will certainly make further diagnostics easier, and you have a usable machine

RE: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Robert Jarratt wrote: > > But from the discussion referred I gather DROM outputs its diagnostics to > > this port too and you might be able to learn what exactly about NVRAM it > > complains. > > > Ah OK, so you think the DROM console also outputs to the SROM diagnostics?

RE: AlphaStation 200 NVRAM Problem

> But from the discussion referred I gather DROM outputs its diagnostics to > this port too and you might be able to learn what exactly about NVRAM it > complains. Also you might be able to correct configuration, e.g. by poking at > NVRAM or elsewhere appropriately; notice that the manual also

RE: AlphaStation 200 NVRAM Problem

> > > > I don't think the SROM diagnostics are going to help much because the > > failure is in the DROM sequence, which comes after the SROM. > > But from the discussion referred I gather DROM outputs its diagnostics to > this port too and you might be able to learn what exactly about NVRAM

RE: AlphaStation 200 NVRAM Problem

> Information on using that is however scarce and scattered, you can find > some here to start: and then the > pinout for the serial diagnostic port is included here: > 199909/cd1/alpha/pcdsatia.pdf> > (the

Re: AlphaStation 200 NVRAM Problem

On Sat, 23 Apr 2016, Pete Turnbull wrote: > Then the CMOS RAM - which is what the battery is for - has lost its > memory. The CMOS could be an individual chip but it's more likely to be > part of something else, like a Motorola real time clock IC They are socketed on GS series machines, IIRC.

RE: AlphaStation 200 NVRAM Problem

On Fri, 22 Apr 2016, Robert Jarratt wrote: > I am wondering if I have a chance of reviving this system or if it is beyond > repair (by me)? I can't get anything out of the console port, and I don't > know if I should expect to be able to get output from there or not. If I > know that I should

Re: AlphaStation 200 NVRAM Problem

On 23/04/2016 00:35, et...@757.org wrote: In my case there is just a CR2032, and no Dallas module. I will try replacing the CR2032 again. Regards Rob The NVRAM failure warning probably isn't the physical ram, it's the lack of contents. Yep, used to be a problem even in the mid-1990s with

Re: AlphaStation 200 NVRAM Problem

On 23/04/2016 00:37, Robert Jarratt wrote: Just tried replacing the CR2032 again, but I get the same error :-( Then the CMOS RAM - which is what the battery is for - has lost its memory. The CMOS could be an individual chip but it's more likely to be part of something else, like a Motorola

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Robert > Jarratt > Sent: 23 April 2016 00:17 > To: 'General Discussion: On-Topic and Off-Topic Posts' > <cctalk@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Probl

RE: AlphaStation 200 NVRAM Problem

In my case there is just a CR2032, and no Dallas module. I will try replacing the CR2032 again. Regards Rob The NVRAM failure warning probably isn't the physical ram, it's the lack of contents. -- Ethan O'Toole

RE: AlphaStation 200 NVRAM Problem

> > Someone mentioned there is a battery. It could be held by that, or a module > from ST Microelectronics or Dallas Semiconductor. The latter two tend to be > plastic packages that are ~28 pins or so and taller than normal chips. The > Dallas and ST modules have RAM/real time clock and a

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Glen Slick > Sent: 22 April 2016 23:26 > To: General Discussion: On-Topic and Off-Topic Posts > <cctalk@classiccmp.org> > Subject: RE: AlphaStation 200 NVRAM Problem >

RE: AlphaStation 200 NVRAM Problem

I posted a while back about this problem. I am wondering if I have a chance of reviving this system or if it is beyond repair (by me)? I can't get anything out of the console port, and I don't know if I should expect to be able to get output from there or not. If I know that I should expect

RE: AlphaStation 200 NVRAM Problem

On Apr 22, 2016 3:10 PM, "Robert Jarratt" wrote: > > I posted a while back about this problem. > > I am wondering if I have a chance of reviving this system or if it is beyond > repair (by me)? I can't get anything out of the console port, and I don't > know if I

RE: AlphaStation 200 NVRAM Problem

> Just wondering if I should expect anything on the serial port or on the > monitor if my AlphaStation has an NVRAM self test failure. Anyone know? > > I still need to identify the NVRAM chip(s), although replacing them means > learning how to desolder and resolder surface mount stuff, which I

RE: AlphaStation 200 NVRAM Problem

> > I don't know if it applies to the AlphaStation 200 but I have a PWS > > 500a > which > > defaults back to the AlphaBios firmware whenever the battery dies. > > After replacing the battery, I have to connect a keyboard and monitor > > and go through the AlphaBios menus to reset it to SRM.

RE: AlphaStation 200 NVRAM Problem

> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Peter > Coghlan > Sent: 06 January 2016 21:39 > To: General Discussion: On-Topic and Off-Topic Posts > <cctalk@classiccmp.org> > Subject: Re: AlphaStation 200 NVRAM Problem

Re: AlphaStation 200 NVRAM Problem

> > I tried starting up my AlphaStation 200 today. All I get is some beeps and > an LED diagnostic code that suggests the NVRAM test failed. I swapped the > battery, as the old one was dead, but it still refused to work. I have tried > connecting to the serial port and got nothing (although I