Page 2 of 2

Re: M68k opcode sizes test ROM

Posted: Wed Sep 13, 2017 2:37 pm
by notaz
I'd say there is no benefit of handling warm boot differently in a test like this, unless you want to also test effects of reset.

Re: M68k opcode sizes test ROM

Posted: Wed Sep 13, 2017 3:09 pm
by r57shell
I just put common MD initialization, so I thought flashcart should not have any issues with it, because it runs many games very well which has similar MD initialization.

Here is test new version: http://www.mediafire.com/file/jl2227tc4 ... s_test.bin
Tell me if it fails or success.
It works under megaeverdrive1 md2 asia pal

Re: M68k opcode sizes test ROM

Posted: Wed Sep 13, 2017 7:03 pm
by Sik
Checking for warm boot is only useful for like when games want to keep the options and high scores after pressing Reset (so you can skip reinitializing those). Otherwise you're better off not doing a special case for it.

Re: M68k opcode sizes test ROM

Posted: Wed Sep 13, 2017 9:46 pm
by notaz
r57shell wrote:
Wed Sep 13, 2017 3:09 pm
Here is test new version: http://www.mediafire.com/file/jl2227tc4 ... s_test.bin
Tell me if it fails or success.
It's fine now on MED but on raw flashcart it still black screens ~80% of the time.

Re: M68k opcode sizes test ROM

Posted: Thu Sep 14, 2017 9:45 am
by r57shell
here also without bne.s start: http://www.mediafire.com/file/46op66mkn ... _test1.bin
notaz wrote:
Wed Sep 13, 2017 9:46 pm
It's fine now on MED but on raw flashcart it still black screens ~80% of the time.
I remember once my test ROM was failing because of bug in flashcard with size alignment.
So, if without bne.s start doesn't still working, try align size with zeroes up to 1 MB, and so on, and see what happens.
Also, make sure it's aligned to 65 kb at least, because even under emulator it will fail if not aligned to 65 kb because it actually access that part of zeroes!