Hi Filipe, I will update the library. I will let you know when it is available.
Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens flyway38 <[email protected]> Verzonden: zondag 27 november 2022 13:59 Aan: jallib <[email protected]> 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 [email protected] 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: [email protected] <[email protected]> namens flyway38 <[email protected]> Verzonden: zondag 27 november 2022 13:25 Aan: jallib <[email protected]> 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 bit NVMDATL_NVMDAT0 at NVMDATL : 0 var volatile bit NVMDATL_NVMDAT1 at NVMDATL : 1 var volatile bit NVMDATL_NVMDAT2 at NVMDATL : 2 var volatile bit NVMDATL_NVMDAT3 at NVMDATL : 3 var volatile bit NVMDATL_NVMDAT4 at NVMDATL : 4 var volatile bit NVMDATL_NVMDAT5 at NVMDATL : 5 var volatile bit NVMDATL_NVMDAT6 at NVMDATL : 6 var volatile bit NVMDATL_NVMDAT7 at NVMDATL : 7 -- ------------------------------------------------ var volatile byte NVMDATH at { 0x81D } var volatile bit NVMDATH_NVMDAT8 at NVMDATH : 0 var volatile bit NVMDATH_NVMDAT9 at NVMDATH : 1 var volatile bit NVMDATH_NVMDAT10 at NVMDATH : 2 var volatile bit NVMDATH_NVMDAT11 at NVMDATH : 3 var volatile bit NVMDATH_NVMDAT12 at NVMDATH : 4 var volatile bit NVMDATH_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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%40googlegroups.com<https://groups.google.com/d/msgid/jallib/29d685d9-fda5-4afa-b1ae-b7ceadf17b8en%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/879bf075-9f21-43be-ae02-12673fc49500n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/879bf075-9f21-43be-ae02-12673fc49500n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/GVXP195MB16374130D559ED9341E3671AE6109%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.
