PDA

View Full Version : Assm questions - getting started....



Chris_D
03-25-2009, 04:37 AM
Hello,

I am starting to work with Asm.· I have never done asm, but want to explore it on the propeller.· I have written a spin routine and am working towards converting it to asm, but need to understand what I am doing along the way.· This code below is basically nonsense at this point, but it serves as a tool to help me understand how to do things.· Below the code are my explanations of what I think should happen, I am hoping someone can take some time to clarify or correct any missunderstandings....

*******************
Dat
······················· Org 0
:Loop·················· CMPS _TenMsecFlag,CNT·· WC
············· If_N···· Jmp #:Loop
······················· Mov _TenMsecFlag, Cnt
······················· Adds _TenMsecFlag, Ten_Msec
······················· Jmp #:Loop
Ten_Msec····· Long····· 800000·····
_TenMsecFlag· RES······ 1
*******************

Dat {this line informs the prop tool that I am defining an asm routine (or other data statements)

Org 0 {informs the compiler to start at cog address zero

:Loop {is a label to which I can reference with a Jmp statement

CMPS _TenMsecFlag,CNT·· WC {This is the first of two lines needed to perform a conditional statement (IF~then).· It will compare two signed variables, checking to see if _TenMsecFlag is less than CNT and if it is, will set the C register as 1.· The WC is what actually causes the C register to be written.

If_C···· Jmp #:Loop { IF_C tests the C register and will perform the rest of the line if C =·1 (meaning that CNT is·less than _TenMsecFlag).· The JMP instruction specifies that flow is redirected to the label :LOOP.· This keeps the loop repeating until the CNT passes the _TenMsecFlag value.


Mov _TenMsecFlag, Cnt {this moves the value·at CNT into _TenMSecFlag.

Adds _TenMsecFlag, Ten_Msec {This adds the signed value of Ten_MSec (Defined lower down) to _TenMSecFlag.· With this, is sets up the target for the CNT to catch up too which should be 10 milliseconds.

Jmp #:Loop {As previous, this will redirect program flow back up to the Loop label

Ten_Msec····· Long····· 800000 { This creates a sort of constant in the form of a Long variable which is equal to 800000.

_TenMsecFlag· RES······ 1 {This reserves a single Long variable, which is local to this routine, that can be manipulated etc.

I suspect I am way off base on most of this, but it is a place to start from. So, if anyone cares to help me out, I sure would appreciate it.· I am sure there will be MANY other questions along the way too.

Thanks!

Chris


·

Ale
03-25-2009, 04:42 AM
Just two notes:

CNT is unsigned, so used the unsigned versions of everything.

RES will reserve space, so no code afterwards!. There is no concept of local variables. Just local symbols between global symbols.

The rest seems ok. I do not remember if IF_N is equivalent to IF_C though. IF_B (below) will probably serve the same purpose.

mpark
03-25-2009, 06:13 AM
I'm sure you realize that you are basically trying to duplicate the waitcnt instruction. Nothing wrong with that as an educational exercise.

You can't really compare _TenMsecFlag and CNT directly, signed or unsigned. Well, you can, it just won't do what you want.
Consider the case when incrementing _TenMsecFlag causes it to overflow. Signed or unsigned, it will be less than CNT.

The "Mov _TenMsecFlag, Cnt" after the wait loop is unnecessary and will in fact introduce a small error in the wait time. On the other hand, you'll want to initialize _TenMsecFlag before entering the loops.

Too bad you chose such a tricky task for your first foray into assembly language, but you seem to be well on your way.

mctrivia
03-25-2009, 06:47 AM
there is nothing wrong with using res like you did but I would recomend using long 0 instead as a general guideline.

They do the same thing except long 0 will let you know for sure what the starting value is and res does not. Though if you are extremely short on space res will save you a long in your final program.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Need to make your prop design easier or secure? Get a PropMod (http://propmodule.com) has crystal, eeprom, and programing header in a 40 pin dip 0.7" pitch module with uSD reader, and RTC options.

MagIO2
03-25-2009, 03:30 PM
Interesting!

Ok, mpark is right, your trying to duplicate the waitcnt. But I think in some environments it would be handy to have a own implementation of waitcnt. If you have to wait for a long time (and a 10th of a second is definitely a long time for a uC - it could exercise 2million operations in that time) it could make sense to do something else in between continuously.

In fact the problem is that CNT is a neverending counter with an ending number of possible values. So, when the limit is reached ($ffff_ffff_ffff_ffff) it starts from the beginning. So, in the area close to the wrap-around your comparation will not work. I guess you have to check the result of your add. If this wrapped around (C flag is set), you have to skip the cmp unless CNT is positive.
Have to think about that when I'm back home.

Did you understand what mpark tried to tell you in with "Mov _TenMsecFlag, Cnt" ... ?
Just want to point that out a little bit clearer for newbies:

If you do it your way, you get the counter-value at a certain point of time. The mov instruction needs 4 clocks. You don't know exactly at which of those 4 ticks the CNT is read (only Chip knows that ;o). And the commands before doing the mov need some time as well. So, in the end the time you wait will be Ten_Msec plus the runtime of the commands that have been executed since you detected the match with _TenMsecFlag. If you have a wait time which is not an even multiple with the clockticks you need for the commands this can even vary.
So, this is not good for programming a clock as the deviation grows with the runtime.

If you want the timing to be more accurate, you should do it that way:

Dat
Org 0
_TenMsecFlag mov _TenMsecFlag, CNT ' <- nice trick to save one LONG by reusing the command as variable afterwards (of course you should not run this 'code' again)
:Loop CMPS _TenMsecFlag,CNT WC ' <- this is the part I still have to think about as it does not work as desired
If_N Jmp #:Loop
Adds _TenMsecFlag, Ten_Msec ' this always adds to the last time you waited for, so the delta will be always the same
Jmp #:Loop
Ten_Msec Long 800000

Please note: Of course a self-defined waitcnt can never be as accurate as the waitcnt. CNT reached the exact value of _TenMsecFlag somewhere in the middle of executing the :Loop and the extra handling for the wraparound will not make it better. But it is only a small deviation which does not sum up.

Post Edited (MagIO2) : 3/25/2009 12:42:41 PM GMT

Chris_D
03-25-2009, 04:53 PM
Wow,· thanks much guys for the feedback.· As you noted, this code would be similar to WaitCNt, but much more usefull for stuff I do.· I am sure the waitCNT is more accurate, but having something sitting there "waiting" is not an effective use of time.· So, this routine could be placed within a larger loop and when the flag triggers every 10 milliseconds, it can perform the tasks needed at those intervals. So, in the bigger picture of events, this routine is just a mechanism to let me do things at 10 msec intervals within a larger loop that does other things much more frequently.

I can see from your comments that I am confused about a few things though.

Regarding the CNT function.· If I understand your cautions, this counter runs from 0 to the overflow of a Long $ffff_ffff_ffff_ffff as opposed to running from max negative value to max positive value?· If this is the case, then I will have to rethink the wrap around problem. For some reason, I had it in my mind that CNT was a LONG and would wrap around the same way LONGs do.· This is also the reason I went with the COMS and ADDS functions.

Now onto a few other items I need to clarify...

In the following...·· Jmp #:Loop·· ... why do I use the # symbol?·I thought I understood this but when I re-read the manual again, I got a bit confused about its use here.

This command...··· Ten_Msec····· Long····· 800000·· ...creates a Long variable (pointer) and assigns it the value of 800000.· Instead of using a variable, could I have used the literal value of 800000 in the program?



Thanks guys


Chris






·

MagIO2
03-25-2009, 05:43 PM
Without # the jump will do what every other command will do as well. It treats :Loop as an register and jump to the place the register points to. So, for indirect jumps that would be fine, but you definitely want to jump to that adress. So you want to jump to an immediate adress and immediates are prefixed with an #. So, here PASM is simply more consequent than other assemblers. But as most people started with other assembler-dialects, this is a high potential for bugs.

Immediates can only be 9 bit. So, if your Ten_Msec is only 9 bit (max. 511) wide you can use # instead. If it is bigger than you need to store this value as long somwhere.

CNT runs from 0 to $ffff_ffff_ffff_ffff and then starts from 0 again. In terms of signed values this would be a switch from MAX_NEGATIVE to 0. And another switch would be from $07fff_ffff_ffff_ffff to $1000_0000_0000_0000. That's why Ale told you that CNT is unsigned. Because this means a switch from MAX_POSITIVE to -1 in sense of signed numbers. So, when using CMP instead of CMPS you would have one problem less.

Say your CNT is $ffff_ffff_ffff_0000 when you reach your mov/add. The result would be $0000_0000_0000_B350.
If you do CMP now CNT will be bigger than that until it wrapped around. That's why you have to wait with the CMPs until CNT wrapped around. Then you would compare $0000_0000_0000_B350 against 0 and upwards, which gives you the right result.




PS: xxx -> bugfix

Post Edited (MagIO2) : 3/25/2009 12:46:02 PM GMT

Chris_D
03-25-2009, 05:59 PM
MAGIO2,· Thanks very much for the feedback!

This is starting to make more sense to me now.· Once I digest this first step a bit more I will be expanding on my quest.· I have been programming in BASIC for about 25 years now, tried C a couple times and just hated it.· But so far, Asm seems very interesting!·

Thanks!

Chris

kuroneko
03-25-2009, 06:42 PM
MagIO2 said...
CNT runs from 0 to $ffff_ffff_ffff_ffff

Make that 0 to $FFFF_FFFF.

mpark
03-25-2009, 06:44 PM
MagIO2 said...
CNT runs from 0 to $ffff_ffff_ffff_ffff and then starts from 0 again. In terms of signed values this would be a switch from MAX_NEGATIVE to 0. And another switch would be from $0fff_ffff_ffff_ffff to $1000_0000_0000_0000. That's why Ale told you that CNT is unsigned. Because this means a switch from MAX_POSITIVE to -1 in sense of signed numbers. So, when using CMP instead of CMPS you would have one problem less.

Actually, that should be·-1 to 0, so not a big deal.

You can·consider CNT signed or unsigned. In either case,·its value continually increases by 1 until a certain point when its value suddenly decreases by 232-1. The only difference is where that point is. CMP doesn't buy you anything over CMPS in this situation, imho.


·

MagIO2
03-25-2009, 07:39 PM
ups ... sorry ... dunno why i'm currently on the trip to make a long 64 bits wide ;o) And with MAX_NEGATIVE I meant the max. in sense of the absolute value. $FFFF_FFFF is -2147483648.
With CMP you only have the problem of a not working compare once. (at $ffff_ffff->$0000_0000)
With CMPS you have the problem twice. (at $ffff_ffff->$0000_0000 and at $7fff_ffff -> $1000_0000)
And I am not sure what the adds is doing when you add 800000 to $7fff_ffff. Guess the result will be with sign bit still set to 0.

Chris_D
03-25-2009, 07:59 PM
Regarding the Signed / Unsigned...

In reading through the manual, it seems to indicate that all Longs are signed but yet many operations provide for unsigned.· So then I tried searching through the manual to determine how to create an unsigned variable and didn't find anything.·

I suspect I am missing something or am confused about something regarding this.

How would I go about making an usigned variable?



Chris

Mike Green
03-25-2009, 08:31 PM
Chris_D,
Spin uses all signed arithmetic, but, for most operations, there's no difference between signed and unsigned values. In particular, addition and subtraction work the same. There's no way to tell Spin that a variable contains an unsigned 32-bit value in the range $80000000 - $FFFFFFFF. You just need to be careful about comparisons, multiplication, and division.

Chris_D
03-25-2009, 08:47 PM
Ahh, thanks for clearing that up Mike.· This will all come together for me, I just need to get my head out of BASIC and more into "the basics" of computing.·



Chris

MagIO2
03-25-2009, 08:53 PM
A long is a long ... this means that it has 32 bits nothing more and nothing less.

When we talk about signed and unsigned we talk about the usage of the bits. In unsigned usage bit 31 is a binary digit. In signed it is the bit which tells you, whether the value is negative (1) or positive (0). Because of this different meanings you need different compare, add and subtract commands.

For shorter examples I now use signed/unsigned bytes where bit 7 is the sign and this is no working code (as you can't add two immediate values), it only shows the principle

add #%01111111, #%00000001 WC -> result is %10000000 with carry not set
adds #%01111111, #%00000001 WC -> result is %00000000 with carry set (or is it %10000000 but carry is set - not sure about that currently)

cmp #%00000000, #%10000000 WC -> carry is set because %10000000 is bigger than %00000000
cmps #%00000000, #%10000000 WC -> carry is not set because %10000000 (-1) is not bigger than %00000000 (0)

Of course you should very clearly know what you do, when you mix signed and unsigned commands on the same register.

Spin seems to be a bit more restrictive in the usage of a long as the most numerical operators assume it to be signed.

Post Edited (MagIO2) : 3/25/2009 2:25:15 PM GMT

Chris_D
03-27-2009, 02:46 AM
Hmmm,

I finally got some programming time this afternoon so I wrote a very simple SPIN program to find out the range of·CNT.· While I am not sure CNT is the same in Spin or ASM, when used in this example, CNT wraps around· and starts back up at -2137508107 (obviously the timing is such that I am not printing at the exact moment of wrap around).· So I would expect that CNT wraps around the same way when used in ASM?

Chris

PUB start

· SerIO.start(31,30,0,115200)
·· Delay := 20000000
· 'start led flashing
· led.start(16)············· ' Start the led object (pin 16 flashes a VGA led on the demoboard)

· repeat·· 'loop forever more
···· WaitCnt(Delay + CNT)
···· SerIO.Dec(CNT)
···· SerIO.str(string("<",13))
····

Mike Green
03-27-2009, 02:53 AM
CNT does wrap around, going from $00000000 to $7FFFFFFF, then $80000000 to $FFFFFFFF, then back to $00000000. Spin treats these as 32-bit signed integers. Assembly has two different sets of instructions. One set treats these as signed integers. The other treats these as 32-bit unsigned integers. The differences are mostly in the meaning of the carry flag.

nohab
03-27-2009, 06:02 PM
MagIO2 said...
ups ... sorry ... dunno why i'm currently on the trip to make a long 64 bits wide ;o) And with MAX_NEGATIVE I meant the max. in sense of the absolute value. $FFFF_FFFF is -2147483648.
With CMP you only have the problem of a not working compare once. (at $ffff_ffff->$0000_0000)
With CMPS you have the problem twice. (at $ffff_ffff->$0000_0000 and at $7fff_ffff -> $1000_0000)
And I am not sure what the adds is doing when you add 800000 to $7fff_ffff. Guess the result will be with sign bit still set to 0.
According to my calculator, $FFFF_FFFF is -1 and $8000_0000 is -2147483648

/Nicke

·

MagIO2
03-27-2009, 07:10 PM
Yes, yes ... I know ... I only wanted to confuse a little bit ;o)

No .. I did not think about it hard enough. Of course it is as you said, which makes calculation easier. You still can add positive numbers to negative numbers with the right result.

Cluso99
03-27-2009, 08:44 PM
waitcnt does one more thing - it puts the cog into very low power mode. Be careful, you must add a minimum to CNT for the waitcnt to work (not wait for a wraparound whichfrom memory is about 90 seconds). I think the minimum is about 5.

Secondly, CNT is incremented on each clock cycle and an instruction takes (mostly) 4 clock cycles. So don't fall into the trap of trying to compare equal because there is a 3/4 chance it will never equal.

Thirdly, the instruction cycle pipeline is IdSDeR where I=fetch instruction fetch, d=decode (and previous instruction wRiteback), S=source data fetch, D=destination data fetch, e=execute instruction (and fetch next I=instruction), R=wRiteback result (and decodes next instruction),....

So your instruction Mov _TenMsecFlag, Cnt should fetch CNT on the "S" cycle.

However, the waitcnt instruction I believe CNT is compared on the "e" cycle, with the "e" cycle being repeated until a match is found.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:

· Home of the MultiBladeProps: TriBladeProp (http://forums.parallax.com/showthread.php?p=786418), SixBladeProp (http://forums.parallax.com/showthread.php?p=780033), website (Multiple propeller pcbs) (http://bluemagic.biz/cluso.htm)
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator) (http://forums.parallax.com/showthread.php?p=790917)
· Prop Tools under Development or Completed (Index) (http://forums.parallax.com/showthread.php?p=753439)
· Emulators: Micros eg Altair, and Terminals eg VT100 (Index (http://forums.parallax.com/showthread.php?p=778427))
· Search the Propeller forums (via Google) (http://search.parallax.com/search?site=parallax&client=parallax&output=xml_no_dtd&proxystylesheet=parallax&proxycustom=<HOME/>&ie=&oe=&lr=)
My cruising website is: ·www.bluemagic.biz (http://www.bluemagic.biz)·· MultiBladeProp is: www.bluemagic.biz/cluso.htm (http://www.bluemagic.biz/cluso.htm)