[jallib] [jallib build] buildbot success in jallib on jallib-standard

2021-10-02 Thread build 
Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason: 
Build Source Stamp: HEAD
Blamelist: rob.jansen

Build succeeded!
Logs are attached.

sincerely,
 -The Buildbot

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/E1mWqV7-0006DK-FV%40casadeyork.com.
Updating '.':

UU   CHANGELOG

UU   TORELEASE

UU   include/external/rtc/rtc_ds3231.jal

Dsample/16f1823_rtc_ds3231.jal

Asample/16f1825_rtc_ds3231.jal

Updated to revision 3767.

2164 samples to validate...

1117 libraries to validate...

All files validated :)

Environment config

JALLIB_ROOT=/home/mattschinkel/jallib/slave/standard/build

JALLIB_REPOS=/home/mattschinkel/jallib/slave/standard/build/include

JALLIB_SAMPLEDIR=/home/mattschinkel/jallib/slave/standard/build/sample

JALLIB_JALV2=/home/mattschinkel/bin/jalv2

JALLIB_PYTHON=python2.7



Time duration: 354 secs

jal jalv25r5 (compiled Sep 23 2021)

Required parameter to hex is missing!

no source file, use /home/mattschinkel/bin/jalv2 --help for help

Error while compiling file (status=1).

See previous message.

2164 samples to compile...

All samples compile :)

Environment config

JALLIB_ROOT=/home/mattschinkel/jallib/slave/standard/build

JALLIB_REPOS=/home/mattschinkel/jallib/slave/standard/build/include

JALLIB_SAMPLEDIR=/home/mattschinkel/jallib/slave/standard/build/sample

JALLIB_JALV2=/home/mattschinkel/bin/jalv2

JALLIB_PYTHON=python2.7



Time duration: 1759 secs

[jallib] [jallib/jallib] 0a6bd3: Update of DS3231 RTC library with alarm functional...

2021-10-02 Thread 'Rob Jansen' via jallib 
  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: 0a6bd3637b9046eb5ea1d7e787be8e0b1e0ba1b5
  
https://github.com/jallib/jallib/commit/0a6bd3637b9046eb5ea1d7e787be8e0b1e0ba1b5
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2021-10-02 (Sat, 02 Oct 2021)

  Changed paths:
M CHANGELOG
M TORELEASE
M include/external/rtc/rtc_ds3231.jal
R sample/16f1823_rtc_ds3231.jal
A sample/16f1825_rtc_ds3231.jal

  Log Message:
  ---
  Update of DS3231 RTC library with alarm functionality.

Also changed sample file from 16f1823 to 16f1825.


-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/jallib/jallib/push/refs/heads/master/1974e2-0a6bd3%40github.com.

Re: [jallib] interrupt on change issue

2021-10-02 Thread Rob Hamerling 


Hi Vasili,

On 01/10/2021 13.11, vsurducan wrote:

Hi Rob and Rob, :)
I've tried with or without ISR, with AND IOCAP reset or normal IOCAP 
reset. This IOC is erratic and has a lot of latency. The RDY_IN signal 
is 20ms square 50% duty cycle, the RDY_OUT signal has a latency most 
of the time...but sometimes has a 20mS pulse as it should.


I'm using IOC for quadrature encoders on the wheels of an RC vehicle for 
navigation. With higher speeds the interrupt frequency is significantly 
higher then once per 20ms. Nevertheless this seems to work quite well 
(but latency is not a real issue).


Below my test with a 12F1572 and modified version of your program on a 
little board with LEDs on pins A0, A1 and A2.
The IOC of RDY_IN is handled by an interrupt routine. Both rising and 
falling edge interrupts are activated and RDY_OUT (in my setup on 
pin_A2)  is controlled in the ISR as well. The input signal for RDY_IN 
is generated in the forever loop on pin_A1. When connecting pin_A0 with 
pin_A1  RDY_OUT is following RDY_IN neatly (visual observation shows all 
3 LEDs blinking synchronously).


Hopefully this is of some help to solve your issue.

Regards, Rob.


=
alias pin_RDY_IN is pin_A0
alias pin_RDY_IN_direction is pin_A0_direction
pin_RDY_IN_direction = input
OPTION_REG_WPUEN = 0
WPUA_WPUA0 = 0 ; pull-up disabled on RA0

alias pin_RDY_OUT is pin_A2
alias pin_RDY_OUT_direction is pin_A2_direction
pin_RDY_OUT_direction = output
pin_RDY_OUT = low

alias pin_TRIGGER is pin_A1
pin_A1_direction = OUTPUT
pin_TRIGGER = low

-- main program

