jallib Google Group

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

2013-05-19T13:11:49Z

Hi guys,

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

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this build
Build Source Stamp: HEAD
Blamelist:

Build succeeded!
Logs are attached.

sincerely,

Bug in format.jal ?

2013-05-14T16:41:24Z

Hello all,
I think i found a small bug in format.jal
I had problems when i tried to display in my lcd (format_dword_dec) a value
greater than 999.
Exemple : A35 instead of 1035
To resolve this problem i changed 2 lines in the procedure "format_dword_dec
"
original :
176 const word c10_000 = 10_000

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

2013-05-12T13:11:42Z

Hi guys,

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

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this build
Build Source Stamp: HEAD
Blamelist:

Build succeeded!
Logs are attached.

sincerely,

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

2013-05-05T13:12:20Z

Hi guys,

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

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this build
Build Source Stamp: HEAD
Blamelist:

Build succeeded!
Logs are attached.

sincerely,

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

2013-04-29T15:43:48Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

[jallib] r3248 committed - Updated changelog, minor modifications devicefiles.html

2013-04-29T07:28:26Z

Revision: 3248
Author: robhamerling
Log: Updated changelog, minor modifications devicefiles.html

[link]

Modified:
/trunk/CHANGELOG
/trunk/doc/html/devicefiles.ht ml

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

2013-04-29T03:23:23Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

device files

2013-04-28T19:19:29Z

Hi guys,

As you've probably seen I've committed new device files.
This is the result of a discussion in Jallist with Gordon Williams and
Kyle York. Some tests show a significant reduction of code memory mainly
because of reduced bank switching.
For the baseline and classic midrange the bytes required for port

[jallib] r3247 committed - Update of device files documentation....

2013-04-28T19:07:17Z

Revision: 3247
Author: robhamerling
Log: Update of device files documentation.
Rewrite of section about memory allocation!

[link]

Modified:
/trunk/doc/html/devicefiles.ht ml

[jallib] r3246 committed - Device files with dev2jal script version 0.1.46...

2013-04-28T19:04:17Z

Revision: 3246
Author: robhamerling
Log: Device files with dev2jal script version 0.1.46
- Un-enumerate CDAFVR and ADFVR bits of FVRCON (14 and 14H core).
- Shadow bytes of ports declared volatile (baseline and midrange).
- Remove 'pragma inline' of all pseudo variables which take

[jallib] r3245 committed - Most recent dev2jal Rexx script version 0.1.46, and related files

2013-04-28T18:58:06Z

Revision: 3245
Author: robhamerling
Log: Most recent dev2jal Rexx script version 0.1.46, and related files
[link]

Modified:
/trunk/tools/Dev2Jal.cmd
/trunk/tools/devicespecific.js on

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

2013-04-28T13:11:36Z

Hi guys,

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

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this build
Build Source Stamp: HEAD
Blamelist:

Build succeeded!
Logs are attached.

sincerely,

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

2013-04-26T16:13:16Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

[jallib] r3244 committed - Added library for LTC2942 chip

2013-04-26T07:54:34Z

Revision: 3244
Author: robhamerling
Log: Added library for LTC2942 chip

[link]

Added:
/trunk/include/external/batter y
/trunk/include/external/batter y/ltc2942.jal
Modified:
/trunk/CHANGELOG

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

2013-04-26T02:33:14Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

[jallib] r3243 committed - Fixed syntax error in rtc_ds1307 library

2013-04-25T18:16:55Z

Revision: 3243
Author: robhamerling
Log: Fixed syntax error in rtc_ds1307 library

[link]

Modified:
/trunk/include/external/rtc/rt c_ds1307.jal

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

2013-04-25T16:43:25Z

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: robhamerling

BUILD FAILED: failed compile
Logs are attached.

sincerely,
-The Buildbot

[jallib] r3242 committed - Partly correction of rtc_ds1307 library

2013-04-25T08:23:19Z

Revision: 3242
Author: robhamerling
Log: Partly correction of rtc_ds1307 library

[link]

Modified:
/trunk/include/external/rtc/rt c_ds1307.jal

Re: Issue 164 in jallib: Problem with DS1307 library

2013-04-25T08:13:55Z

Updates:
Status: Started

Comment #2 on issue 164 by robhamerling: Problem with DS1307 library
[link]

This issue was prematurely marked as fixed. The switch in rtc_init() from
12- to 24-hour mode is incorrect in more than one way.
Temporary fix: when the ds1307 is in 12-hour mode it is switched to 24-hour

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

