SECONDARY CORE

dsPIC33C CH

☀️ Light

The SECONDARY CORE block links the secondary core firmware image in master core projects for dual-core dsPIC33CH devices.

Overview

The SECONDARY CORE block is used in master core projects to link the secondary (slave) core firmware image. This block enables dual-core applications on dsPIC33CH family devices by specifying the path to the secondary core .s image file generated by a separate Simulink model configured for the secondary core.

Key Features:

• Links secondary core .s image file into master project
• Supports absolute and relative path configurations
• Stores both path formats for portability
• Automatically sets the model’s SlaveModelReference parameter

When to use:

• Building dual-core applications on dsPIC33CH devices where master and secondary cores run separate Simulink models
• The secondary core device name ends with “S1” suffix (e.g., dsPIC33CH512MP508S1 for secondary, dsPIC33CH512MP508 for master)

Note: Output pins must be driven by one core exclusively. Input pins can be used by both cores simultaneously.

Block Dialog

Screenshots taken with chip 33AK512MPS512

Ports

This is a configuration-only block with no signal ports.

Parameters

Path Storage

The block maintains two internal path representations:

• SLAVE_sFile_Save (hidden) - Absolute path used at build time
• SLAVE_sFile_Save_relative (hidden) - Relative path for portability

When a secondary image is selected, the block:

1. Stores the absolute path
2. Computes the relative path from the master model’s directory
3. Updates the block display to show the selected image folder name
4. Sets the model parameter SlaveModelReference with the full file path

Path Configuration

Absolute Path:

• Full path to the .s file (e.g., C:\Projects\MyApp\Secondary.X\slave1_image\slave1_image.s)
• Used directly for builds
• Not portable across machines

Relative Path:

• Path relative to the master model directory (e.g., \Secondary.X\slave1_image\slave1_image.s)
• Preferred for version control and project portability
• Block automatically resolves to absolute path when model folder exists

Workflow

1. Create secondary core model - Configure MCHP Master block with secondary device (ending in S1)
2. Build secondary model - Generates .s image file in <model>.X/slave1_image/slave1_image.s
3. Add SECONDARY CORE block to master model - Select “Select slave image” and browse to the generated .s file
4. Build master model - Automatically links the secondary core image into the master firmware

Related Blocks

• Master - Master core and device configuration