INTCON_GIE = high
INTCON_IOCIE = high -- enable IOC interrupts
IOCAP_IOCAP0 = high -- enable positive edge interrupts RDY_IN
IOCAN_IOCAN0 = high -- enable negative edge interrupts RDY_IN

procedure IOC() is
    pragma interrupt
    if INTCON_IOCIF then                -- IOC interrupt
    if IOCAF_IOCAF0 then    -- edge interrupt on RDY_IN
    if pin_RDY_IN then  -- was a positive edge
    pin_RDY_OUT = high
    else    -- negative edge
    pin_RDY_OUT = low
    end if
    IOCAF = IOCAF & 0xFE    -- clear IOCAF0
    end if
    INTCON_IOCIF = 0    -- reset IOC interrupt flag
    end if
end procedure

forever loop
    pin_TRIGGER = high
    delay_1ms(20)
    pin_TRIGGER = low
    delay_1ms(20)
end loop



--
*Rob H*amerling, Vianen, NL

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/24f3dc21-9e72-2932-ea0b-ed3a6a0d64e2%40gmail.com.

Re: [jallib] interrupt on change issue

2021-10-02 Thread 'Oliver Seitz' via jallib 
Hi!

That's something else, I think it's called "fast interrupt" or the like. It's 
not such an easy thing, as it restricts a project to have only *one* ISR 
(=Interrupt Service Routine), which, e.g. with the serial_hw_int_cts library is 
not possible as that library uses interrupts transparently to the user. So, 
activating that switch can be dangerous, depending on what libraries you use.

If there is one or more ISR procedures in a program, INTCON_GIE can be 
activated safely. What we were talking about is a single "fake ISR" which the 
compiler could always generate if there is no real ISR, just in case the 
program accidentally enables INTCON_GIE.

There are two philosophies:

1. Make program errors have an effect to make them visible and easier 
correctable

2. Try to hide program errors and increase reliability, doing your best to just 
keep running

IMHO I dont' really have a preference. But watchdogs and especially PPS lock 
features are clear approaches to Nr. 2.

Greets,
Kiste

 

Am Samstag, 2. Oktober 2021, 08:38:12 MESZ hat vsurducan  
Folgendes geschrieben: 





Hi Rob, Kiste,
I'm not sure on the actual compiler, but one of old pragma interrupt versions 
allows you to save, restore all registers and retfie manually at your need.
I still believe it was a great option.

On Fri, Oct 1, 2021 at 8:46 PM Rob Hamerling  wrote:
>  
>  
> Hello Kiste,
> 
> 
> On 01/10/2021 17.30, 'Oliver Seitz' via jallib wrote:
> 
> 
>> I didn't check what the compiler does if there's no 
>>interrupt service routine. Would it be smart to always waste five program 
>>words just to be sure not to accidentally restart the program? I.e., always 
>>put a RETFIE at position 0x0004 when there's no pragma interrupt?
>> 
> Yeah, I've thought about that too, but that would mask design errors. Not a 
> good idea in my opinion. 
> 
> Regards, Rob.
> 
> 
> 
> 
> -- 
> Rob Hamerling, Vianen, NL
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jallib+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jallib/d5cd970e-5e81-f278-548d-d9476f0e8dc3%40gmail.com.
> 


-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qt0LpyrKTn_f1r-Ze%3DAk%3Dfam3ika_4b4wqRAmCt924_mQ%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/246922508.716341.1633159041947%40mail.yahoo.com.

Re: [jallib] interrupt on change issue

2021-10-02 Thread vsurducan 
Hi Rob, Kiste,
I'm not sure on the actual compiler, but one of old pragma interrupt
versions allows you to save, restore all registers and retfie manually at
your need.
I still believe it was a great option.

On Fri, Oct 1, 2021 at 8:46 PM Rob Hamerling  wrote:

>
> Hello Kiste,
>
> On 01/10/2021 17.30, 'Oliver Seitz' via jallib wrote:
>
>I didn't check what the compiler does if there's no 
> interrupt service routine. Would it be smart to always waste five program 
> words just to be sure not to accidentally restart the program? I.e., always 
> put a RETFIE at position 0x0004 when there's no pragma interrupt?
>
> Yeah, I've thought about that too, but that would mask design errors. Not
> a good idea in my opinion.
>
> Regards, Rob.
>
>
>
> --
> *Rob H*amerling, Vianen, NL
>
> --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jallib+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/d5cd970e-5e81-f278-548d-d9476f0e8dc3%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qt0LpyrKTn_f1r-Ze%3DAk%3Dfam3ika_4b4wqRAmCt924_mQ%40mail.gmail.com.