Pull request #20: Code Maintenance Release v1.1.0

Merge in MCU16CE/dspic33ck-power-pwm-complementary from develop to master

* commit 'f82537a66f0b9b8ddadc723ceb194b5d6191fa76':
  * Updated deployment files of this code example
  * Fixed typos in head comment of file main.c
  * Updated changelog file reflecting changes in version 1.1.0
  * Updated tool chain versions, data sheet links and copyright date in README file
  * Switched XC16 C-Compilter version to v2.00 * Switched Device File Pack version to v1.10.341 * Set compiler code optimization to level #1
  * Regenerated content using MCC Plug-In version 5.3.7
  * Removed interrupt register bits not supported anymore by DFP versions 1.5 and later
  Updated gitignore file to filter new clutter generated by MPLAB X IDE 6.05 and later
  Fixed pipeline issue

Author: MCHP-Carl

.citd/Jenkinsfilek8s

@@ -5,14 +5,26 @@ metadata:
 spec:
   containers:
     - name: xc16-mplabx-sonar-fmpp-python
-      image:  artifacts.microchip.com:7999/microchip/citd/bundles/xc16-mplabx-sonar-fmpp-python-yarn-node:1.50-5.40-4.2-0.9.16-3.x-1.17.3-12.x
+      image:  artifacts.microchip.com:7999/microchip/citd/bundles/xc16-mplabx-sonar-fmpp-python-yarn-node:latest
       imagePullPolicy: Always
       command: ['cat']
       tty: true
       resources:
         requests:
-          cpu: 1
-          memory: 1Gi
+          cpu: 500m
+          memory: 1500Mi
         limits:
-          cpu: 2
+          cpu: 1
           memory: 2Gi
+    - name: buildtools
+      image: artifacts.microchip.com:7999/microchip/buildtools/doxygen:1.8.15-r0
+      imagePullPolicy: Always
+      command: ['cat']
+      tty: true
+      resources:
+        requests:
+          cpu: 500m
+          memory: 750Mi
+        limits:
+          cpu: 1
+          memory: 1Gi

.citd/cloudprovider.yml

@@ -1,20 +1,54 @@
 # .gitignore file
 #
-# Set up for Microchip/MPLAB X development
+# Set up for Microchip/MPLAB X® development
 # 
-# Default gitignore files for code examples, only removing/ignoring usual MPLAB X clutter
+# Default gitignore files for code examples, only removing/ignoring usual MPLAB X® clutter
 
-# Object files
+# Excluding object files
 *.o
 *.ko
 *.obj
 *.elf
 
-# Executables
+# Excluding documentation output directories and file types
+docs/
+*.mp4
+.mchp_private/doxygen/doxylog.txt
+.mchp_private/doxygen/doxymsg.txt
+.mchp-private/doxygen/doxylog.txt
+.mchp-private/doxygen/doxymsg.txt
+mchp_private/doxygen/doxylog.txt
+mchp_private/doxygen/doxymsg.txt
+mchp-private/doxygen/doxylog.txt
+mchp-private/doxygen/doxymsg.txt
+
+# Excluding archive and backup directories
+.archive/
+.backup/
+
+# Excluding documentation input directories
+#_dox/
+#_dox/images/
+
+# Excluding test output directories
+test/
+.test/
+
+# Excluding SiMetrix/Simplis temporary simulation directories
+SIMPLIS_Data/
+TMP/
+
+# Excluding any executables
 *.exe
 
-# Netbeans specific
+#Excluding Files/Folders Auto-Generated by Test Harness
+.generated_files/
+node_modules/
+
+# Excluding Netbeans specific build directories and file types
 ~*.*
+.generated_files/
+queuelogs/
 nbproject/build/
 nbproject/dist/
 nbproject/private/
@@ -24,22 +58,25 @@ dist/
 private/
 disassembly/
 *.zip
+!code-templates.zip
 *.mk
 *.bash
+*.dump
 Makefile-genesis.properties
 
-# MPLAB X Trace specific
+# Excluding MPLAB X® Trace files
 *.log
 *.inx
 
+# VisualStudio Code specific
+buildLog/
+
 # KDE specific
 .directory
 
 # Misc
 .svn
 *.bak
-*.doc
-*.docx
 
 
 

.gitignore

