Search the web
Sign In
New User? Sign Up
vmu-dev · The VMU Development list
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
[vmu] Please COMMENT your stuff...   Message List  
Reply | Forward Message #132 of 1156 |
Re: comments

On 26 Mar 00, marcus@... (Marcus Comstedt) wrote:

> > Well, as it looks to me, you are pushing the 16 bit address onto the stack
> > which follows the JMPF instruction at address $0122. Since you said that
> > the "unlimited flash write" function in the firmware doesn't have code to
> > switch back to the game, I assume it just ends with a RET. So the address
> > you pushed onto the stack is used as a 'return address', thus continuing
> > execution at the point in the firmware where the documented routine for
> > "read flash rom" resides. And after that is done, it switches us back to
> > the game. Neat.
>
> Spot on. Almost. What you got wrong is just that $0123 is not
> precisely the location of the "read flash rom" function. The function
> starts at $0120 (which is why this is the target of the JMPF), and looks
> like this:
>
> 0120- 20 e0 27 | int120link: CALLF LE027
> 0123- b8 0d | NOT1 EXT, 0
> 0125- 21 01 25 | JMPF L0125

Uh... guess I simply read your code wrong, then. At first glance it
looked to me as if you were pushing the contents of Rom location $0123 and
$0124 onto the stack (which contain #$01 and #$20, the two values directly
following the #$21 value of the JMPF instruction), while actually you were
just pushing the lo- and hi-byte of the 16 bit value #$0123 onto the
stack...

The usage of your Assembler still confuses me at times. Is there a manual
available somewhere that describes its usage a little more detailled?

> Since the address that was pushed to the stack
> is $0123 and not $0120, the $E027 function is never called, and I only
> get the return back to the game.

Yup... now I see. ;)

Bye


Alessandro
---
You get what anyone gets. You get a lifetime.



Thu Apr 6, 2000 3:52 am

tyro@...
Send Email Send Email

Forward
Message #132 of 1156 |
Expand Messages Author Sort by Date

Hello. Just wanted to mention it... when anyone of you posts source code, even if it's only a small part, PLEASE COMMENT IT, preferably EVERY SINGLE LINE! ...
Alessandro Sanasi
tyro@...
Send Email
Mar 7, 2000
2:25 am

tyr-@... (alessandro sanasi) wrote: original article:http://www.egroups.com/group/vmu-dev/?start=51 ... Those kind of comments are in IMO worse...
Marcus Comstedt
marcus@...
Send Email
Mar 7, 2000
2:14 pm

... Agreed. Of course it's better to actually write what purpose an instruction has instead of just explaining the function. But I also think that when the...
Alessandro Sanasi
tyro@...
Send Email
Mar 19, 2000
10:23 pm

tyr-@... (alessandro sanasi) wrote: original article:http://www.egroups.com/group/vmu-dev/?start=83 ... stack ... that ... code to ... address ... ...
Marcus Comstedt
marcus@...
Send Email
Mar 26, 2000
11:41 pm

... Uh... guess I simply read your code wrong, then. At first glance it looked to me as if you were pushing the contents of Rom location $0123 and $0124 onto...
tyro@...
Send Email
Apr 6, 2000
2:54 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help