PIC18F27Q84
PIC18F47Q84
PIC18F57Q84
28/40/44/48-Pin, Low-Power, High-Performance
Microcontroller with XLP Technology
The PIC18-Q84 microcontroller family is available in 28/40/44/48-pin devices for many automotive and
industrial applications. The many communication peripherals found in the product family, such as Controller
Area Network (CAN), Serial Peripheral Interface (SPI), Inter-Integrated Circuit (I2C), and two Universal
Asynchronous Receiver Transmitters (UARTs), can handle a wide range of wired and wireless (using
external modules) communication protocols for intelligent applications. Combined with the Core Independent
Peripherals (CIPs) integration capabilities, this capacity enables functions for motor control, power supply,
sensor, signal and user interface applications. Additionally, this family includes a 12-bit Analog-to-Digital
Converter (ADC) with Computation and Context Switching extensions for automated signal analysis to reduce
the complexity of the application.
Suggestions for new microcontroller support
-
- Posts: 261
- http://meble-kuchenne.info.pl
- Joined: Thu Dec 10, 2020 2:35 pm
- Has thanked: 36 times
- Been thanked: 17 times
-
- Posts: 1
- Joined: Thu Mar 27, 2025 3:50 pm
Re: Suggestions for new microcontroller support
Any plans to support the recent Raspberry Pi Pico 2 / RP2350 board/chip family? If so what's the timeline?
Thanks,
Kapila
Thanks,
Kapila
Re: Suggestions for new microcontroller support
Hello Martin,
I have removed the midi component from my PIC18F15Q41 test to see if the compiler runs without errors.
Unfortunately there is an error message.
::: error: (1504) the PIC18 extended instruction set was enabled but is not supported by this compiler
(908) exit status = 1
Where can I switch it on and off? Where can I switch it on and off? I have not switched it on. And can I expect
the PIC18F04/05/06 - 14/15/16Q41 family to be ready soon?
Thanks
Dirk
I have removed the midi component from my PIC18F15Q41 test to see if the compiler runs without errors.
Unfortunately there is an error message.
::: error: (1504) the PIC18 extended instruction set was enabled but is not supported by this compiler
(908) exit status = 1
Where can I switch it on and off? Where can I switch it on and off? I have not switched it on. And can I expect
the PIC18F04/05/06 - 14/15/16Q41 family to be ready soon?
Thanks
Dirk
-
- Matrix Staff
- Posts: 1953
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 626 times
- Been thanked: 656 times
Re: Suggestions for new microcontroller support
Hi Dirk,
To prevent the Suggestions for new microcontroller support being hijacked,
can post all correspondence regarding PIC18F15Q41 to here
To prevent the Suggestions for new microcontroller support being hijacked,
can post all correspondence regarding PIC18F15Q41 to here
Martin
18F47Q43 target file needed
Hi,
I'm working on project where i need to use 18F47Q43 controller. Currently it is not available in list. May i know when it can be available as I don't want to change the controller.
I'm working on project where i need to use 18F47Q43 controller. Currently it is not available in list. May i know when it can be available as I don't want to change the controller.
-
- Matrix Staff
- Posts: 1953
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 626 times
- Been thanked: 656 times
Re: Suggestions for new microcontroller support
Hello I have moved your post to a more appropriate section of the forums.
Thank your suggestion, it has been added to the list.
Thank your suggestion, it has been added to the list.
Martin
-
- Valued Contributor
- Posts: 1573
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 355 times
- Been thanked: 560 times
Re: Suggestions for new microcontroller support
Hi
Any thoughts on supporting the RPi Pico 2-W ?
Regards
Any thoughts on supporting the RPi Pico 2-W ?
Regards
Re: Suggestions for new microcontroller support
Hello,
since the PIC18F14K22 does not have a Schmitt trigger on pin A3, I would like to replace it with the PIC18F16Q41. Support for this chip is still incomplete. The I2C interface still does not work. Currently, I2C only works via software, which is slow and consumes a lot of resources.
I have now started a new project with the PIC18F27K42. Here, too, I2C is only available via software, even though the data sheet states that the chip has two I2C interfaces. Initialisation alone requires 1.3% of the memory, which is very large. I need these interfaces to be hardware-based. The newer chips are no longer fully supported. What is going on here?
Thank you for your help.
Dirk
since the PIC18F14K22 does not have a Schmitt trigger on pin A3, I would like to replace it with the PIC18F16Q41. Support for this chip is still incomplete. The I2C interface still does not work. Currently, I2C only works via software, which is slow and consumes a lot of resources.
I have now started a new project with the PIC18F27K42. Here, too, I2C is only available via software, even though the data sheet states that the chip has two I2C interfaces. Initialisation alone requires 1.3% of the memory, which is very large. I need these interfaces to be hardware-based. The newer chips are no longer fully supported. What is going on here?
Thank you for your help.
Dirk
-
- Valued Contributor
- Posts: 1509
- Joined: Wed Dec 09, 2020 9:37 pm
- Has thanked: 138 times
- Been thanked: 723 times
Re: Suggestions for new microcontroller support
I suggest the esp32_p4!
I've just received one of these bad boys..
Flowcode up and running in a matter of minutes - idf.py set-target esp32p4
Then recompile and 'Hello world' is go....
Pushing that 360MHz CPU to its limits!
It has quite a few 'extras' - dedicated display and camera port (Raspberry Pi compatible)
An ethernet port
USB Port(s) depending on model
More flash and RAM
i3c (for Stefan)
Microphone and speaker connections
etc
So - what does the fcd file require - (or hopefully) there is one in the pipes? I used the esp32-c6 target in Flowcode - and haven't yet really looked at which has the 'closest' to use as a base.
I suspect 'many' options are the same - for example GPIO_22 will have the same register mapping - so some things such as i2c should work as is. UART worked no problem - which gives a little evidence to this theory....
Other things - Camera/ DSI maybe not so much?
Lots of features to try though!
Looking forward to putting it through it's paces over the next few weeks (months/years?)
Martin
I've just received one of these bad boys..
Flowcode up and running in a matter of minutes - idf.py set-target esp32p4
Then recompile and 'Hello world' is go....
Pushing that 360MHz CPU to its limits!
It has quite a few 'extras' - dedicated display and camera port (Raspberry Pi compatible)
An ethernet port
USB Port(s) depending on model
More flash and RAM
i3c (for Stefan)
Microphone and speaker connections
etc
So - what does the fcd file require - (or hopefully) there is one in the pipes? I used the esp32-c6 target in Flowcode - and haven't yet really looked at which has the 'closest' to use as a base.
I suspect 'many' options are the same - for example GPIO_22 will have the same register mapping - so some things such as i2c should work as is. UART worked no problem - which gives a little evidence to this theory....
Other things - Camera/ DSI maybe not so much?
Lots of features to try though!
Looking forward to putting it through it's paces over the next few weeks (months/years?)
Martin