Page 4 of 16

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 21:35
by exxos
With STE TOS206 ST536 TOS it does show up the STram test. But it does not see the TTram :(

I think it keeps on turning on 24 bit addressing by itself which is probably why :roll:

Capture.PNG

If I changed the header to 209 it just freezes then :(

Capture.PNG

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:00
by stephen_usher
Use my fixcrc program to fix that. :-)

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:03
by exxos
stephen_usher wrote: 05 Dec 2022 22:00 Use my fixcrc program to fix that. :-)
Never thought of that...

Though generally TOS doesn't lock up completely after failing the CRC test.. Unless something else funky is going on

EDIT:

Saying that it won't help.. As soon as Hatari sees "2.xx" it switches on 24bit addressing :(

I think someone mentioned this could be disabled in Hatari last time I was messing with it all.. with the usual "if you compile it yourself" type of "help" :roll:

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:19
by Badwolf
My fairly heavily modded Hatari oddly prints the dashes without reverse text then bombs at the start of the TT-RAM test.

With memvalid it just bombs early doors.

No bus error logged in the console, which is odd.

Screenshot 2022-12-05 at 22.17.57.png

BW

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:25
by exxos
Badwolf wrote: 05 Dec 2022 22:19 My fairly heavily modded Hatari oddly prints the dashes without reverse text then bombs at the start of the TT-RAM test.

With memvalid it just bombs early doors.

No bus error logged in the console, which is odd.
So you know how to do mods to Hatari then ? If that's the case if I could find line of code which has mentioned you could probably just remove that for me ? I would assume if it stopped switching to 24bit addressing then it would allow TTram to work ...

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:31
by Badwolf
exxos wrote: 05 Dec 2022 22:25 So you know how to do mods to Hatari then ? If that's the case if I could find line of code which has mentioned you could probably just remove that for me ? I would assume if it stopped switching to 24bit addressing then it would allow TTram to work ...
Yep, just found the line & nixed it.

tos.c:

Code: Select all

	if (ConfigureParams.System.nCpuLevel < 2 || (TosVersion < 0x0300 && !bIsEmuTOS)) {
			ConfigureParams.System.bAddressSpace24 = true;
TT-RAM test is slow as molasses, as described.



BW

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:33
by exxos
Badwolf wrote: 05 Dec 2022 22:31 Yep, just found the line & nixed it.

tos.c:

Code: Select all

	if (ConfigureParams.System.nCpuLevel < 2 || (TosVersion < 0x0300 && !bIsEmuTOS)) {
			ConfigureParams.System.bAddressSpace24 = true;
TT-RAM test is slow as molasses, as described.

BW


argh, how many seconds did it take you to do that ? :lol: GIMMIE!!! :chairsmack:

I only just found the email about it :lol:
Have a look at tos.c :

/* 32-bit addressing is supported only by CPU >= 68020, TOS v3, TOS v4 and EmuTOS */
if (ConfigureParams.System.nCpuLevel < 2 || (TosVersion < 0x0300 && !bIsEmuTOS))
{
ConfigureParams.System.bAddressSpace24 = true;
M68000_CheckCpuSettings();
}

I think it should work if you change the 0x0300 into 0x0200.

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 22:55
by stephen_usher
You could just change the TOS header to read 3.06 instead. :-)

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 23:00
by exxos
stephen_usher wrote: 05 Dec 2022 22:55 You could just change the TOS header to read 3.06 instead. :-)
That's what I mentioned earlier.. It just goes to desktop without doing any RAM tests :shrug:

Re: TOS RAM test routine ?

Posted: 05 Dec 2022 23:02
by Badwolf
exxos wrote: 05 Dec 2022 22:33 argh, how many seconds did it take you to do that ? :lol: GIMMIE!!! :chairsmack:
:lol:

I'd been hacking that file already for my own nefarious ends.

I'm afraid a debug Linux version is probably not much use to you.
stephen_usher wrote: 05 Dec 2022 22:55 You could just change the TOS header to read 3.06 instead. :-)
That should work -- isn't that where we came in? :D

BW