ST536 STE EDITION

[exxos]

FFS!

IMG_2383.JPG

[Badwolf]

FFS!

Think that's a ground. Not sure it'd explain your issues. :(

BW

[exxos]

Think that's a ground. Not sure it'd explain your issues. :(

Yes it was a ground I checked. Generally all grounds have to be connected but did not make any difference. (just built up a second board )

However I do seem to have figured the resetting problem out.. I just simply added another wait state onto ROM access. It could potentially mean the ST536 firmware (which I used) might not actually be geared up for "slow rom" access :roll:

But anyway... It has run through several loops in total so far..

IMG_2384.JPG

IMG_2385.JPG

There is no MAPROM loaded yet. So ROM will be slower than it would normally be.

The next problem is TT-ram isn't found :(

EMUTOS now boots. Pretty weird (though I've had similar before with TOS) that one OS can work fine, and another won't boot at all.

Has the splash screen been removed in 1.3 ?! It just says EMUTOS 1.3 on boot and goes right to desktop ? I don't use EMUTOS much, so don't know if you're supposed to hold down the key to get the splash screen or something ? I thought it would be useful if it would display if it found TT-RAM or not. But no idea.

Anyway booted GB6.. Got the "usual" doesn't like my floppies issue :(

IMG_2386.JPG

And finally the GB6 benchmark. Though I thought EMUTOS added blitter support ages ago ? GB6 reports not blitter ? :shrug:

IMG_2387.JPG

But I suppose anyway, its great news that at least the STE536 seems stable other than the TTram issue. Ultrasatan seems to lockup TOS after memory test, so no idea whats going on there either.

[exxos]

EMUTOS found ultrasatan. It booted up GB6 and running tests again fine.

Though am I doing something wrong or is this supposed to be normal behaviour ? I did not have a floppy in the drive and when I tried to save desktop , it said drive A is not responding (there is no floppy in the drive) but shouldn't it be saving to the C: drive when C: drive is selected and the boot drive ?

IMG_2388.JPG

As for TOS not liking Ultrasatan. It could possibly be the register thing for AutoBoot does not work on the STE for some reason :shrug: . Have to disable some stuff in firmware to figure that out. Though I think currently I need to focus more on the TTram issues anyway.

[Badwolf]

A few questions here.

* Emutos, as released, only shows the splash screen at cold boot. It's build-time option to have it show every time. CTRL-ALT-SHIFT-DEL should get it up.
* Emutos will disable blitter when TTRAM is found to avoid the desktop trying to blit in and out of it.
* On the Emutos splash screen you can choose your boot drive (by pressing a letter -- the boot drive will be highlighted). Perhaps this was inadvertently set to A.

BW

[exxos]

* Emutos, as released, only shows the splash screen at cold boot. It's build-time option to have it show every time. CTRL-ALT-SHIFT-DEL should get it up.

If I do the cold reset on the keyboard, EMUTOS just displays garbage, but it doesn't work with TOS206 either, it just hangs on a white screen.

Powering down for 5 seconds and back up again, still no splash screen.

* Emutos will disable blitter when TTRAM is found to avoid the desktop trying to blit in and out of it.

That would make sense. Though GB6 doesn't find the RAM, in fact TOS doesn't either. So why the blitter is disabled without TTram seems odd then.

* On the Emutos splash screen you can choose your boot drive (by pressing a letter -- the boot drive will be highlighted). Perhaps this was inadvertently set to A.

I don't know, I cannot get the splash screen to appear :lol: :roll:

[Badwolf]

* Emutos, as released, only shows the splash screen at cold boot. It's build-time option to have it show every time. CTRL-ALT-SHIFT-DEL should get it up.

If I do the cold reset on the keyboard, EMUTOS just displays garbage, but it doesn't work with TOS206 either, it just hangs on a white screen.

Powering down for 5 seconds and back up again, still no splash screen.

That's not a good sign all around. Possible your screen isn't syncing in time after the cold start? Hold down left shift to hold the splash screen (if it appears).

* Emutos will disable blitter when TTRAM is found to avoid the desktop trying to blit in and out of it.

That would make sense. Though GB6 doesn't find the RAM, in fact TOS doesn't either. So why the blitter is disabled without TTram seems odd then.

It would sugest emutos did find the TTRAM. Desktop Configuration under the Options on the desktop should show the memory configuration.

I have found some versions of GB6 won't detect AltRAM even if they're running from it! Not sure if that's relevant as I imagine you know what version you're running :)

BW

[exxos]

I have found some versions of GB6 won't detect AltRAM even if they're running from it! Not sure if that's relevant as I imagine you know what version you're running :)

If you're using the latest official on the website then all it does is tries to allocate some ttram.. if it can, it switches to alt-ram mode, if not, it assume STram.

Code: Select all

ZZ&=mxalloc&(16,1) 'see if we can allocate some fast-ram, returns -32 or 16948100
'assume negative numbers are error

'check variable location in RAM for 68020 CPU - over 16MB area 
IF VARPTR(Z$)>=&h1000000 AND VAL(GET_CPU$)>68010 THEN CHECK_ALTRAM&=1 : Z$="RUN FROM ALT_RAM" :FLAG=1

'check variable location in RAM for 68000 CPU over 4MB area 
IF VARPTR(Z$)>=&h400000 AND VAL(GET_CPU$)<=68010 THEN CHECK_ALTRAM&=1 : Z$="RUN FROM ALT_RAM" :FLAG=1


'alt-ram location not found, but we allocated ram, then we must have a condition not meet above
'most likely falcon with alt-ram in the 16MB block somewhere, so will just have to assume that here..
'so alt-ram found above the 4MB area and varibles found above the 4MB area.. CPU not matter here ?
IF FLAG=0 AND ZZ&>=&h400000 AND VARPTR(Z$)>=&h400000 THEN  CHECK_ALTRAM&=1 : Z$="RUN FROM ALT_RAM" 

Older versions may have tried getting information from the cookie jar. Looking at my Code, looks like I gave up with that idea. Problem is alt-ram could be allocated, but nothing set the cookie for GB6 to read. So that could malfunction and may be why I gave up and just went with mxalloc instead to see if RAM was there.

[exxos]

It would sugest emutos did find the TTRAM. Desktop Configuration under the Options on the desktop should show the memory configuration.

Its not saying anything about TTram..

IMG_2391.JPG

IMG_2392.JPG

I double checked and the blitter is not present.. So maybe EMUTOS disabled the blitter on the 030 CPU...

Think I'm just going to stick with TOS206 for now. I'm just not familiar with what EMUTOS is doing all the time and it's just confusing matters for me :(

[Badwolf]

Its not saying anything about TTram..
...
I double checked and the blitter is not present.. So maybe EMUTOS disabled the blitter on the 030 CPU...

I'm pretty sure it only turns it off if TT-RAM is found, but you're right nothing there.

Of course, there are different versions of EmuTOS (country codes, ROM sizes, releases). Certain ones don't even support TT-RAM.

You're completely free of AUTO folder programs, I take it? BLITFIX will simply turn off Blitter in some circumstances, IIRC.

BW

PS YAARTTT has a hidden memory setting, BTW. Press 'M' at the menu and you can enter a block to test. Eg. 01000000 to 02000000.