30.1 Configuration Bits

In dsPIC33CK1024MP710 family devices, the Configuration Words are implemented as volatile memory. This means that configuration data will get loaded to volatile memory (from the Flash Configuration Words) each time the device is powered up. Configuration data are stored at the end of the on-chip program memory space, known as the Flash Configuration Words. Their specific locations are shown in Table 30-1. The configuration data are automatically loaded from the Flash Configuration Words to the proper Configuration Shadow registers during device Resets.

When creating applications for these devices, users should always specifically allocate the location of the Flash Configuration Words for configuration data in their code for the compiler. This is to make certain that program code is not stored in this address when the code is compiled. Program code executing out of configuration space will cause a device Reset.

Note: Performing a page erase operation on the last page of program memory clears the Flash Configuration Words.

Table 30-1. dsPIC33CKXXXXMPXXX Configuration Addresses
Register Name	Single Partition			Dual Partition, Active			Dual Partition, Inactive
Register Name	1024k	512k	256k	1024k	512k	256k	1024k	512k	256k
FSEC⁽²⁾	0x0AFF00	0x057F00	0x02BF00	0x057F00	0x02BF00	0x015F00	0x457F00	0x42BF00	0x415F00
FBSLIM⁽²⁾	0x0AFF10	0x057F10	0x02BF10	0x057F10	0x02BF10	0x015F10	0x457F10	0x42BF10	0x415F10
FSIGN⁽²⁾	0x0AFF14	0x057F14	0x02BF14	0x057F14	0x02BF14	0x015F14	0x457F14	0x42BF14	0x415F14
FOSCSEL	0x0AFF18	0x057F18	0x02BF18	0x057F18	0x02BF18	0x015F18	0x457F18	0x42BF18	0x415F18
FOSC	0x0AFF1C	0x057F1C	0x02BF1C	0x057F1C	0x02BF1C	0x015F1C	0x457F1C	0x42BF1C	0x415F1C
FWDT	0x0AFF20	0x057F20	0x02BF20	0x057F20	0x02BF20	0x015F20	0x457F20	0x42BF20	0x415F20
FPOR	0x0AFF24	0x057F24	0x02BF24	0x057F24	0x02BF24	0x015F24	0x457F24	0x42BF24	0x415F24
FICD	0x0AFF28	0x057F28	0x02BF28	0x057F28	0x02BF28	0x015F28	0x457F28	0x42BF28	0x415F28
FDMTIVTL	0x0AFF2C	0x057F2C	0x02BF2C	0x057F2C	0x02BF2C	0x015F2C	0x457F2C	0x42BF2C	0x415F2C
FDMTIVTH	0x0AFF30	0x057F30	0x02BF30	0x057F30	0x02BF30	0x015F30	0x457F30	0x42BF30	0x415F30
FDMTCNTL	0x0AFF34	0x057F34	0x02BF34	0x057F34	0x02BF34	0x015F34	0x457F34	0x42BF34	0x415F34
FDMTCNTH	0x0AFF38	0x057F38	0x02BF38	0x057F38	0x02BF38	0x015F38	0x457F38	0x42BF38	0x415F38
FDMT	0x0AFF3C	0x057F3C	0x02BF3C	0x057F3C	0x02BF3C	0x015F3C	0x457F3C	0x42BF3C	0x415F3C
FDEVOPT	0x0AFF40	0x057F40	0x02BF40	0x057F40	0x02BF40	0x015F40	0x457F40	0x42BF40	0x415F40
FALTREG	0x0AFF44	0x057F44	0x02BF44	0x057F44	0x02BF44	0x015F44	0x457F44	0x42BF44	0x415F44
FBTSEQ	0x0AFFFC	0x057FFC	0x02BFFC	0x057FFC	0x02BFFC	0x015FFC	0x457FFC	0x42BFFC	0x415FFC
FBOOT⁽¹⁾	0x801800
Note: FBOOT resides in calibration memory space. Changes to the Inactive Partition Configuration Words affect how the Active Partition accesses the Inactive Partition.