This is an archived, read-only copy of the United-TI subforum , including posts and topic from May 2003 to April 2012. If you would like to discuss any of the topics in this forum, you can visit Cemetech's
z80 & ez80 Assembly subforum. Some of these topics may also be directly-linked to active Cemetech topics. If you are a Cemetech member with a linked United-TI account, you can link United-TI topics here with your current Cemetech topics.
Z80 & 68k Assembly =>
z80 & ez80 Assembly
Author |
Message |
|
Lindenk
Newbie
Joined: 28 Jul 2009 Posts: 3
|
Posted: 28 Aug 2009 11:28:45 am Post subject: |
|
|
For some reason when I try to assemble my ~11k of code TASM and ObjHex outputs a 97k hex file mostly made up of 0's. I've made a simple hello world program to test it and the output on my calculator's screen was something like "llling..." which obviously isn't right so I even tried using one out of a tutorial which gave me the same output. Reinstalling TASM and ObjHex and TI83Plus.inc hasn't changed anything and manually defining my bcalls instead of using the include file didn't work either...
Does anyone have any idea what I should do? |
|
Back to top |
|
|
Graphmastur
Advanced Member
Joined: 25 Mar 2009 Posts: 360
|
Posted: 28 Aug 2009 04:32:23 pm Post subject: |
|
|
You did not add this:
.nolist
#include "ti83plus.inc"
.list
You also didn't do:
.org $9D93
.db $BB, $6D
oh, and instead of this:
_ClrLCDFull =4540h
You would need to do this:
.define _ClrLCDFull 4540h
But that is only if you want to use your own customized variables. Did TASM give any errors? What seems to have happened is that TASM created the file, but didn't really write anything. |
|
Back to top |
|
|
Lindenk
Newbie
Joined: 28 Jul 2009 Posts: 3
|
Posted: 28 Aug 2009 04:58:50 pm Post subject: |
|
|
I was using the include file but i thought I'd try to see if it would make a diffenence if i defined them myself. The output was the same and I didn't get any errors so I'm assuming it works...
Here's what it gives me in hex |
|
Back to top |
|
|
FloppusMaximus
Advanced Member
Joined: 22 Aug 2008 Posts: 472
|
Posted: 28 Aug 2009 07:10:14 pm Post subject: |
|
|
To begin with, you have a whole bunch of code placed before the .org statment. The .org needs to be placed before the code, so that the assembler knows where in memory the code is supposed to be loaded.
Second, the first line of code in the program (after the shell header, if any) is the first thing that will be executed. I rather suspect that 'PutSprite' is intended to be a subroutine, not your main program, so it should not be the first thing in the file. |
|
Back to top |
|
|
Lindenk
Newbie
Joined: 28 Jul 2009 Posts: 3
|
Posted: 28 Aug 2009 09:54:38 pm Post subject: |
|
|
Oh wow, I didn't expect that to make that much of a difference...
Thanks, I really feel like a noob right about now |
|
Back to top |
|
|
|
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.
»
Go to Registration page