Hi Rob, Thank you for the info and your commitment to JAL.
In the meantime, I made some compromises and headed to use 16F1788. But I put the project on hold because I was not very satisfied, because of those compromises. Now that 16F17156 is available in JAL, I can rollback and use it.... But it seems also that it is not (yet ?) available in SOIC package, which is the form factor I use (mandatory constraint) 18F24Q71 is not in stock either in soic package at my distributor (M*user) So, I still got stuck with it.... I'l keep you update, but as you see, it could take a while....... Have a nice day, David Le vendredi 26 mai 2023 à 20:48:22 UTC+2, [email protected] a écrit : > Hi David, > > Yesterday I saw that a new version of MPLABX was released so I ran the > Python script to generate the device files. And guess what, both chips you > mentioned where in. > > I could not test the device files since I do not have the IC's so I > attached them (16f17156 and 18f24q71) to this post for you to test the one > you are going to use. If it works for you I can add them to the Jallib > release. > > Kind regards, > > Rob > > > Op maandag 10 april 2023 om 20:12:29 UTC+2 schreef [email protected]: > >> Hi David, >> >> Same issue, not yet in MPLABX so not able to generate a device file yet. >> >> I wanted to suggest the site of Microchip to select the device but I saw >> you already found it. >> >> It is indeed not a handy site or you must be very patient. >> >> Kind regards, >> >> Rob >> >> ------------------------------ >> *Van:* [email protected] <[email protected]> namens Pinhead < >> [email protected]> >> *Verzonden:* maandag 10 april 2023 19:13 >> *Aan:* [email protected] <[email protected]> >> *Onderwerp:* Re: [jallib] Device file for PIC16F17156 >> >> >> Thanks Rob, >> >> >> In the meantime, I was also looking also for another model and found >> 18F24Q71 that could meet my expectations, but it is not (yet) supported by >> jal either..... >> >> >> What I need: >> >> >> MANDATORY: >> >> - Two SPI bus (CLK and Data will be shared; /CS will select the chip) >> - One I²C bus >> - One simple serial port (DT + CK) >> - One OPA that can be configured in Unity gain mode >> - ADC (8 bit resolution is enough) >> - At least two 16-bit timers >> - At least two 8-bit timers >> - 28-pins form factor with 25 I/O pins (/MCLR not included) >> - 128-bits of EEPROM or HEF or NVRAM >> >> - A fair amount of program memory since my application will include a lot >> of strings (at least 7 k) >> >> >> NICE TO HAVE: >> >> - PPS >> - ADC can be configured to internally connect to OPA_Output as input >> - RTCC >> >> I will not buy or order samples as long as I am not sure at 80% of which >> reference I will use, so I will not be able to test a device file in real >> condition, but thanks for the proposal. >> >> >> By the way, The Microchip selection tool on their website really sucks. >> Does anyone know of a simplier way to enter criteria to search for a >> suitable part ? >> >> >> Have a nice day >> >> >> >> >> Le 10-04-23 à 18:58, Rob CJ a écrit : >> >> Hi David, >> >> As soon as the devices is part of MPLABX I can create a device file. >> Since it is not yet available in MPLABX 6.05 I also did not yet order a >> sample for testing. >> >> When a new version of MPLABX is out where and that device is in, I can >> send you an untested device file. >> >> I do not know when a new version of MPLABX is released so we have to wait >> for it. >> >> Kind regards, >> >> Rob >> >> ------------------------------ >> *Van:* [email protected] <[email protected]> namens >> [email protected] <[email protected]> >> *Verzonden:* maandag 10 april 2023 17:41 >> *Aan:* jallib <[email protected]> >> *Onderwerp:* [jallib] Device file for PIC16F17156 >> >> Hi there, >> >> Starting a new project, I was considering using the 16F17156. But the >> device is still very new and the device file apparently does not exists yet. >> Do you have an idea if and when it could be available ? Otherwise, I >> can also consider using another PIC.... >> >> Thanks for your answer, and have a nice day, >> >> David >> -- >> 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/97722f64-5f8b-495c-afe4-d9f97c3e56c2n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jallib/97722f64-5f8b-495c-afe4-d9f97c3e56c2n%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/GVXP195MB163791E6F225FA4A4B994CABE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM >> >> <https://groups.google.com/d/msgid/jallib/GVXP195MB163791E6F225FA4A4B994CABE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.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/d162cc1d-8f79-5230-2a28-be44ba631dbb%40gmail.com >> >> <https://groups.google.com/d/msgid/jallib/d162cc1d-8f79-5230-2a28-be44ba631dbb%40gmail.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/70913344-2e65-475a-b0d9-b746a5dc63bdn%40googlegroups.com.
