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

[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/E1nLvki-0002ba-Jy%40casadeyork.com.
Updating '.':

Adoc/dita/tutorials/images/logo_small.png

UU   doc/dita/tutorials/license.xml

UU   doc/dita/tutorials/tutorial_ICSP.xml

UU   doc/dita/tutorials/tutorial_adc_intro.xml

UU   doc/dita/tutorials/tutorial_blink_a_led.xml

UU   doc/dita/tutorials/tutorial_changelog.xml

UU   doc/dita/tutorials/tutorial_dfplayer.xml

UU   doc/dita/tutorials/tutorial_fat32.xml

UU   doc/dita/tutorials/tutorial_getting_started.xml

UU   doc/dita/tutorials/tutorial_gp2d02.xml

UU   doc/dita/tutorials/tutorial_i2c1.xml

UU   doc/dita/tutorials/tutorial_i2c2.xml

UU   doc/dita/tutorials/tutorial_i2c3.xml

UU   doc/dita/tutorials/tutorial_lcd.xml

UU   doc/dita/tutorials/tutorial_pata_hard_disk.xml

UU   doc/dita/tutorials/tutorial_pwm1.xml

UU   doc/dita/tutorials/tutorial_pwm2.xml

UU   doc/dita/tutorials/tutorial_pwm_intro.xml

UU   doc/dita/tutorials/tutorial_sd_card.xml

UU   doc/dita/tutorials/tutorial_servo_rc_master.xml

UU   doc/dita/tutorials/tutorial_spi_introduction.xml

UU   doc/dita/tutorials/tutorial_spi_sram_23k256.xml

UU   doc/dita/tutorials/tutorials.ditamap

Updated to revision 3815.

2727 samples to validate...

1120 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: 239 secs

jal jalv25r6 (compiled Oct 29 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.

2727 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: 1816 secs

Re: [jallib] Can you call a procedure from a main program and an interrupt?

[vsurducan]

Multiple interrupts as handled by libraries right know are generating
incontrolled jitter to any timing sensitive applications. Unfortunately
almost nothing can be doneexcept grouping everything in one interrupt
carefully controlled.

On Sun 20 Feb 2022, 5:27 PM Rob CJ  Hi Kiste,
>
> Thanks for your reply. I thought that it would work when disabling the
> interrupt but I did not think of what you said about variable reuse. That
> could have been the problem. The current I2C procedures wait for a transfer
> to be completed and the PIC is always the master so that should be OK.
>
> I agree with you better not to do this in an interrupt so I keep it as it
> is.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* 'Oliver Seitz' via jallib 
> *Verzonden:* zondag 20 februari 2022 09:26
> *Aan:* jallib@googlegroups.com 
> *Onderwerp:* Re: [jallib] Can you call a procedure from a main program
> and an interrupt?
>
> Hi Rob,
>
> it is possible to call a procedure from both the main program and  from an
> interrupt alternately, but I would try to avoid that, it's... I'd call it
> dangerous.
>
> As jal is not reentrant, you have to make absolutely sure, that no single
> part of any procedure is running twice in any case. (The only exception I
> know of are the multiplication/division functions which are safe to be
> called from an interrupt while running in the main program, but those are
> not seen as functions to the user anyway) That means, that if you use e.g.
> a print procedure inside the interrupt, you also have to disable interrupts
> each time you're using a similar print procedure in the main program. All
> decimal print procedures use the same background code, so in this sense,
> they're "the same procedure" and need to be surveyed not to run from both
> the main program and the interrupt at the same time.
>
> And, you should compile with --no-variable-reuse, as the compiler is
> probably not aware of procedures being called from an interrupt.
>
> Can be that you obeyed that rule by disabling interrupts when using I2C in
> the main program. But then, there's hardware involved. You need to make
> sure that the hardware is idle and in a reset, initialized state each time
> before enabling interrupts. I'm not so familiar with the I2C peripheral to
> decide if that's a problem. And, also all devices on the I2C bus need to be
> reset and initialized each time the interrupt is enabled.
>
> I do prefer handing over the alarm to the main program via volatile flag
> bit.
>
> Greets,
> Kiste
>
> Am Samstag, 19. Februar 2022, 09:58:53 MEZ hat rob...@hotmail.com <
> rob...@hotmail.com> Folgendes geschrieben:
>
>
> Hello all,
>
> Some time ago I made a library for the clock IC DS3231. This library is
> part of Jallib release 1.7.0.
>
> This IC has an I2C interface and is capable of handling two alarms. When
> an alarm is activated an interrupt is generated.
>
> Reading the alarm flag from the IC also uses - of course- the I2C
> interface but the I2C interface is also used by the main program.
>
> I thought that if I would disable all interrupts when calling the I2C
> routines from the main program and only enable it while not used by the
> main program that I could call the  same I2C routines from the interrupt
> routine and so be able to read the alarm flag from the IC to see if alarm 1
> or alarm 2 was activated.
>
> Unfortunately this did not work.
>
> I thought that when an interrupt is called some info is saved and after
> the interrupt restored but I also thought that I could then call any
> routine from the interrupt as long that I am certain that no I2C transfer
> was active (which should be since the interrupt is disabled when the main
> program is using the I2C routines).
>
> Any ideas why this does not work? Am I missing something?
>
> What the current sample program does is just setting a global flag in the
> interrupt routine and the main program polls this flag and then reads the
> alarm flag of the IC via I2C but this undermines a bit the use of the
> interrupt.
>
> Thanks.
>
> Kind regards,
>
> Rob
>
> --
> 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/ff12f63c-0d1d-4897-8ca4-511869ab68c0n%40googlegroups.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/1119054585.183229.1645345612576%40mail.yahoo.com
> 

Re: [jallib] Can you call a procedure from a main program and an interrupt?

[Rob CJ]

Hi Kiste,

Thanks for your reply. I thought that it would work when disabling the 
interrupt but I did not think of what you said about variable reuse. That could 
have been the problem. The current I2C procedures wait for a transfer to be 
completed and the PIC is always the master so that should be OK.

I agree with you better not to do this in an interrupt so I keep it as it is.

Kind regards,

Rob


Van: 'Oliver Seitz' via jallib 
Verzonden: zondag 20 februari 2022 09:26
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Can you call a procedure from a main program and an 
interrupt?

Hi Rob,

it is possible to call a procedure from both the main program and  from an 
interrupt alternately, but I would try to avoid that, it's... I'd call it 
dangerous.

As jal is not reentrant, you have to make absolutely sure, that no single part 
of any procedure is running twice in any case. (The only exception I know of 
are the multiplication/division functions which are safe to be called from an 
interrupt while running in the main program, but those are not seen as 
functions to the user anyway) That means, that if you use e.g. a print 
procedure inside the interrupt, you also have to disable interrupts each time 
you're using a similar print procedure in the main program. All decimal print 
procedures use the same background code, so in this sense, they're "the same 
procedure" and need to be surveyed not to run from both the main program and 
the interrupt at the same time.

And, you should compile with --no-variable-reuse, as the compiler is probably 
not aware of procedures being called from an interrupt.

Can be that you obeyed that rule by disabling interrupts when using I2C in the 
main program. But then, there's hardware involved. You need to make sure that 
the hardware is idle and in a reset, initialized state each time before 
enabling interrupts. I'm not so familiar with the I2C peripheral to decide if 
that's a problem. And, also all devices on the I2C bus need to be reset and 
initialized each time the interrupt is enabled.

I do prefer handing over the alarm to the main program via volatile flag bit.

Greets,
Kiste

Am Samstag, 19. Februar 2022, 09:58:53 MEZ hat rob...@hotmail.com 
 Folgendes geschrieben:


Hello all,

Some time ago I made a library for the clock IC DS3231. This library is part of 
Jallib release 1.7.0.

This IC has an I2C interface and is capable of handling two alarms. When an 
alarm is activated an interrupt is generated.

Reading the alarm flag from the IC also uses - of course- the I2C interface but 
the I2C interface is also used by the main program.

I thought that if I would disable all interrupts when calling the I2C routines 
from the main program and only enable it while not used by the main program 
that I could call the  same I2C routines from the interrupt routine and so be 
able to read the alarm flag from the IC to see if alarm 1 or alarm 2 was 
activated.

Unfortunately this did not work.

I thought that when an interrupt is called some info is saved and after the 
interrupt restored but I also thought that I could then call any routine from 
the interrupt as long that I am certain that no I2C transfer was active (which 
should be since the interrupt is disabled when the main program is using the 
I2C routines).

Any ideas why this does not work? Am I missing something?

What the current sample program does is just setting a global flag in the 
interrupt routine and the main program polls this flag and then reads the alarm 
flag of the IC via I2C but this undermines a bit the use of the interrupt.

Thanks.

Kind regards,

Rob


--
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/ff12f63c-0d1d-4897-8ca4-511869ab68c0n%40googlegroups.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/1119054585.183229.1645345612576%40mail.yahoo.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 

[jallib] [jallib/jallib] 66bb46: Update of Tutorial Book

['Rob Jansen' via jallib]

  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: 66bb46a38b379a361d5abfff01c996463d984bc6
  
https://github.com/jallib/jallib/commit/66bb46a38b379a361d5abfff01c996463d984bc6
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2022-02-20 (Sun, 20 Feb 2022)

  Changed paths:
A doc/dita/tutorials/images/logo_small.png
M doc/dita/tutorials/license.xml
M doc/dita/tutorials/tutorial_ICSP.xml
M doc/dita/tutorials/tutorial_adc_intro.xml
M doc/dita/tutorials/tutorial_blink_a_led.xml
M doc/dita/tutorials/tutorial_changelog.xml
M doc/dita/tutorials/tutorial_dfplayer.xml
M doc/dita/tutorials/tutorial_fat32.xml
M doc/dita/tutorials/tutorial_getting_started.xml
M doc/dita/tutorials/tutorial_gp2d02.xml
M doc/dita/tutorials/tutorial_i2c1.xml
M doc/dita/tutorials/tutorial_i2c2.xml
M doc/dita/tutorials/tutorial_i2c3.xml
M doc/dita/tutorials/tutorial_lcd.xml
M doc/dita/tutorials/tutorial_pata_hard_disk.xml
M doc/dita/tutorials/tutorial_pwm1.xml
M doc/dita/tutorials/tutorial_pwm2.xml
M doc/dita/tutorials/tutorial_pwm_intro.xml
M doc/dita/tutorials/tutorial_sd_card.xml
M doc/dita/tutorials/tutorial_servo_rc_master.xml
M doc/dita/tutorials/tutorial_spi_introduction.xml
M doc/dita/tutorials/tutorial_spi_sram_23k256.xml
M doc/dita/tutorials/tutorials.ditamap

  Log Message:
  ---
  Update of Tutorial Book

All tutorials are up to date and all broken links have been updated or removed.


-- 
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/a449fb-66bb46%40github.com.

Re: [jallib] Can you call a procedure from a main program and an interrupt?

['Oliver Seitz' via jallib]

 Hi Rob,
it is possible to call a procedure from both the main program and  from an 
interrupt alternately, but I would try to avoid that, it's... I'd call it 
dangerous. 
As jal is not reentrant, you have to make absolutely sure, that no single part 
of any procedure is running twice in any case. (The only exception I know of 
are the multiplication/division functions which are safe to be called from an 
interrupt while running in the main program, but those are not seen as 
functions to the user anyway) That means, that if you use e.g. a print 
procedure inside the interrupt, you also have to disable interrupts each time 
you're using a similar print procedure in the main program. All decimal print 
procedures use the same background code, so in this sense, they're "the same 
procedure" and need to be surveyed not to run from both the main program and 
the interrupt at the same time.
And, you should compile with --no-variable-reuse, as the compiler is probably 
not aware of procedures being called from an interrupt. 
Can be that you obeyed that rule by disabling interrupts when using I2C in the 
main program. But then, there's hardware involved. You need to make sure that 
the hardware is idle and in a reset, initialized state each time before 
enabling interrupts. I'm not so familiar with the I2C peripheral to decide if 
that's a problem. And, also all devices on the I2C bus need to be reset and 
initialized each time the interrupt is enabled.  
I do prefer handing over the alarm to the main program via volatile flag bit.
Greets,Kiste
Am Samstag, 19. Februar 2022, 09:58:53 MEZ hat rob...@hotmail.com 
 Folgendes geschrieben:  
 
 Hello all,
Some time ago I made a library for the clock IC DS3231. This library is part of 
Jallib release 1.7.0.
This IC has an I2C interface and is capable of handling two alarms. When an 
alarm is activated an interrupt is generated. 
Reading the alarm flag from the IC also uses - of course- the I2C interface but 
the I2C interface is also used by the main program. 
I thought that if I would disable all interrupts when calling the I2C routines 
from the main program and only enable it while not used by the main program 
that I could call the  same I2C routines from the interrupt routine and so be 
able to read the alarm flag from the IC to see if alarm 1 or alarm 2 was 
activated. 
Unfortunately this did not work. 
I thought that when an interrupt is called some info is saved and after the 
interrupt restored but I also thought that I could then call any routine from 
the interrupt as long that I am certain that no I2C transfer was active (which 
should be since the interrupt is disabled when the main program is using the 
I2C routines).
Any ideas why this does not work? Am I missing something?
What the current sample program does is just setting a global flag in the 
interrupt routine and the main program polls this flag and then reads the alarm 
flag of the IC via I2C but this undermines a bit the use of the interrupt.
Thanks.
Kind regards,
Rob


-- 
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/ff12f63c-0d1d-4897-8ca4-511869ab68c0n%40googlegroups.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/1119054585.183229.1645345612576%40mail.yahoo.com.