Page 63 of 110
Re: REV 3 - The beginning
Posted: 28 Apr 2022 15:33
by exxos
Badwolf wrote: 28 Apr 2022 15:28
You could try changing the code to hard coded values rather than worry about the memory detect?
It's basically only setting ramvalid to a magic number and ramtop, from what I can see. Presumably something else comes along and adds it to the memory pool later? Maybe that's the difference between TOS3 and TOS2?
I did try all this earlier but did not change anything.. I was trying to trick it into thinking it had TTram rather than trying to test it. I tried all sorts of combinations to no avail.
Code: Select all
move.l #$05000000,(_ramtop).w
move.l #$05000000,(memttop).w
move.l #$05000000,(_phystop).w
move.l #$1357bd13,(_ramvalid).w /* ramtop is valid (ramvalid == RAMMAGIC) */
Re: REV 3 - The beginning
Posted: 28 Apr 2022 15:35
by exxos
stephen_usher wrote: 28 Apr 2022 15:30
As TOS 2.06 has no idea about TT-RAM it doesn't have code in it to make sure that the RAM it's allocating for the screen is in ST-RAM. TOS 3.06 would have this logic built into it.
Similarly, TOS 2.06 won't have the logic to prevent it using TT-RAM for DMA.
Indeed. The PAK patches seem to alleviate those problems, but enabling the lot causes other problems as previously mentioned.
I have pretty much been going through line by line turning on the patches one at a time and trying there is combinations but to no avail.
Re: REV 3 - The beginning
Posted: 28 Apr 2022 16:06
by Badwolf
exxos wrote: 28 Apr 2022 15:33
I did try all this earlier but did not change anything.. I was trying to trick it into thinking it had TTram rather than trying to test it. I tried all sorts of combinations to no avail.
It could be this is just being done too early and is confusing things as per Stephen's suggestion.
I note the way Hatari hacks TOS is to basically do an Maddalt() at some point rather than hacking the variables.
BW
Re: REV 3 - The beginning
Posted: 28 Apr 2022 16:15
by exxos
Badwolf wrote: 28 Apr 2022 16:06
It could be this is just being done too early and is confusing things as per Stephen's suggestion.
I note the way Hatari hacks TOS is to basically do an Maddalt() at some point rather than hacking the variables.
Yep, That is what I mean. Declaring the RAM to early with of course, as we all know will screw up 206. The PAK changes fix that some, but it causes the AES to screw up. So damned if you do and damned if you don't kind of thing.
But maybe the PAK changes do not fix the problem fully, hence the AES issue. I think it is just turning into a complete disaster trying to update TOS206 with TTram . The only possible workaround would be to allow the memory test show one start-up, I just not allocate the RAM. But really that is somewhat pointless if they PRG has to be loaded to allocate the RAM to use it anyway :roll:
I still have not figured out why 306 won't work with the TF536 either. slightly annoying as 306 seems to need 512K space, TOS206 only needs 256K :roll:
Re: REV 3 - The beginning
Posted: 28 Apr 2022 19:36
by Badwolf
exxos wrote: 28 Apr 2022 16:15
I still have not figured out why 306 won't work with the TF536 either. slightly annoying as 306 seems to need 512K space, TOS206 only needs 256K :roll:
Your chip is a 4096, isn’t it?
BW
Re: REV 3 - The beginning
Posted: 28 Apr 2022 20:07
by exxos
Badwolf wrote: 28 Apr 2022 19:36
Your chip is a 4096, isn’t it?
Yep.
Re: REV 3 - The beginning
Posted: 28 Apr 2022 21:41
by exxos
ahhhh So it seems the PAK patches were trying to set the Falcon's Videl up not the ST shifter :shrug: So now LOW & Medium res are behaving as they should! :D
IMG_0523.JPG
Capture.PNG
Need to start some testing now , see what I broke :lol:
Re: REV 3 - The beginning
Posted: 28 Apr 2022 21:47
by stephen_usher
:dualthumbup:
Re: REV 3 - The beginning
Posted: 28 Apr 2022 22:39
by exxos
ALT-RAM working without any "install" software. GB6 running fine in ALT-RAM :)
IMG_0524.JPG
YAART saw alt-ram and passes fine.
IMG_0525.JPG
MAPROM 4KC LOADED.
IMG_0526.JPG
BLITTER ADDED :)
Oddly in 206 it should be disabled if I am reading the code right :shrug:
IMG_0527.JPG
@agranlund BLITFIX seems to hard disable the cache in the desktop menu, can't turn it on anymore ? Assume by design ?
I had another thought about using patched ROM images., maybe a tweak to maprom. In that if it finds a file eg: TOS.BIN, it would load that into fastram, if the file isn't found, then it copies the ROM to fast ram like normal.
I have 5k free space in TOS206 ;)
Re: REV 3 - The beginning
Posted: 29 Apr 2022 13:12
by exxos
:lol:
Capture.PNG
Anyway, I'm looking into the ST-RAM cache issue again now I am the master of TOSsing :lol: There are that many fixes for the floppy drive already. So i'm going to try turning some of them on now and see if they have any effect with my new setup.