CURRENT PROTOTYPE STATUS (SEC 64MHz 68000)

[BlankVector]

Hey! Yes, but we both made some progress...

Oh, good news! This was a weird problem.
Feel free to ask if you have another strange problem, EmuTOS with debug traces can be very useful to debug things.

[exxos]

Hey! Yes, but we both made some progress...

Oh, good news! This was a weird problem.
Feel free to ask if you have another strange problem, EmuTOS with debug traces can be very useful to debug things.

Actually still have same problem :cry:

[BlankVector]

Actually still have same problem :cry:

Oh. So please start trying EMUTOSUK.PRG as I advised to see what happens.

[exxos]

Oh. So please start trying EMUTOSUK.PRG as I advised to see what happens.

OK will do that now and see what happens...

[exxos]

Oh. So please start trying EMUTOSUK.PRG as I advised to see what happens.

OK will do that now and see what happens...

I just get this after loading the PRG.. nothing else..

IMG_3747.JPG

[BlankVector]

I just get this after loading the PRG.. nothing else..

Oh. That's very unexpected.
Did you see the EmuTOS welcome screen before the crash?
Note that some AUTO/ACC programs may not be compatible with EmuTOS. Be sure to press Control (just once) at the welcome screen to avoid loading any AUTO/ACC program, hence avoiding trouble.

[exxos]

Did you see the EmuTOS welcome screen before the crash?

Nope, nothing, just white screen while loading PRG, then that error dump. What is at that address ?? Says undefined in the Atari memory map docs...

Note that some AUTO/ACC programs may not be compatible with EmuTOS. Be sure to press Control (just once) at the welcome screen to avoid loading any AUTO/ACC program, hence avoiding trouble.

Blank floppy with TOS104 loaded from ROM... Only emutos on the floppy nothing else at all.

[BlankVector]

Blank floppy with TOS104 loaded from ROM... Only emutos on the floppy nothing else at all.

I have just tested the very same setup with Hatari and it works fine.
It also worked fine on my real STe (TOS 1.62 + EMUTOSFR.PRG)

How can it fail for you??
Maybe CPU, RAM, or other hardware issue??

PS: About the strange address, I suspect a jump to a bogus address (wrong RAM, buffer overflow...), then execution of a bogus instruction.

[exxos]

How can it fail for you??
Maybe CPU, RAM, or other hardware issue??

PS: About the strange address, I suspect a jump to a bogus address (wrong RAM, buffer overflow...), then execution of a bogus instruction.

Likely is a hardware issue, but I don't know what... Actually I can load GemBench6 and it will run all day. So its not a huge fault.. just I have no idea where the problem lies...


If I use slow ROM access, floppy format works fine in GEM...

But with EMUTOS...

IMG_3748.JPG

... I get that after loading PRG...


EDIT:

The diagnostic cart tests all seem fine, other than first boot, keeps saying "I7 BUS ERROR NOT DETECTED" :shrug:

err.jpg

[BlankVector]

The diagnostic cart tests all seem fine, other than first boot, keeps saying "I7 BUS ERROR NOT DETECTED" :shrug:

Does this mean that your hardware doesn't trigger proper Bus Error when expected? That matters for EmuTOS, because it uses Bus Error much to detect optional hardware (Blitter, TT & Falcon hardware, etc.).

BTW, on all your pictures, I see that SR=$27xx, which means that interrupts are masked. Probably because the EmuTOS startup sequence has not enabled interrupts yet. And the PC value is surprising low, this is why I suspect a bad jump to low memory.

Now I need to sleep a bit. Maybe new ideas will come during the night.