Re: [jallib] PicKit minus - Free is not always bug free

2022-10-23 Thread vsurducan 
Rob, I know you know, :) be sure.

The error from your picture appears to me each time there is a connector
problem ( for example Vpp has a contact issue which appears and disappears
intermittently) or the PIC life has ended ( it's not able to retain address
0 content) or the supply voltage is below the specifications for
programming.

That is what I can think about.

I suggest checking Evans software/firmware pair for newer pics ( if you
didn't yet), it is worth it for sure.


On Sun, Oct 23, 2022 at 8:14 PM Rob CJ  wrote:

> Hi Vasile,
>
> I know software is not bug free. I had no other connections to the
> programmer pins. It could be a bad connection (although IPE from MPLABX had
> no problem.
>
> I will try again later to see if the problem persists. Sometimes it helps
> to just restart the programmer software.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* 'Evan Venn' via jallib 
> *Verzonden:* zondag 23 oktober 2022 15:31
> *Aan:* jallib@googlegroups.com 
> *Onderwerp:* Re: [jallib] PicKit minus - Free is not always bug free
>
> I have just created a test program that fills that chip. No issues.
>
> However, until I get the hex I cannot assure you.
>
> There may be issues in the format of the hex thru to physical issues.  We
> have very robust test beds that rule out physical issues, so, can focus on
> the software.
>
> Your call to send to me for assurance.
>
> Evan
>
> Get Outlook for Android 
> --
> *From:* jallib@googlegroups.com  on behalf of
> vsurducan 
> *Sent:* Sunday, October 23, 2022 11:50:44 AM
> *To:* jallib@googlegroups.com 
> *Subject:* Re: [jallib] PicKit minus - Free is not always bug free
>
> Rob, what is "bug free" ?  I have never heard about such a thing...
> :)
> Assuming your pickit3 software and companion definition file is compatible
> with PIC16F8857, your problem might be from an incorrect connection to ICSP
> or heavily loaded iclk and dat lines. One option is to "filter" those lines
> with 200ohm-680ohm resistors in series between the pic and your load, while
> your programmer stays connected directly to the PIC ICSP lines using as
> short as possible cable ( aka 20-30cm).  The other issue I saw is the USB
> cable length and quality.
>
> On Sun, Oct 23, 2022 at 12:47 PM rob...@hotmail.com 
> wrote:
>
> Hello all,
>
> This is for your information. I am looking at a problem I have with my
> PIC16F18857. It goes haywire when the code size becomes large (> 16 Kbyte).
>
> I did not yet find the root cause but I ran into another issue with the
> PicKit minus software.
>
> Although I am normally able to program the PIC16F18857 with this software
> it gives the following error when programming this large program (see
> attachment). It seems that the program is programmed correctly but still
> you do not want this type of error.
>
> The problem does not occur when using MPLABX IPE.
>
> So maybe better go for Evans PICKit Plus Software, not free but I assume
> bug free  ...
>
> 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/eb4d4a4d-5a10-45ab-8872-630303f75d32n%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/CAM%2Bj4qu8fndi2YQWVNuDPtb84Lb0vU8DcOVPVME0ni_qy%2BMyJg%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/CWXP265MB25182CE15D1E50E66689ED99F92F9%40CWXP265MB2518.GBRP265.PROD.OUTLOOK.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
>

Re: [jallib] PicKit minus - Free is not always bug free

2022-10-23 Thread Rob CJ 
Hi Vasile,

I know software is not bug free. I had no other connections to the programmer 
pins. It could be a bad connection (although IPE from MPLABX had no problem.

I will try again later to see if the problem persists. Sometimes it helps to 
just restart the programmer software.

Kind regards,

Rob


Van: 'Evan Venn' via jallib 
Verzonden: zondag 23 oktober 2022 15:31
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] PicKit minus - Free is not always bug free

I have just created a test program that fills that chip. No issues.

However, until I get the hex I cannot assure you.

There may be issues in the format of the hex thru to physical issues.  We have 
very robust test beds that rule out physical issues, so, can focus on the 
software.

Your call to send to me for assurance.

Evan

Get Outlook for Android

From: jallib@googlegroups.com  on behalf of vsurducan 

Sent: Sunday, October 23, 2022 11:50:44 AM
To: jallib@googlegroups.com 
Subject: Re: [jallib] PicKit minus - Free is not always bug free

Rob, what is "bug free" ?  I have never heard about such a thing...
:)
Assuming your pickit3 software and companion definition file is compatible with 
PIC16F8857, your problem might be from an incorrect connection to ICSP or 
heavily loaded iclk and dat lines. One option is to "filter" those lines with 
200ohm-680ohm resistors in series between the pic and your load, while your 
programmer stays connected directly to the PIC ICSP lines using as short as 
possible cable ( aka 20-30cm).  The other issue I saw is the USB cable length 
and quality.

