With the goal of learning how to use the DCS_SDK, I decided to make a simple program for the job.

Here's what happened, I tried compiling (compile myfile.z80) and everything was OK, however, the assembled programs (when opened with WabbitEmu and DCS7) are TI-Basic programs!

So, I tried a few programs to test this.

When ran using Asm(prgmNAME I always get INVALID.

Any ideas? Here are a few programs I tried:


Code:




Code:



Code:



Code:



Any ideas? I am using cmd and then "compile myfile.z80" (myfile.z80 is in the source folder) to compile.

These are just some, I tried about 10, always the same error.

EDIT: compile.bat also returns no errors in the cmd.

I'll look at this a bit more, but this stuck out to me: Don't use .org 40339, use the hexadecimal equate, $9D93. Also, that would be: compile myfile. No .z80, because the batch file automatically takes care of that.

The problem is probably your compile line. It is indeed just "compile myfile", not "compile myfile.z80" or "compile myfile.asm". My preferred header format is:


Code:
Notice that progstart is $9d93.

Code:



Code:


I get:

The proper syntax is bcall(_command), not B_CALL _command. Also, did you know that you can copy-paste text from command windows?

This. To copy and paste text, right click in the command window and choose Mark (or whatever it is in your language), select the text, and right click it again and choose Copy to copy it to your clipboard.

Kerm I'm sorry but I stopped using the DCS SDK, I got Spasm and created a simple python program customized for me that I just double click and it compiles and runs in WabbitEmu (it sends both the compiled program and DoorsCS).

It works very well for me. I'd also like to know how far including "dcs7.inc" affects my programs because I always include it (as you have in your header).

dcs7.Inc allows you to use Doors CS, MirageOS, ION, and TI-OS routines in your program.

Cool to see you're learning assembly scout it's actually extremely fun to code in, once I Relearned it again, I lost interest in learning a HLL like java

And, scout, the reason the syntax is like that for bcalls is because its not an actual instruction -- it's a macro that stands in place of the instruction RST 28h / .db xxxx

Ashbad: I learnt Assembly a few months ago, I'm relearning it now to understand it better, so I'm skipping a few things

But Java is cool Though I will agree, low level languages are a little more fun

Java is for people who aren't able to use x86 or (whatever a Mac uses) assembly xD

Though, x86 on windows is horrible, you have to be so careful and you have to set so many things up before you can even start writing

but yes, java is cool

[/off topic]

A three line batch script wrapped around the existing SDK would have done that for you, but whatever. Why didn't you ask?

What Souvik1997 said.

Yeah, but I'm happy now

Whatever. Anyway, how is your assembly-writing progressing? Did you write a massively-multiplayer CALCnet game yet?

I'll try and make a quadratic solver (with no input, I define, in the code, a,b and c) tonight. It looks a hard to do maths in Assembly though.

It's hard to do floating point math. It's easy to do integer math, and it's pretty simple to do fixed-point math. For example, to do all the parabolic calculations in Obliterate, I use 16-bit values, where the upper 8 bits are the decimal part of each number, and the lower 8 bits are the fractional part. The AI is more complex; in parts of it I needed to use 24-bit and 32-bit numbers to be able to retain enough precision for the AIs to be even moderately accurate.

Meh, I'm not gonna do that any more, since I can't deal negative numbers in Assembly.

I have learnt a lot of stuff today, loops, labels, variables (ints and strings).

I also learnt how to use hex inline Assembly, so I can use Hexadecimal, which is much better than Assembly for some stuff, not better, but cooler.

I learnt jr and jp and know the differences between the two.

Tomorrow I'll learn the F register (which I started learning now) but I didn't understand it at all.

According to Hot Dog:


Code:


The first one won't set the F register, but this:


Code:


This will, Aren't they the same????

Assembly can easily deal with negative numbers, or do you mean that you don't understand negative numbers? If it's the latter, I'd be happy to help you understand how signed numbers work in z80 ASM.

It's not better or faster for anything unless that's the way you learned (cf. Zeda).

Excellent, including limitations and size (2 bytes vs 3 bytes)?

You basically just need to worry about the results from comparisons, like z/nz and c/nc.

They do the same thing; ld a,1 \ dec a \ ld a,250 is functionally identical to ld a,250. The 'dec a' line sets the z flag, though, so I'm not sure what he's going for there.

I understand when to use jp and when to use jr. If it's a short jump, jr, if it's a long jump (impossible to be done with jr (128bytes or -128bytes)) I should use jp.

@Kerm: I know *a lot* of hex codes by heart that I prefer to use in hexadecimal rather than in mnemonics.