Now what?
Bruce Plecan
nacelp at bright.net
Tue May 25 20:39:27 GMT 1999
OK, for grins lets make believe I got something that says what the ALDL code
looks like, ie the list of erroe codes first, how does that get me from
where I am?, to reading code?.
Grumpy
| > | Looking at the code is really the only way to figure out things.
| > Is not this re-edit just the coded part?.
| Yes that is some of the code. I am not sure there is enough for it to
| be all of the code. On mine there was a considerable ammount of code
| 0xA000- 0xFFFF was pretty much all code.
> If
| > | you have the ALDL output stream that is a good place to start.
| >
| > Meaning using Gcar?.
|
| I am not familiar with Gcar. What you really need is the description
| of the ALDL outputed data stream. THen you figure out what code
| outputs the ALDL data, and you figure out where that code gets the
| data from. At the point you know where the data came from, you know
| where some of the internal data is stored. From that you can
| generally figure out where some of the related data is gotten from, or
| stored to.
| Roger
| > Grumpy
| > | Roger
| > | > snip
| > | > 90FC L90FC: pulx What needs to be done with this to make
sense
| > of
| > | > it??
| > | > 90FD pulx
| > | > 90FE pula
| > | > 90FF pulb
| > | > 9100 ins
| > | > 9101 rts
More information about the Gmecm
mailing list