Difference between revisions of "PIC32"
Line 17: | Line 17: | ||
===MPLAB X Tools - Debugger - Watches doesn't work for large arrays=== | ===MPLAB X Tools - Debugger - Watches doesn't work for large arrays=== | ||
The watch doesn't read the whole array. Export to CSV to see all values, or examine map file. MPLAB 5.25. Reference: https://www.microchip.com/forums/m790353.aspx | The watch doesn't read the whole array. Export to CSV to see all values, or examine map file. MPLAB 5.25. Reference: https://www.microchip.com/forums/m790353.aspx | ||
+ | |||
+ | ===Atomic Operations on bits=== | ||
+ | You shouldn't use SPIxCONbits, but instead SPIxCONCLR or SET, generally. | ||
===Resets=== | ===Resets=== |
Revision as of 23:22, 25 October 2019
Some things I've learned about PIC32MX.
Tips
MX is not MZ
Essentially there are two distinct PIC32 architectures. MX and MZ (let's forget about MM). 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)
Read Registers Whilst Debugging
If you put just a register macro, e.g. U1STA; or U1MODE; in the code, and even if nothing happens to that register, it can be read by hovering over it while debugging. Useful to just type out a number of registers in the code, and then pause, and check them while debugging. An example:
U1MODE; U1STA; IFS1; IEC1; RCON;
MPLAB X Tools - Debugger - Watches doesn't work for large arrays
The watch doesn't read the whole array. Export to CSV to see all values, or examine map file. MPLAB 5.25. Reference: https://www.microchip.com/forums/m790353.aspx
Atomic Operations on bits
You shouldn't use SPIxCONbits, but instead SPIxCONCLR or SET, generally.
Resets
Dest and Source Sizes
Incorrect Dest and Source sizes for DMA can cause resets. It will register as POR and BOR, but it's due to for example, the source of SPIxBUF being set to size 10 bytes, (which is incorrect, SPIxBUF can only be 1,2 or 4 bytes depending on settings).
Insufficient Power
Self explanatory.
DMA
DMA - If you CFORCE, and it finishes, you must CHEN again to CFORCE again
Subject.
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/