Time for another release - Jallib 1.5.0

41 views
Skip to first unread message

Matthew Schinkel

unread,
Nov 23, 2019, 11:45:45 PM11/23/19
to jallib
Hi guys,

Jallib has had several updates, so it's time to get ready for our next release. 

I'll begin building the beta package in about two weeks (around December 7th). Please try to get any last updates in before then. 

Thanks,
Matt.

Eur van Andel

unread,
Dec 3, 2019, 10:55:10 AM12/3/19
to jal...@googlegroups.com

On 24 Nov 2019, at 05:45:45, Matthew Schinkel <mattsc...@hotmail.com> wrote:

Jallib has had several updates, so it's time to get ready for our next release. 

I'll begin building the beta package in about two weeks (around December 7th). Please try to get any last updates in before then. 

I’m having weird issues with I2C and a device driver for the 18f67k22. 

The SCK signal starts shaking like a madman and keeps this up until a power cycle. 

Some sensors which worked fine in the past give lost of issues now. 


Has anyone seen this?

---
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-653-286573




Rob CJ

unread,
Dec 3, 2019, 12:39:57 PM12/3/19
to Eur van Andel, jal...@googlegroups.com
Hi Eur,

Which I2C library are you talking about? There are several.

Do you have a reproduction scenario or is it just sending an I2C command?

Kind regards,

Rob



Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Eur van Andel <e...@fiwihex.nl>
Verzonden: dinsdag 3 december 2019 16:55
Aan: jal...@googlegroups.com <jal...@googlegroups.com>
Onderwerp: Re: [jallib] Time for another release - Jallib 1.5.0
 
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/0A26F418-1622-4651-A8E5-EC8C228AFB3F%40fiwihex.nl.

RobJ

unread,
Dec 7, 2019, 7:38:47 AM12/7/19
to jallib
Hi Eur,

I have done an IIC Master test using the hardware IIC library and tested on a PIC18F67K22 but did not see any problems. The IIC library seems to work fine and there were no strange signals on the IIC clock or IIC data line.

Kind regards,

Rob

Matthew Schinkel

unread,
Dec 14, 2019, 9:57:20 PM12/14/19
to jallib
Hi everyone,

I ran torelease.py which reported the following. Please see if there are any libraries or samples listed that you want in the release.

Unreleased libraries (excluding unreleased device files)
--------------------------------------------------------
include/external/battery/ltc2942.jal
include/external/motion_sensor/BackUp/04-03-19-183635_accelerometer_gyroscope_bmi160.jal
include/external/oxygen/goel370.jal
include/external/pressure/bmp085.jal
include/external/rtc/rtc_mcp7940.jal
include/external/sound/beep.jal
include/external/storage/flash_sst25vf.jal
include/jal/debug_queue.jal
include/peripheral/adc/adc_channels.jal

9 unreleased libraries + 8 unreleased device files


Unreleased samples (excluding unreleased basic blink samples)
-------------------------------------------------------
sample/12f1572_steppermotor.jal
sample/12f617_large_array.jal
sample/16f1519_bmp085.jal
sample/16f1615_steppermotor.jal
sample/16f1765_steppermotor.jal
sample/16f1825_large_array.jal
sample/16f18325_steppermotor.jal
sample/18f2585_oxygen_goel370.jal
sample/18f26k22_sst25vf.jal
sample/18f27j53_sst25vf.jal
sample/18f4620_glcd_digits_stm032qvt.jal
sample/18f4620_quadrature_counter_ls7366r.jal
sample/18f4620_rotary_encoder_e6b2.jal
sample/18f4620_rtc_mcp7940.jal
sample/18f4620_timer.jal
sample/18f67j50_debug_queue.jal

16 unreleased sample files + 8 unreleased basic blink samples

