On 9 Oct 2008, at 18:27 , Sebastien Lelong wrote:

>
>> These are defined in Rob's device file use guide, right ?
>
> And where can I read that?
>
> See jalapi, "device files" in the menu.
> http://jallib.googlecode.com/svn/trunk/unvalidated/doc/html/index.html

Never been there. Wonderful documentation. Let me start nitpicking  
right away:

>                       +----------+   +-----------+
>                       | device   |   |  general  |
>                       | specific |---|  include  |
>                       | include  |   |chipdef.jal|
>                       +----------+   +-----------+

It ain't called chipdef.jal anymore.

Also:

>  var  volatile  byte  TRISA  at  <addr>

Why? TRIS will not change other than by code. Peripheral setting will  
override the TRIS function, but not change TRIS.

>       HS_PLL          - as HS + PLL
>       HS_USB          - as HS + USB
>       EC_CLKOUT       - External Clock (TTL) signal on OSC1, OSC2  
> is ClockOut

Single dash comments?


> pwm_ccp1
> pwm_ccp2
> pwm_ccp3
> pwm_ccp4
> pwm_ccp5

Is a good example of hacking the same lib for different outputs. I  
propose this is the way to do it for, say, multiple LCDs.

There should be metatags for pins and ports that must be declared  
*before* including the lib, like "-- Declarations".

But it does not answer my question: how shall we name the PIC pins  
that are needed to control an *external* device.

My proposal: name them according to the device pins they are  
connected to, like:

        var bit TC77_SIO is pin_c4
        pin_c4_direction = input

        var bit TC77_SCK is pin_c5
        pin_c5_direction = output






---
ir EE van Andel [EMAIL PROTECTED]  http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to