Configuring the dsPIC33CH Slave Project in MPLAB® Code Configurator (MCC) Classic

Last modified by Microchip on 2024/04/10 14:10
Contents

Setting up the Slave core in a Slave project involves importing the settings for the Slave core configured in the Master project. The settings imported are grouped under the Master Core section in the MPLAB® Code Configurator (MCC) System Resources. The following sections explain the procedures involved in setting up the Slave core.

Configuring Master Core

  • Create an MPLAB X IDE project or open an already existing MPLAB X IDE project with the Slave device selected from the dsPIC33CH family.
  • Launch MCC by:
    • Clicking on the MCC icon in MPLAB X IDE, or
    • Navigating to Tools > Embedded > MPLAB Code Configurator v3: Open/Close.
  • Master Core appears as a System Resource in the Slave project.

The Master core contains the configuration fuses of the Slave core (Master Slave Interface (MSI), Slave ICD, Slave Internal Oscillator, and Slave Watchdog) configured in the Master project. To display the settings selected in the Master project, the settings need to be imported from the Master project. The procedure to import the settings is explained in the "Importing Slave Core Settings" section of the "Importing dsPIC33CH Settings to the Slave Project in MPLAB Code Configurator (MCC) Classic" page.

Master Core in the Project Resources for Slave project

Back to Top

Configuring MSI

The MSI controls are non-editable in the Slave project. All the settings related to MSI have to be done in the Master project and must be imported from the Master project. Interrupts for the protocols can be configured only after importing the settings.

MSI controls for Slave project have to be imported from Master project

Back to Top

Configuring SLAVE ICD, SLAVE INTERNAL OSCILLATOR, and SLAVE WATCHDOG

On the first launch of MCC, the configurations related to Slave ICD, Internal Oscillator, and Watchdog have default values in the Slave project. You cannot change any of these configurations in the Slave project. If any change is required, these configurations need to be modified in the Master project, save the settings, and import the modified settings to the Slave project. After importing the settings, you will see the configurations made in the Master project, which apply to the Slave project.

Settings for ICD, Oscillator, and watchdog timer are also not editable

Back to Top

Pin Module

All the pins are available for selection in the Slave core by default. However, by default, ownership of output pins lies with the Master core. For the pins that are being used by the Slave core, the ownership of those pins has to be assigned to the Slave core in the Master project and those settings need to be imported in the Slave project.

Pin Manager shows all pins available to Slave, but in reality they have to be given ownership by the Master

The Description column within the Notifications [MCC] tab indicates the Slave project does not possess ownership of the selected pins.

Description of pin indicates ownership has to be assigned by Master

Back to Top

Learn More

Back to Top