Files listed in TORELEASE, but missing in Jallib
------------------------------------------------
Line#  File
 908   include/external/seven_segment/seven_segment_multiplexer.jal
 956   include/jal/large_byte_array_1_pic14.jal
 957   include/jal/large_byte_array_1_pic16.jal
 958   include/jal/large_dword_array_1_pic14.jal
 957   include/jal/large_byte_array_1_pic16.jal
 958   include/jal/large_dword_array_1_pic14.jal
 959   include/jal/large_dword_array_1_pic16.jal
 960   include/jal/large_word_array_1_pic14.jal
 961   include/jal/large_word_array_1_pic16.jal
 987   include/networking/esp8266.jal
1040   include/peripheral/timer/timer_frequency.jal
1044   include/peripheral/timer/timer1.jal
1045   include/peripheral/timer/timer3.jal
1068   project/jalpic_one/board/board.png
1094   project/pic18f14k50_usb_io/18f14k50_usb_io_board_pcb.pdf
1095   project/pic18f14k50_usb_io/18f14k50_usb_io_board_schematic.pdf

Rob CJ

unread,
Dec 15, 2019, 2:36:58 AM12/15/19
to jal...@googlegroups.com
Hi Matt,

Thanks for checking this.

I added sample/12f617_large_array.jal to TORELASE, apparently I had forgotten it since it was already on GitHub.

I do not understand the following list since the large array samples would not compile without them and they are present in the last bee-packages:
 956   include/jal/large_byte_array_1_pic14.jal
 957   include/jal/large_byte_array_1_pic16.jal
 958   include/jal/large_dword_array_1_pic14.jal
 957   include/jal/large_byte_array_1_pic16.jal
 958   include/jal/large_dword_array_1_pic14.jal
 959   include/jal/large_dword_array_1_pic16.jal
 960   include/jal/large_word_array_1_pic14.jal
 961   include/jal/large_word_array_1_pic16.jal

Same as for this one: 
987   include/networking/esp8266.jal
I remember that you had suggested some time ago that I needed to move it to the networking directory which I did at that time.

Also this file is on GitHub:
1068   project/jalpic_one/board/board.png
But I did not see it in the last bee-package. Strange. If I remember correctly I named it 'Board.jpg' in the beginning but then changed it to 'board.jpg' (no capital). Does it have to do with Windows vs Linux?

When I run the torelease.py script on my Windows computer I do not get the list of listed in TORELASE but missing in Jallib.

Any idea why it reports them as missing in Jallib? 

It almost looks as if the script has run on a not up-to-date (synced) version of GitHub.

Kind regards,

Rob


Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Matthew Schinkel <mattsc...@hotmail.com>
Verzonden: zondag 15 december 2019 03:57
Aan: jallib <jal...@googlegroups.com>
Onderwerp: [jallib] Re: Time for another release - Jallib 1.5.0
 
--
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+un...@googlegroups.com.

Rob CJ

unread,
Dec 16, 2019, 6:05:56 AM12/16/19
to jal...@googlegroups.com
Hi Matt,

I ran torelease.py (with the argument 'True' so that it includes missing device files and sample files just to see if we missed something) but I did not get some of the results you mentioned earlier.

I attached the torelease.lst results that I got and this seems to be OK.

Can you check why you got different results?

BTW. I saw something strange in the last build results, see below. No idea what is going on here.

------
jal jalv25r3 (compiled Sep 15 2019)
​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.​
​1932 samples to compile...​
​All samples compile :)​
------

Kind regards,

Rob




Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Rob CJ <rob...@hotmail.com>
Verzonden: zondag 15 december 2019 08:36
Aan: jal...@googlegroups.com <jal...@googlegroups.com>
Onderwerp: Re: [jallib] Re: Time for another release - Jallib 1.5.0
 
torelease.lst

Matthew Schinkel

unread,
Dec 16, 2019, 9:03:31 PM12/16/19
to jallib
Seems my script isn't working correctly. You may ignore the section "Files listed in TORELEASE, but missing in Jallib". I won't know how to fix it.

I'll look into the compiler message.

Matt.
Reply all
Reply to author
Forward
0 new messages