The CCP configuration tab is used to initialize the CCP stack. Once that CCP stack is get initialized then on a infinite loop there is a routine that waits for CAN calibration commands (e.g. from CANape). In fact the whole driver and stack was taken from Vector. You can find more information here.

So, basically once you configure the CAN instance to be used exclusively for CCP (from the config tab) there is nothing else you should do from the model - the microprocessor will sit and wait for calibration commands.

You do not need any extra CAN configuration/receive/transmit blocks. The CCP Setup will configure the CAN instance you have selected in the UI and will initialize all the CCP stack for you. Then that CCP stack which is called on the application main() function infinite loop will handle all the CAN communication for calibration.

Of course, you could use another CAN instance for other purposes if you need, but for the Calibration itself you should not reuse the CAN instance assigned for CCP.

I do not have any examples about this - in fact my knowledge about CAN calibration is very limited.

If you take the generated code and transplant it to the S32DS project it should work normally. Keep in mind that the Matlab toolbox is just generating some header file to pass the configuration parameters to the CCP stack (which in turn is something that Vector is providing for free) The alternative to Matlab generated code - would be to take the latest version from Vector and integrate it directly in your S32DS.