REV 3 - REV 5 - The beginning (ST536)

[exxos]

The 1 before the apostrophe is the number of bits, so in the first code you're assigning a two line wide output (D[1:0] = two wires) with a single bit (1'b00 means D[0] is 0 and D[1] is in an unknown state).

ah, see I have no idea what I am doing. I thought it was 1 as in when its 1, it is high Z, and 0 as in actually goes 0. :roll:

So now I am flipping bit 13, not bit 5 :lol: I can see the bit going low now.. but still no IDE autoboot.

According to :

Capture.JPG

When "bit 5" goes low, it should be the same as a IRQ from ACSI pin 10 :shrug: , but still no auto boot :pullhair: @agranlund ??

Edit:
After seeing mono detect I think my simple idea of just flipping bit 5 won't work, because if someone is in mono mode then it would also get flipped. So I would need to copy the values from ram, then change bit 5. But that doesn't fit in a 144xl chip. So I think I'm going to have to shelf that feature for now :(

I tried setting bit 7 high and low thinking it would trip TOS into rebooting but nope. Looking like they might be active high as I get %00000100 on $FFFA03. $FFFA02 I get BERR as expected. So no idea why it doesn't work !?

Oddly if I poke 255 to $FFFA03 it locks up in STOS (cursor still flashing). Maybe just setting the bit isn't enough. Possible the MFP could be "undoing" the values I set :shrug:But poking %110 still shows as the same number if I write and ready back.

[exxos]

I have dumped the current build onto my website https://www.exxosforum.co.uk/atari/last/TF536/index.htm

Basically this must use MAPROM18 which is included in the zip. TOS206 will not function correctly without it. The ST-RAM cache thing I cannot get working. I cannot figure out the IDE autoboot thing either. But you can still boot hooking up the ACSI wire from the ST536 to pin 10 ACSI port. There is probably not much point spending countless hours trying to get the code to fit for the sake of a bodge wire. Autobooting a Windows compatible drive doesn't seem to work. No idea why. Besides all that, I'm supposed to be taking a break working on all this stuff :roll:

So anyway, these are the current results.

IMG_0474.JPG

With NVDI... And holy hell this thing is fast...

IMG_0475.JPG

[Badwolf]

Autobooting a Windows compatible drive doesn't seem to work. No idea why.

I don't think HDDriver supports booting from Windows compatible partitions. EmuTOS does, though.

BW

[exxos]

I don't think HDDriver supports booting from Windows compatible partitions. EmuTOS does, though.

Oddly booting from ultrasatan boots from a dos compatible card but not IDE :shrug:

[Badwolf]

Oddly booting from ultrasatan boots from a dos compatible card but not IDE :shrug:

Byte order? Hard discs are voodoo.

BW

[Steve]

I think I do reverse my cf card > ide cable on the tf536 to get it to work with anything, not sure if it's the same issue here.

[exxos]

I think I do reverse my cf card > ide cable on the tf536 to get it to work with anything, not sure if it's the same issue here.

You had to do some funky cable swapping on the original r2. But on the r5 that is fixed.

IMG_0476.JPG

[PhilC]

Sounds like I better update my R5 and then build my other one

[JezC]

Sounds like I better update my R5 and then build my other one

I'd better build both of mine...though the biggest issue is my lack of '030s...one 'spare' to go across the 2x v5 & 1x v2 TF536...plus one additional for a DFB1 at some point :roll:

Oh, and the SDRAM (but at least they are reasonably available ATM) ;)

[agranlund]

When "bit 5" goes low, it should be the same as a IRQ from ACSI pin 10 :shrug: , but still no auto boot :pullhair: @agranlund ??

Yep TOS basically polls address 0xFFFFFA01 in a busy-loop until bit5 is zero, like so:

Code: Select all

btst #5,(MFP_GPIP).w

TF536r2 allows the read to reach the motherboard in order to get the full value of that register, then it clears bit 5 and signals ACK.

Edit: If you are not already doing so, it's probably worth treating all FFxxxxxx addresses as 00xxxxxx somewhere in the top level so you don't have to check both variations all over the place.
You never know which one of them some software will use, and both are equally valid and the same thing.