Pitfalls related to PIC24's and mikroPascal for dsPIC30/33 and PIC24.

Last update: 2011-06-09.

Using {$UNDEFINE...} in stead of {$UNDEF...} (error in help, only $UNDEF works).

If you are using the lv24-33 programmer, make sure that the programmer's "MCU-VCC" and "VCC" points are connected together on your target board as in this circuit diagram
Also make sure the 2 "GND" connections are connected together via a short wire.

Forgetting to set "IOLockProtection" (IOLock) to "disabled" in the project configuration. Needed when using mE's "Peripheral Pin Select" library. See also next point...

Temporary: Some older versions (< v2.00) of the mikroProg suite are not able to reset the "IOLock" configuration bit (at least for the P24FJ64GA002). In this case only the first "PPS_Mapping" called will succeed. Use the "PPS" library on the website in this case.

Forgetting to set I/O pins to digital when no analog input is needed. E.g.

  ADPCFG := 0xFFFF;       // Configure AN pins as digital I/O

Forgetting to map the peripheral inputs and output to remappable controller pins. E.g (using mE's "Peripheral Pin Select" library) :

  // Uart1
  Res := PPS_Mapping (7, _INPUT,  _U1RX);  // RP7 is uart1 input  pin 16
  Res := PPS_Mapping (6, _OUTPUT, _U1TX);  // RP6 is uart1 output pin 15

  // SPI1
  Res := PPS_Mapping (10, _OUTPUT, _SCK1OUT); //SPI 1 clock output  pin 21
  Res := PPS_Mapping (11, _INPUT,  _SDI1);    // SPI1 data input    pin 22
  Res := PPS_Mapping (12, _OUTPUT, _SDO1);    // SPI 1 data output  pin 23

v4.80 bèta: Make sure "SSA" optimisation is "off" (IDE, Tools, Output settings) if using constructions like this one.

-------------------------------------------