Hi Andreas, Thanks.to Mic
I do not buy the chips but I order free samples at Microchip. You can only do that if you have a business which I do not have so I explained to Microchip that I need them for our Jallib community to test device files. The number of samples you can order is limited in quantity and in the time period so I cannot order samples for all new devices at the same time. That is also the reason why your devicefile was not yet in. It was available on GitHub (like other new chips) but it was not yet tested and so not release. The testing of the device is quite simple. I run the available LED blink sample files to see if they work. It can still be that the device file contains a bug so if you run into one, just report it. I have not encountered real errors over the last years. I do see that Microchip sometimes fixes incorrect register names when a new version of MPLABX comes out. I always update all new device files as to keep it consistent. Once a sample works, all related devices for that same family are added to the Jallib release. You can download the bee-package if you want the latest and greatest device files and libraries. Today I ran into one issue, I ordered a sample of a PIC18F46q71 and it did not work. I was already informed by Rob Hamerling that he encountered the same issue but I had no sample to test it. It seems that the bug is in the MPLABX IPE software of Microchip since I wanted to program it with the SNAP programmer (the newer chips are not supported by Microchip with the PICkit3 software) but as said it did not work. Luckily I had received the latest version of the PICKit+ software from Evan and that did the job. If I had not know it up front I would have spent hours to find it out but Rob Hamerling had it already working with his own programmer so the chip and the device file should be OK. And about the compiler. There are issues reported that I would like to fix but in some cases it is very hard to do since it is not code that I have written. So sometimes I do an attempt and if it is not successful then I stop and try again some other time. You can find the reported issues on GitHub under Jallib/compiler. Most of the time there is a workaround but it would be better to get the bugs out. Good luck with your project. Kind regards, Rob ________________________________ Van: '[email protected]' via jallib <[email protected]> Verzonden: woensdag 12 april 2023 19:28 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] missing devicefile for 16F18075.jal I never thought you are buying new chips to physically test them before release the new device files. Outstanding quality comitment!! Now I understand why the compiler does such a great job over all the years! Thank you Rob! Andreas On Wednesday, April 12, 2023 at 7:02:19 PM UTC+2 [email protected] wrote: Hi Andreas, I received the PIC16F18075 and tested and, as you already mentioned, it works. I added the device to the Jallib release so it will be in the next bee-package. In the change log you can see which other device files and libraries have been added. Kind regards, Rob Op zondag 2 april 2023 om 09:36:00 UTC+2 schreef [email protected]: Thanks for the feedback. I ordered the samples for this PIC and do some testing too and add the device file to the release. Kind regards, Rob ________________________________ Van: '[email protected]' via jallib <[email protected]> Verzonden: zaterdag 1 april 2023 20:32 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] missing devicefile for 16F18075.jal Hi, I have been working with this file for a while now, and all seems fine as it usually does. On Tuesday, March 28, 2023 at 11:34:26 PM UTC+2 [email protected] wrote: Thanks a lot Rob! I will let you know if I can see anything wrong with it in a few days. Thanks for the superfast response! Andreas On Tuesday, March 28, 2023 at 2:19:43 PM UTC+2 Rob CJ wrote: Hi, That device file is not yet released since it was not tested yet. You can give it a try, see attached device file. I assume it works since I did not encounter any problems over the last year. I am curretly using an 16F18076 without problems in the device file (not in the chip though 🙁). Can you let us know if it works? Thanks. Kind regards, Rob ________________________________ Van: '[email protected]' via jallib <[email protected]> Verzonden: dinsdag 28 maart 2023 13:16 Aan: jallib <[email protected]> Onderwerp: [jallib] missing devicefile for 16F18075.jal Hello everyone, I started a new projet based on this device, but no devicefile yet. Can anyone provide one? Thank you! -- 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/a8f785f8-ac3f-4fe1-af7e-42a324fa0ac3n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/a8f785f8-ac3f-4fe1-af7e-42a324fa0ac3n%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/bd47bfff-c658-497d-b54c-b322cbe1d527n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/bd47bfff-c658-497d-b54c-b322cbe1d527n%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/54e32dbe-ec91-4394-91cf-aeb467626da1n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/54e32dbe-ec91-4394-91cf-aeb467626da1n%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/GVXP195MB16377FD344F5AA5E9BF34C63E69B9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.
