Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > 64tass v1.45 bug
2006-04-16 16:42
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.
2006-04-16 17:48
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.
2006-04-16 17:57
ready.

Registered: Feb 2003
Posts: 441
Thanx man, now it works fine!

Ready.
2006-04-17 01:05
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...
2006-04-18 10:27
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!!
2006-04-18 12:30
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!


;)
2006-04-18 14:24
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
2007-02-11 17:54
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.
2007-02-11 18:07
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.
2007-02-11 18:26
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?
2007-02-11 18:48
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
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Mike
Peacemaker/CENSOR/Hi..
rambo/Therapy/ Resou..
MWR/Visdom
Nordischsound/Hokuto..
Alta
DeMOSic/MS^LSD^ONS
The Human Co../Maste..
stephan-a
psych
Guests online: 136
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Mojo  (9.7)
4 Coma Light 13  (9.6)
5 Edge of Disgrace  (9.6)
6 What Is The Matrix 2  (9.6)
7 The Demo Coder  (9.6)
8 Uncensored  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 No Listen  (9.6)
2 Layers  (9.6)
3 Cubic Dream  (9.6)
4 Party Elk 2  (9.6)
5 Copper Booze  (9.6)
6 Dawnfall V1.1  (9.5)
7 Rainbow Connection  (9.5)
8 Onscreen 5k  (9.5)
9 Morph  (9.5)
10 Libertongo  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Censor Design  (9.3)
5 Triad  (9.3)
Top Webmasters
1 Slaygon  (9.6)
2 Perff  (9.6)
3 Sabbi  (9.5)
4 Morpheus  (9.4)
5 CreaMD  (9.1)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.038 sec.