[TI ASM] Problems assembling

[CompWiz]

I'm sure I'm doing something very simple wrong. I'm starting in on the asm in 28 days guide after doing some with the assembly programming basics guide a few months ago. I set up the folder exactly how the 28 days said to, but when I tried to assemble the hello world program, tasm gave me errors. I copied it directly out of the guide, so it wasn't a typing error. I then tried to compile the first program from assembly programing basics, and it assembled with no errors. However, devpack said that the file was not found. I didn't get any output. Here is the text of both programs, as well as a picture of the DOS output and the contents of the assembler folder.

28 days hello world program

Code: Select all

.nolist
#include "ti83plus.inc"
#define    ProgStart    $9D95
.list
.org    ProgStart - 2
    .db    t2ByteTok, tAsmCmp
    b_call(_ClrLCDFull)
    ld    hl, 0
    ld    (PenCol), hl
    ld    hl, msg
    b_call(_PutS)            ; Display the text
    b_call(_NewLine)
    ret

msg:
    .db "Hello world!", 0
.end
.end

assembly programming basics first program

Code: Select all

#define B_CALL(xxxx)	rst 28h \ .dw xxxx		;This defines the two macros, bcall and bjump
#define B_JUMP(xxxx)	call 50h \ .dw xxxx		;Don't worry about bjump too much because you won't you use it very often

_clrlcdfull		=4540h			;The calls we will be using are defined here
_homeup		=4558h

	.org	9D95h			;This tells the calculator that the program will start at the mem adress 9D95h

	B_CALL(_homeup)		;Bringing up the home screen
	B_CALL(_clrlcdfull)				;Clearing the screen
	ret				;Returning to TI-OS
.end					;End of program
END

[Jim e]

That first program needs the macro B_CALL defined.

For your second program, it didn't find the output from tasm, so if you could show the contents of the batch file that would help.

[threefingeredguy]

You could also use Spasm+Wabbit. My batchfile for that is [quote="MakeSSP.bat]assembler ssptwo.z80 ssptwo.bin
wabbit ssptwo.bin ssptwo.8xp[/quote]and I am thinking about adding a line to send it to PindurTI. Then you don't have to worry about many of tasm's problems.

Your problem though is that Sigma uses a different include file. Try "bcall" instead of "B_CALL".

[CompWiz]

ok, I got the hello world program working, thanks. changing the B-CALL to bcall did it.

Isn't wabbit for apps only?

Does anyone know where I can find the latest version of latenite?

[NanoWar]

Wabbit is also a devpack replacement and can produce .8xp files.

Scan the Latenite thread for a link.

[kv83]

Does anyone know where I can find the latest version of latenite?

You may want to wait a few days, since a new version is on the move i believe. It will fix quite a few "minor" bugs in it. If you can't wait, you'll find it in the LateNite thread somewhere on the last 5 pages iirc

[benryves]

Download for Latenite is here; http://benryves.com/bin/latenite/
Contains very outdated version of Brass + templates, so (as kv suggested) probably best to stick to Notepad for the moment until I get the 1.0.6.0 released.

If you use Brass, chuck .binarymode ti8x somewhere in your source then asseble with "Brass <sourcefile.asm>", and it'll spit out a .8xp.

[CompWiz]

Ok, I'll stick with notepad until the new version of latenite comes out. Thanks all.

[Liazon]

CompWhiz: check to make sure you have the latest version of ti83plus.inc. Some of the old versions screw up TASM32

[benryves]

The official version won't work either unless you add a "#define EQU .equ" in there, delete half of the labels (it contains two copies of each label, one in mixed case, one in lower case) and delete all the macros it has defined in it (which are ZDS syntax). Look around on ticalc.org for devpacks containing a TASM-converted include file (or use something like Dwedit's include file, which is also TASM friendly).

[CompWiz]

yeah, I downloaded the one that said it was set up for tasm.