Page 4 of 7
Posted: Wed Feb 20, 2008 11:58 am
by Jorge Nuno
TmEE co.(TM) wrote:I tried it on real HW and :
A button doesn't do anything.
That's the weirdest glitch I've ever seen... LOL
And worse I've got no idea why it doesn't capture the A button
TmEE co.(TM) wrote:B works perfectly.
At least the the most important part works... Did you actually read or write something like reading the VDP status?
TmEE co.(TM) wrote:C crashes the proggy and TV usually looses sync...
This seems an address error exception to me, and a bug in the interrupt handler...
Thanks for the feedback
EDIT: Source and binary updated, please redownload.
Posted: Wed Feb 20, 2008 4:33 pm
by TmEE co.(TM)
B took me to sky scroller not to data read/write part...... now reading what the button should do, it seems some things are swapped or something.... strange.
Posted: Wed Feb 20, 2008 4:40 pm
by Jorge Nuno
That's even "weirder", oh god... but in gens/fusion it works ok, I really don't understand what's going on
/me opening the source file in despair...
The decision is made on line 512, VBL at line 1650 calls the joypad reading routine, which is on line 1770...
Nope I must be blind... I can't find anything bad in those regions...
Posted: Wed Feb 20, 2008 5:53 pm
by TmEE co.(TM)
I check most stuff on real HW immediately after writing... but I don't remember having such issues...
Posted: Wed Feb 20, 2008 5:56 pm
by Jorge Nuno
What?
You said that A doesn't work, B does what A was supposed to do, and C makes the rom crash and the TV loses sync... those are the issues I wasn't expecting...
Posted: Wed Feb 20, 2008 6:04 pm
by TmEE co.(TM)
What ? - I check almost everything I do on real HW immediately, i.e writing a piece of code, flash the cart, plug into MD, see what happens.
maybe you read controller too fast or something ? it shouldn't cause such behaviour though...
Posted: Wed Feb 20, 2008 6:06 pm
by Jorge Nuno
Normally once every VBL, except when a critical exception occurs...
Can you pause the intro screen/sky?
Posted: Wed Feb 20, 2008 6:11 pm
by TmEE co.(TM)
I couldn't get any pause action up... I check controllers in main loop not in VBL routine, in fact, I usually don't use VBL routine
Posted: Wed Feb 20, 2008 6:25 pm
by Jorge Nuno
So Start doesn't work, A neither, B the program thinks its A, and C?
Posted: Wed Feb 20, 2008 6:30 pm
by TmEE co.(TM)
C functioned, but the proggy crashed, and TV usually lost sync
Posted: Wed Feb 20, 2008 6:35 pm
by Jorge Nuno
Ummm ok I'm coding something that shows the currently held buttons bitmap on-screen, please wait a few moments...
Posted: Wed Feb 20, 2008 6:59 pm
by Jorge Nuno
Done! there is an hexadecimal value on-screen that shows the Held buttons in real time, please tell me what buttons change that value (FFh)
Don't forget to redownload it... (same links)
Wait, I guess I'm doing something really stupid in the Joypad read routine...
I think it's fixed now... (I think), if it isn't then tell me which buttons change the FF value, please.
Also this is the only program I know that makes the VDP output the digital pixel data... (I sent an early build of this to HWman sometime ago)
EDIT: due to RAM addressable testing the program now takes a looooong time before showing something...
Posted: Thu Feb 21, 2008 6:42 pm
by TmEE co.(TM)
How long is looooong ? I tried on my MD1 and MD2 and I got nothing after a minute of waiting...
Posted: Thu Feb 21, 2008 7:03 pm
by Jorge Nuno
Can you wait for 3 minutes
? Unless you tell me a better way of testing how much RAM is available
...
Also I've just uploaded a new version, it should be a little faster in the initialization...
Posted: Thu Feb 21, 2008 8:54 pm
by Stef
Jorge Nuno wrote:Can you wait for 3 minutes
? Unless you tell me a better way of testing how much RAM is available
...
Also I've just uploaded a new version, it should be a little faster in the initialization...
3mn for RAM checking ???
Can't you just test one byte each 256 bytes of the memory map ?
If you have RAM, you can assume the block size is at least 256 bytes