|
Hello Joey. No, should be 2 volts because it's minimum for ls02 logic high level. Check the power board.
|
Thank you for your inputs.
I only have time to do a quick check on U45. ?Both pin 2 and pin 8 have 1.21v. Is this the?normal voltage for these pins? ?
I'll check on the other points suggested when I get back home. ?
Thanks again for your help.
On Thursday, February 11, 2021, 10:52 PM, mjkirk12 via groups.io <mjkirk12@...> wrote: Joey,? Given that UART and Timer failed in diagnostic tests,? I would check POWER_OK signal as Vladimir suggests. POWER_OK can block IRQ (interrupt requests) from UART and Timer as shown in schematic (found on K1000.net) 
|
Joey,? Given that UART and Timer failed in diagnostic tests,? I would check POWER_OK signal as Vladimir suggests. POWER_OK can block IRQ (interrupt requests) from UART and Timer as shown in schematic (found on K1000.net) 
|
Vladimir is correct - all clock signals should be square wave shaped (high harmonic content) for clean clock transitions.
If they are sine shaped (less harmonics) that can cause issues for digital logic.
An oscilloscope and/or scope probes with insufficient bandwidth (< 20 MHz)? can also filter out these harmonics and show a sine shape clock as well.
A good (>100 MHz BW) scope with matching 100 MHz BW probes are needed to see the true clock shape.
|
I attach a bad signal photo) 
|
Ok, so if you have oscilloscope check frequency form at pin 15 of the cpu. It should be square wave without stretching or shaping. If it's sine, you have problems with clock generator. At my last repairing I observe sine wave at that pin, U38 was bad and I replaced it.
|
Also, check for /Power OK high U045, pins 2 and 8. That line goes to CPU pins 25 and 24, interupt levels.
|
PAL chip used in k1000 have lock bit, maded after factory programming. It prevent to read rom or write. I try to read this chip with my gal/pal programer but unfortunetly, hex is empty.
|
PAL is programmable array logic - they are blank (like a ROM) and need to be programmed.
You would need the original JEDEC programming bitmap file (Like a ROM hex/bin file) and a PAL programmer.
Not sure if that is possible, unless someone read out a known good device.
PAL devices are no longer made - finding a blank one may not be easy.
I would probe the chip select signals to the timer and UART - maybe they are not responding to the CPU?
|
The OS chips are new and the?PAL chip?is much easier to replace than the CPU. ?I guess I'll try to replace that first.? Thanks for the insights.
On Thursday, February 11, 2021, 12:10 AM, mjkirk12 via groups.io <mjkirk12@...> wrote: K1000 schematic shows 68000 CPU is clocked at 10 MHz (20 MHz oscillator divided by 2).? ?This is 100 nanosecond clock cycle.
If your scope has 20 MHz bandwidth or greater, it may be enough to trigger on DTACK events.
If CPU is accessing non-existent memory ("off the rails"), then DTACK signal will never pulse low.
This would imply the software (code) in the ROM chips is bad,? PAL chip is bad or CPU could be bad.
|
K1000 schematic shows 68000 CPU is clocked at 10 MHz (20 MHz oscillator divided by 2).? ?This is 100 nanosecond clock cycle.
If your scope has 20 MHz bandwidth or greater, it may be enough to trigger on DTACK events.
If CPU is accessing non-existent memory ("off the rails"), then DTACK signal will never pulse low.
This would imply the software (code) in the ROM chips is bad,? PAL chip is bad or CPU could be bad.
|
Thanks for the reply. The K1000?guide does say an oscilloscope is needed to perform some of the troubleshooting. Unfortunately, ?I only have a cheap portable?scope with ?very limited functions.??
On Wednesday, February 10, 2021, 11:28 PM, mjkirk12 via groups.io <mjkirk12@...> wrote: DTACK is Motorola 68000 CPU signal? for Data Transfer Acknowledge.? ? It is very fast signal? - a few tens of nanoseconds in duration.
To see it toggle, you would need an oscilloscope or logic analyzer set to edge trigger on the event.
Some info on the topic:?https://en.wikipedia.org/wiki/DTACK_Grounded
|
More info on bus timing:?? Timing diagram below shows a bus read cycle on a 68000 CPU - at bottom is DTACK signal. Taken from:?? Four clock cycles (fastest speed) shows DTACK active low (0 volts) for 1.5 cycles.? ? With a 20 MHz CPU clock, DTACK low is 75 nanoseconds,? with 10 MHz clock DTACK low is 150 nanoseconds. An oscilloscope with 50 MHz bandwidth or higher would be needed to see these events. For slower speed memory or peripheral devices (e.g. UART for MIDI), the bus cycle is extended (more clocks,? wait states) until the DTACK is asserted - indicating bus cycle is complete. 
|
DTACK is Motorola 68000 CPU signal? for Data Transfer Acknowledge.? ? It is very fast signal? - a few tens of nanoseconds in duration.
To see it toggle, you would need an oscilloscope or logic analyzer set to edge trigger on the event.
Some info on the topic:?https://en.wikipedia.org/wiki/DTACK_Grounded
|
Dear all,
I am going thru Chapter 5 Basic Troubleshooting of the K1000 and under letter I., it says check for DTack toggling on U017, pin 10.??It further states:??
"If this line never goes low, the unit is hung in a non-existent memory access. DTack is generated by PAL (U08, pin 16)."
I'd appreciate it if someone with a working K1000 can check the voltage on U017, pin 10.??Does the voltage change from high to low and back???Basically I want to know what is the behavior of the voltage on this pin in a working K1000.??
Thanks in advance.??
On Tuesday, February 9, 2021, 6:19 PM, Joey Mastrili via groups.io <jmastrili@...> wrote:
Thank you for all?the helpful comments.
I have removed, cleaned, and reseated all the socketed?IC's a few times with the same results. I also see no visible breaks in the PCB?traces.?
Thanks for the offer to send me the?OS?files.?Unfortunately, I?have no IC programmer and cannot burn new chips. ?I'll check the traces around the ACIA chips as suggested.
On Tuesday, February 9, 2021, 2:06 AM, Vladimir <shtirlitzz11@...> wrote: Hello Joey. Could you do the dump of the new OS chips for comparing it. Or I could make the dumps of two OS chips and send you binnary) surely if you have the programer. UART and timer signals come from HD63 ACIA chips, did you check traces around those?
|
Thank you for all?the helpful comments.
I have removed, cleaned, and reseated all the socketed?IC's a few times with the same results. I also see no visible breaks in the PCB?traces.?
Thanks for the offer to send me the?OS?files.?Unfortunately, I?have no IC programmer and cannot burn new chips. ?I'll check the traces around the ACIA chips as suggested.
On Tuesday, February 9, 2021, 2:06 AM, Vladimir <shtirlitzz11@...> wrote: Hello Joey. Could you do the dump of the new OS chips for comparing it. Or I could make the dumps of two OS chips and send you binnary) surely if you have the programer. UART and timer signals come from HD63 ACIA chips, did you check traces around those?
|
Hello Joey. Could you do the dump of the new OS chips for comparing it. Or I could make the dumps of two OS chips and send you binnary) surely if you have the programer. UART and timer signals come from HD63 ACIA chips, did you check traces around those?
|
Did you remove (gently) and re-install the all socketed IC chips?? ? Pin oxidation can cause poor connections preventing boot.
Also visually inspect soldered IC and other parts for cracks in solder - reheat and reflow any suspicious ones.
Check for any PCB trace cracks that would give intermittent operation - if you 'nicked' a copper PCB trace with a tool that could break the connection - would need to add wire to fix.
I repaired a non-booting Alesis QS7 mainboard just by removing, cleaning with isopropyl alcohol and re-inserting the ROM chip into the socket.
A non-booting Yamaha CS1X board had one bad (nicked) PCB trace on a data bus line - adding a wire jumper brought it back to life.?
|
Give the output relay a tap to loosen it up a bit, then try.
Sent from my HAL 9000 in transit to Jupiter
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Joey Mastrili via groups.io Sent: Sunday, February 07, 2021 9:14 PM To: [email protected]Subject: Re: [K1000-K1200] 1000PX - not booting Let's take a few steps back: 1. The K1000 powers up but does not boot. I see blocks on the lcd upon power up and that was it. 2. I checked voltages and they were ok. I also resoldered the connectors since the power supply was already out. 3. The synth still didn't boot despite having correct voltages so I assumed there was a problem with the OS. 4. With new OS chips installed, the synth still did not boot but at least went into diagnostics mode. 5. During diagnostics, all tests pass except for the timer and UART. Every time these tests are run, the synth freezes, that is, I hear the relay immediately click and then the lcd goes blank. 6. I replaced the electrolytic capacitors in the power supply. All voltages read as they were before the new capacitors were installed. 7. Now the synth is back to square one-- just solid boxes in the lcd, and it wont even go into diagnostics mode anymore. If the new OS chips are dead, it's possible that whatever killed the original OS chips also killed the new ones. If the OS chips are not dead, something else is preventing the synth from completing the boot process. My guess is it's something common to the timer and UART circuits. Everyone is welcome to chime in. ? Joey <> On Monday, February 8, 2021, 6:43 AM, Vladimir <shtirlitzz11@...> wrote: [Edited Message Follows] Looks like OS chips. I had one with eprom chips problem. When I tested U32V2.1L checksum was failed, it's write at the label of the chip.
|
Let's take a few steps back:
1.?The K1000 powers up but does not boot. ?I see blocks on the lcd upon power up and that was it. ?
2.?I checked voltages?and they?were?ok. I also resoldered?the connectors since the power supply was already out.
3.?The synth still didn't boot despite having correct voltages?so I assumed there was a problem with the OS.?
4.?With new OS chips installed, the synth?still?did not?boot?but?at least went into diagnostics mode. ?
5.?During diagnostics, all tests?pass except for the timer and UART. Every time these tests are run, the synth freezes, that is,?I hear the relay immediately?click and then?the lcd goes blank.?
6. I?replaced?the electrolytic capacitors in the?power supply. ?All voltages read as they were before the new capacitors were installed.?
7.?Now the synth is back to square one-- just?solid boxes in the lcd, and it wont even go into diagnostics mode anymore.?
If the new OS chips are dead, it's possible that?whatever?killed the original OS chips also killed the new ones.?
If the OS chips are not dead, ?something else is preventing the synth from completing the boot process. ?My guess is it's something common to the timer and UART circuits.?
Everyone is welcome to chime in. ?
Joey?
On Monday, February 8, 2021, 6:43 AM, Vladimir <shtirlitzz11@...> wrote: [Edited Message Follows]
Looks like OS chips. I had one with eprom chips problem. When I tested U32V2.1L checksum was failed, it's write at the label of the chip.
|
