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

2022-02-19 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/E1nLaze-00089J-F3%40casadeyork.com.
Updating '.':

Ddoc/dita/tutorials/images/logo.jpg

Adoc/dita/tutorials/images/logo.png

Adoc/dita/tutorials/images/logo_old.jpg

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_getting_started.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_installation.xml

UU   doc/dita/tutorials/tutorial_serial_communication.xml

UU   doc/dita/tutorials/tutorials.ditamap

Updated to revision 3814.

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: 238 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: 1819 secs



[jallib] [jallib/jallib] a449fb: Small Tutorial Book fix.

2022-02-19 Thread 'Rob Jansen' via jallib
  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: a449fb4b73d00e01dc3bc4d5956e544bfa17097a
  
https://github.com/jallib/jallib/commit/a449fb4b73d00e01dc3bc4d5956e544bfa17097a
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2022-02-19 (Sat, 19 Feb 2022)

  Changed paths:
R doc/dita/tutorials/images/logo.jpg
A doc/dita/tutorials/images/logo.png
A doc/dita/tutorials/images/logo_old.jpg
M doc/dita/tutorials/tutorial_adc_intro.xml
M doc/dita/tutorials/tutorials.ditamap

  Log Message:
  ---
  Small Tutorial Book fix.


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


[jallib] [jallib/jallib] d92c6c: Update of Tutorial Book

2022-02-19 Thread 'Rob Jansen' via jallib
  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: d92c6c505b1625c8de1a059ddc3508e99ba04883
  
https://github.com/jallib/jallib/commit/d92c6c505b1625c8de1a059ddc3508e99ba04883
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2022-02-19 (Sat, 19 Feb 2022)

  Changed paths:
M doc/dita/tutorials/license.xml
M doc/dita/tutorials/tutorial_ICSP.xml
M doc/dita/tutorials/tutorial_blink_a_led.xml
M doc/dita/tutorials/tutorial_changelog.xml
M doc/dita/tutorials/tutorial_getting_started.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_installation.xml
M doc/dita/tutorials/tutorial_serial_communication.xml
M doc/dita/tutorials/tutorials.ditamap

  Log Message:
  ---
  Update of Tutorial Book

First update. Work not yet completed. Fixed broken links and removed references 
to SVN and Google fpr download, replaced this by the Jallib website.
Also removed the errors when generating the tutorial books.


-- 
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/9f24cf-d92c6c%40github.com.


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

2022-02-19 Thread rob...@hotmail.com
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.