Help finding up to date course or book on Pics micros

Is there an up to date course on learning to program the pic micro-controllers strictly in c/c++? If there is a book or course that doesn’t get too bogged down in heavy math and theory and provides practical projects while also not lightly glossing over things that would be nice

Hello @majorkuso

Is there a reason why you want to learn PIC?

If you have to choose, I say that you take a look at STM32, instead.

they seem cheap and seem to be used everywhere, i also have a pickit3 that I can use. What advantage would the stm32 have over 32bit pics or avr micros?

does anyone have any resources for learning the topics?

Well, if you already have the pickit, then sitck with it.

It is simply because ressources for STM32 are being updated more frequently and that more boards with recent features are being made from it.
AVR might also be an option if you’re willing to explore.

1 Like

Hey @majorkuso! Welcome to the RobotShop community!

You can probably find plenty online with a few good searches, such as:
[ PIC related info to get started ]

[ More general microcontroller/embedded C tutorials]

Enjoy those resources and continuously keep looking for more everywhere! :slight_smile:
As you get more experience with one architecture, make sure to explore others too. This is important since often you’ll find a good quality example or open source piece of code for one architecture that you’ll then need to port over to yours!

Good luck with your learning! :wink:

Sincerely,

P.-S.: I’ve only scanned through the resources above, but they seemed decent enough to be helpful!

thanks guys I will keep this in mind, speaking of the avr do you think microchip will make a unified tool or platform for programming both. I guess in a way get rid of the divide between the 2 ?

1 Like

@majorkuso

That is a very good question. I figure this is unlikely, at least in the near future. Both ecosystems have coexisted for a long time and if I were to take an educated guess it would most likely be because they offer something different/solve different problems or fulfill different needs. Software solutions (to develop on those platform) are usually tightly coupled with those needs. They also have different toolchains.

Therefore, it will probably take a while for them to merge (if ever).

As for the libraries (libc environment, device drivers, etc.) since they target different µC architecture those will also most likely stay separate.

All in all, just write good ANSI C code to keep it portable and decouple it from architecture specific details so you can move it around easily! :wink:

Sincerely,

1 Like