Help! Baltik48 is Bad!

ZXNet echo conference «hardware.zx»

From Pawel Swiridenko To All 6 February 2006

Hello, All There is Baltik48 not working... The malfunction manifests itself as follows: When connecting to TV and supplying 5V to it A black square appears on the screen, with the button reset this opus is not eliminated, although reset to It's clear that the clock generator is also working... What else to check...

From Konstantin Sviridov To All 7 February 2006

Hello hero In my experience, at Baltic the most frequent problems arose due to firmware K155RE3 (less often K556RT4). The jumpers burned during programming in these chips were restored over time. If you have an oscilloscope, it makes sense make sure there are signals at the outputs of the K155PE3 microcircuits (M and D). By results think further.

From Oleg Golenkoff To All 7 February 2006

Hello, volton vol> What else to check... I had this kind of crap when the track under the socket on KAY burned out :( in I wouldn't have noticed... if this is what I think, check if all the signals are on percent (or from it) work... more precisely, are the tracks working properly: rolleyes: maybe somewhere Is the logic flawed? I don’t remember what exactly I had :( it was a long time ago... :sleep:

From Pawel Swiridenko To All 7 February 2006

Hello, volton I also have a suspicion on these pzu'shki (i.e. PE3), but so as there is no oscilloscope, the signals are obviously I can’t look, although it’s logical the probe shows how the norm (H, L) is all the legs of these RZUs are present both H and L signals...

From Alexander Zan To All 7 February 2006

Hello, volton 2 volts It's a crazy request, but maybe you won't be too lazy to see how the paths go under mikruhoy D18 and resistors next to it, look at your board and draw at least instructions on how they pass / with which D18 legs and resistors they are connected. Yes it’s not clear how exactly the paths go under D29, it’s especially interesting how Pin 9 is connected to pin 40 of the processor, a printed conductor or a pendant. The default combinations of jumpers on the meters are also interesting. This is all you need to restore the scarf in virtual form. (http://sblive.narod.ru/ZX-Spectrum/Baltik/Baltik.htm there is the correct diagram).

From Dmitry Demyanenko To All 7 February 2006

Hello, breeze First you need to make sure that the processor executes the firmware correctly, click on The buttons should click on the speaker, if it clicks then most likely the multiplexer Paper/Ink or the attribute register has crashed or something is preventing them from working, for example there is no frequency on the shift register But most likely sclerosis has grabbed a trivial ROM

From Dmitry Demyanenko To All 7 February 2006

Hello, volton vol> I also have a suspicion vol> to these pockets (i.e. PE3), Better check the soldering of the track in this steppe, otherwise there will be It’s problematic to find an empty PE and, moreover, flash it, although it will sting inside you these PE jumpers are stuck and re-burning will cure it (but again you need programmer for this matter)

From Pawel Swiridenko To All 9 February 2006

Hello, volton The culprit was 555TM8 (D41), according to the RL4/91 scheme!!! Screensaver "1990 COMPANION v1.2" :)

From Pawel Swiridenko To All 22 February 2006

Hello, volton Troubles with the keyboard?!!! Doesn't react at all! D35 is working, there is no suspicion on D29, D24! Maybe the decoder is worth checking (D34-ID4)...

From Niyaz Mukhametzyanov To All 23 February 2006

Hello, volton I have the same problem, what should I do? http://zx.pk.ru/showthread.php?t=2132&page=2&pp=10

From Pawel Swiridenko To All 23 February 2006

Hello, DR ZX By the way, at the working Baltic it was noticed that the reed switch type keyboard is not yours doesn't respond though when you forcefully short-circuit the keyboard signals, does it work?

From Alexander Zan To All 23 February 2006

Hello, volton vol> Troubles with the keyboard?!!! vol> Doesn't react at all! vol> D35 is working, there is no suspicion on D29, D24! vol> Maybe the decoder is worth checking (D34-ID4)... INT is making noise?

From Niyaz Mukhametzyanov To All 24 February 2006

Hello fan I'll try it now.