Enterprise Forever
:UK => Hardware => Maintenance => Topic started by: Quickie on 2022.May.25. 10:55:34
-
Hi,
First of all let me thank you joining this community.
I am a happy owner of an Enterprise 128 which has been working bulletproof until now (fingers crossed).
As it didn't come with any software I decided to build a floppy controller based on the WD1772 + EXDOS 1.4 and give it a try with a Gotek device. It proved to work fine and for the first time I experienced what EP hardware was capable of :)
Having said this I decided to give this FDC to a colleague who has an EP64. He told me that on his EP64 the FDC didn't work as it caused crashes and green screen hanging when booting.
My colleague send me his EP64 and those are all the actions I tried to understand what was going on / fixing it:
- Updated with EXOS 2.4 eprom W27C512
- When the EP64 boots without the FDC it shows briefly the EXOS 2.4 screen and boots to the "ENTERPISE" screen
- When I performed an advanced memory test on EXOS 2.4, it reported random memory errors: BAD 0016Kb, BAD 0064Kb...
So I decided to change the 4164 RAM ICs on U10 and U17 for NOS memory of the same vendor and speed. No luck: the error messages kept appearing randomly on the same locations.
- I have made a 1536Kb RAM expansion. I installed it on the EP64 to check how it behaved, knowing in forehand that works fine. Well, with this computer it keeps giving me errors on different RAM memory locations with the Advanced test: BAD 0080Kb, BAD 0192Kb...
I gave a last try to check the 74F157 multiplexors. I removed them and tested on a MiniPro. They passed the test. Swapped them on the EP64 for new 74LS157 (just to test, I know the F series are faster) and behaved the same way, so I kept de F157s.
Finally I tried to start the EP64 with the FDC and the memory expansion and the computer got again stuck on the boot with some green screen, garbage on border (like a tape loading pattern) or some random "@" here and there.
I am expecting the worst (having a defective Dave custom IC), but before considering this worst case scenario I wanted some advice from more versed colleagues on the Enterprise.
Thanks
-
Try to add 4.7K Pull-up resistors (to +5V) on Data lines. Most easy install at U7.
[attachimg=1]
-
Hi Zozo,
Thanks a lot for your swift reply.
Ok, I will give it a try and made the pullups with some 4.7k resistors I do have.
Have you ever faced this problem in the past?
P.S.: I am going to give it a try with this hacky resistor pack:
(https://lh3.googleusercontent.com/pw/AM-JKLVgBGYJK3CvMJxAAzD1tAOujBgE8ZgdXxmh5uKFY81d-FGxyt6o8z9hiWYk4u-zdrD2JjhY58Wn9vBMMWpNqNmF7etEZE6tNLjWkPwTZuvTLN5gg-JHukdt0zSKs8uwcDms3RiGphJfJPatMedeJO0z=w800-h600-no?authuser=0)
Update: Ok, for the first time the EP64 is able to go further the EXOS 2.4 memory test with the FDC plugged in.
On the first try it quickly passed the test and marked all 1600Kb as good and afterwards I was presented with an EXOS 2.4 black screen with new memory tests. After a while an error appeared and the EXOS 2.4 text transformed to @POS 2.4:
(https://lh3.googleusercontent.com/pw/AM-JKLW2Vx0Y16u5zmoig3sljnbJ7sKTvpWb8hlgiTZpDs9rmjOEgMIaqMDoswMyXXkMcc07SkNqRL21Jfrq-HSqexeiam2jhFUiOfM8qU8OJBOOHVMGRtvOMUf2cK-2t0o33z3bu5DyL91wFE1dksXAQ0AA=w800-h600-no?authuser=0)
I tried to boot more times by resetting the EP64, no luck. On the next memory tests random memory adresses arise:
(https://lh3.googleusercontent.com/pw/AM-JKLUhbfbyiaNCDzo2ap9QfOpVQbSKhkLd8fPJpWjAAnBQm0kylP97Wad1qi6dv5lXwOF__pGtVgN1sK3g9JzEf4Othq0deVWcEhpdmUSMryEs3C8U3Ri72LwOVB9X1zq1R1gHRSmIhR2-KT-YciZgj2QG=w800-h600-no?authuser=0)
After that, the usual green screen with garbage :(
-
Last hint: try another Z80, preferably new CMOS version.
-
¡That was it! Even if there were no evidences from being manufactured in Singapore (@gflorez gave me the hint) I had previously checked the M1 line and was healthy...
However I have followed your advise and changed this Zilog Z80A for a Sharp Z80B...and for the first time ever the EP64 booted to IS-Basic, with the FDC controller connected and the memory expansion properly recognized!
(https://lh3.googleusercontent.com/pw/AM-JKLVnu0lPZA-3COxo13Nh-5qiSeAu686ovs4NQdD-tZi8qyTTHVssYIIv3ZMsRZZMZuVMWSQIOvxPynuRbTaRdYnnrugItGNVW8byCnGJQNobl6TZVakJ32YZdud9ThH5Z8DOsFGVXBpKAAr1ZzEaYTOs=w800-h600-no?authuser=0)
Thanks a lot!!
-
Can you make photos of the faulty Z80?
-
Sure,
Here is the culprit Zilog Z80:
(https://lh3.googleusercontent.com/pw/AM-JKLUU4snLQmNdDBoPHCMcGjKPfrci4nf7OwMGC9DPxiJWnVRe-f_A9bgkrWqDJNyLFyYRsPevTvWsyYwzLW39x9hlwyngLTrWcjR5-0KFVgarHzOPeOb7QF_YZGmb_R8rBAy0lOp46NIKFlG6pPJVt9qM=w1024-h768-no?authuser=0)
-
I have many similars in bad CPU bin...
[attach=2]
[attach=1]
-
The stickers to the left should be removed ;)
-
The stickers to the left should be removed ;)
:smt043
-
Funny!
I have one with the Q.C. sticker at the right.... The one from my first EP. It was problematic with a Microteam EXDOS card connected, hangs and random errors on Zozo's Ram test.
[attach=1]
The bottom one is also made in Philippines, removed from an Amstrad CPC. The chance was to put a finger over it, as it gets hot very fast and hangs.
The problem with these faulty Z80s is that they are not completely broken.
-
Yeah, indeed.
They seem to present an erratic behavior on the data bus, or at least the unit I had to deal with. On a first thought I did check the M1 signal (being aware of problems with Zilog Z80s present on some Sinclair Spectrums), but this showed a healthy behavior.
-
Sinclair saving money with defective components... but thanks to him a lot of people started with computers.