Alternative to pic16 Series

Thread Starter

ep.hobbyiest

Joined Aug 26, 2014
199
I am using PIC16F18875 controller in my design but i am planning to switch to a higher clock pic from pic18f series. I was looking for microchip product selector but I want suggestion before picking up randomely.
 

BobTPH

Joined Jun 5, 2013
4,053
It all depends ib how many pins and what peripherals you need.

Edit: If you need more performance, I would go to PIC24 or 33.

Bob
 

BobTPH

Joined Jun 5, 2013
4,053
Read my first post. I don’t have the information, and all I would do is what you need to do, go to the product selector on te Microchip website and set the filters to make sure it has what you need.

Bob
 

Thread Starter

ep.hobbyiest

Joined Aug 26, 2014
199
yes. that one option also i have but i as i said in my first post that i need suggestion before picking up. i never used other than pic16 series.
 

nsaspook

Joined Aug 27, 2009
8,909
yes. that one option also i have but i as i said in my first post that i need suggestion before picking up. i never used other than pic16 series.
The PIC18 Q43 and Q84 series are a good upgrade path if you want to stick with the 8-bit architecture.
https://www.microchip.com/en-us/pro...microprocessors/8-bit-mcus/pic-mcus/pic18-q84
https://www.microchip.com/en-us/pro...microprocessors/8-bit-mcus/pic-mcus/pic18-q43

https://forum.allaboutcircuits.com/threads/pic18-q43-ntsc-b-w-video-signal-demo.175611/post-1586729
 

trebla

Joined Jun 29, 2019
470
Moving from pic16 to pic18 is much easier than jumping to PIC24. I suggest take some latest pic18 like suggested by @nsaspook , so you can start with smaller steps and master some advanced features (like DMA) later. After that is easier to go toward PIC24 and PIC32 cores if you need.
 

atferrari

Joined Jan 6, 2004
4,475
Hi @nsaspook

I do not intend to derail this thread but right now, I am preparing a short list of 18F micros to buy so I can do things with newer ones.

Good you posted here, because I recall some previous post of yours, few weeks ago, saying that a certain family within the 18F was kind of a "lost cause" or something like that. Could you help? I would post in a separate thread if necessary.
 

nsaspook

Joined Aug 27, 2009
8,909
I think I posted that a interface board with a PIC18 was obsolete. Look at the errata sheet for the chips you select for possible candidates.

Some are, IMO losers.
https://ww1.microchip.com/downloads/en/DeviceDoc/80162e.pdf
14. Module: Core
Certain combinations of code sequence, code placement, VDD, FOSC and temperature may cause a corrupted read of fetched instructions or data. A corrupted instruction fetch will cause the part to execute an incorrect instruction with unpredictable results. Microchip cannot predict which combinations of these conditions will cause this failure. If this failure mechanism exists in your system, it should become evident during statistically significant preproduction testing, using your particular code sequence and placement, across multiple date codes. Preproduction testing should exercise all the functions of your application across system variables. Any changes to code should be tested in the same manner prior to being implemented.
That is a killer.
 

JohnInTX

Joined Jun 26, 2012
4,602
I think I posted that a interface board with a PIC18 was obsolete. Look at the errata sheet for the chips you select for possible candidates.

Some are, IMO losers.
https://ww1.microchip.com/downloads/en/DeviceDoc/80162e.pdf

That is a killer.
‘It may or may not execute its instruction set.’ I remember those. Dark, frustrating days. Errata for the chip combined with errata for the ICE 2K/4K bondout chips, full speed maybes and device sensitive compiler bugs made for some pretty convoluted build-time switch hierarchies.
 
Last edited:

John P

Joined Oct 14, 2008
1,917
I would say, before you jump to another type of processor that you don't know well, check and see whether the PIC16F parts are really too slow. Could it be that you aren't using them efficiently, and a review of how your software runs could show you a way to get what you want without changing? Or is your compiler just plain wasteful? 8 million instructions a second can do a lot.
 
Top