Hi Rob,
Possibly a stupid comment on my part, but why must all types be included in the JAL package. I can imagine that companies have very specific wishes, but is this also the case with the JALLERS? A JAL extract from this would at least be much easier for me and save you a lot of time answering my nagging . regards Hans Op dinsdag 27 juni 2023 om 10:16:55 UTC+2 schreef Rob CJ: > Hi Oliver, > > Nice suggestion. > > I could adapt the Python script that creates the device file to add a list > of untested device files and add a compiler warning to these device files. > > There is one thing I am not sure about. Normally all samples are validated > and build when something changes and when that fails (compiler errors) no > new bee-package is released. What I am not sure about if all goes well if > some samples will create compiler warnings. The fact is that these device > files are tested with the corresponding blink samples so that will then > create compiler warnings. > > Question for anybody else who knows this. Is it allowed to have samples > files that create warnings when being compiled? Does that not break the > build? > > Thanks. > > Kind regards, > > Rob > > ------------------------------ > *Van:* 'Oliver Seitz' via jallib <[email protected]> > *Verzonden:* maandag 26 juni 2023 11:05 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* Re: [jallib] Releasing untested device files > > Hi all, > > If you would maintain a list of tested devices, all untested ones could > have a compiler warning in the device file. That way, users would be warned > that issues may arise, and they can be asked to inform Rob if no issues > arise (and the device can be added to the "tested" list). > > Greets, > Kiste > > Am Montag, 26. Juni 2023 um 09:35:51 MESZ hat [email protected] < > [email protected]> Folgendes geschrieben: > > > Hi all, > > When new PICs are released, I create new device files using the data > provided in MPLABX. > > Normally I do a test of a device file by running the blink-a-led sample > program. For that I order free samples from Microchip. > > Microchip seems to change this and now you must have a business (and a VAT > number) in order to get samples and it seems that it is no longer free. > Since I have no business and did not plan to buy all available PIC > microcontroller I plan to release all new device files untested. > > In the years that I have taken over the device file creation from Rob > Hamerling I did not found any issues lately with device files since > Microchip is doing a better job than in the past. > > The advantage of this is that I can release a device file as soon as it is > available in MPLABX and you do not need to wait for me to get a sample to > test it. > > Let me know what you think. > > Thanks > > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/32e0d734-ab4e-455e-b66f-828dc78bd531n%40googlegroups.com > > <https://groups.google.com/d/msgid/jallib/32e0d734-ab4e-455e-b66f-828dc78bd531n%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/1800797843.2813413.1687770347855%40mail.yahoo.com > > <https://groups.google.com/d/msgid/jallib/1800797843.2813413.1687770347855%40mail.yahoo.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/32ce441f-33fe-48c5-a309-5b2dc6ac805bn%40googlegroups.com.
