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.
Good luck .

dariods wrote: ↑

30 May 2023 22:18

Code example please

Code depends on what you intend to do with RB1

How to enable weak pull up resistor on all pins of PORTB except RB1 on PIC16F886 It's explained in the datasheet: Each of the PORTB pins has an individually configurable internal weak pull-up. Control bits WPUB<7:0> enable or disable each pull-up (see Register 3-7). Each weak pull-up is automatical...

This information cannot be controlled from code. It may only be set in IDE. Same goes for configuration words (single word in case of PIC16F874).

Is it just a case of creating the device files for the missing devices manually based on their data sheets? I know its a bit of a long-winded annoying task but at least it would keep the show on the road. Yes, it's possible to write definition files for the processors you listed, and both compiler ...

... it does look like necto has killed off the MikroC traditional compilers and that's a shame. Yes, that's exactly what happened. The PRO compilers not included in NECTO Studio will have their regular updates until they become a part of the NECTO. Studio. After that, it will not be recommended to ...

Will NECTO Studio ever get updated so that mikroPascal and mikroBASIC are part of the compiler? Note the "Save Harbour" statement preceding the promises The following outlines our general product direction and should be used for information purposes only. Although we do our best to do as planned, t...

Here you'll find how mE informed (or rather misled) its clients about these processors' implementation for last three years. I don't think you'll get any sensible answer now (well, maybe a repeat of promises for implementation under NECTO, which also have a long history). BTW, NECTO page contains a...

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 swit...

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 ).

If not too much of program memory missing, maybe you could optimize your code?

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 c...

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...

Actually the correct address is 0xF000 Yes, but compiler automatically adds 0xF000 to EEPROM address parameters in .mlk file so the addresses there do not need the offset. That fix allows me to use EEPROM Editor tool properly. Now I can set needed cells by values. :) But I still cant read and write...

That's due to error in definition file - follow instructions in this topic. The fix is for another processor but will work for yours as well.