@@ -2,23 +2,23 @@
   "metaDataVersion": "1.0.0",
   "category": "com.microchip.ide.project",
   "content": {
-    "metaDataVersion": "1.0.0",
+    "metaDataVersion": "1.3.0",
     "name": "com.microchip.mplabx.project.dspic33ck-power-pwm-complementary",
-    "version": "1.0.0",
+    "version": "1.1.0",
     "displayName": "dsPIC33CK/CH-MP PWM Configuration: Complementary PWM Output",
     "projectName": "dspic33ck-power-pwm-complementary",
     "shortDescription": "Complementary PWM Output Configuration Example for dsPIC33CK-MP devices",
 	"ide": {
 		"name": "MPLABX",
-		"semverRange": ">=5.40.0"
+		"semverRange": ">=6.05.0"
 	},
 	"compiler": {
 		"name": "XC16",
-		"semverRange": "^1.50.0"
+		"semverRange": "^2.00.0"
 	},
 	"dfp": {
 		"name": "dsPIC33CK-MP_DFP",
-		"semverRange": "^1.4.102"
+		"semverRange": "^1.10.341"
 	},
 	"device": {
 		"metaDataVersion": "1.0.0",
@@ -30,11 +30,6 @@
 			"versionRange": "*"
 		}
 	},
