Login
Back to forumReply to this topicGo to last reply

Posted By

C=Owl27
on 2020-10-28
14:42:44
 Burring a Diag264 Cart

Hello Plus4world.

I have a minipro tl866 and downloaded the diag264 ntsc bin file.
Using the low bin version. It is 16k.

I went ahead and burned it to a ST m27c512.
Placed it into my prepared cartridge socket.

When the Plus4 powers up I get a static screen full of one character.

I'm using SukkoPera's OpenC16Cart pcb.
The top jumpers are in following order:
Middle:Top:Top:Bot:Bot Middle:Top:Top:Bot:Bot

I hope somebody here could help me clear up some things.

Should the 16k bin be doubled to 32k before burning?

Any thoughts or suggestions would be greatly appreciated.

Posted By

siz
on 2020-10-28
16:50:10
 Re: Burring a Diag264 Cart

27c512 is 64k. AFAIK diagrom is 16k so you have to copy it 4 times.
edit: I'm not familiar with that cart so I'm not that sure.

Posted By

C=Owl27
on 2020-10-28
20:25:20
 Re: Burring a Diag264 Cart

Thank you siz for the response.
Well it is still the same.
I recall that the reason the board as two chip slots is that
each could hold 32 and together they can make 64.
But I am a novice and know very little about this.
The volts was preset to 13. But I have seen in videos people using 13.5.
Just have to keep trying.

Posted By

C=Owl27
on 2020-11-02
13:07:55
 Re: Burring a Diag264 Cart

C=Owl27

Finally overcame the hurdle.
I took out each microchip and cleaned the sockets and pins.
I used rolled up and flattened paper slid under the microchips to pull them out.
After resetting them, now the Diag264 runs.

Firstly, since initially I couldn't get the cartridge to work,
after doing the cleaning,
I put my st m27c512 chip, which I burned the diag264 to,
into the 3+1 slot.

Turning on the Plus 4 it began to diagnose.
Whew! Finally!







But I did not have the chance to press the F1 key to get it going.
The diag264 started immediately after power on.

On a whim I put the new chip into the cartridge pcb,
Plugged it in and it also started going.

So it looked like the culprit all along was bad contacts with the ICs.

I went on to burn a new Low and Hi 3+1 software.
And they too now work.
I wanted to take more pictures of it,
but my makeshift composite out pin separated from the soldered wire.

I will have to make a proper cable tomorrow.
My new Svideo cable is too short for the space I am using presently,
and my original cable still has the bad ground.
I have one din left after all my connectors.
I had to eventually use the crappy RF cable in TV mode to see the final
results.

But long story short, the 3+1 now works as well.
I suspect it was my 8501 processor. One of the pins looked slightly ajar.
Glad it was a simple fix.

Incidentally when I put the original 3+1 chips into the board,
and ran the diagnostic, they seem to pass.
The screen displays their availability,
but they refuse to load.
Not sure what that is about.
The new burnt chips work like a charm now.
And also pass in the diag264.

Summery:
1)Bad connections with ICs (8501)
2)The diag264, when in the 3+1 slot auto starts at power on.
3)The cartridge also now works once the connections were cleaned and reset.

Posted By

crock
on 2020-11-03
02:42:02
 Re: Burring a Diag264 Cart

"2)The diag264, when in the 3+1 slot auto starts at power on."

Diag264 auto-starts whichever slot it's in. Since v0.9, the low-rom version will work from cartridge, 3+1 low, or basic socket. You never need to press F1, that is a feature of the 3+1 software and would not make much sense as Diag264 is also there to diagnose KB problems.

Also, from your picture, you have a problem with your TED chip, in that the 24/25 row register is broken. You can tell this from the black dots across the top of the display. From experience, this will not stop software working, but it will cause some screen corruption on software which does smooth scrolling.

Rob

Posted By

C=Owl27
on 2020-11-03
03:19:06
 Re: Burring a Diag264 Cart

Very much appreciated for the diagnosis.
Today with my new cable I still get intermittent flashing characters on the screen.
Or also weird cycle movements across the screen.
Also suddenly the L key and up and down cursor keys stopped working.
I think the keyboard ribbon is starting to fail.
Also when it is plugged in again it still shows a fail in the diag264.
If the ribbon is failing I will replace it with a plugin version.

The only reason I thought F1 key was because of the location I put the chip in.
Your programs is wonderful and should run at startup.
And I thank you very much for making it.



Back to topReply to this topic


Copyright © Plus/4 World Team, 2001-2024