On Sun, Oct 23, 2022 at 12:47 PM rob...@hotmail.com 
mailto:rob...@hotmail.com>> wrote:
Hello all,

This is for your information. I am looking at a problem I have with my 
PIC16F18857. It goes haywire when the code size becomes large (> 16 Kbyte).

I did not yet find the root cause but I ran into another issue with the PicKit 
minus software.

Although I am normally able to program the PIC16F18857 with this software it 
gives the following error when programming this large program (see attachment). 
It seems that the program is programmed correctly but still you do not want 
this type of error.

The problem does not occur when using MPLABX IPE.

So maybe better go for Evans PICKit Plus Software, not free but I assume bug 
free  ...

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/eb4d4a4d-5a10-45ab-8872-630303f75d32n%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/CAM%2Bj4qu8fndi2YQWVNuDPtb84Lb0vU8DcOVPVME0ni_qy%2BMyJg%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/CWXP265MB25182CE15D1E50E66689ED99F92F9%40CWXP265MB2518.GBRP265.PROD.OUTLOOK.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/GVXP195MB16375AC7BCFD66E6C4EDC9FEE62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread Rob CJ 
Hi David,

The XML files are provided by Mircochip if you download MPLABX.

If we would want to use the ROM code size (which is known from the XML) it 
woule be possible to add something like this to the compiler functionality:

  target_code_size

So in your program you would have something like:

const HEF_OFFSET_ADDRESS = target_code_size - HEF_NR_OF_BYTES (or just minus 
128).

I attached the XML for your PIC.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens 
pinhe...@gmail.com 
Verzonden: zondag 23 oktober 2022 16:48
Aan: jallib 
Onderwerp: Re: [jallib] HEF usage: One suggestion and one question

Just another thought:
In the device include file of older PIC's with dedicated eeprom, I see  a 
directive defining that eeprom, by adress and size.
For example, for a 16F628A :
pragma  eeprom   0x2100,256

Is this the kind of info you retrieve from the XML files ?
For my information, where could I see the content of such a XML file (say the 
one for the 16F1705 I use) ?



Le dimanche 23 octobre 2022 à 16:38:42 UTC+2, evan@googlemail.com a écrit :
We asked Microchip for the information.  We are Microchip Approved Software 
Partners so we can ask for key information.

This information was the used to populate the PIckit parts database.

--



Get Outlook for Android

From: jal...@googlegroups.com  on behalf of 
pinhe...@gmail.com 
Sent: Sunday, October 23, 2022 3:35:36 PM
To: jallib 
Subject: Re: [jallib] HEF usage: One suggestion and one question

Thanks all for those creative answers

@Rob : Indeed, using one HEF location as an indicator to know if the settings 
have already been initialised or not was my fallback solution.   As you explain 
(and I wasn't aware of that), if you do not receive the value in the XML from 
Microchip, you can not put that value in the include file  unfortunately.

About the discussion to deduce the offset by assuming the HEF size is always 
128 bytes, that seems very risky to me.   Furthermore, in the document Rob H 
linked, there are already a bunch of PIC's for which that size is not at all 
128 bytes.

I do not know what data is included in the Microchip XML files, but how does 
the programmers (ICD, PicKit, )  know how much HEF there is ?   Or do they 
not at all make the difference between normal flash and HEF ?   Seems weird to 
me (but I'm not an expert)

Enjoy your Sunday

Daiv

Le dimanche 23 octobre 2022 à 13:11:27 UTC+2, Rob Hamerling a écrit :

Hi RobJ and others,

My assumption that HEF-size is always 128 comes from:
https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf
In the explanation colums it says:
HEF: High–Endurance Flash 128B Non–volatile data storage with high–endurance 
100k E/W cycles
It doesn't say if it is always in the highest program address region.
Searching all datasheets isn't the favorite aspect of my hobby

As far as size of program memory concerns: the device file contain a "pragma 
code", but I cannot find in the docs if there is a companion built-in constant 
definition, for example like there is one for bank size: "CONST 
target_bank_size = cexpr".
If such a constant doesn't exists yet it would be handy to add it to the 
compiler.

Regards, RobH



--
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+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/61cdd53e-398c-4c2d-8786-2762984b7e3an%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/02a30931-3dbe-4249-a3b2-4dcfe77aa78cn%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/GVXP195MB16377F5ABB33A6F6036CAFDEE62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.


PIC16F628A.PIC
Description: PIC16F628A.PIC

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

2022-10-23 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/E1omdy0-000513-2K%40casadeyork.com.
Updating '.':

UU   sample/18f46q10_glcd_ili9341_font.jal

Updated to revision 3863.

2738 samples to validate...

1139 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: 241 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.

2738 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: 1817 secs

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread pinhe...@gmail.com 
Just another thought:   
In the device include file of older PIC's with dedicated eeprom, I see  a 
directive defining that eeprom, by adress and size.
For example, for a 16F628A : 
pragma  eeprom   0x2100,256

Is this the kind of info you retrieve from the XML files ?
For my information, where could I see the content of such a XML file (say 
the one for the 16F1705 I use) ?



Le dimanche 23 octobre 2022 à 16:38:42 UTC+2, evan@googlemail.com a 
écrit :

> We asked Microchip for the information.  We are Microchip Approved 
> Software Partners so we can ask for key information. 
>
> This information was the used to populate the PIckit parts database.
>
> --
>
>
>
> Get Outlook for Android 
> --
> *From:* jal...@googlegroups.com  on behalf of 
> pinhe...@gmail.com 
> *Sent:* Sunday, October 23, 2022 3:35:36 PM
> *To:* jallib 
> *Subject:* Re: [jallib] HEF usage: One suggestion and one question 
>  
> Thanks all for those creative answers
>
> @Rob : Indeed, using one HEF location as an indicator to know if the 
> settings have already been initialised or not was my fallback solution.   
> As you explain (and I wasn't aware of that), if you do not receive the 
> value in the XML from Microchip, you can not put that value in the include 
> file  unfortunately.
>
> About the discussion to deduce the offset by assuming the HEF size is 
> always 128 bytes, that seems very risky to me.   Furthermore, in the 
> document Rob H linked, there are already a bunch of PIC's for which that 
> size is not at all 128 bytes.
>
> I do not know what data is included in the Microchip XML files, but how 
> does the programmers (ICD, PicKit, )  know how much HEF there is ?   Or 
> do they not at all make the difference between normal flash and HEF ?   
> Seems weird to me (but I'm not an expert)
>
> Enjoy your Sunday
>
> Daiv
>
> Le dimanche 23 octobre 2022 à 13:11:27 UTC+2, Rob Hamerling a écrit :
>
>
> Hi RobJ and others,
>
> My assumption that HEF-size is always 128 comes from:
>
> https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf
>
> In the explanation colums it says:
>
> HEF: High–Endurance Flash 128B Non–volatile data storage with 
> high–endurance 100k E/W cycles
>
> It doesn't say if it is always in the highest program address region.
> Searching all datasheets isn't the favorite aspect of my hobby
>
> As far as size of program memory concerns: the device file contain a 
> "pragma code", but I cannot find in the docs if there is a companion 
> built-in constant definition, for example like there is one for bank size: 
> "CONST target_bank_size = cexpr".   
> If such a constant doesn't exists yet it would be handy to add it to the 
> compiler.
>
> Regards, RobH
>
>
>
> -- 
> *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+un...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jallib/61cdd53e-398c-4c2d-8786-2762984b7e3an%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/02a30931-3dbe-4249-a3b2-4dcfe77aa78cn%40googlegroups.com.

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread 'Evan Venn' via jallib 
We asked Microchip for the information.  We are Microchip Approved Software 
Partners so we can ask for key information.

This information was the used to populate the PIckit parts database.

--



Get Outlook for Android

From: jallib@googlegroups.com  on behalf of 
pinhe...@gmail.com 
Sent: Sunday, October 23, 2022 3:35:36 PM
To: jallib 
Subject: Re: [jallib] HEF usage: One suggestion and one question

Thanks all for those creative answers

@Rob : Indeed, using one HEF location as an indicator to know if the settings 
have already been initialised or not was my fallback solution.   As you explain 
(and I wasn't aware of that), if you do not receive the value in the XML from 
Microchip, you can not put that value in the include file  unfortunately.

About the discussion to deduce the offset by assuming the HEF size is always 
128 bytes, that seems very risky to me.   Furthermore, in the document Rob H 
linked, there are already a bunch of PIC's for which that size is not at all 
128 bytes.

I do not know what data is included in the Microchip XML files, but how does 
the programmers (ICD, PicKit, )  know how much HEF there is ?   Or do they 
not at all make the difference between normal flash and HEF ?   Seems weird to 
me (but I'm not an expert)

Enjoy your Sunday

Daiv

Le dimanche 23 octobre 2022 à 13:11:27 UTC+2, Rob Hamerling a écrit :

Hi RobJ and others,

My assumption that HEF-size is always 128 comes from:
https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf
In the explanation colums it says:
HEF: High–Endurance Flash 128B Non–volatile data storage with high–endurance 
100k E/W cycles
It doesn't say if it is always in the highest program address region.
Searching all datasheets isn't the favorite aspect of my hobby

As far as size of program memory concerns: the device file contain a "pragma 
code", but I cannot find in the docs if there is a companion built-in constant 
definition, for example like there is one for bank size: "CONST 
target_bank_size = cexpr".
If such a constant doesn't exists yet it would be handy to add it to the 
compiler.

Regards, RobH



--
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/61cdd53e-398c-4c2d-8786-2762984b7e3an%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/CWXP265MB25180CB26E850122514FB194F92F9%40CWXP265MB2518.GBRP265.PROD.OUTLOOK.COM.

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread pinhe...@gmail.com 
Thanks all for those creative answers

@Rob : Indeed, using one HEF location as an indicator to know if the 
settings have already been initialised or not was my fallback solution.   
As you explain (and I wasn't aware of that), if you do not receive the 
value in the XML from Microchip, you can not put that value in the include 
file  unfortunately.

About the discussion to deduce the offset by assuming the HEF size is 
always 128 bytes, that seems very risky to me.   Furthermore, in the 
document Rob H linked, there are already a bunch of PIC's for which that 
size is not at all 128 bytes.

I do not know what data is included in the Microchip XML files, but how 
does the programmers (ICD, PicKit, )  know how much HEF there is ?   Or 
do they not at all make the difference between normal flash and HEF ?   
Seems weird to me (but I'm not an expert)

Enjoy your Sunday

Daiv

Le dimanche 23 octobre 2022 à 13:11:27 UTC+2, Rob Hamerling a écrit :

>
> Hi RobJ and others,
>
> My assumption that HEF-size is always 128 comes from:
>
> https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf
>
> In the explanation colums it says:
>
> HEF: High–Endurance Flash 128B Non–volatile data storage with 
> high–endurance 100k E/W cycles
>
> It doesn't say if it is always in the highest program address region.
> Searching all datasheets isn't the favorite aspect of my hobby
>
> As far as size of program memory concerns: the device file contain a 
> "pragma code", but I cannot find in the docs if there is a companion 
> built-in constant definition, for example like there is one for bank size: 
> "CONST target_bank_size = cexpr".   
> If such a constant doesn't exists yet it would be handy to add it to the 
> compiler.
>
> Regards, RobH
>
>
>
> -- 
> *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/61cdd53e-398c-4c2d-8786-2762984b7e3an%40googlegroups.com.

Re: [jallib] PicKit minus - Free is not always bug free

2022-10-23 Thread 'Evan Venn' via jallib 
I have just created a test program that fills that chip. No issues.

However, until I get the hex I cannot assure you.

There may be issues in the format of the hex thru to physical issues.  We have 
very robust test beds that rule out physical issues, so, can focus on the 
software.

Your call to send to me for assurance.

Evan

Get Outlook for Android

From: jallib@googlegroups.com  on behalf of vsurducan 

Sent: Sunday, October 23, 2022 11:50:44 AM
To: jallib@googlegroups.com 
Subject: Re: [jallib] PicKit minus - Free is not always bug free

Rob, what is "bug free" ?  I have never heard about such a thing...
:)
Assuming your pickit3 software and companion definition file is compatible with 
PIC16F8857, your problem might be from an incorrect connection to ICSP or 
heavily loaded iclk and dat lines. One option is to "filter" those lines with 
200ohm-680ohm resistors in series between the pic and your load, while your 
programmer stays connected directly to the PIC ICSP lines using as short as 
possible cable ( aka 20-30cm).  The other issue I saw is the USB cable length 
and quality.

On Sun, Oct 23, 2022 at 12:47 PM rob...@hotmail.com 
mailto:rob...@hotmail.com>> wrote:
Hello all,

This is for your information. I am looking at a problem I have with my 
PIC16F18857. It goes haywire when the code size becomes large (> 16 Kbyte).

I did not yet find the root cause but I ran into another issue with the PicKit 
minus software.

Although I am normally able to program the PIC16F18857 with this software it 
gives the following error when programming this large program (see attachment). 
It seems that the program is programmed correctly but still you do not want 
this type of error.

The problem does not occur when using MPLABX IPE.

So maybe better go for Evans PICKit Plus Software, not free but I assume bug 
free  ...

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/eb4d4a4d-5a10-45ab-8872-630303f75d32n%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/CAM%2Bj4qu8fndi2YQWVNuDPtb84Lb0vU8DcOVPVME0ni_qy%2BMyJg%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/CWXP265MB25182CE15D1E50E66689ED99F92F9%40CWXP265MB2518.GBRP265.PROD.OUTLOOK.COM.

Re: [jallib] PicKit minus - Free is not always bug free

2022-10-23 Thread 'evan....@googlemail.com' via jallib 
Send me the hex.  I will ensure it works.  I am sure it does, but, even if 
it does not.. it will because we will ensure it does. :-)

Evan
On Sunday, 23 October 2022 at 11:50:56 UTC+1 vasile wrote:

> Rob, what is "bug free" ?  I have never heard about such a thing...
> :)
> Assuming your pickit3 software and companion definition file is compatible 
> with PIC16F8857, your problem might be from an incorrect connection to ICSP 
> or heavily loaded iclk and dat lines. One option is to "filter" those lines 
> with 200ohm-680ohm resistors in series between the pic and your load, while 
> your programmer stays connected directly to the PIC ICSP lines using as 
> short as possible cable ( aka 20-30cm).  The other issue I saw is the USB 
> cable length and quality. 
>
> On Sun, Oct 23, 2022 at 12:47 PM rob...@hotmail.com  
> wrote:
>
>> Hello all,
>>
>> This is for your information. I am looking at a problem I have with my 
>> PIC16F18857. It goes haywire when the code size becomes large (> 16 Kbyte).
>>
>> I did not yet find the root cause but I ran into another issue with the 
>> PicKit minus software.
>>
>> Although I am normally able to program the PIC16F18857 with this software 
>> it gives the following error when programming this large program (see 
>> attachment). It seems that the program is programmed correctly but still 
>> you do not want this type of error.
>>
>> The problem does not occur when using MPLABX IPE.
>>
>> So maybe better go for Evans PICKit Plus Software, not free but I assume 
>> bug free  ...
>>
>> 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+un...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jallib/eb4d4a4d-5a10-45ab-8872-630303f75d32n%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/1611f65e-f8f4-43ab-a56b-721173aa89aen%40googlegroups.com.

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread Rob Hamerling 


Hi RobJ and others,

My assumption that HEF-size is always 128 comes from:

https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf

In the explanation colums it says:
HEF:High–Endurance Flash128B Non–volatile data storage with 
high–endurance 100k E/W cycles

It doesn't say if it is always in the highest program address region.
Searching all datasheets isn't the favorite aspect of my hobby

As far as size of program memory concerns: the device file contain a 
"pragma code", but I cannot find in the docs if there is a companion 
built-in constant definition, for example like there is one for bank 
size: "CONST target_bank_size = cexpr".
If such a constant doesn't exists yet it would be handy to add it to the 
compiler.


Regards, RobH


--
*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/ebc2e7a4-0564-d062-6f0f-8675c9a0dc38%40gmail.com.

Re: [jallib] PicKit minus - Free is not always bug free

2022-10-23 Thread vsurducan 
Rob, what is "bug free" ?  I have never heard about such a thing...
:)
Assuming your pickit3 software and companion definition file is compatible
with PIC16F8857, your problem might be from an incorrect connection to ICSP
or heavily loaded iclk and dat lines. One option is to "filter" those lines
with 200ohm-680ohm resistors in series between the pic and your load, while
your programmer stays connected directly to the PIC ICSP lines using as
short as possible cable ( aka 20-30cm).  The other issue I saw is the USB
cable length and quality.

On Sun, Oct 23, 2022 at 12:47 PM rob...@hotmail.com 
wrote:

> Hello all,
>
> This is for your information. I am looking at a problem I have with my
> PIC16F18857. It goes haywire when the code size becomes large (> 16 Kbyte).
>
> I did not yet find the root cause but I ran into another issue with the
> PicKit minus software.
>
> Although I am normally able to program the PIC16F18857 with this software
> it gives the following error when programming this large program (see
> attachment). It seems that the program is programmed correctly but still
> you do not want this type of error.
>
> The problem does not occur when using MPLABX IPE.
>
> So maybe better go for Evans PICKit Plus Software, not free but I assume
> bug free  ...
>
> 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/eb4d4a4d-5a10-45ab-8872-630303f75d32n%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/CAM%2Bj4qu8fndi2YQWVNuDPtb84Lb0vU8DcOVPVME0ni_qy%2BMyJg%40mail.gmail.com.

Re: [jallib] Re: exit of master/slave?

2022-10-23 Thread Rob CJ 
Hi all,

Agree. We coule makt it something gradual.

I started with the ili9341.jal library.

-- Define the interface alias for the ILI9341.
alias ili9341_spi_host is spi_master_hw


Kind regards,

Rob


Van: jallib@googlegroups.com  namens vsurducan 

Verzonden: zondag 23 oktober 2022 08:54
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Re: exit of master/slave?

I agree with Matt. I think this is a fake issue,
Perhaps Rob Hammerling needed to see you at work and plugged you in the socket. 
:)  ( deep respect for Rob, just an innocent joke)
One guy from Microchip was not attentive and changed the terms to sound good 
for his ears ( definitely his and not her, women are attentive).
I really like hoci and hico. :0) People with a deep sense of humor here.

On Sat, Oct 22, 2022 at 9:56 PM Matthew Schinkel 
mailto:mattschin...@hotmail.com>> wrote:
I think we're going the wrong way with this whole thing.

I don't see how we are going to keep the new naming out of new files, and I 
hope we aren't planning to send nasty emails to everyone that puts the word 
slave in their lib/sample. That would be quite bad for Jallib. Instead of us 
changing everything, maybe we should only change this where microchip and other 
chip vendors have.

The reason for the change should be "to match the vendors wording". Not to 
remove it completely, because that can't be enforced due to freedom of speech 
and will prevent some from adding files to Jallib. The person making the 
library can name it as they please.

Can we list all libraries containing the terms master/slave, then note which 
are not matching the vendors wording?

Since microchip is using host/client for SPI, I think we should keep 
spi_master_hw.jal, but replace it's contents with only a few lines like:
include spi_host_hw
alias spi_master_hw is spi_host_hw

Some vendors still refer to it as spi master/host and some as spi slave/client. 
Therefore we should keep both a spi_host and a spi_master library.

Nobody owns Jallib, therefore nobody should enforce this new wording. Our 
policy should be "try to use the vendors wording, but it's up to the creator".

I think this solution should work better for everyone.

Peter, I don't think we'll be making any other changes to SPI naming, this 
seems to be enough change for now.

Matt.

On Wednesday, October 12, 2022 at 1:36:57 PM UTC-4 Rob Hamerling wrote:

Hi guys,

Like similar changes in other places, I see in the Microchip datasheets that 
the terms 'master' and 'slave' are being replaced by 'host' and 'client'. Seems 
a positive and desirable change to me. I would like to suggest to follow 
Microchip in this for Jallib. I'm afraid this is not a simple operation. It is 
not only about file names, but also related 'includes' in samples. But it will 
also have effects on existing user programs!   What are your thoughts about 
this?

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/3d96f421-f2a8-4536-8d29-9f1ddaccfaden%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/CAM%2Bj4qvWds4_KeZ%2Bu3SZmc9JVG_zfZ%3DOGuPqhXnOqbkjWQAukQ%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/GVXP195MB1637C15DB186920B5455F474E62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] HEF usage: One suggestion and one question

2022-10-23 Thread Rob CJ 
Hi Rob,

I checked the Jallib sample files that I created for testing the HEF library 
and it seems you are right but I am not sure if that will be the case for the 
future.

The example below is for a 2k PIC (16F1507) sample file. You you take the ROM 
size and substract 128 bytes.

-- High Endurance Flash (HEF) address declarations.
const HEF_NR_OF_BYTES= 128
const HEF_ADDRESS_OFFSET = 2048 - HEF_NR_OF_BYTES
include pic_data_hef

In the device file of this PIC you find:
pragma  code 2048

To make life easier you could extend all device files with something like (for 
this PIC as example):
const ROMSIZE = 2048

And then it becomes:
const HEF_ADDRESS_OFFSET = ROMSIZE - HEF_NR_OF_BYTES

Kind regards,

Rob



Van: jallib@googlegroups.com  namens Rob Hamerling 

Verzonden: zaterdag 22 oktober 2022 20:19
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] HEF usage: One suggestion and one question


Hi David,

On 22/10/2022 00.31, pinhe...@gmail.com wrote:
I am starting a new project using a PIC16F1705.
I willl use the "pic_data_hef" library.
This libray requires the definition of a constant containing the start address 
of the HEF, and named HEF_ADDRESS_OFFSET.
For the 16F1705, that value is 0x1F80

My suggestion: Couldn't that constant be defined in the device include file, so 
that, if I decide to port my code to another PIC, the value of the constant 
would be automatically updated, and thus, avoiding possible errors ?

Maybe there is a method to determine the HEF offset.
Assuming:
- HEF is always 128 words
- HEF is last part of program memory
HEF-offset = amount of program memory less 128

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/eaf6a66d-0ff1-f9a9-1e8d-5d217f3ef37f%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/GVXP195MB16373C1652EEF7F91AF8C179E62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

[jallib] [jallib/jallib] 884944: Update 18f46q10_glcd_ili9341_font.jal

2022-10-23 Thread 'Rob Jansen' via jallib 
  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: 8849446fa9c880eeab9c07f9d923b58850b58acd
  
https://github.com/jallib/jallib/commit/8849446fa9c880eeab9c07f9d923b58850b58acd
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2022-10-23 (Sun, 23 Oct 2022)

  Changed paths:
M sample/18f46q10_glcd_ili9341_font.jal

  Log Message:
  ---
  Update 18f46q10_glcd_ili9341_font.jal


-- 
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/015974-884944%40github.com.