Hi,
I have experience in ti-basic, and I want to move on to assembly programming, but I just can't find guides for it.
The other guides I found are mostly for other versions like the ti-83 and don't work on my ti-84.
I really appreciate any help.

Asm in 28 days will get you going on the correct path, and the Doors CSE SDK will set you up on compiling. The difference that I'm aware of between monochrome and the color calc is how you call upon the lcd. There might be other smaller ones, but you'll have to wait on one of the asm gurus to pop in to answer them. If you have further questions, feel free to ask away!

I have tested this code which came from here:
https://www.youtube.com/watch?v=etdKnhwWtwA

but I think it is only for ti 83 because something is wrong with it i think it is the bcall thats not working
AsmPrgm84C
219F9D
EF0A45
EF2E45
C9
48692100

besides i have tested learning asm in 28 days the first hello world code doesn't work

Be more specific than "doesn't work".

There are a few important differences for the CSE:

• Lots of things change address, so you need ti84pcse.inc rather than ti83plus.inc. You can get this from the DCSE 8 SDK.
  
• The identifying token for asm programs is different. (tAsm84CCmp)
  
• Many bcalls aren't available because we haven't discovered where they moved to yet.
  
• The display works in an entirely different fashion.

"Hello World" for CSE, since it doesn't need to change much:
Code:

Oh and can you also tell me what the editing program is?

You can use any text editor, such as Notepad, Notepad++, Programmer's Notepad, Text Wrangler, Sublime--whatever.

And I also want to know hex code not just z80.

You should also note that http://wikiti.brandonw.net/index.php?title=Calculator_Documentation is a great resource that outlines a lot of the hardware differences between the z80 line of calcs.

Thank you Tari, I hadn't had a chance to post my questions but I was sure there had to be something wrong with the code, it was giving me syntax errors.

What do you mean by this sentence? "Hex code" is not a programming language, it's a method of representing numbers. If you mean that you want to program in machine language by memorizing hexadecimal opcodes, rather than using an assembler, this sounds like a terrible idea in almost all circumstances for two reasons:
a) There's a 1-1 correspondence between assembly code and machine code. Assembly literally consists of assigning mnemonics to different instructions, because the human brain remembers language better than numbers. If you have access to a computer, there's no reason not to let it remember the mapping for you.
b) Hexadecimal representation of machine code by itself actually tells you very little about what the opcode is doing, making it more difficult to memorize. If you really really want to learn and understand machine code, learn the binary representation, which in many cases actually conveys information about the structure of the opcode and the arguments it takes. From binary it's trivial to convert into whatever representation is required.

Using hex code on the calculator. I'm just interested in knowing it.

Then still (b) applies.

You can also assemble the code and look at the hex output from the assembler. If you have it produce a listing (.lst) file, you'll have the memory address, the hex code, and the assembly mnemonic all side by side. I'd recommend writing your code on the computer and if absolutely necessary copy the hex code from the listing or uncompressed hex output. But it's probably worth it just to spend the $5 on a link cable.

After hours, finally find this one Ti84+cse assembly programming source that actually work, with minor issues ...

1) Seems the "Hell" is deleted or not shown. But if you add words "Hello World, from ABC", the words say "o World, from ABC" appeared.

2) Can ASM but not AsmComp( in Ti84+cse

3) I use the Doors CS7 SDK on Mac. all work except it provides a kind of not exactly "warning message" as there is no warning ... The program I named H4OK.asm and "sh compile.sh H4OK.asm"

with extra 2 lines not sure what it meant:


Code:



Full terminal list as below:


Code:


mono version as below:


Code:

${varname^^} is a bash-ism to convert the string to all uppercase, so that the output will be H4OK.8xp; since your input is already H4OK.asm, it seems like all is well. Please try using bash instead of sh if you have it available, though.

Are you using Tari's source code above?

Strange as the shebang is already #!/bin/bash as the first line of the compile.sh
and I do also
Code:
, hence I am not sure what happens.



So confusing me that actually this is this thread and why I post it here https://www.cemetech.net/forum/viewtopic.php?t=10630 and repeat here. Yes it is Teri source.


Code:


This will do it but other than the above shell issue of variable there the asm program can produce the message but you have to add 4 characters it erased!


Code:

Ah, there's an error in Tari's source. It should be:

Code:

so that the first instruction in your program falls at UserMem.

Edit: Moves the homescreen cursor row and column to the top-left corner. c.f. the 83psysroutines.pdf documentation: https://archive.org/details/pdfy-UJfjMPdvGB444Am_ .

Many thanks.

What a surprise it still work even if the memory location is moved 4 bytes in advance. Need to learn how it still work now!

The items that would be off by 4 bytes are: absolute jump targets (jp), call targets within the program (call), and memory addresses of constants and variables within the program (e.g. your str1 and str2). Straight-line code or code that only uses relative jumps (jr) is relocatable, a fact that some programs take advantage of!