[Wish] PIC16F18325

[Toley]

I would like to see this familly PIC16F1832x (mostly the 16F18325 one) added to your compilers.

I know it's hard to follow Microchip part release flow. But new chips always bring and combine newest fonctionnality. If someone wants to create innovative desing, he must be among the firsts to integrate those new fonctionnality.

[aleksa.jovanovic]

Hi,

I will forward this to the development department,
but be assured that they are working to the fullest trying to incorporate new chips as fast as possible.

Best regards,
Aleksa

[janni]

As much as I appreciate the effort developers have to put out to keep the compilers in shape, problem of updating the definition files seems to be mostly organisational. These files have to be updated eventually so the work has to be done - there's no fundamental reason to delay the work till next compiler update. It also does not make the company looking good if many faulty definition files stay without correction for most of the year, like it takes place now.

As it has been suggested more than once, the definition files could be made accessible separately from compilers and updated or corrected whenever necessary. After all, these are separate files, working on one doesn't require testing of the compiler+IDE combo.

[aleksa.jovanovic]

I will speak with the development department about this.
Thank you for your suggestion.

Best regards,
Aleksa

[Toley]

As much as I appreciate the effort developers have to put out to keep the compilers in shape, problem of updating the definition files seems to be mostly organisational. These files have to be updated eventually so the work has to be done - there's no fundamental reason to delay the work till next compiler update. It also does not make the company looking good if many faulty definition files stay without correction for most of the year, like it takes place now.

As it has been suggested more than once, the definition files could be made accessible separately from compilers and updated or corrected whenever necessary. After all, these are separate files, working on one doesn't require testing of the compiler+IDE combo.

100% agree with you Janni. Maybe a conversion tool could be publicly available so peoples can produce their own defs files based on Microchip's ones. Naturally at their own risk.

Edit: But the remaining problem will be with mikroProg.

[tekkieguy]

Just adding my vote to add the PIC16F18323, PIC16F18324, PIC16F18325, PIC16F18326, PIC16F18344, PIC16F18345 and PIC16F18346 to the MikroC compiler list of parts. These appear to be very cost effective parts (ie. cheap) with lots of capabilities. In the meantime I'm using Microchips software to program them. Since its been 3 months from the first request I thought I'd refresh the request. Any timeline to when they will be added?

[biljana.nedeljkovic]

Hello,

Thank you for the suggestion.
It was reported to our development team.

We expect it to be supported in the next release of the compiler.

Kind regards,
Biljana

[Toley]

Any timeline to when they will be added?

We expect it to be supported in the next release of the compiler.

As usual the same answer is given without any precise timeline.

[biljana.nedeljkovic]

Hello Serge,

Unfortunately, I do not have any precise information about the dates of the compiler's releases, that is the reason I do not know any particular date for certain.

The request was submitted.
Thank you for the patience.

Kind regards,
Biljana

[Toley]

New version came out (6.6.3) and this chip is still not there.

[biljana.nedeljkovic]

Hello,

The new release was planned before this submission, where we mainly planned to add site license feature.
http://www.mikroe.com/site-license/

Next update will certainly add support for new devices.

Publicly available conversion tool you mentioned is an interesting idea. Thank you for the feedback.


Best regards,
Biljana

[Toley]

Microchip already released a new version of this chip. PIC16F18326 same pinout but more mappable peripherals and 2x ROM and 2x RAM. So if ever mE release a version that support PIC16F18325 it will be overpassed.

[ilferrari]

Why is this even on the wish list? Other compilers like XC8 are updated as soon as new devices are released. ME take years. They have not updated their 16 bit compiler in 2.5 years and counting. When it finally comes out the new devices will be old.

[Toley]

Other compilers like XC8 are updated as soon as new devices are released.

You cannot compare third party compiler with XC8. XC8 is Microchip's own compiler, if they don't support their own chip nobody will do and they will not sell any.

But the fact remains that mikroe takes too much time to release compilers update, unless they have a new hardware product to support and promote.

My guess is that they don't have any engineering staff onsite working on the compilers. All the compilers upgrades are given to an external consulting firm and they have to order specific task and pay for the job to be done. This is why they only make specific updates to support their new products and no support for new devices.

[Aleksandar.Mitrovic]

Hi,

First of all, we have our own development team which is working continuously on the updates for all of our compilers, GUI's, libraries, applications.

In resent time we support microchip ARM, Kinetis, release new Visual TFT, updates for PIC, and many other things...

We are trying to follow up new releases of the chips for all compilers as much as we can.

I apologize of behalf of our team if some compilers have been unintentionally neglected. This summer we have planed release for the dsPIC and PIC.
Therefore I suggest you to inform us if you need some specific MCU to be supported, just in case if its not on our list.

Kind regards from the mikroE team,
Aleksandar