Просмотр полной версии : Help fixing Vector-06c
Hello,
First off my apologies, I'm in the USA and I only speak English.
A long time ago I bought a BK-0010 and a Vector-06c off of Ebay. The BK-0010 works fine but the Vector has lots of problems. I've already replaced the CPU and two flipflop chips so at least it boots, but now I'm stuck.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2667.jpg
As you can see the colors are very washed out. I followed svofski's modifications to get a good sync signal, but when I tried to wire resistors R16-R29 directly to the inverter I only get a white screen. So I reverted it.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2669.jpg
When I turn on the computer I hear a buzzing noise, the "rus" LED is on, and I see this checker pattern on the screen. When I hit "vvod" and "blk" the screen goes blank, the LED turns off, and the buzzing stops. I also hear a "click" noise.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2670.jpg
I hooked the cassette port up to my PC and played back a wav file. I can hear it on the Vector-06c's speaker but nothing else happens.
I'm not sure what to check next. I think the computer is running but it won't load a program and I can't get a good picture out of it. Any help would be greatly appreciated. Thank you!
Hello,
First off my apologies, I'm in the USA and I only speak English.
A long time ago I bought a BK-0010 and a Vector-06c off of Ebay. The BK-0010 works fine but the Vector has lots of problems. I've already replaced the CPU and two flipflop chips so at least it boots, but now I'm stuck.
...
Hello.
I am writing through an online translator.
The checkered picture when turned on is a good sign.
If the boot grid does not appear, the memory may be defective.
Can I find the serial number and release date of this computer?
A relay seems to be installed near the speaker, this is an exceptional rarity.
Hello.
I am writing through an online translator.
The checkered picture when turned on is a good sign.
If the boot grid does not appear, the memory may be defective.
Can I find the serial number and release date of this computer?
A relay seems to be installed near the speaker, this is an exceptional rarity.
Yes, the sticker on the back says "00706 12 89". I noticed this motherboard is slightly different than the pictures I saw. For instance r30 is missing. Also the keyboard has real switches.
Yes, the sticker on the back says "00706 12 89". ...
Thank.
Please look carefully at the tracks, from the underside, around the board mounting holes. They are often squashed and short-circuited.
The checkered picture when turned on is a good sign.
If the boot grid does not appear, the memory may be defective.
But the pattern in the original poster's screenshot does not look like a boot grid at all.
Here's a proper "boot grid" (barring the text at the top that could be different depending on the bootloader ROM version and the filled blocks that only appear when the bootloader is loading byte blocks from the cassette tape):
https://lh3.googleusercontent.com/proxy/DnvUghFGIt1okm0r6a_oHtm9le67s5Yvpw9QIakemhAvKyVAfs q0VwgLsy-p3YUCgkfH3534U_3yUFrDCBTytOoc
Even putting the issue with washed colors aside, the first picture does not look like the bootloader has properly started. And the second pic rather looks like there's an issue with h/vsync (which is actually quite possible since Vector-06c has known issues with its video output not being 100% conformant to the standards. Old Soviet TVs did tolerate this, but it's not necessarily true with CRT monitors like the NEC you have)
I did find a dead bug in the case but I removed it. There's some rust on a few chips, but other than that everything looks okay. I've been removing the chips and testing them, one by one. So far I've found three bad ones. I think I might just have to keep replacing chips until I find all the bad ones. The circuit board has "556-04-89-3" written on it.
I did find a dead bug in the case but I removed it. There's some rust on a few chips, but other than that everything looks okay. I've been removing the chips and testing them, one by one. So far I've found three bad ones. I think I might just have to keep replacing chips until I find all the bad ones. The circuit board has "556-04-89-3" written on it.
It could be not only the chips. I'd suggest you tested that the motherboard gets clean power (all the required voltages and polarities), and if there are polar capacitors on the motherboard, I would replace them since some Soviet capacitors were known to loose their capacity over time.
If that does not help, you'd need an oscilloscope / logic analyzer to figure out if what's going on (e.g. if the CPU reads data from ROM and not RAM on cold boot - this is controlled by a flip-flop wired to the three keyboard buttons in the upper right)
Perhaps I need to elaborate on the last sentence a little bit: Vector-06c uses a primitive ROM shadowing technique. On cold boot / after hard reset the motherboard gets initialized in a way that the CPU reads data from the on-board ROM but writes data to the RAM. And there's a flip-flop that can be switched either manually by simultaneously pressing the two rightmost buttons in the upper right, or (in later revisions of the motherboard and the bootloader) programmatically by the bootloader firmware). Once the switch did happen, the bootloader ROM is no longer accessible unless the next hard reset.
I do have an oscilloscope and a logic analyzer. Originally the flip flop triggering the ROM chip select was stuck between levels so I replaced it. I haven't checked the capacitors but the power levels are all good.
Strangely, sometimes when I turn it on I get a different behavior. The screen rolls no matter how I adjust the brightness and contrast. When I press the reset buttons, the checkerboard turns purple and then is replaced by vertical lines. The buzzing does not stop and the "rus" LED does not turn off. This happens randomly, I can't find any pattern. I think my next step should be to replace all the capacitors.
I don't know how to upload a video here but here are two screenshots of what happens. https://hosting.photobucket.com/images/i/cyb2600/IMG_2673.PNG https://hosting.photobucket.com/images/i/cyb2600/IMG_2674.PNG
The screen rolls no matter how I adjust the brightness and contrast.
This, as well as horizontal distortion I can see in your pics speaks about your NEC not picking horizontal / vertical sync properly.
Does the video signal look right if you hook up an oscilloscope to the video output?
- - - Добавлено - - -
Also, take a look at this wiring diagram, especially capacitor marked as C33 on the right:
https://i.imgur.com/d1XlPX6.jpg
Even if the original capacitor is healthy, it's capacity is insufficient and it distorts the video signal.
So you might want to hook an additional capacitor in parallel as suggested in the wiring diagram.
I'll look at the sync with the oscilloscope when it happens again. 80% of the time I get a stable picture, where the screen turns black when I hit the reset buttons and the buzzer stops. 20% of the time I get the rolling picture and it doesn't respond to the resets.
This is what the composite sync looks like when I have a stable picture.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2676.jpg
Edit: Yes, I added a 220uf electrolytic capacitor across C33. I made every modification in that circuit diagram except for wiring the resistors directly to the inverter. When I did that I only get a solid white screen.
- - - Добавлено - - -
Perhaps I need to elaborate on the last sentence a little bit: Vector-06c uses a primitive ROM shadowing technique. On cold boot / after hard reset the motherboard gets initialized in a way that the CPU reads data from the on-board ROM but writes data to the RAM. And there's a flip-flop that can be switched either manually by simultaneously pressing the two rightmost buttons in the upper right, or (in later revisions of the motherboard and the bootloader) programmatically by the bootloader firmware). Once the switch did happen, the bootloader ROM is no longer accessible unless the next hard reset.
When I boot the computer up, all 4 chip selects on the ROM are high. When I press the reset buttons, I see continuous data on the two inverted chip select inputs. Should they go high again after the boot ROM is copied to RAM?
it doesn't respond to the resets.
That could be a clue, actually.
Does the CPU gets a proper RST signal? What happens on the address bus right after that? Do the address lines of the bootloader ROM chip get the same signals that are on the address bus?
Another place to look is whether video memory refresh works properly (as far as I recall it uses its own EEPROM to form all the right signals)
- - - Добавлено - - -
Should they go high again after the boot ROM is copied to RAM?
The ROM is not copied to RAM (apologies for probably misleading you with an inappropriate use of the word "shadowing").
It's rather like chip select (inverted, I assume) goes low for ROM and high for RAM when the CPU is reading data and vice versa when CPU is writing data.
The reset line is low, it goes high for a second when I press the reset buttons. I see activity on the data and address busses but I haven't yet verified it's the same on the CPU as the ROM. I haven't looked at all at the video memory circuit.
Do you know what causes the "rus" light to turn off and for the buzzing to stop? Is that evidence the ROM is executing?
When I boot the computer up, all 4 chip selects on the ROM are high.
If those chip select inputs are inverted, that's suspicious. As it probably means that the reset schematics is faulty.
Still, if the motherboard serial number ends in something like 89-03, it could also be that you're dealing with an old revision of the motherboad, and I vaguely recall old revisions did require a manual hard reset after power on.
So - after pressing and releasing the two rightmost buttons in the upper right the chip select for the ROM chip should go low, and the CPU should start reading instructions from ROM address 0000
- - - Добавлено - - -
Do you know what causes the "rus" light to turn off and for the buzzing to stop? Is that evidence the ROM is executing?
Actually, yes - it could mean signs of life. At least if we are to believe this guy's post: https://zx-pk.ru/threads/29199-reanimatsiya-vektora.html?p=965695&viewfull=1#post965695
The serial number does end in 89-3. The computer does nothing but buzz until the reset buttons are pressed. The ROM seems to have 4 chip selects, two active high and two active low. The two "active high" ones are tied to +5 so they're always high. The two "active low" are high until the reset buttons are pressed, then there's data continuously on both. It seems like the CPU is executing code from the ROM. I think the problem might be with the RAM or the video circuitry.
If you can hook up the Vector's "tape in" to your soundcard "line out", try opening this web page:
http://sensi.org/scalar/ware/555/
then click on the ellipsis next to "test.zip" - you'll see
testtp [pack].rom 997▶
testtp.rom 1024▶
Power up the Vector, then press and release "VVOD" and "BLK" simultaneously to make sure a proper hard reset and entering the bootloader mode.
Then click on the Play button symbol next to "testtp.rom"
When the sound stops playing, the "rus" led should start flashing.
If that's the case, press and release "BLK+SBR" simultaneously - this will deactivate the bootloader and start executing the manufacturer self-test.
I powered on the Vector and see the checkerboard and hear buzzing and "rus" light is on.
I pressed "VVOD" and "BLK" simultaneously. The screen goes black, the "rus" light turns off, the buzzing stops, and I hear the relay go click.
I play the "testtp.rom" and hear the tones on the Vector06-c speaker.
When it's done playing the LED doesn't flash and the screen stays black.
I powered on the Vector and see the checkerboard and hear buzzing and "rus" light is on.
I pressed "VVOD" and "BLK" simultaneously. The screen goes black, the "rus" light turns off, the buzzing stops, and I hear the relay go click.
I play the "testtp.rom" and hear the tones on the Vector06-c speaker.
When it's done playing the LED doesn't flash and the screen stays black.
The checkerboard, when turned on, indicates that the image is formed correctly. This is typical of Vector, which does not autostart on power-up.
But until the download grid appears, yellow on a blue background, the program from the tape recorder will not load.
There is a suspicion that the bootloader checks the memory, then detects an error and loops on this test.
- - - Добавлено - - -
I believe one should test memory.
Since the bootloader cannot be used, there are two options: either change the bootloader microcircuit to another, into which to write the memory test; or connect an external bootloader microcircuit to the long "ВУ" connector, which is much more difficult.
Does anybody have the pinout for the р565ру6 RAM? I'm seeing some very strange signals on pins 14 and 13. I think everyone is right about the capacitors being bad.
Does anybody have the pinout for the р565ру6 RAM? I'm seeing some very strange signals on pins 14 and 13. I think everyone is right about the capacitors being bad.
http://www.asvcorp.ru/darch/electronics/565ru6/index.html
CodeMaster
12.08.2020, 19:14
Does anybody have the pinout for the р565ру6 RAM?
Datasheet (https://eandc.ru/pdf/mikroskhema/kr565ru6.pdf)
Take a good quality photo of the underside of the board.
Thank you. This is what I see on pin 15 of the RAMs. I don't think that's right!
https://hosting.photobucket.com/images/i/cyb2600/IMG_2679.jpg
- - - Добавлено - - -
Take a good quality photo of the underside of the board.
The blue wires are my additions. I also scorched the board a bit when I removed a chip with a heat gun.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2681_(2).jpg?width=450&height=278&fit=bounds&crop=fill
https://s8.hostingkartinok.com/uploads/images/2020/08/67c5f9fa3c8d187a246573654693fdb7.jpg
Marked in yellow where you need to clean.
Marked in red, I can't see.
I cleaned all three areas up with rubbing alcohol until they were shiny, and I verified none of the traces were broken from corrosion. Unfortunately it didn't make any difference.
There is a suspicion that the bootloader checks the memory, then detects an error and loops on this test
Are you sure that the bootloader has a built-in RAM test? Never heard of this before...
Still, the bootloader uses the upper RAM for its stack and variables (0xe000-0xffff). Coincidentally, this is also the upper bank of the video frame buffer - the only one used by the bootloader in order to reserve all RAM below 0xe000 for loading programs (hence the pixel "garbage" in the upper right corner of the bootloader grid screen)
So if the corresponding memory chips are corrupted or do not receive proper signals, neither the grid will be visible nor the bootloader will be able to operate normally.
Also, it's strange that you can hear signal coming to the tape input from the speaker. I cannot recall this being the case, as the tape input should go directly to the comparator circuitry.
I would double-check if you are not mistakenly using tape out instead of tape in.
Could be a quirk of the early motherboard revision you have, though.
Thank you. This is what I see on pin 15 of the RAMs. I don't think that's right!
In fact this could be a regeneration cycle (pin 15 is CAS, inverted)
Can you monitor pin 4 (RAS, inverted) along with pin 15?
Pin 4 should be low and pin 15 should be high to trigger regeneration.
But anyways the low frequency "envelope" on your screenshot from the oscilloscope does not look good at all.
Maybe I connected to tape out instead of tape in? I used pin 1, with pin 2 for ground.
This computer came with a schematic and a couple tapes. The schematic looks identical to the ones on the vector06c.fdd5-25.net site except the page numbers are different at the bottom.
- - - Добавлено - - -
In fact this could be a regeneration cycle (pin 15 is CAS, inverted)
Can you monitor pin 4 (RAS, inverted) along with pin 15?
Pin 4 should be low and pin 15 should be high to trigger regeneration.
But anyways the low frequency "envelope" on your screenshot from the oscilloscope does not look good at all.
https://hosting.photobucket.com/images/i/cyb2600/IMG_2683.jpg
Channel 6 is pin 4, channel 7 is pin 15, so it seems like it's regenerating.
Maybe I connected to tape out instead of tape in? I used pin 1, with pin 2 for ground.
I have taken a look at the schematics, and tape in is pin 3 of the DIN socket marked as O_O on the backside. Pin 1 is tape out that goes right into the base of the speaker amplifier transistor so this explains why you hear the sound from the speaker.
Отправлено с моего SM-T720 через Tapatalk
Ah, that makes sense. I tried again plugged into pin 3 and it was the same behavior unfortunately.
Perhaps this diagram from a working machine will be of some help:
https://s8.hostingkartinok.com/uploads/images/2017/10/111f5b7d10d251adcd6ea3ae4d54e9da.jpg
KTSerg is a much better expert in these timings. Serg, if it's difficult for you to explain in English, write in Russian and I will happily translate.
Thank you! I think I see in the schematic where to grab those signals, I'll test.
- - - Добавлено - - -
Are you sure that the bootloader has a built-in RAM test? Never heard of this before...
Still, the bootloader uses the upper RAM for its stack and variables (0xe000-0xffff). Coincidentally, this is also the upper bank of the video frame buffer - the only one used by the bootloader in order to reserve all RAM below 0xe000 for loading programs (hence the pixel "garbage" in the upper right corner of the bootloader grid screen)
I attached 3 data probes to a13-a15 and one to wr to see if the computer was trying to access the upper RAM (0xe000-0xffff).
https://hosting.photobucket.com/images/i/cyb2600/InkedIMG_2689_LI.jpg
At around +1000ms I hit the wwod and blk keys. It looks does two bursts of reads and writes to the 0xe000-0xffff region at around +1400 and +1700. Then a14 goes low and will stay low indefinitely.
At around +2700ms I hit blk and sbr, and it looks like it's trying to read that upper block again.
I also have these manuals and tapes. They appear to be BASIC and Assembly manuals.https://hosting.photobucket.com/images/i/cyb2600/IMG_2690.jpg
Are you sure that the bootloader has a built-in RAM test? Never heard of this before...
Это самое начало штатного заводского загрузчика.
...
LXI SP,0DCF0H
LXI D,55AAH
M000EH: PUSH D
POP H
MOV A,L
CMA
CMP H
JNZ M000EH
...
- - - Добавлено - - -
I cleaned all three areas up with rubbing alcohol until they were shiny, and I verified none of the traces were broken from corrosion. Unfortunately it didn't make any difference.
I didn't talk about corrosion. The conductors run next to the mounting holes. They are often crushed, and neighboring ones are connected to each other.
Ah, I misunderstood. I checked the pins, none of them were bent over or touching traces.
I checked the pins, none of them were bent over or touching traces.
What KTSerg rather means is that due to excessive mechanical load on the motherboard's mounting holes, the traces themselves could have been deformed up to a point where they short-circuit somewhere near a hole. So I'd suggest you carefully inspected traces near each of the mounting holes and made sure they have not been deformed / damaged.
I see. No, I don't see any deformed traces. I looked the board over on both sides, the only unusual thing I saw was a cut trace on the top side. It looks like it was deliberately cut, though, not an accident.
I disassembled the Vector BIOS that came with a Vector emulator. It looks like after it initializes some ports, the next thing it does is write zero's to all the RAM. I hooked up the logic analyzer to CAS, RAS, and WE as well as 5 of the data lines. It looks like it is indeed writing 0's to the RAM, and the RAS and CAS timing looks good.
https://lh3.googleusercontent.com/O_Ep5dwd611Rzix2xLCd7LU5v0d2Kxajvk0y6JBvKWNKk_aQ3A f65zHtw1Ard5sPsDZOY9DV2Kb0e4eV27MHK1323kSOYsmoCoCj NvpIzyXey55hWeOWFywCaPzKUVAB3ZdcUFWZenbsmblouxJWvp utRRyCs7JCffHK15QLtbqmJp0zfKgLc-qqAP8_b1Vxs2xIbejfNkJi5Ll66QqPGaTx1rYrPDXABsSrwJTH GMnV31h1kM_kzkHqtxg_jTq6xiqnWH35g7yLd--w20_KzZt8FZGzZMxzAR8nXqcBayAQIQ7QL9qsmxrnxiFuMvkIN YhWqRLYIPjwcmLyqE2N6eBmz44gCufZiQeLSw9nYdp4TzE5E0Q YJWNa_rfW6q75mgGdTkl4Nr9QiDlAmT4Q4ROW_U03nZBKiyCgg _pPiMxrgGKQ9cdASV_hq2BdKqvt0Gc4jaYPyBgBoytjnErkNDs cNzk-sM-SyGbgXKBILarkrrc62I5egvEDMLFdjWJnRIuYI9dM87I5w674l dS29vyg2ew8ozh-rW4u4yHZL6D5lNfvftHEcUtIBQRZcqnQ7PMuhTXXYxhdyEzg4O Ke9WQXDzv_DUEguQ5m5Sow5JHANMn3FXZE9Dp8thcD0lkOsZRh MePlizKVDN4ej0h5wLzk8RYGvaKX5PYAymDebEzSwEqEptEQaQ WBL4UPmQ=w1920-h458-no?authuser=0
After it's finished zeroing out the RAM, it pushes 55 and AA on the stack. Then it pops them back off, does a 1's complement of 55 (which is AA) and compares the two. If they don't match it loops and tries again. I guess this is a memory test. If the memory is bad, at least where the stack pointer is pointing, it never proceeds.
..
After it's finished zeroing out the RAM, it pushes 55 and AA on the stack. Then it pops them back off, does a 1's complement of 55 (which is AA) and compares the two. If they don't match it loops and tries again. I guess this is a memory test. If the memory is bad, at least where the stack pointer is pointing, it never proceeds.
This is the memory test I already mentioned.
Only usually it goes before clearing memory, and not after.
Do you have enough knowledge and experience to replace the ROM chip containing the bootloader?
Do you have the ability to write a new ROM chip with the desired program?
To begin with, you can write a memory test to the new ROM.
Instructions for replacing the ROM. But it may not match a little, since it is for replacing the К556РТ5 microcircuit, and you most likely have К556ТР7.
http://www.sensi.org/scalar/ware/543/
There is another way.
You can try swapping the memory chips.
To do this, you need to cut two wires. The sections are marked in yellow.
And solder the two wires as marked in red.
At the same time, the microcircuits will swap and if the replacement ones are in good order, then the computer can work.
And then you will need to run a memory test, find and replace defective microcircuits.
https://s8.hostingkartinok.com/uploads/images/2020/08/9d84e67066a41f9d0d8bfdc86deb5365.jpg
With the logic analyzer I could see it writing 01010101 and 10101010 to bank 3 of the RAM, but it was reading back 01011101 10101010 - bit 5 is stuck high, that RAM chip must be bad. At least this confirms the read/write circuit works otherwise. I'm going to try to replace the fault RAM with a 4164 with A7 tied to ground.
Given that this is the third bad chip I've found in this computer I'm expecting there to be more problems. I have a Chinese USB EPROM programmer but I don't think it can burn this type of PROM. I have a very old Stag PP39 programmer that might be able to do it. I'd have to find a blank chip, too. Otherwise I'm sure some sort of adapter could be made.
With the logic analyzer I could see it writing 01010101 and 10101010 to bank 3 of the RAM, but it was reading back 01011101 10101010 - bit 5 is stuck high, that RAM chip must be bad. ...
According to the D67 scheme?
... I have a Chinese USB EPROM programmer but I don't think it can burn this type of PROM. I have a very old Stag PP39 programmer that might be able to do it. I'd have to find a blank chip, too. Otherwise I'm sure some sort of adapter could be made.
If we are talking about replacing and programming ROM, then any eeprom will do. I bet w27c512.
Success! It now boots, but the colors seem inverted. The background is yellow and the lines are blue. I'll try connecting the resistors directly to the inverters as in the schematic, but last time I tried that I only got a white screen. I'll also try to load that test program, other RAM may possibly be bad. Thanks everyone for your help.
... I'll also try to load that test program, other RAM may possibly be bad. ...
Test RAM.
http://sensi.org/scalar/ware/649/
It looks like it found two more bad RAMs. D78 and D64?
https://hosting.photobucket.com/images/i/cyb2600/IMG_2726.jpg
Same result with second utility
https://hosting.photobucket.com/images/i/cyb2600/IMG_2727.jpg
EDIT: I replaced the two bad RAMs, it's booting fine now. I loaded a few games and they seem to work other than the colors being wrong.
EDIT 2: I rewired the resistors to the inverter as per the instructions and now I get a perfect picture.
...
EDIT: I replaced the two bad RAMs, it's booting fine now. I loaded a few games and they seem to work ...
EDIT 2: I rewired the resistors to the inverter as per the instructions and now I get a perfect picture.
Congratulations on your successful computer recovery.
Color test.
http://www.sensi.org/scalar/ware/770/
For what purpose did you buy this particular computer?
D9 - 556PT5 or 556PT7 ?
If 556PT6, then replacing the bootloader chip will significantly expand the ability to download programs (FDD, HDD, external RAM, external ROM, LAN, ... - you need special controllers).
D9 is a PT5, the 512 byte ROM. Are there instructions on how to upgrade this to a larger ROM? Since it uses two Chip Select lines I'm not sure if I could directly replace it with a 27256? I'd definitely like to use the "Combodevice" so I can load software faster and try out some Demos.
I used to collect old computers, and I bought this one and a BK-0010 off of E-Bay 10-15 years ago. I also got a "Nu Pogodi" Game & Watch clone and an Elektronika "Video 01" Pong clone. I don't recall how much I paid for them but they were pretty inexpensive back then. I wish I had bought an MK-85 back then when things were cheap. The BK-0010 worked fine but the Vector-06c didn't. Since I've been stuck at home during this quarantine I decided to finally fix it. In total 5 chips were bad - two flip flops and three DRAMs.
D9 is a PT5, the 512 byte ROM. Are there instructions on how to upgrade this to a larger ROM? Since it uses two Chip Select lines I'm not sure if I could directly replace it with a 27256? I'd definitely like to use the "Combodevice" so I can load software faster and try out some Demos.
...
I already gave a link to the instructions for replacing the ROM.
You can change it to any ROM, I wrote that now 27512 is installed on my computer, and previously I installed 290011. I installed a socket in the computer and change the microcircuit when necessary. I installed jumpers on the ROM, and several different programs were written into it at once.
cyb2600, write what kind of ROM you have, here they will tell you how to connect it.
I have blank 27256 and 27512, I can use either.
I have blank 27256 and 27512, I can use either.
There are a lot of options for improvement.
ROM pin mapping.
https://s8.hostingkartinok.com/uploads/images/2020/08/f0118a9ca469818bb72a6ab5d7c3d99c.png
I suggest installing a 28-pin socket on the board to install the ROM.
Pins: 1, 2, 20, 21, 23, 24, 27, 28 - bend the leads, do not solder them into the board, isolate them from the board contacts.
Connect pins 26 and 28 (A13 always "1").
Connect old pin 21 - new pin 20.
Connect new pin 21 and D1 pin 17 (A10).
Connect new pin 24 and D1 pin 18 (A9).
Connect pins 23, 2, 27 to jumpers to select a program (for 8 program of 2K).
Рrograms will need to be written to the ROM from the addresses:
A14="0":
2000h
2800h
3000h
3800h
A14="1":
6000h
6800h
7000h
7800h
It is not necessary to connect free address pins (23, 2, 27) with jumpers, you can connect them to the power supply or the case, and write only one program to the ROM.
The corner at the first contact of the socket will need to be cut, since chip D1 will interfere.
Поправьте описание доработки, если онлайн переводчик накосячил.
cyb2600, congratulations on restoration of your new awesome computer! I hope you're going to spend some quality time with it.
A friend of mine is developing a ROM adapter for tidy ROM replacement. It's a work in progress at the moment:
https://github.com/desaster/vector06c-rom-adapter
Thanks. The modification looks easy enough to do own my own, although the adapter certainly would be tidier. Is there a reason to load multiple BIOSes? Or do you put something else in the extra ROM space?
... Is there a reason to load multiple BIOSes? Or do you put something else in the extra ROM space?
A lot of bootloader programs:
http://sensi.org/scalar/categories/42/
A universal boot, which is quite enough for most users:
http://sensi.org/scalar/ware/540/
I have several options written in my ROM, but I haven’t switched for many years and I don’t even remember which options you can choose.
Some users have installed a program with additional features in the ROM:
http://sensi.org/scalar/ware/541/
The instructions for revision are there.
Is there a reason to load multiple BIOSes? Or do you put something else in the extra ROM space?
I think the main point of this particular ROM adapter is to keep it nice, tidy and easily reversible. Also the soviet chips have different pin pitch, 2.5 vs 2.54, and the adapter is supposed to help with that. But it's definitely more work and the author warns us that it's an untested concept so far.
I think the next thing I should do is try to get a Combodevice, if I can't then there's no reason to replace the ROM. I actually like the existing boot loader. You don't have to type in a command to load a game and it gives you a visual representation of the loading progress. It seems to work very reliably, too.
The pretty bootloader is what instantly turned me into a fan of v06c back in the day.
The ROM upgrade only becomes necessary when you build a Combodevice or some other kind of ramdisk and/or floppy controller, because the stock one can't boot from a floppy or ramdisk.
At first I was skeptical of a a 512 byte BIOS, but it's actually very convenient. I don't have to type any commands from BASIC to load a game. The keyboard is very nice too, it has a very soft touch. Far superior to the keyboard on the BK-0010.
Судя по картинке, клавиатура герконовая, похоже это кишиневский вектор (ну и год выпуска об этом говорит). До сих пор считал, что герконовые клавиатуры для вектора стали позже делать.
The keyboard circuit board has "33 11 89" written on it with black ink. and "7 103 541" etched onto the circuit board.
I think the manual has some warranty information in the back. It appears to have been purchased in 1990
https://hosting.photobucket.com/images/i/cyb2600/IMG_2770.jpg
Produced January 31, 1990 in Minsk.
You can file a formal complaint about product quality to 220817 Minsk, Kulman, 1, MPOVT OJSC :D
I was wrong about Kishinev, interesting information.
At first I was skeptical of a a 512 byte BIOS
Would you please let me suggest a small correction, if you don't mind?
To be precise, it's not BIOS at all, as this ROM is not even available to any application programs running on a Vector (and neither does it contain any reusable input/output routines).
This is just a bootloader, no more and no less. Once you reset the machine in "normal mode" (via BLK+SBR), the bootloader ROM is completely disabled, and only becomes active again if you reset the machine in "bootloader mode" via "VVOD+BLK".
I believe the Vector is unique in this regard, as in the majority of 8-bit home computers of the era the on-board ROM is an inherent part of the machine's address space.
True, it's purely a boot loader and not a BIOS. I can't think of any other home computer without a BIOS. Maybe a very early home PC like the Altair 8080. I don't know if those things even had a boot loader or if they had to be bootstrapped manually through the front panel.
Unrelated question:
The ribbon cable connecting the computer to the keyboard was getting frayed so I removed it and replaced it with a new one. I foolishly thought the connection was 1:1, that pin 1 would go to pin 1, 2 to 2, and so on. I realize now that isn't the case. I tried rewiring it using the following diagram but it still doesn't work.
http://vector06c.fdd5-25.net/v06c_ck_page4.jpg
But that keyboard seems to have some active components on it whereas mine doesn't, just switches and a couple of LEDs. Is the pinout different for reed switch keyboards?
Reed switches keyboard version (http://www.sensi.org/scalar/media/w/vector-06c-schematics.pdf) (page 3)
That worked. Thank you!
I was able to order a Combodevice so I guess I'll be installing a new bootloader ROM.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved. Перевод: zCarot