2013-04-25T03:05:33Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

Re: [jallib] r3241 committed - Corrected init() of rtc_ds1307 library (issue #164)

2013-04-24T19:08:23Z

Although I have done the fix, validated the library and the samples
compile OK, I have no ds1307 on hand to test it. I hope somebody with
such an rtc chip is so kind to do a test and report the results (correct
or not).

The version of before this fix destroyed the seconds and hours values.

Re: Issue 164 in jallib: Problem with DS1307 library

2013-04-24T18:53:26Z

Updates:
Status: Fixed
Labels: Component-External

Comment #1 on issue 164 by robhamerling: Problem with DS1307 library
[link]

Fixed the initialization routine according to datasheet.

This library will be subject of revision with issue 185 (and 186).

[jallib] r3241 committed - Corrected init() of rtc_ds1307 library (issue #164)

2013-04-24T18:42:22Z

Revision: 3241
Author: robhamerling
Log: Corrected init() of rtc_ds1307 library (issue #164)

[link]

Modified:
/trunk/include/external/rtc/rt c_ds1307.jal

Re: [jallib] Re: flash memory full...

2013-04-24T13:29:54Z

Greetings,
You can send it to me & I'll take a look. Are you using any inline
functions in expressions (a = func1() + b)? This is a known issue. Do you
know if it works with any version of the compiler? That will make tracking
down differences easier.

Re: [jallib] Re: Issue 185 in jallib: Refactoring of RTC libraries

2013-04-23T18:55:49Z

The jallib ds1302 had some bugs too, I had a ds1302 library released in
jallist files area and that happened to be my first jal library that was in
2003 I guess.

Sunish

Re: [jallib] Re: Issue 185 in jallib: Refactoring of RTC libraries

2013-04-23T17:55:23Z

Hi Sunish,

Thank you! I've only a ds1302 (and some PICs with RTCC), so this is all
very welcome! I hope I can make a consistent set.
So far I've only looked at the ds1302 library and found it ugly. Naming
convention is not at all up to Jallib standards. Luckily it was never
released (there is not even a sample).

Re: [jallib] Re: flash memory full...

2013-04-23T17:20:49Z

Kyle,
A bit unrelated, but I have some programs which compiles fine but doesn't
run when optimizations (load reduce and temp reduce) are enabled. There's
no difference between p or q version. I can send you the code but its
pretty big and did not send as I couldn't reduce it to just the minimum to

Re: [jallib] Re: Issue 185 in jallib: Refactoring of RTC libraries

2013-04-23T17:13:37Z

Rob,
Iam sending my modifications to your mail id. I use ds1307 extensively and
attempted to make a common library. But it may not be fully jallib
compliant.

I can test 1302,1307 amd mcp series rtc as I have them and also write
sample as I already have working projects.

Re: [jallib] Re: flash memory full...

2013-04-23T17:14:19Z

I don't think it's worth to optimize this on compiler side. If one is low on code memory, I think it's best to do it manually, by even splitting up texts to compose different messages from shorter fragments. The question which led me to this posting was: "Is it worth to look for string optimization in this particular program?"

Re: flash memory full...

2013-04-23T16:39:09Z

Greetings,
Is this really a common scenario? At one time I considered optimizing this
(I think the original picbsc did so) but I didn't think it common enough to
worry about.
--kyle

Re: Issue 185 in jallib: Refactoring of RTC libraries

2013-04-23T14:42:11Z

Updates:
Status: Started

Comment #2 on issue 185 by robhamerling: Refactoring of RTC libraries
[link]

Work on refactoring has started, taking the RTCC_HW library as model.
Common routines like bcd2bin, mult60, day-of-week calculation, etc. will go

Re: [jallib] flash memory full...

2013-04-22T07:59:08Z

Oliver Seitz <karlki...@yahoo.com> said, in message
1366616444.74861.YahooMail...@ web121006.mail.ne1.yahoo.com:

Hi all,

Here's how to do it in one command:

awk -F, '($1 ~ / db /){n+=NF;}END{print n;}' MyProgram.asm

Spotting this situation can be done as follows:

grep " db " serial.asm | sort | uniq -c | awk '($1 > 1)'

flash memory full...

2013-04-22T07:40:44Z

I was recently wondering why my program got so big, so here's a bash line which will give a number which can be sometimes interesting:
cat MyProgram.asm | grep " db " | cut -d 0 -f 2- | fold -1 | grep -c x
It outputs the number of bytes used in constant tables (for PIC18 cores, for smaller cores this line would have to be modified).

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

2013-04-21T13:11:48Z

Hi guys,

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

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this build
Build Source Stamp: HEAD
Blamelist:

Build succeeded!
Logs are attached.

sincerely,

Re: [jallib] port initialization problem

2013-04-20T09:23:52Z

var byte*5 test
test=0
this would trigger the warning.
Greets,
Kiste

Re: [jallib] port initialization problem

2013-04-20T09:11:57Z

If such a warning would be added, there would probably pop up thousands of useless warnings and the libraries would have to be blown up by a real lot of explicit casts to get rid of the warning again.
Compiler warnings are no repacement for reading the manuals.
Greets,
Kiste

Re: [jallib] port initialization problem

2013-04-20T08:34:42Z

PORTA = 0 will not trigger a warning as 0 or 1 is a valid byte.

Sunish

Re: [jallib] port initialization problem

2013-04-20T08:17:10Z

warning: assignment to smaller type; truncation possible
You want an additional
warning: assignment to larger type
A statement like PORTA = 0 would trigger this warning, no?
Greets,
Kiste

Re: [jallib] port initialization problem

2013-04-20T07:24:15Z

Can we have some kind of compile time warning on assigning bit to
portdirections ?

Sunish

Re: [jallib] port initialization problem

2013-04-20T07:21:43Z

Oh yeah, looks like I've started getting old, forgot the all_output and
all_input in spite seeing the topic on jallist.

Thanks everybody.
Sunish

Re: [jallib] port initialization problem

2013-04-20T07:07:41Z

Hi Sunish,

I'm afraid it is your own fault. Just about 3 weeks ago it was also
mentioned in Jallist. Apparently people (even you and me!) forget that
'INPUT' and 'OUTPUT' are bit constants.

Should be: PORTA_low_direction = ALL_INPUT
A bit constant '1' expands to a byte 0b0000_0001 (or a nibble 0b0001)

Re: [jallib] port initialization problem

2013-04-20T06:26:12Z

Hi Sunish,

You may suspect aliases, but not port_low_direction or enable_digital_io.
Several times aliases made me a lot of problems, I avoid to use them
without debug.

Vasile

Re: [jallib] port initialization problem

2013-04-20T04:27:22Z

PORTA_direction = all_input
which is a byte constant and will set all pins to input.
I did not check the "enable_digital_io" part.
Greest,
Kiste

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

2013-04-20T02:23:22Z

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: robhamerling

Build succeeded!
Logs are attached.

sincerely,
-The Buildbot

port initialization problem

2013-04-20T02:11:15Z

Not sure whether its a compiler or library issue, 3pins a1,a2,a3 not
becoming input in spite of enable_digital_io in the following code.

include 16f886 -- target PICmicro
--
pragma target OSC HS
pragma target clock 20_000_000
pragma target WDT disabled
pragma target MCLR internal

Re: [jallib] hi and a proposed lib for the AD9850 DDS

2013-04-19T18:14:35Z

Thank you!
We have a validator script to check if the source code is up to Jallib
standards. I had to make a only few changes in the header comments, you
might check! I didn't notice any language issues (Jal, Spanish or
English...)

Regards, Rob.

--
R. Hamerling, Netherlands --- [link]

[jallib] r3240 committed - Added sample for use of dds_ad9850 library

2013-04-19T18:05:47Z

Revision: 3240
Author: robhamerling
Log: Added sample for use of dds_ad9850 library

[link]

Added:
/trunk/sample/16f877a_dds9850. jal
Modified:
/trunk/CHANGELOG

Re: [jallib] hi and a proposed lib for the AD9850 DDS

2013-04-19T17:04:09Z

This is the code for the example about AD8950 lib...

Please check it for language and sysntax issues, remember that i'm a
Spanish speaking man... ;-)

Regards, Pavel.

Re: [jallib] hi and a proposed lib for the AD9850 DDS

2013-04-19T15:58:36Z

Hi to all

Sorry for the delay, My ISP was in trouble and I migrate to another
solution... (ISP, note the different email address, )

This 2 past weeks I was working outside my town and have not access to
the email and with little time to code...

I'm back now and have hand on the 16f877 example...

Re: [jallib] hi and a proposed lib for the AD9850 DDS

2013-04-19T13:20:14Z

Hi Pavel,

I forgot to answer, so you are excused for not sending a sample program
(at least I didn't see it).

Please send a sample with the 16f877. But every other PIC is OK.

Regards, Rob.

--
R. Hamerling, Netherlands --- [link]