18F16Q40 PIC MCU not present in MicroC v7.6.0 compiler MCU list

[leo73]

Hello Every one,
I need to program 18F16Q40 PIC MCU, i installed MicroC V 7.6.0 unfortunatelly, when i open a new project, this MCU version is not present in mikroC mcu list.
Is possible buy PIC18FxxK42.mlk/PIC18FxxK40.mlk file definition?

How can i do please?
Datasheet Link:
https://ww1.microchip.com/downloads/aem ... 2216D.pdf

15.Feb.2023 14.00
I found one similar discussion (for 18F66Q40), I do not know if can set 18F16Q40 MCU. However in attachment the MCU library file.
viewtopic.php?f=88&t=71362&hilit=glcd+k40&start=15

Some one have some else good solution?

Thank you to your reply.
Regards.
Leo.

[janni]

Hi Leo,

Unfortunately, except for Q10 processors, mC PRO will not work with Qxx ones due to their RAM structure. Compiler has some addresses hard coded and they cannot be moved by changes to definition files.

Is possible buy PIC18FxxK42.mlk/PIC18FxxK40.mlk file definition?

Definition files for these families come with the compiler - did you mean some specific processors missing in the compiler distribution?

I found one similar discussion (for 18F66Q40)

That's about a K40 processor. If you thought that its definition file could be easily converted to a Q40 processor then the answer is no .

[leo73]

Hello janni,
My solution is search a MCU mikroC compatible and must have 20pins(28io), 64kb rom, >=2kb ram, same pinout of16F18346.
What pic MCU can i mount?
Thank you.

[janni]

Unfortunately, I don't have a better answer for your requirements than the 18F16Q40 or 18F16Q41 processors .

The PIC AI compiler that comes with Necto can nominally work with this processors but there are no official definition files for this family and, due to some really stupid decisions, one cannot just add and use new definition files to Necto - any changes to its database (that's a new addition deciding about 'registered' processors besides definition files) are destroyed as soon it connects to internet.

You'd have to switch to another compiler to be able to work with newer processors, I'm afraid.

[leo73]

janni excuse me if I insist. I want to understand well !
An alternative to the 16F18346 pic that has 20pins(28I/O), 64kb ram and 2kb rom exists or not?

[janni]

Sorry, I thought it was clear - both 18F16Q40 and 18F16Q41 fulfill your requirements (well ,except that no processor can have 20pins and 28 I/Os ).

[leo73]

Sorry my mistakes.
You're nice !!!

[leo73]

Evening to every one,
We'll wait Mikro elektronica company try a good solution to programme Q pic8 series.
I Think, for a moment is more better draw another project boards using 18F26k22 series. Same Eagle project and change MCU only. Finished !!
:

[paulfjujo]

hello Leo

you better have to go with MPLAB and XC8
for new MCU .... like PIC18F27Q10 not supported by mikroC

..Unfortunately, except for Q10 processors, mC PRO will not work with Qxx ones due to their RAM structure.

i didn't discover 18Fxx*Q10 MCU in MikroC pro 7.60 MCU list !

MikroC Pro is now, an abandonware software..
and Necto Studio is a too much complicated application !
it's a big shame... because MikroC was realy an easy way to compile MCU program.

I Think, for a moment is more better draw another project boards using 18F26k22 series

look at 18F27K42 , better than 18F26K22 and cheaper ... even if it needs more time to study this MCU (datasheet > 800 pages)

[janni]

i didn't discover 18Fxx*Q10 MCU in MikroC pro 7.60 MCU list !

And I didn't say it's there . What I did write though is true. With enough care and patience one may write definition files for Q10 processors and compiler will work with them. Due to shortage of K40 processors last year I had to switch to Q10s and thus, to avoid porting my old code to another compiler I've prepared definition files for 26Q10 and 47Q10 processors for mP PRO. Happily enough, none of my code depends on mE's libraries so that was all I needed (well, my EEPROM and Flash libs had to be adjusted as well).

[s.struve]

Hello janni,
would you be so kind to post those files here? Maybe I can copy/paste to some extent for the files for µC. I have run into the same problem and have already made designs for PIC18F47Q10 MCUs.

[janni]

I certainly can post the definition files for PIC18F47Q10 though porting them to mC won't be much fun. You'll also have to correct the library list in .mlk file.

47Q10Defs.rar

(26.23 KiB) Downloaded 70 times

Good luck .

[davegsm82]

I would be really interested to know if anyone gets the 27Q10 processor working with 7.60 as I've just ordered some of these for a project and realised they aren't supported. I should have checked first.

I still get unreasonably upset that Mikroe have abandoned MikroC pro for pic, as others say, NECTO is just too complicated and restrictive, I've given up trying to use it. All I wanted to do is generate a .bin/.hex file to use with my PICKIT programmer but seems like you can't do that, so it's no use to me. MicroC was and still IS an excellent product and to simply abandon it for something to try and wring more money out of people who don't use the ecosystem says a lot about a company.

Regards, Dave.

[paulfjujo]

hello,

I would be really interested to know if anyone gets the 27Q10 processor working with 7.60 as I've just ordered some of these for a project and realised they aren't supported.

The las rescent ( or not too old) PIC i can use with MikroC 7.60 is PIC18F27K42
No way for using the 18FxxQ10 ! with MikroC ... or maybe with Necto Studio ? too complicated ...

So , i preferred to use MPLABX IDE V6.00 and XC8 C99 ... even the compiling time is heavy .. and need to have more than 4Go of RAM ...
( MikroC compile 10x faster than MPLABX for 18F27K42)

it is not easy to pass from MikroC to MPLAB , need a lot of efforts, but at least can be used instead of MikroC.

a little example with MPLABX 18F27Q10 as starter ..

P18F27Q10_tests_UART1_ADC_I2C_SPI.X.zip

(995.12 KiB) Downloaded 22 times

MCC tool can help .. but generate too much code

[hexreader]

Even Necto Studio only supports Q10 and Q43 PICs - and not in any way that is usable without some serious STK baggage

+1 for using XC8 for PIC16Q40 and Q41 PICs

-1 for using MCC while learning. It just complicates things for simple examples. Move to MCC when you get familiar and experienced.

I can zip up a few 16Q40 and 16Q41 XC8 projects if you want me to. Can't remember how far I got with these projects. Some may work, others may not.

Forget any ideas of using MikroE toolchain for Q40 or Q41 PICs