| |
ready.
Registered: Feb 2003 Posts: 441 |
64tass v1.45 bug
Using 64tass v1.45 or earlier by Breeze and Singular (64TASS V1.45), I can't compile the illegal op code ANC. I need:
....
lda ($2e),y
anc #$ff
ror
....
I have managed 64tass to compile the ANC op code in this way:
....
lda ($2e),y
.byte $0b, $ff
ror
....
In this way it works fine. Hope this can be helpful for a new version of 64tass.
BR,
Ready. |
|
| |
WVL
Registered: Mar 2002 Posts: 902 |
did you use the option -i while compiling?
i, --m6502 NMOS 65xx
Selects NMOS 6502. Enables extra illegal opcodes. Useful for demo coding for C64, disk drive code, etc.
|
| |
ready.
Registered: Feb 2003 Posts: 441 |
Thanx man, now it works fine!
Ready. |
| |
The Phantom
Registered: Jan 2004 Posts: 360 |
Hmph.. So that's how it's done...
Was always afraid to ask why the illegal opcodes never worked in my code, only because most of you guys come down hard on newbie old schoolers as myself... |
| |
ready.
Registered: Feb 2003 Posts: 441 |
Glad my "silly" question helped you. Sometimes newbies like me need to put aside their ego and be careless about other people bad comments or insults. But I'm glad there are still people who are always ready to help newbies even in their most "simple and silly" problems!! |
| |
TNT Account closed
Registered: Oct 2004 Posts: 189 |
Yes, it's stupid to give important files names like "readme" or "readme.html". Who in their right mind would guess that searching "illegal" in either of those files would reveal the sacred secret of -i switch!
;)
|
| |
ready.
Registered: Feb 2003 Posts: 441 |
I must admit I'm always too lazy to go through the readme files. Too lazy even to to a search for "illegal". Mea culpa |
| |
ready.
Registered: Feb 2003 Posts: 441 |
Hello,
back again on another problem with TASM, but this time I read the readme file, still it did not help.
I get the following message while compiling:
Ooops! Too many passes...
I can't find it into the error lists in the readme.txt
It is strange since it does not seem to be caused by the excessive length of my source code. In fact cutting a certain part of it does not eliminate the message, but simply deleting a single instruction in the right place fixes the problem.
Any sugestion?
thanks,
Ready. |
| |
Scout
Registered: Dec 2002 Posts: 1570 |
Quote: Hello,
back again on another problem with TASM, but this time I read the readme file, still it did not help.
I get the following message while compiling:
Ooops! Too many passes...
I can't find it into the error lists in the readme.txt
It is strange since it does not seem to be caused by the excessive length of my source code. In fact cutting a certain part of it does not eliminate the message, but simply deleting a single instruction in the right place fixes the problem.
Any sugestion?
thanks,
Ready.
This sounds like a bug alright but maybe you can solve this using the .align $0100 command.
Put it somewhere near the area where it goes wrong. |
| |
WVL
Registered: Mar 2002 Posts: 902 |
U-oh.. that's a real bug somewhere, yes :) I had it happen sometimes too, but could never pinpoint where it was coming from. I contacted SoCi about this once, and (iirc) he said he was aware of it, but wanted some sources that would reproduce the error.
Unfortunately, I just kept adding code and the error disappeared by itself again, so I couldnt send a source that had problems. (You might try switching to v1.44 or earlier, that helped me out anyway).
If your source still has problems, why not send it in to Soci? |
| |
ready.
Registered: Feb 2003 Posts: 441 |
Hi,
I experienced the same situation as you, WVL, while coding the plotting part of Aurora for Level64. The message popped out, then after adding some code it went away.
Now I have just fixed it thanks to Scout's hint. I did not use .align $0100, but he made me think about some branch problem. I had:
...
cmp dx
bpl label1
...
...
label1
...
and it gave the problem. Then I tried:
...
cmp dx
bmi label2
jmp label1
label2
...
...
label1
...
and 64TASS compiled it fine. I guess you can try the same, by chaning branch codes into jump codes while developing your code, then once it is done, try to change each jump back to branch.
In case I have more about it, I'll write it here.
Ready. |
... 17 posts hidden. Click here to view all posts.... |
Previous - 1 | 2 | 3 - Next |