recommended pic 16/32bit

[sairfan1]

I already have worked with different 8bit PIC controllers and now looking forward to work on 16/32bit PIC MCUs. Just like for 8bit there are some controllers which are most commonly used and many resources/examples are available on net, I want to know which PIC16/32bit are more suitable to start with and later bit more functional, I will be working around some basic communications etc.

 

[Aussie Susan]

Your requirements are very general but I would suggest that you look at the Explorer 16 board as it already contains thinks such as an LCD display but mostly because it can take a number of different processors which are mounted on "plug in modules" (PIMs). This means that you can start off with one processor and then upgrade to another that has more memory/peripherals/whatever.
The MCUs that come on PIMs range from PIC24FJ devices through dsPIC33EP to some PIC32MX MCUs.
There are also a number of daughter boards that can be plugged in for WiFI, Ethernet, graphics and USB interfaces to name a few.
As for what the various MCUs can and can't do, you really need to look at the comparison charts that are on the Microchip web site as they are all described there.
Susan

 

[sairfan1]

Thanks, I want mcu only will develop board to evaluate it. Thats why i want to know most common mcu type in dip package for which lot of material available on net.

 

[pic.programmer]

What do you mean by basic communication ? UART, SPI, I2C ? If yes, you can use PIC32MX150F128B are a few other PIC32MX which comes in DIP28 Package. They work from 3.3V but the I2C, SPI and UART pins are 5V tolerant. You can interface SIM900 or any other I2C or SPI devices (3.3V / 5V type) directly to it and use it.

 

[Aussie Susan]

Personally I would go for the PIC24/dsPIC33 devices as these are closer to the 8-bit devices in the way they operate.
The PIC32 devices are based around the MIPS core and therefore are just a little "different" (not better or worse, but the OP said they had 8-bit PIC experience and therefore the transition to PIC32 is a little harder in my opinion).
Susan

 

[pic.programmer]

I think it is better to undergo the transition. OP asked for 16 or 32 bit PIC microcontrollers and I think 32 bit ones are better than 16 bit ones.

 

[bigdogguru]

OP asked for 16 or 32 bit PIC microcontrollers and I think 32 bit ones are better than 16 bit ones.

Such a judgement call requires a thorough understanding of the specific application, as the OP has not clarified the specifics, it is difficult to make that call.


BigDog

 

[pic.programmer]

OP said that he will be doing communication projects and I think it can be done with any 8, 16 and 32 bit PICs. OP didn't mention what Compiler(s) he has used and what Compiler(s) he will use for 16 or 32 bit devices. My choice of Compiler for 32 bit PICs is mikroC PRO PIC32 (I am not promoting mikroC) because it is easier to learn and has lot of libraries for I2C, SPI, UART and other things. If OP uses mikroC Compiler then he can use PIC24 / dsPIC or PIC32 because mikroE also has mikroC PRO dsPIC Compiler.

More can be answered only after OP answers what Compiler he is going to learn and use because he needs exampl projects to learn. I think even if he uses Microchip Compilers he will get examples for PIC24 / dsPIC and PIC32.

 

[sairfan1]

thanks everyone for such a useful discussion. @pic.programmer you are right, it was important to mention compiler that i missed in my post. I mostly use MikorC and some time XC, I mentioned basic communication(UART, LIN, SPI, I2C) and driving TFTs to start with and to understand this family of MCUs. With the time I will be definitely doing different projects like home automation, IoT etc.

It would be great if you guys mention MCU number which are more commonly used so that I can get help from internet just like in case of 8bit family, there are 18F45K22, 18F4550, 16F877A, 16F84 and so on, one can find lot of resources for these MCUs. And also once I select the MCU I will develop its PCB to make easy to integrate with my existing modules.

 

[FvM]

I think even if he uses Microchip Compilers he will get examples for PIC24 / dsPIC and PIC32.

For designers who are familiar with the Microchip Application Library, the argument sounds upside down. With a Microchip compiler, he gets a framework of ready-to-use libraries that can be seamlessly integrated into productive code. I'm not sure if you can say the same about MikroC libraries.

 

[c_mitra]

With the original IBM PC running MS-DOS (I did try and use PC-DOS too) 3.0, I did learn a lot about computers. With 3.2 MS-DOS came GW BASIC and I introduced many to the strange dark world of programming- something like a black art. I never had the good luck of attending classes and learning first hand- everything is by trial and error.

I think with your basic experience, you should be able to decide yourself your exact needs. There are dozens of PICs with different configurations and you just select the one you need.

 

[pic.programmer]

If you are going to use TFT and also going to store the TFT related data in MCU then you need lot of ROM. So, better use PIC32 with 128 or 256 KB RAM and 512KB ROM. If you can use non microchip MCUs then you have choice of STM32, Stellaris and Tiva MCUs. Choose MCU which has 512 KB or more ROM and 256 KB or more RAM. Also based on how many UART, I2C and SPI channels you need decide the MCU. My choice of PIC32 is PIC32MX795F512 but PIC32MZ are better devices but I have not used them Some PIC32MZ's have 1 MB ROM. I also use PIC32, STM32, Stellaris and Tiva with mikroC Compilers.

I have not worked with XCx Compilers much and hence can't give answer related to those Compilers and their libraries.

I mainly use mikroC Compilers and I have done a few projects which use TFTs and I have use mikroE's VisualTFT software for that. The only problem with mikroC is you don't get code for the libraries but they work fine.

If you want to learn then try using XCx Compilers and their libraries and also try to write your own libraries. if you want make your work easier then use mikroE softwares using mikroE libraries.

One more thing, if you use VisualTFT software for TFT GUI designing then you have option to store the TFT data in MCU or external SD Card. I don't know whether you get this feature when using Microchip's TFT libraries because I have not used them.

 

[sairfan1]

Thanks @pic.programmer I was looking at PIC32MX795F512 datasheet its good choice. Datasheet says it has Graphics features (Interface to external graphic controller) can you please help on this what kind of graphic controller its talking about? for example there are TFTs with ILI9341 does it help to work with this kind of graphic controllers or its talking about something else?

And also in what scenario DMA is used. Thanks.