Running programs on different dsPIC's causing problems

[Bob Shannon]

There have been several messages about programs that ran fine on one dsPIC not working on other chips.

There are a few important things to check before assuming that this is a compiler problem!

Some dsPIC's have bits in the option registers that will assign some I/O pins to internal peripherals. As an example port E on a 30F2010 can be assigned to the PWM module after each reset, or as GPIO pins based on a configuration register bit.

Also some internal peripheral modules are turned on by default after a reset, like the ADC.

Different dsPIC's map internal peripherals to different ports. As a result code written for one dsPIC is not really directly transportable to another chip.

You really need to study the data sheet for the part in question, as well as the family reference manual for the subset of dsPIC's you are using.

That being said, it seems that there are still many issues with the compilers that need to be addressed.

[LGR]

Completely agree. This appears to be a frequently recurring theme. And it isn't all related to peripherals, though I'm sure a lot of it is.