REV 3 - REV 5 - The beginning (ST536)

[exxos]

If I run all the conditions through the master clock it does improve things greatly, but if I use a slower clock then does not boot up :roll:

IMG_6383.JPG

[Badwolf]

But more bonkers things going on, address strobe is high and DTACK is clearly pulsing when there is no possible way it could even do that.. unless I am missing something ?! there is no blitter or anything else on this machine I don't see how DTACK Is being driven. The PLD only has DTACK as a input, so I cannot see how the chip can even be driving that as a output unless the compiler is seriously screwing up somehow. I did have a span of the software ringing of a blank page for the design summary, intermittently not seen the PLD, and after a while it would not even let me copy and paste in the thing.. I think the more you use it the more it starts screwing up.

Is blue still ST-AS there? Why's it pulsing in between what appear to be normal bus accesses?

To me that looks like blue is actually 030 AS and this is behaving perfectly normally with a load of 50MHz accesses (causing no DTACK) and then the occasional ST-RAM access (blue goes low followed ~250ns later by yellow both then terminate at the same time).

BW

[exxos]

Is blue still ST-AS there? Why's it pulsing in between what appear to be normal bus accesses?

To me that looks like blue is actually 030 AS and this is behaving perfectly normally with a load of 50MHz accesses (causing no DTACK) and then the occasional ST-RAM access (blue goes low followed ~250ns later by yellow both then terminate at the same time).

Both scope probes are on the 68K socket.. Because the code wasn't isolating ST_AS from AS30.. It is actually both ST_AS and AS30..


But like in this image when I disable it from seeing TTRAM and TOS..

IMG_6383.JPG

There is still something glitching somewhere...

But I think that is the least of my problems currently, because one moment everything works fine, I restart and it locks up loading the ROM in TOS... I was thinking my code changes were causing this problem, but it is intermittent, so I just have no idea why that is happening.

[terriblefire]

do you have a simple simulation of the code? I usually find the problem when i do that

[exxos]

do you have a simple simulation of the code? I usually find the problem when i do that

Wouldn't know how to do one even. Anything I can see a little odd is ST_DTACK does not always register as a high just before it locks up.. But it should not really affect anything anyway.

[terriblefire]

Wouldn't know how to do one even. Anything I can see a little odd is ST_DTACK does not always register as a high just before it locks up.. But it should not really affect anything anyway.

email me the code. Bit busy this afternoon but i'll see what i can do

[exxos]

email me the code. Bit busy this afternoon but i'll see what i can do

ok will do thanks.

[AndresPlazaR]

Hi everyone,

Quick non-technical interruption: I just want to tell you that I have been following each post and, even if I don't understand all the interactions that you are having, I really enjoy the conversation, appreciate all your efforts and I think it is a master class of collaboration and camaraderie.

So, thank you very much,

Andres.

Now, you can keep going. :-D

[exxos]

Quick non-technical interruption: I just want to tell you that I have been following each post and, even if I don't understand all the interactions that you are having, I really enjoy the conversation, appreciate all your efforts and I think it is a master class of collaboration and camaraderie.

Glad someone is enjoying it :lol: :roll: This board is going to have a hard calibration with a sledge hammer before the end of the day...And that will be entertainment! :lol:

[exxos]

So far it still locks up on the second part of the GB6's VDI test.. But only when TOS is running from TTRAM.. And only when the instruction cache is turned off.. But sometimes it will run the test a couple of times before it freezes... I'm really starting to wonder if is just is some bug in the CPU!

Have had it running YAARTTT and nothing fails there....

IMG_6385.JPG