REV 3 - REV 5 - The beginning (ST536)

[exxos]

Managed to get it booting at about 56Mhz, but are having some odd issues. It seems to pass ST-RAM test fine then locks uploading HD Driver. I am currently trying to compile some new firmware to disable the TT-RAM and do some other tests. But it is incredibly slow going because the PLD is full. FITting keeps failing :( It takes about half an hour to compile the firmware. :roll:

Have a few more goes not going to spend much longer on it all. If it was something simple which could be done then it would be worthwhile investigating but not if it's going to be a constant PITA every step of the way. Slightly annoying as I got over 61MHz in the past. It could be very CPU dependent or even PLD dependent etc.

[PhilC]

Try a different CPU thats a common thing, most will do ram check but fail after

[exxos]

Try a different CPU thats a common thing, most will do ram check but fail after

Yeah been trying a few out.

This is about 112MHz / 56MHz. Had to run the CPU on 5.50V to get it to even pass TTram test at all.

56mhz.jpg

Same test without another CPU won't boot at all.

[Matej]

Nice test results.

[JezC]

Sorry if I've missed the answer to this...

Having recently obtained an ST536 at the recent Cyber Legends 2 event (thanks @PhilC !), I'm getting ready to fit it into my H4.

Now PhilC wasn't sure exactly which firmware version was programmed into the CPLD, so I will understand if the steps need to change based on what that firmware version actually is...

When I fit this into one of the DIP expansion sockets, I need to remove the PLCC CPU, fine.

Do I also need to remove the ROM from the motherboard?

Plus, do I need the flying wire (for the DMA ?) connected? I've got my TRUDIE board in that machine at the moment (as I've not yet modified the board with the DMA fix for ACSI to work) so will remove that & fit the ST536 in its place.

Thanks!

[exxos]

Now PhilC wasn't sure exactly which firmware version was programmed into the CPLD, so I will understand if the steps need to change based on what that firmware version actually is...

It should be the latest firmware https://exxosforum.co.uk/atari/last/TF536/index.htm

When I fit this into one of the DIP expansion sockets, I need to remove the PLCC CPU, fine.

Yep.

Do I also need to remove the ROM from the motherboard?

Yep.

Plus, do I need the flying wire (for the DMA ?) connected?

Nope. The wire is no longer used with the current firmware.

I've got my TRUDIE board in that machine at the moment (as I've not yet modified the board with the DMA fix for ACSI to work) so will remove that & fit the ST536 in its place.

While Trudie is built better than normal IDE interfaces, having 2 IDE interfaces isn't going to end well. So you should use the one on the ST536.

I assume your aware you need my patched TOS206 (ST536 TOS) to use with the ST536 as well ?

[PhilC]

@JezC in reality I expect it will be the latest firmware that’s in it, just been a while since I did it.

It’s hot the patched Tos on rom :)

[JezC]

Thanks @exxos @PhilC I'll try it tonight if time allows. I had to dig out the H4 and check it booted/ran Sysinfo ok before making any changes.
That all went ok last night, so hopefully I can sort it while the patient is still on the operating table

Hopefully I can post some progress later this evening.

[JezC]

Ok, so ROM on the mainboard removed, 68k removed, also removed TRUDIE board...

I presume that the ROM_CE wire from the ST536 connects to the same position as the ROM wire from the TRUDIE (so as to use the address decode on the ST536 rather than the links on the main board)?

I'm now hoping that I don't need the DMA wire anymore (as the pin for the DMA IRQ came off the H4 board when I removed the TRUDIE board - oops)...

Note to self - less haste, more speed next time :chairsmack:

[exxos]

You don't connect ROM CE to anything, just use the ROM socket on the ST536. Also that DMA wire isn't even in the later firmware, IIRC I was using it as a debug output pin for something.