This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Sunday, February 24, 2008

Re: [oopic] Re: Omp file in V6 - what is first column

Dogulas

It would appear from the OPS code which you posted that you are using
the oopic C version. I realise only now that the OPS code generated for
the C version is very different in syntax to that of the oopic version
IIB+ chip. Hence the Sub Address Finder will only work with code
generated for the IIB+ chip. I will have to modify the program to be
able to select the Target Device so that the parsing rules can be
changed. I will do this when I get a Ver C chip to play with.

Getting back to the OPS code for the C version, the string search looks
simpler as the object address uses the key "Loc" and much of the info
you are requiring are all in the same string of text nicely delimited
with spaces (ascii 32)

e.g.

C0709:020 ;Loc 41 Dim brake As New oMathI ' Brake calculation
C0710:007 ;Loc 42
C0711:000 ;Loc 43
C0712:000 ;Loc 44
C0713:000 ;Loc 45
C0714:020 ;Loc 46 Dim trekNav As New oNavConI ' Navigation object
C0715:057 ;Loc 47

where:
Loc 41 is the address of the object, brake is the object name and
oMathI is the object class

The bytes at Loc 42 to Loc 45 hold the various properties values for the
oMathI object. Remember these are packed bytes which means that a single
byte can contain more that one set of data. For example the value of the
Mode property will reside in bits 4,5 and 6 of the byte at address 42.
The Operate value is bit 7 of the same byte at address 42.

>
> I assume this is assembly
> for the embedded Pic.
>
>
No it is not assembler code. I think it is what they call tokens which
are passed to the on chip interpreter.
> If the same info is in the OPS file that is in the Omp file, I'm not
> sure I can see it. The Omp file shows not only the address, size,
> class type, and object name, but also a complete breakdown of all sub
> objects. This might be helpful if you needed to access some sub
> object's property that doesn't happen to be the default property of
> the original defined object.
>
>
As explained above the OPS code contains all that and more.

>
>
I also don't see how to determine the memory area (A,I,V,or F) to
> specify with the address.
>
I am not sure how this works, but I think the A,I,V and F refer to the 4
memory banks contained within the Pic chip.

> The only thing I don't see in the Omp file is the sub-address value.
> Is that discernable from the OPS file?
>
As explained it is not directly discernable from what I can see from
within the OPS code but of course it is available by right clicking on
the objects property...hmmm not so easily to automate this.


If you are wanting to easily test writing/reading from/to these address
with SCP, there is a tool called 'SCP Configurator' which is in the
files section of this group. It is a graphical terminal interface which
I developed a few years back when I was learning how to use SCP.

What language are you using for your applications? I use VB6 at the moment.

Regards

Ian


Yahoo! Groups Links

<*> To visit your group on the web, go to:

http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:

http://groups.yahoo.com/group/oopic/join

(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

http://docs.yahoo.com/info/terms/

No comments: