date:20221127

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread Rob CJ

Hi Filipe,

The first line is to set the internal oscillator at 32 MHz.

The second line is to set some default values in the Eeprom before the program 
begins just to test if they are overwritten by the programs.

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of flyway38 

Sent: Sunday, November 27, 2022 8:52:08 PM
To: jallib 
Subject: Re: [jallib] Re: PIC16F19176 EEprom Error

Hi Rob,

Thank you very much.
Just one question...
Why these new lines;
OSCFRQ_HFFRQ = 0b110 -- Fosc 32 -> 32 MHz
and
pragma eedata 129,130,131,132-- initial contents
Only to understand it.
Thank you once again.

Cheers,
Filipe Santos.

On Sunday, November 27, 2022 at 4:02:12 PM UTC rob...@hotmail.com wrote:
Hi Filipe,

The update was quite simple. Attached the new library and a sample program.

I tested it and it works OK.

The updated library and new sample file will be in the next bee-package.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: zondag 27 november 2022 16:27

Aan: jallib 
Onderwerp: Re: [jallib] Re: PIC16F19176 EEprom Error
Hi Filipe,

I will update the library. I will let you know when it is available.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:59
Aan: jallib 
Onderwerp: Re: [jallib] Re: PIC16F19176 EEprom Error

Hi Rob,

Thank you for your feedback.
Its ok, can wait.
To try to solve it myself will need some hints.. In this case will keep this 
thread updated until final solution.
But if you get your hands on this issue, just let me know.
Thank you very much.

Cheers,
Filipe Santos.


On Sunday, November 27, 2022 at 12:35:30 PM UTC rob...@hotmail.com wrote:
Hi Filip,

Correct. This PIC you are using has different register and also - if I am right 
- a way to write EEPROM data in words instead of bytes.

So the currently library needs an update to support your chip.

At this moment I am working on trying to solve compiler issue#25 but partly 
succesful so far. If I get stuck (and it seems I currently am) I can give it a 
try to update the EEPROM library. Of course you can also give it a try yourself.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:25
Aan: jallib 
Onderwerp: [jallib] Re: PIC16F19176 EEprom Error

It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
Pic's Lib file:
-- EEPROM data byte.
if defined(EEDATL) then
   alias _EEPROM_DATA is EEDATL
elsif defined(EEDAT) then
   alias _EEPROM_DATA is EEDAT
elsif defined(EEDATA) then
   alias _EEPROM_DATA is EEDATA
elsif defined(NVMDAT) then
   alias _EEPROM_DATA is NVMDAT
end if

In Pic's Lib have found this definitions:
-- 
var volatile byte   NVMDATL   at { 0x81C }
var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
-- 
var volatile byte   NVMDATH   at { 0x81D }
var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
-- 

Not sure how to proceed with corrections here.
Any ideas will be great.
Thank you.

FS

On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
Hello to all,

Am starting this new project based on PIC16F19176.
Am including Pic_Data_Eeprom lib but compiler gives me this error:

Compilation started at :27/11/2022 12:06:11
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
[Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
[Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got '_eeprom_data')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
[Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
Santos\Desktop\NotasTecnicas\_Projecto -

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

2022-11-27 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/E1ozSLk-0008C9-3Q%40casadeyork.com.
Updating '.':

UU   CHANGELOG

UU   TORELEASE

UU   include/peripheral/data_eeprom/pic_data_eeprom.jal

Asample/16f19176_data_eeprom.jal

Updated to revision 3871.

2789 samples to validate...

1172 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: 341 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.

2789 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: 1915 secs

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread flyway38

Hi Rob,

Thank you very much.
Just one question...
Why these new lines;
OSCFRQ_HFFRQ = 0b110 -- Fosc 32 -> 32 MHz
and
pragma eedata 129,130,131,132-- initial contents
Only to understand it.
Thank you once again.

Cheers,
Filipe Santos.

On Sunday, November 27, 2022 at 4:02:12 PM UTC rob...@hotmail.com wrote:

> Hi Filipe,
>
> The update was quite simple. Attached the new library and a sample 
> program. 
>
> I tested it and it works OK.
>
> The updated library and new sample file will be in the next bee-package.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens Rob CJ <
> rob...@hotmail.com>
> *Verzonden:* zondag 27 november 2022 16:27
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] Re: PIC16F19176 EEprom Error
> Hi Filipe,
>
> I will update the library. I will let you know when it is available.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens flyway38 <
> fsfo...@gmail.com>
> *Verzonden:* zondag 27 november 2022 13:59
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] Re: PIC16F19176 EEprom Error 
>  
> Hi Rob,
>
> Thank you for your feedback.
> Its ok, can wait.
> To try to solve it myself will need some hints.. In this case will keep 
> this thread updated until final solution.
> But if you get your hands on this issue, just let me know.
> Thank you very much.
>
> Cheers,
> Filipe Santos.
>
>
> On Sunday, November 27, 2022 at 12:35:30 PM UTC rob...@hotmail.com wrote:
>
> Hi Filip,
>
> Correct. This PIC you are using has different register and also - if I am 
> right - a way to write EEPROM data in words instead of bytes.
>
> So the currently library needs an update to support your chip.
>
> At this moment I am working on trying to solve compiler issue#25 but 
> partly succesful so far. If I get stuck (and it seems I currently am) I can 
> give it a try to update the EEPROM library. Of course you can also give it 
> a try yourself.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens flyway38 <
> fsfo...@gmail.com>
> *Verzonden:* zondag 27 november 2022 13:25
> *Aan:* jallib 
> *Onderwerp:* [jallib] Re: PIC16F19176 EEprom Error 
>  
> It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
> Pic's Lib file:
> -- EEPROM data byte.
> if defined(EEDATL) then
>alias _EEPROM_DATA is EEDATL
> elsif defined(EEDAT) then
>alias _EEPROM_DATA is EEDAT
> elsif defined(EEDATA) then
>alias _EEPROM_DATA is EEDATA
> elsif defined(NVMDAT) then
>alias _EEPROM_DATA is NVMDAT
> end if 
>
> In Pic's Lib have found this definitions:
> -- 
> var volatile byte   NVMDATL   at { 0x81C }
> var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
> var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
> var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
> var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
> var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
> var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
> var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
> var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
> -- 
> var volatile byte   NVMDATH   at { 0x81D }
> var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
> var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
> var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
> var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
> var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
> var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
> -- 
>
> Not sure how to proceed with corrections here.
> Any ideas will be great.
> Thank you.
>
> FS
>
> On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
>
> Hello to all,
>
> Am starting this new project based on PIC16F19176.
> Am including Pic_Data_Eeprom lib but compiler gives me this error:
>
> Compilation started at :27/11/2022 12:06:11
> jal jalv25r6 (compiled Oct 29 2021)
> generating p-code
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got 
> '_eeprom_data')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
> C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
> Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
> Santos\Desktop\NotasTecnicas\_Projecto - 
> ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" 
> -s "C:\JALLIB~1\lib" -no-variable-reuse  
>
> Errors :6

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

2022-11-27 Thread 'evan....@googlemail.com' via jallib

We are on stock firmware for the PK2 and Pk3.  We have a specific firmware 
for the Pi solution (to resolve the USB timeout issues in the Pi4 USB 
hardware).

Are you referring to the database version?   PK- is in a very hacked 
version of our 2.63.223.1 release.  The database from PK- is not compatible 
with PICKitPlus (even though I offered him our source).  So, we are 
maintaining the master version.  It will be long before that is `taken` 
into PK-.   We are planning to change the database to ensure it cannot be 
lifted again when we add PK4 interoperability.

So, we are as follows:
Application version 6.61.0.74
Device File Version  2.63.236.1
Firmware 2.32.00

What is the version number you are looking at please?





On Sunday, 27 November 2022 at 18:00:44 UTC vasile wrote:

> Evan, I am a bit confused. Pickit+ is using different firmware than the 
> original  Microchip. Pickit- is using Microchip firmware and Pickit+ 
> database That looks strange in my logic, but also shows that Pickit- 
> may be somehow different than Pickit+?
>
> On Sun 27 Nov 2022, 6:10 PM 'evan@googlemail.com' via jallib <
> jal...@googlegroups.com wrote:
>
>> @Filipe 
>>
>> PICKIT- developer took our database, took our ideas and now are hurting 
>> us.  I have spoken on the real issues regarding the changes made to the 
>> database that can cause real damage to microcontrollers.
>> I am personally in debt regarding the development of PICKitPlus.  
>> Please consider donating to our project even if the donation is a token 
>> donation of a few $$.
>>
>> Evan
>>
>> On Saturday, 26 November 2022 at 20:17:34 UTC fsfo...@gmail.com wrote:
>>
>>> Hi again.
>>>
>>> PickitMinus is great!!!
>>> It has that PIC (16F19176) that am using (and many other ones) and it 
>>> worked like a charm.
>>> Thank you so much Rob.
>>>
>>> Cheers,
>>> Filipe Santos.
>>>
>>> On Saturday, November 26, 2022 at 8:08:05 PM UTC flyway38 wrote:
>>>
 Hey Vasile/ Rob.

 Thank you very much for your input.
 Will check that options.

 Best regards,
 Filipe Santos.

 On Saturday, November 26, 2022 at 1:32:51 PM UTC 
 evan@googlemail.com wrote:

> Yes. Not happy that someone took our work. Very unhappy. 
>
> Get Outlook for Android 
> --
> *From:* jal...@googlegroups.com  on behalf 
> of flyway38 
> *Sent:* Saturday, November 26, 2022 12:43:54 PM
> *To:* jallib 
> *Subject:* Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 
> 2 options 
>  
> Hello Evan
>
> Yes, am using standard Pickit 2 software.
> Where do I find newer data base for it?
> Will google for it.
> Thanks.
>
> Regards,
> Filipe Santos.
>
> On Saturday, November 26, 2022 at 12:15:47 PM UTC 
> evan@googlemail.com wrote:
>
> re:  The chip you are trying to add. 
>
> It uses a different protocol for the SPI communications.  You will 
> require to make changes to the application to change from LSB SPI to MSB 
> SPI, and, a host of other application changes in  terms of memory 
> locations.
>
> The newer chips starting with the 16F18855 chip family and then the 
> 18FxxK40 use the different protocol.  
>
> Options:
> IPE for MPLAB 5.xx and onwards
> PICKitPlus
> change programmer to a North Programmer ( very fast).
>
>
>
>
>
> On Saturday, 26 November 2022 at 11:49:30 UTC rob...@hotmail.com 
> wrote:
>
> Hi Filip,
>
> Which software are you using with your PicKit2, is that the standard 
> Microchip software?
>
> I guess you need a more recent database. Did you try that?
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens 
> flyway38 
> *Verzonden:* zaterdag 26 november 2022 11:17
> *Aan:* jallib 
> *Onderwerp:* [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 
> options 
>  
> Hello all,
>
> No help here?
> Tried to use PIC16F1939 as base to my PIC16F19176.
> Changed only Device ID (tried 30A0 as per datasheet and 309C as per 
> JAL PIC lib) and no luck.
> Kept all other parameters as they show similar to my PIC ones (at 
> least the ones I could identify).
> Pickit 2 shows warning message: "Hex File Loaded is large than device"
> Thank you very much.
>
> Regards,
> Filipe Santos.
>
>
> On Friday, November 25, 2022 at 7:37:44 PM UTC evan@googlemail.com 
> wrote:
>
> See 
> https://github.com/Anobium/PICKitPlus/tree/master/PickIt%20ScriptEditor 
> for our editor. 
>
> There are applications changes required to make the new chips.  
>
> But, happy to share the editor.
>
> Evan
>
> On Friday, 25 November 2022 at 19:33:08 UTC fsfo...@gmail.com wrote:
>

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

2022-11-27 Thread vsurducan

Evan, I am a bit confused. Pickit+ is using different firmware than the
original  Microchip. Pickit- is using Microchip firmware and Pickit+
database That looks strange in my logic, but also shows that Pickit-
may be somehow different than Pickit+?

On Sun 27 Nov 2022, 6:10 PM 'evan@googlemail.com' via jallib <
jallib@googlegroups.com wrote:

> @Filipe
>
> PICKIT- developer took our database, took our ideas and now are hurting
> us.  I have spoken on the real issues regarding the changes made to the
> database that can cause real damage to microcontrollers.
> I am personally in debt regarding the development of PICKitPlus.
> Please consider donating to our project even if the donation is a token
> donation of a few $$.
>
> Evan
>
> On Saturday, 26 November 2022 at 20:17:34 UTC fsfo...@gmail.com wrote:
>
>> Hi again.
>>
>> PickitMinus is great!!!
>> It has that PIC (16F19176) that am using (and many other ones) and it
>> worked like a charm.
>> Thank you so much Rob.
>>
>> Cheers,
>> Filipe Santos.
>>
>> On Saturday, November 26, 2022 at 8:08:05 PM UTC flyway38 wrote:
>>
>>> Hey Vasile/ Rob.
>>>
>>> Thank you very much for your input.
>>> Will check that options.
>>>
>>> Best regards,
>>> Filipe Santos.
>>>
>>> On Saturday, November 26, 2022 at 1:32:51 PM UTC evan@googlemail.com
>>> wrote:
>>>
 Yes. Not happy that someone took our work. Very unhappy.

 Get Outlook for Android 
 --
 *From:* jal...@googlegroups.com  on behalf of
 flyway38 
 *Sent:* Saturday, November 26, 2022 12:43:54 PM
 *To:* jallib 
 *Subject:* Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit
 2 options

 Hello Evan

 Yes, am using standard Pickit 2 software.
 Where do I find newer data base for it?
 Will google for it.
 Thanks.

 Regards,
 Filipe Santos.

 On Saturday, November 26, 2022 at 12:15:47 PM UTC
 evan@googlemail.com wrote:

 re:  The chip you are trying to add.

 It uses a different protocol for the SPI communications.  You will
 require to make changes to the application to change from LSB SPI to MSB
 SPI, and, a host of other application changes in  terms of memory 
 locations.

 The newer chips starting with the 16F18855 chip family and then the
 18FxxK40 use the different protocol.

 Options:
 IPE for MPLAB 5.xx and onwards
 PICKitPlus
 change programmer to a North Programmer ( very fast).

 On Saturday, 26 November 2022 at 11:49:30 UTC rob...@hotmail.com wrote:

 Hi Filip,

 Which software are you using with your PicKit2, is that the standard
 Microchip software?

 I guess you need a more recent database. Did you try that?

 Kind regards,

 Rob

 --
 *Van:* jal...@googlegroups.com  namens
 flyway38 
 *Verzonden:* zaterdag 26 november 2022 11:17
 *Aan:* jallib 
 *Onderwerp:* [jallib] Re: Help on integrating PIC16F19176 in Pickit 2
 options

 Hello all,

 No help here?
 Tried to use PIC16F1939 as base to my PIC16F19176.
 Changed only Device ID (tried 30A0 as per datasheet and 309C as per JAL
 PIC lib) and no luck.
 Kept all other parameters as they show similar to my PIC ones (at least
 the ones I could identify).
 Pickit 2 shows warning message: "Hex File Loaded is large than device"
 Thank you very much.

 Regards,
 Filipe Santos.

 On Friday, November 25, 2022 at 7:37:44 PM UTC evan@googlemail.com
 wrote:

 See
 https://github.com/Anobium/PICKitPlus/tree/master/PickIt%20ScriptEditor
 for our editor.

 There are applications changes required to make the new chips.

 But, happy to share the editor.

 Evan

 On Friday, 25 November 2022 at 19:33:08 UTC fsfo...@gmail.com wrote:

 Hey again Evan,

 Thank for the input and corrections.
 Just found a "cheaper" way :D
 https://jared.geek.nz/2013/jan/adding-extra-chips-to-the-pickit-2
 Now only need to find what's similar to my pic, in Pickit 2 original
 library.
 Thanks anyways.

 Greetings
 Filipe Santos.

 On Friday, November 25, 2022 at 7:21:42 PM UTC evan@googlemail.com
 wrote:

 Apologies.

 www.pickitplus.co.uk

 What works out of the box?  We provide PK2 software that is fully
 supported.  We are a Microchip Software Partner.
 Are you developer of what?  PICKITPlus software
 That website doesn't work (server not found)...My error, see URL abouve
 Not sure how to solve my issue that way. - install our software and it
 will work. We have Windows, LX and Pi versions.  We have UI version and
 command line versions.

 Evan

 On Friday, 25 November 2022 at 19:18:10 UTC

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

2022-11-27 Thread 'evan....@googlemail.com' via jallib

@Filipe 

PICKIT- developer took our database, took our ideas and now are hurting 
us.  I have spoken on the real issues regarding the changes made to the 
database that can cause real damage to microcontrollers.
I am personally in debt regarding the development of PICKitPlus.  
Please consider donating to our project even if the donation is a token 
donation of a few $$.

Evan

On Saturday, 26 November 2022 at 20:17:34 UTC fsfo...@gmail.com wrote:

> Hi again.
>
> PickitMinus is great!!!
> It has that PIC (16F19176) that am using (and many other ones) and it 
> worked like a charm.
> Thank you so much Rob.
>
> Cheers,
> Filipe Santos.
>
> On Saturday, November 26, 2022 at 8:08:05 PM UTC flyway38 wrote:
>
>> Hey Vasile/ Rob.
>>
>> Thank you very much for your input.
>> Will check that options.
>>
>> Best regards,
>> Filipe Santos.
>>
>> On Saturday, November 26, 2022 at 1:32:51 PM UTC evan@googlemail.com 
>> wrote:
>>
>>> Yes. Not happy that someone took our work. Very unhappy. 
>>>
>>> Get Outlook for Android 
>>> --
>>> *From:* jal...@googlegroups.com  on behalf of 
>>> flyway38 
>>> *Sent:* Saturday, November 26, 2022 12:43:54 PM
>>> *To:* jallib 
>>> *Subject:* Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 
>>> options 
>>>  
>>> Hello Evan
>>>
>>> Yes, am using standard Pickit 2 software.
>>> Where do I find newer data base for it?
>>> Will google for it.
>>> Thanks.
>>>
>>> Regards,
>>> Filipe Santos.
>>>
>>> On Saturday, November 26, 2022 at 12:15:47 PM UTC 
>>> evan@googlemail.com wrote:
>>>
>>> re:  The chip you are trying to add. 
>>>
>>> It uses a different protocol for the SPI communications.  You will 
>>> require to make changes to the application to change from LSB SPI to MSB 
>>> SPI, and, a host of other application changes in  terms of memory locations.
>>>
>>> The newer chips starting with the 16F18855 chip family and then the 
>>> 18FxxK40 use the different protocol.  
>>>
>>> Options:
>>> IPE for MPLAB 5.xx and onwards
>>> PICKitPlus
>>> change programmer to a North Programmer ( very fast).
>>>
>>>
>>>
>>>
>>>
>>> On Saturday, 26 November 2022 at 11:49:30 UTC rob...@hotmail.com wrote:
>>>
>>> Hi Filip,
>>>
>>> Which software are you using with your PicKit2, is that the standard 
>>> Microchip software?
>>>
>>> I guess you need a more recent database. Did you try that?
>>>
>>> Kind regards,
>>>
>>> Rob
>>>
>>> --
>>> *Van:* jal...@googlegroups.com  namens 
>>> flyway38 
>>> *Verzonden:* zaterdag 26 november 2022 11:17
>>> *Aan:* jallib 
>>> *Onderwerp:* [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 
>>> options 
>>>  
>>> Hello all,
>>>
>>> No help here?
>>> Tried to use PIC16F1939 as base to my PIC16F19176.
>>> Changed only Device ID (tried 30A0 as per datasheet and 309C as per JAL 
>>> PIC lib) and no luck.
>>> Kept all other parameters as they show similar to my PIC ones (at least 
>>> the ones I could identify).
>>> Pickit 2 shows warning message: "Hex File Loaded is large than device"
>>> Thank you very much.
>>>
>>> Regards,
>>> Filipe Santos.
>>>
>>>
>>> On Friday, November 25, 2022 at 7:37:44 PM UTC evan@googlemail.com 
>>> wrote:
>>>
>>> See 
>>> https://github.com/Anobium/PICKitPlus/tree/master/PickIt%20ScriptEditor 
>>> for our editor. 
>>>
>>> There are applications changes required to make the new chips.  
>>>
>>> But, happy to share the editor.
>>>
>>> Evan
>>>
>>> On Friday, 25 November 2022 at 19:33:08 UTC fsfo...@gmail.com wrote:
>>>
>>> Hey again Evan,
>>>
>>> Thank for the input and corrections.
>>> Just found a "cheaper" way :D
>>> https://jared.geek.nz/2013/jan/adding-extra-chips-to-the-pickit-2
>>> Now only need to find what's similar to my pic, in Pickit 2 original 
>>> library.
>>> Thanks anyways.
>>>
>>> Greetings
>>> Filipe Santos.
>>>
>>> On Friday, November 25, 2022 at 7:21:42 PM UTC evan@googlemail.com 
>>> wrote:
>>>
>>> Apologies. 
>>>
>>> www.pickitplus.co.uk
>>>
>>> What works out of the box?  We provide PK2 software that is fully 
>>> supported.  We are a Microchip Software Partner.
>>> Are you developer of what?  PICKITPlus software
>>> That website doesn't work (server not found)...My error, see URL abouve
>>> Not sure how to solve my issue that way. - install our software and it 
>>> will work. We have Windows, LX and Pi versions.  We have UI version and 
>>> command line versions.
>>>
>>> Evan
>>>
>>>
>>> On Friday, 25 November 2022 at 19:18:10 UTC fsfo...@gmail.com wrote:
>>>
>>> Hi Evan
>>>
>>> Not sure if understand correctly your text.
>>> What works out of the box?
>>> Are you developer of what?
>>> That website doesn't work (server not found)...
>>> Not sure how to solve my issue that way.
>>> I know I can add this PIC to Pickit 2 library. Just need some hint to 
>>> start with.
>>> Thanks
>>>
>>> Filipe Santos.
>>>
>>> On Friday, November 25, 2022 at 7:01:28 PM UTC evan@googlemail.com 
>>> wrote:
>>>
>>> Notes: As we

[jallib] [jallib/jallib] 91b9bc: Update of pic_data_eeprom.jal

2022-11-27 Thread 'Rob Jansen' via jallib

  Branch: refs/heads/master
  Home:   https://github.com/jallib/jallib
  Commit: 91b9bc0959104f5ad324fa3f904a84cf00a924d9
  
https://github.com/jallib/jallib/commit/91b9bc0959104f5ad324fa3f904a84cf00a924d9
  Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
  Date:   2022-11-27 (Sun, 27 Nov 2022)

  Changed paths:
M CHANGELOG
M TORELEASE
M include/peripheral/data_eeprom/pic_data_eeprom.jal
A sample/16f19176_data_eeprom.jal

  Log Message:
  ---
  Update of pic_data_eeprom.jal

Included a new sample file for the pic16f19176.


-- 
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/df5e3e-91b9bc%40github.com.

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread Rob CJ

Hi Filipe,

The update was quite simple. Attached the new library and a sample program.

I tested it and it works OK.

The updated library and new sample file will be in the next bee-package.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: zondag 27 november 2022 16:27
Aan: jallib 
Onderwerp: Re: [jallib] Re: PIC16F19176 EEprom Error

Hi Filipe,

I will update the library. I will let you know when it is available.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:59
Aan: jallib 
Onderwerp: Re: [jallib] Re: PIC16F19176 EEprom Error

Hi Rob,

Thank you for your feedback.
Its ok, can wait.
To try to solve it myself will need some hints.. In this case will keep this 
thread updated until final solution.
But if you get your hands on this issue, just let me know.
Thank you very much.

Cheers,
Filipe Santos.


On Sunday, November 27, 2022 at 12:35:30 PM UTC rob...@hotmail.com wrote:
Hi Filip,

Correct. This PIC you are using has different register and also - if I am right 
- a way to write EEPROM data in words instead of bytes.

So the currently library needs an update to support your chip.

At this moment I am working on trying to solve compiler issue#25 but partly 
succesful so far. If I get stuck (and it seems I currently am) I can give it a 
try to update the EEPROM library. Of course you can also give it a try yourself.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:25
Aan: jallib 
Onderwerp: [jallib] Re: PIC16F19176 EEprom Error

It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
Pic's Lib file:
-- EEPROM data byte.
if defined(EEDATL) then
   alias _EEPROM_DATA is EEDATL
elsif defined(EEDAT) then
   alias _EEPROM_DATA is EEDAT
elsif defined(EEDATA) then
   alias _EEPROM_DATA is EEDATA
elsif defined(NVMDAT) then
   alias _EEPROM_DATA is NVMDAT
end if

In Pic's Lib have found this definitions:
-- 
var volatile byte   NVMDATL   at { 0x81C }
var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
-- 
var volatile byte   NVMDATH   at { 0x81D }
var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
-- 

Not sure how to proceed with corrections here.
Any ideas will be great.
Thank you.

FS

On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
Hello to all,

Am starting this new project based on PIC16F19176.
Am including Pic_Data_Eeprom lib but compiler gives me this error:

Compilation started at :27/11/2022 12:06:11
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
[Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
[Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got '_eeprom_data')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
[Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
Santos\Desktop\NotasTecnicas\_Projecto - 
ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" -s 
"C:\JALLIB~1\lib" -no-variable-reuse

Errors :6   Warnings :0

Any help here will be very appreciated.
Thank you.

Greetings,
Filipe Santos.

--
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/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread Rob CJ

Hi Filipe,

I will update the library. I will let you know when it is available.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:59
Aan: jallib 
Onderwerp: Re: [jallib] Re: PIC16F19176 EEprom Error

Hi Rob,

Thank you for your feedback.
Its ok, can wait.
To try to solve it myself will need some hints.. In this case will keep this 
thread updated until final solution.
But if you get your hands on this issue, just let me know.
Thank you very much.

Cheers,
Filipe Santos.


On Sunday, November 27, 2022 at 12:35:30 PM UTC rob...@hotmail.com wrote:
Hi Filip,

Correct. This PIC you are using has different register and also - if I am right 
- a way to write EEPROM data in words instead of bytes.

So the currently library needs an update to support your chip.

At this moment I am working on trying to solve compiler issue#25 but partly 
succesful so far. If I get stuck (and it seems I currently am) I can give it a 
try to update the EEPROM library. Of course you can also give it a try yourself.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:25
Aan: jallib 
Onderwerp: [jallib] Re: PIC16F19176 EEprom Error

It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
Pic's Lib file:
-- EEPROM data byte.
if defined(EEDATL) then
   alias _EEPROM_DATA is EEDATL
elsif defined(EEDAT) then
   alias _EEPROM_DATA is EEDAT
elsif defined(EEDATA) then
   alias _EEPROM_DATA is EEDATA
elsif defined(NVMDAT) then
   alias _EEPROM_DATA is NVMDAT
end if

In Pic's Lib have found this definitions:
-- 
var volatile byte   NVMDATL   at { 0x81C }
var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
-- 
var volatile byte   NVMDATH   at { 0x81D }
var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
-- 

Not sure how to proceed with corrections here.
Any ideas will be great.
Thank you.

FS

On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
Hello to all,

Am starting this new project based on PIC16F19176.
Am including Pic_Data_Eeprom lib but compiler gives me this error:

Compilation started at :27/11/2022 12:06:11
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
[Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
[Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got '_eeprom_data')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
[Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
Santos\Desktop\NotasTecnicas\_Projecto - 
ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" -s 
"C:\JALLIB~1\lib" -no-variable-reuse

Errors :6   Warnings :0

Any help here will be very appreciated.
Thank you.

Greetings,
Filipe Santos.

--
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/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%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

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread flyway38

Hi Rob,

Thank you for your feedback.
Its ok, can wait.
To try to solve it myself will need some hints.. In this case will keep 
this thread updated until final solution.
But if you get your hands on this issue, just let me know.
Thank you very much.

Cheers,
Filipe Santos.


On Sunday, November 27, 2022 at 12:35:30 PM UTC rob...@hotmail.com wrote:

> Hi Filip,
>
> Correct. This PIC you are using has different register and also - if I am 
> right - a way to write EEPROM data in words instead of bytes.
>
> So the currently library needs an update to support your chip.
>
> At this moment I am working on trying to solve compiler issue#25 but 
> partly succesful so far. If I get stuck (and it seems I currently am) I can 
> give it a try to update the EEPROM library. Of course you can also give it 
> a try yourself.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens flyway38 <
> fsfo...@gmail.com>
> *Verzonden:* zondag 27 november 2022 13:25
> *Aan:* jallib 
> *Onderwerp:* [jallib] Re: PIC16F19176 EEprom Error 
>  
> It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
> Pic's Lib file:
> -- EEPROM data byte.
> if defined(EEDATL) then
>alias _EEPROM_DATA is EEDATL
> elsif defined(EEDAT) then
>alias _EEPROM_DATA is EEDAT
> elsif defined(EEDATA) then
>alias _EEPROM_DATA is EEDATA
> elsif defined(NVMDAT) then
>alias _EEPROM_DATA is NVMDAT
> end if 
>
> In Pic's Lib have found this definitions:
> -- 
> var volatile byte   NVMDATL   at { 0x81C }
> var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
> var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
> var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
> var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
> var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
> var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
> var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
> var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
> -- 
> var volatile byte   NVMDATH   at { 0x81D }
> var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
> var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
> var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
> var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
> var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
> var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
> -- 
>
> Not sure how to proceed with corrections here.
> Any ideas will be great.
> Thank you.
>
> FS
>
> On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
>
> Hello to all,
>
> Am starting this new project based on PIC16F19176.
> Am including Pic_Data_Eeprom lib but compiler gives me this error:
>
> Compilation started at :27/11/2022 12:06:11
> jal jalv25r6 (compiled Oct 29 2021)
> generating p-code
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got 
> '_eeprom_data')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
> C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
> Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
> Santos\Desktop\NotasTecnicas\_Projecto - 
> ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" 
> -s "C:\JALLIB~1\lib" -no-variable-reuse  
>
> Errors :6   Warnings :0
>
> Any help here will be very appreciated.
> Thank you.
>
> Greetings,
> Filipe Santos.
>
> -- 
> 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/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%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/879bf075-9f21-43be-ae02-12673fc49500n%40googlegroups.com.

Re: [jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread Rob CJ

Hi Filip,

Correct. This PIC you are using has different register and also - if I am right 
- a way to write EEPROM data in words instead of bytes.

So the currently library needs an update to support your chip.

At this moment I am working on trying to solve compiler issue#25 but partly 
succesful so far. If I get stuck (and it seems I currently am) I can give it a 
try to update the EEPROM library. Of course you can also give it a try yourself.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: zondag 27 november 2022 13:25
Aan: jallib 
Onderwerp: [jallib] Re: PIC16F19176 EEprom Error

It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
Pic's Lib file:
-- EEPROM data byte.
if defined(EEDATL) then
   alias _EEPROM_DATA is EEDATL
elsif defined(EEDAT) then
   alias _EEPROM_DATA is EEDAT
elsif defined(EEDATA) then
   alias _EEPROM_DATA is EEDATA
elsif defined(NVMDAT) then
   alias _EEPROM_DATA is NVMDAT
end if

In Pic's Lib have found this definitions:
-- 
var volatile byte   NVMDATL   at { 0x81C }
var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
-- 
var volatile byte   NVMDATH   at { 0x81D }
var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
-- 

Not sure how to proceed with corrections here.
Any ideas will be great.
Thank you.

FS

On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:
Hello to all,

Am starting this new project based on PIC16F19176.
Am including Pic_Data_Eeprom lib but compiler gives me this error:

Compilation started at :27/11/2022 12:06:11
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
[Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
[Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got '_eeprom_data')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
[Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
Santos\Desktop\NotasTecnicas\_Projecto - 
ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" -s 
"C:\JALLIB~1\lib" -no-variable-reuse

Errors :6   Warnings :0

Any help here will be very appreciated.
Thank you.

Greetings,
Filipe Santos.

--
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/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%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/GVXP195MB16379CAB7DFE438CEAE4A01FE6109%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

[jallib] Re: PIC16F19176 EEprom Error

2022-11-27 Thread flyway38

It seems none of these definitions (in Pic_Data_Eeprom Lib) are defined in 
Pic's Lib file:
-- EEPROM data byte.
if defined(EEDATL) then
   alias _EEPROM_DATA is EEDATL
elsif defined(EEDAT) then
   alias _EEPROM_DATA is EEDAT
elsif defined(EEDATA) then
   alias _EEPROM_DATA is EEDATA
elsif defined(NVMDAT) then
   alias _EEPROM_DATA is NVMDAT
end if 

In Pic's Lib have found this definitions:
-- 
var volatile byte   NVMDATL   at { 0x81C }
var volatile bitNVMDATL_NVMDAT0   at NVMDATL : 0
var volatile bitNVMDATL_NVMDAT1   at NVMDATL : 1
var volatile bitNVMDATL_NVMDAT2   at NVMDATL : 2
var volatile bitNVMDATL_NVMDAT3   at NVMDATL : 3
var volatile bitNVMDATL_NVMDAT4   at NVMDATL : 4
var volatile bitNVMDATL_NVMDAT5   at NVMDATL : 5
var volatile bitNVMDATL_NVMDAT6   at NVMDATL : 6
var volatile bitNVMDATL_NVMDAT7   at NVMDATL : 7
-- 
var volatile byte   NVMDATH   at { 0x81D }
var volatile bitNVMDATH_NVMDAT8   at NVMDATH : 0
var volatile bitNVMDATH_NVMDAT9   at NVMDATH : 1
var volatile bitNVMDATH_NVMDAT10  at NVMDATH : 2
var volatile bitNVMDATH_NVMDAT11  at NVMDATH : 3
var volatile bitNVMDATH_NVMDAT12  at NVMDATH : 4
var volatile bitNVMDATH_NVMDAT13  at NVMDATH : 5
-- 

Not sure how to proceed with corrections here.
Any ideas will be great.
Thank you.

FS

On Sunday, November 27, 2022 at 12:19:18 PM UTC flyway38 wrote:

> Hello to all,
>
> Am starting this new project based on PIC16F19176.
> Am including Pic_Data_Eeprom lib but compiler gives me this error:
>
> Compilation started at :27/11/2022 12:06:11
> jal jalv25r6 (compiled Oct 29 2021)
> generating p-code
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got 
> '_eeprom_data')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
> C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
> [Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
> Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
> Santos\Desktop\NotasTecnicas\_Projecto - 
> ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" 
> -s "C:\JALLIB~1\lib" -no-variable-reuse  
>
> Errors :6   Warnings :0
>
> Any help here will be very appreciated.
> Thank you.
>
> Greetings,
> Filipe Santos.
>

-- 
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/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%40googlegroups.com.

[jallib] PIC16F19176 EEprom Error

2022-11-27 Thread flyway38

Hello to all,

Am starting this new project based on PIC16F19176.
Am including Pic_Data_Eeprom lib but compiler gives me this error:

Compilation started at :27/11/2022 12:06:11
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
[Error] (lib/pic_data_eeprom.jal) [Line 194]  "_eeprom_data" not defined
[Error] (lib/pic_data_eeprom.jal) [Line 194]  ')' expected (got 
'_eeprom_data')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  '=' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  'end' expected (got ')')
[Error] (lib/pic_data_eeprom.jal) [Line 194]  {procedure starts at 
C:\JALLIB~1\lib/pic_data_eeprom.jal:190}
[Error] (lib/pic_data_eeprom.jal) [Line 194]  unexpected token: ")"
Compiler CommandLine:  C:\JALLIB~1\compiler\jalv2.exe "C:\Users\Filipe 
Santos\Desktop\NotasTecnicas\_Projecto - 
ParquimetrosTelemetricos\Desenvolvimento\PIC\16f19176_serial_hardware.jal" 
-s "C:\JALLIB~1\lib" -no-variable-reuse  

Errors :6   Warnings :0

Any help here will be very appreciated.
Thank you.

Greetings,
Filipe Santos.

-- 
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/83019dff-9b87-4ac5-88fd-231a3b4c720fn%40googlegroups.com.

Re: [jallib] Re: PIC16F19176 EEprom Error

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

Re: [jallib] Re: PIC16F19176 EEprom Error

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

Re: [jallib] Re: Help on integrating PIC16F19176 in Pickit 2 options

[jallib] [jallib/jallib] 91b9bc: Update of pic_data_eeprom.jal

Re: [jallib] Re: PIC16F19176 EEprom Error

Re: [jallib] Re: PIC16F19176 EEprom Error

Re: [jallib] Re: PIC16F19176 EEprom Error

Re: [jallib] Re: PIC16F19176 EEprom Error

[jallib] Re: PIC16F19176 EEprom Error

[jallib] PIC16F19176 EEprom Error

13 matches

Site Navigation

Mail list logo

Footer information