|
Post by mog42 on Mar 20, 2002 16:26:28 GMT -5
I tried using TASM, but it always said it found errors and it never outputted a .hex file. I know there weren't bugs in the program because I copied it from a tutorial. I also followed the directions for creating asm.bat and start.bat files. Anyways, I downloaded a different tutorial that recommended using ZiLOG Developement Studio. I haven't had any problems compiling programs with it, but it does take up about 10 megs of hard drive space and it takes a while to download.
|
|
|
Post by Chris on Mar 24, 2002 14:01:18 GMT -5
if u want tasm to output .hex files, u can configure it to use objhex instead of devpack 8x, i already have a .zip file with everything in it, let me know if u want me 2 send it
|
|
|
Post by feamsr00 on Mar 24, 2002 23:37:01 GMT -5
Im currious to see exactly how hard is to make a complier. Im pretty fluent in C++, so does anyone have or can tell me where to find the opcodes for the 83+?
|
|
|
Post by Chris on Mar 25, 2002 11:40:44 GMT -5
ticalc.org, but the tasm isn't the part that outputs the hex code, that is done by objhex or obj83, i'm pretty sure i know what tasm does, but i really don't know how to explain it in words that anybody would understand btw i'm not trying to say that anybody is dumb, it's just that i was never good at explaining things, and i'm not quite sure how to word this so it can make sense to anyone (even me)
|
|
|
Post by feamsr00 on Mar 25, 2002 21:17:06 GMT -5
Its ok, I know exactly how you feel.
|
|
|
Post by Jbirk on Mar 29, 2002 3:28:23 GMT -5
Use objhex, or obj83 to output in hex. The reason you got errors is because TASM didn't recognize a line call, or syntax.
You can't use a bcall that isn't defined...ect.
|
|
|
Post by Chris on Mar 30, 2002 11:04:00 GMT -5
didn't i already say to use objhex or obj83 somewhere in this thread?
|
|
|
Post by Jbirk on Mar 30, 2002 17:45:23 GMT -5
Yes, you did and you were right, objhex or obj83 convets the binary to hex. What more is there to say?
|
|
|
Post by mog42 on Apr 1, 2002 16:32:17 GMT -5
Oh, I forgot to mention that I did have objhex in the TASM folder, which was why I was confused when it didn't output a .hex file.
|
|
|
Post by Jbirk on Apr 2, 2002 1:50:21 GMT -5
try: objhex filename.bin > filename.hex
|
|
|
Post by The encapturer on Apr 2, 2002 14:38:41 GMT -5
I'm just wondering, what would be the alternative to using TASM? Everything I tried used it somewhere.
|
|
|
Post by Jbirk on Apr 3, 2002 2:35:57 GMT -5
An alternative to TASM woud be ZDS. You would then have to change the header info to support ZDS's requiements, and adjust ti83plus.inc so that it is compatable with ZDS. ZDS is also much more case sensitive than TASM. You would still need devpac8x or objhex though.
BTW, TASM is so versitile, I created an application with it!
|
|
|
Post by The encapturer on Apr 5, 2002 15:36:12 GMT -5
OK, so I completely understand about TASM and ZDS. I'm guessing there are no others that are useful. Am I right?
|
|
|
Post by Jbirk on Apr 6, 2002 4:07:50 GMT -5
No, there are a ton of Z80 compilers and linkers that would work perfectly for compiling calc programs. Just search your favorite search engine for Z80 assemblers, and you will be given a bunch.
All I was saying above is that TASM and ZDS seem to be the most popular assemblers for use on the calculator. Tasm is my favorite, but ZDS is actually created by Zilog the makers of the Z80180 chip in your calc, thus it is probably safe to assume that the ZDS assembler can assemble even the most archaic of z80 instructions... The instructions that TASM doesn't understand can be added by editing the .tab file containing all the commands and there op codes; for example, ret is defined as C9!
|
|
|
Post by The encapturer on Apr 9, 2002 12:19:53 GMT -5
Hmmm... Very nice. Thanks for the information.
|
|