-	"peripherals": [
-		"GPIO",
-		"PWM",
-		"Timer"
-	],
 	"keywords": [
 		"dsc",
 		"dspic",

.main-meta/main.json

@@ -1,6 +1,7 @@
-![image](images/microchip.png) 
+![image](images/microchip.png)
 
 # dsPIC33C High-Resolution PWM Configuration I
+
 **Complementary PWM Waveform Generation**
 
 <p><center><a target="_blank" href="https://www.microchip.com/MA330048" rel="nofollow">
@@ -9,94 +10,106 @@
 - - -
 
 ## Summary
-Learning how to use the High Resolution PWM Module of dsPIC33C MP devices 
 
-Lab 1: Complementary Waveform Generation
+Learn how to use the High Resolution PWM Module of dsPIC33C MP devices
+
+**Lab 1: Complementary Waveform Generation**
 Code example for dsPIC33CK and dsPIC33CH devices introducing the basic configuration of the high-resolution PWM module using one PWM generator channel generating a single, complementary PWM waveform
 
 - - -
 
 ## Related Documentation
-- [dsPIC33CK256MP508 Family Data Sheet](https://ww1.microchip.com/downloads/en/DeviceDoc/dsPIC33CK256MP508-Family-Data-Sheet-DS70005349G.pdf)
-- [dsPIC33CK256MP508 Family Silicon Errata and Data Sheet Clarification](https://ww1.microchip.com/downloads/en/DeviceDoc/dsPIC33CK256MP508-Family-Silicon-Errata-and-Data-Sheet-Clarification-DS80000796G.pdf)
+
+- [dsPIC33CK256MP508 Family Data Sheet](https://www.microchip.com/DS70005349)
+- [dsPIC33CK256MP508 Family Silicon Errata and Data Sheet Clarification](https://www.microchip.com/80000796)
 
 Alternative Controller Plug-In Module:
-- [dsPIC33CH512MP508 Family Data Sheet](http://ww1.microchip.com/downloads/en/DeviceDoc/dsPIC33CH512MP508-Family-Data-Sheet-DS70005371D.pdf)
-- [dsPIC33CH512MP508 Family Silicon Errata and Data Sheet Clarification](http://ww1.microchip.com/downloads/en/DeviceDoc/dsPIC33CH512MP508-Family-Silicon-Errata-and-Data-Sheet-Clarification-DS80000805F.pdf)
+
+- [dsPIC33CH512MP508 Family Data Sheet](http://www.microchip.com/70005371)
+- [dsPIC33CH512MP508 Family Silicon Errata and Data Sheet Clarification](http://www.microchip.com/80000805)
 
 **Please always check for the latest data sheets on the respective product websites:**
+
 - [dsPIC33CK256MP508 Family](https://www.microchip.com/dsPIC33CK256MP508)
 - [dsPIC33CH512MP508 Family](https://www.microchip.com/dsPIC33CH512MP508)
 
-## Software Used 
-- [MPLAB® X IDE v5.40](https://www.microchip.com/mplabx-ide-windows-installer)
-- [MPLAB XC16 Compiler v1.50](https://www.microchip.com/mplabxc16windows)
-- [Microchip Code Configurator v3.95](https://www.microchip.com/mplab/mplab-code-configurator)
+## Software Used
+
+- [MPLAB&reg; X IDE v6.05](https://www.microchip.com/mplabx)
+- [MPLAB&reg; XC16 Compiler v2.00](https://www.microchip.com/xc16)
+- [MPLAB&reg; Code Configurator v4.85](https://www.microchip.com/mcc)
 
 ## Hardware Used
+
 - Digital Power Development Board, Part-No. [DM330029](https://www.microchip.com/DM330029)
 - dsPIC33CK Digital Power Plug-In Module (DP PIM), Part-No. [MA330048](https://www.microchip.com/MA330048)
 - Alternatively: dsPIC33CH Digital Power Plug-In Module (DP PIM), Part-No. [MA330049](https://www.microchip.com/MA330049)
 
 ## Supported Target Devices
+
 - [dsPIC33CK256MP506](https://www.microchip.com/dsPIC33CK256MP506)
 - [dsPIC33CH512MP506](https://www.microchip.com/dsPIC33CH512MP506)
 - Code compatible with all Single and Dual Core dsPIC33C MP families of devices
 
 - - -
 
 ## Setup
+
 - Plug-In the dsPIC33CK Digital Power Plug In Module into the Digital Power Development Board PIM socket J1
 - Open and compile the firmware and program the DSC
 
-<br><center><img src="images/dm330029.jpg" width="400"></center>
+<p><center><img src="images/dm330029.jpg" width="500"></center></p>
 
 ## Operation
+
 After the device has been programmed and the MCU starts up, PWM generator #3 is generating a 200 kHz complementary waveform at the PWM3H/PWM3L outputs. 
 
-<br><center><img src="images/pwm200kHz.png" width="400"></center><br>
+<p><center><img src="images/pwm200kHz.png" width="500"></center></p>
 *200 kHz Switching Frequency Output*
 
 By pressing the on-board push button *USER* on the Digital Power Development Board, the switching frequency is toggled between the initial 200 kHz and 1 MHz.
-<br><center><img src="images/pwm1MHz.png" width="400"></center><br>
+<p><center><img src="images/pwm1MHz.png" width="500"></center></p>
 *1 MHz Switching Frequency Output*
 
-
 Please refer to section *FIRMWARE QUICK-START GUIDE* below for more information on the initialization process and code structure.
 
-<br><center><img src="images/dm330029-pinmap.png" width="800"></center><br>
- 
+<p><center><img src="images/dm330029-pinmap.png" width="800"></center></p>
+
 - - -
 
 ## FIRMWARE QUICK-START GUIDE
 
-This code example builds on previous code examples showing how to use Microchip Code Configurator (MCC) to set up device clock domains. 
-Although MCC also supports configuration tools for the High Resolution PWM module, PWM configuration in this example builds on generic peripheral drivers to help users better understand the peripheral architecture and key aspects of specific configurations and operating modes. 
+This code example builds on previous code examples showing how to use Microchip Code Configurator (MCC) to set up device clock domains.
+
+Although MCC also supports configuration tools for the High Resolution PWM module, PWM configuration in this example builds on generic peripheral drivers to help users better understand the peripheral architecture and key aspects of specific configurations and operating modes.
+
 In each PWM example code project the PWM configuration procedure is located in the user file pwm.c, where each register bit required to achieve/enable the specific function or mode of interest is set and its function described with comments.
 Once users are familiar with the architecture, features and capabilities, both configuration options (generic peripheral library or MCC) may be used.
 
-*a) Project Directory Structure*
+### a) Project Directory Structure
+
 The project contains two sub-directories
+
 - config: location of all hardware abstraction header files
-- drivers: location of generic peripheral drivers 
+- drivers: location of generic peripheral drivers
 - MCC Generated Files: all device configuration files auto-generated by MCC
 - root: application user code
 
-On the hard drive, main.c/h are located in the MPLAB X project directory. 
-All other user files, incl. peripheral drivers, are located in the sub-directory *sources*. 
-Files generated by MCC are always located in their own sub-directory *mcc_generated-files* 
+On the hard drive, main.c/h are located in the MPLAB&reg; X project directory.
+All other user files, incl. peripheral drivers, are located in the sub-directory *sources*.
+Files generated by MCC are always located in their own sub-directory *mcc_generated-files*
+
+### b) Using the generic PWM peripheral driver
 
-*b) Using the generic PWM peripheral driver*
 The PWM peripheral driver files p33c_pwm.c/h provide data structures representing the Special Function Register (SFR) sets of PWM generators and the PAM base module. These 'virtual' PWM objects are used to load, read and modify PWM generator configurations without the need to hard-coded instructions, which would make the code hard to migrate from one peripheral to another or even across devices.
 To simplify PWM configurations, in these examples, each register is reset to a known default state before the user configuration of interest is set. Thus, only the register setting which really matter for a certain features/function are shown.
 
 To learn more about the generic PWM driver, its supported features and intended use cases, please read the comments inside p33c_pwm.c.
 
-*c) Executing the Code Example*
-This code has been written to automatically start up and perform the function of interest. Please read the demo instructions on top of file main.c to learn more about the code example, test points, expected signals and demo mode operation.
-
+### c) Executing the Code Example
 
+This code has been written to automatically start up and perform the function of interest. Please read the demo instructions on top of file main.c to learn more about the code example, test points, expected signals and demo mode operation.
 
-- - - 
+- - -
 
-© 2020, Microchip Technology Inc.
+&copy; 2023, Microchip Technology Inc.

README.md

@@ -1,11 +1,38 @@
+# dspic33ck-power-pwm-complementary, release v1.1.0
+
+### Release Highlights
+
+Version 1.1.0 of this code example is a maintenance cycle release, which is required to keep the source code provided being fully supported by the most recent development tool chain. In this release no functional changes have been made in comparison with the previous version.
+
+### Toolchain Updates
+
+* Changed minimum MPLAB X IDE version to 6.05 and later - [Get latest Version](https://www.microchip.com/mplabx)
+* Changed minimum XC16 compiler version to v2.00 - [Get latest Version](https://www.microchip.com/xc16)
+* Changed minimum Device File Pack (DFP) version to 1.10.341
+* Microchip Code Configurator Update
+  * Updated MCC Plug-In version to require v5.3.7 or later
+  * Updated mc3 file contents to work with core version 4.85.1 or later
+
+### Features Added\Updated
+
+* Updated gitignore file filtering clutter of MPLAB X IDE 6.05 and later
+* Fixed typos in leading comment of main.c
+* Removed interrupt register bits, which are not supported by DFP versions v1.5.135 and later
+* Removed empty virtual folder 'config' from section Sources in MPLAB X project explorer
+* Changed label of PWM Module register set from P33C_PWM_SFRSET_t to P33C_PWM_MODULE_t
+
+© 2023, Microchip Technology Inc.
+
+- - -
+
 # dspic33ck-power-pwm-complementary, release v1.0.0
 
 ### Release Highlights
+
 This is the initial release demonstrating the basic configuration of a high-resolution PWM generator of the dsPIC33C family of devices.
 This example is part of a series of code examples highlighting specific operating modes and features.
 
 ### Features Added\Updated
+
 In this initial version the on-board LED of the dsPIC33CK Digital Power Plug-In Module is toggled with a interval period of 300 ms, when the controller is running at maximum speed of 100 MIPS.
 After startup, PWM generator #3 is generating a 200 kHz complementary waveform at the PWM3H/PWM3L outputs. By pressing the on-board push button *USER* on the Digital Power Development Board, the switching frequency is toggled between the initial 200 kHz and 1 MHz.
-
-

changelog.md

@@ -60,7 +60,7 @@
  *   is added (100ns at rising edge of PWMxH and 150ns at falling edge of
  *   PWMxH). The initial frequency after startup is set to 200 kHz. By
  *   pressing push button [USER], the frequency is stepped to 1 MHz. By 
- *   pressing [USER] again, the frequency switches back to 200 khz,
+ *   pressing [USER] again, the frequency switches back to 200 kHz,
  *   The duty ratio will always remain 25% of the switching period.
  * 
  * Please note:

dspic33ck-power-pwm-complementary.X/main.c

@@ -53,11 +53,11 @@
 #include "system_types.h"
 #include "reset.h"
 
-#include "reset.h"
+#include "watchdog.h"
 #include "tmr1.h"
+#include "reset.h"
 #include "interrupt_manager.h"
 #include "traps.h"
-#include "watchdog.h"
 
 #warning "This file will be removed in future MCC releases. Use system.h instead."
 

dspic33ck-power-pwm-complementary.X/mcc_generated_files/mcc.h

@@ -131,8 +131,8 @@
 void SYSTEM_Initialize(void)
 {
     PIN_MANAGER_Initialize();
-    INTERRUPT_Initialize();
     CLOCK_Initialize();
+    INTERRUPT_Initialize();
     TMR1_Initialize();
     INTERRUPT_GlobalEnable();
     SYSTEM_CORCONModeOperatingSet(CORCON_MODE_PORVALUES);

dspic33ck-power-pwm-complementary.X/mcc_generated_files/system.c

@@ -136,18 +136,6 @@ void ERROR_HANDLER _SoftTrapError(void)
       TRAPS_halt_on_error(TRAPS_NVM_ERR);
     }
 
-    if(INTCON3bits.DMT)
-    {
-      INTCON3bits.DMT = 0;  //Clear the trap flag
-      TRAPS_halt_on_error(TRAPS_DMT_ERR);
-    }
-
-    if(INTCON3bits.DAE)
-    {
-      INTCON3bits.DAE = 0;  //Clear the trap flag
-      TRAPS_halt_on_error(TRAPS_DAE_ERR);
-    }
-
     if(INTCON3bits.DOOVR)
     {
       INTCON3bits.DOOVR = 0;  //Clear the trap flag