Difference between revisions of "PIC32"
| Line 1: | Line 1: | ||
| + | Some things I've learned about Pic32. | ||
==Tips== | ==Tips== | ||
===MX is not MZ=== | ===MX is not MZ=== | ||
Revision as of 01:12, 24 October 2019
Some things I've learned about Pic32.
Tips
MX is not MZ
Essentially there are two distinct PIC32 architectures. MX and MZ. The reference manuals (Family Reference Manuals) that apply to MZ do not apply to MX. A simple thing to misunderstand for beginners. Use the reference manual that is mentioned in your Pic's particular datasheet.
Pic32 can be Power Hungry
Check your voltage regulator if you find that your code keeps resetting, when in debug mode. I found that my resets were due to not enough power. The more peripherals you turn on, the more power you will need. This is one reason why code will work, then suddenly fail after adding functionality (say turning on DMA, or a constant UART stream)
Resources
Family Reference Manuals
Start here. These will be your required reading for any peripheral. The data sheets will also be required. With these two in hand, you should be able to flip almost any bit needed. Make sure you get the Reference manual for your particular implementation (MX or MZ).
Peripheral Library Examples
There are a number of well commented (unlike most garbage online) examples that are ideal for someone learning about setup of pic32 peripherals in the Peripheral Libraries Examples. Link: https://people.ece.cornell.edu/land/courses/ece4760/PIC32/PLIB_examples/plib_examples/
