Thanks Peter V,

That solved that problem. Now, I am going to start looking at what you got here, may take awhile. As for the implementation to SX/B, input from other people may be required for this, any ideas. My first attempt at that is failing miserably.

Thanks again

Ray

Here is a description of used variables.
You can load it in the sxkey editor (tabs are used to format the text)
to keep the formatting.

regards peter

Post Edited (Peter Verkaik) : 1/6/2006 6:31:04 PM GMT

Ray,
My library was intended for assembly and make it easier to use VP's.
VP's have an isr part that runs independantly and usually do the hardware I/O,
its main code part uses flags and buffers to send and receive data or setting
parameters, for example for PWM. SX/B commands can not create a VP
with a single command, whereas macros can, as this as done by the library.
The mechanisms in the library show a way how to do that.
Normal commands can of course also be written as macros. The library
shows how a single piece of code (eg. a single command) is inserted
only once, any duplicate use of such a command would merely call
this single piece of code. Also note that those pieces of code can be
called from anywhere as a jump to that code is placed in the lower half
of a page (SX/B uses this also when you declare a SUB in advance).
With a macro you don't need to declare its use in advance.
So its quite possible to wrap the assembly code of an SX/B command
into a macro.
Like you, I don't think the library can be made SX/B compatible,
as we don't know how SX/B develops in the future. However, SX/B could
implement a mechanism as shown in the library, to have VP commands in SX/B,
much like the Javelin Stamp has. But that is up to the SX/B developers.
But it could be done.

regards peter

Since the subject of VP's has been mentioned within this thread, I would like to see a definition of what a VP is. I have looked at the code for the SPI, I2C, and it does not mention specifically what a VP is supposed to be doing. I have my own idea, the VP runs within an interrupt independently from everything else, but that means very little to me.

So, would somebody care to enlighten me on the subject, I keep thinking that this is something that is very important, and should not be left out of SX/B, or asm for that matter. I might be making a bigger deal of this than should be.

Thanks to anybody that wants to give it shot.

Ray 

Thanks, I certainly got a better understanding of a VP. Now, thinking about the library, I think that probably the VP's would be in a separate library, and commands, or custom stuff would be in another file. Since their is a nine file limit, their has to be some thought put into how and what goes into what file.

After reading the posts for the VP's, I can see a real need for being able to implement VP's within SX/B. In the very near future I want to test and experiment with the Sharp IR sensors, as it turns out the sensor needs access to an ADC chip. So, now if I have an A/D VP, I could eliminate the need for one or multiple amounts of ADC chips. I could do experiments like, running three sensors of one A/D VP, or have three A/D VP's running that would service a sensor, or ...

As for taking the library concept from theory to real application, I have an idea for this. As soon as I get the big picture resolved, I will post it, and then we can go from there. I like to use and implement the KISS principle, so I am thinking in terms of something that is real simple to start, but can cover both the asm, and SX/B aspect.

Thanks

Ray

So, here is my idea, below I have inserted a piece of code that I used in another thread. This is the standard pause, turn on an led, and then pause, turn off the led. The reason I chose this example is because it is pretty simple in code style, and it has an element to it where it could be used in asm, and SX/B

What I am talking about is the pause command aspect. In SX/B I noticed that the code is not optimized, and it has been stated many times before that SX/B is a learning tool, and the compiler is not optimized. What that means is, when you use the pause command, I will just stick with that command for the time being, in SX/B it is like a macro, the code, that makes up the pause command, gets used, or expanded, with each use of pause.

So, what I am thinking is that, first off, piddle with the pause part of the listed code so it looks like a command, name the command wait. That way we could have a good example of a macro wrapper implementing a subroutine, that could be the profile for all other entries into the lib. Then discuss where in the main code you would have to put the include statement, and what the structure of the new wait command is supposed to look like within the include file.

The reason I chose the pause or wait as the candidate, is because once the wait command gets worked out in asm then it could be tried out as an optimized replacement for the pause command in SX/B. That way it would be a learning experience as to how to use a library with SX/B. I left the code example in SX52 format, but it is a very simple task to make it work in SX28 format.

Any ideas, maybe somebody has a better suggestion.

Thanks

Ray

******CODE

For starters I guess:

WAIT macro

call _wait

endmacro

_wait:

Loop    ;If I remember correctly this would time in at 1.3 seconds at 50MHz
          ; one of the improvements could be to make this 1 second at all frequencies.
 decsz Counter1
   jmp Loop
 decsz Counter2
   jmp Loop
 decsz Counter3
   jmp Loop

ret

************************************

;;;
;; Tut003.src
;;;

device sx52
device oschs3      ;High speed crystal, 1MHz - 75MHz
IRC_CAL IRC_FAST   ;For use with external crystal/oscillator
freq 50_000_000

reset Main                 ;Label where the program starts

;Data memory

;org $08
 org $0A            ;SX52 -> $0A, SX28 -> $08 Data memory
                           ;                         satrt
Counter1 ds 1
Counter2 ds 1
Counter3 ds 1
;End of data

;Code memory
 org $0             ;Code memory start position
Main
 mov w,#$1f         ;
 mov m,w
 mov !rd,#%11111110

Loop
 
 decsz Counter1
   jmp Loop
 decsz Counter2
   jmp Loop
 decsz Counter3
   jmp Loop
 clrb rd.0

Loop1
      decsz Counter1
   jmp Loop1
 decsz Counter2
   jmp Loop1
 decsz Counter3
   jmp Loop1
 setb rd.0
 jmp Loop

jmp $      ;I like to use this to end my code
           ;at this point it is in endless loop.
end

SX/B Syntax: PAUSE Value1 {[, | *] Value2}