hal: microchip: pic32c: Add PIC32CZ_CA device family pack files

Add device family pack files for PIC32CZ-CA70, PIC32CZ-CA80, PIC32CZ-CA90 and PIC32CZ-CA91 series.
https://packs.download.microchip.com/Microchip.PIC32CZ-CA70_DFP.1.2.32.atpack
https://packs.download.microchip.com/Microchip.PIC32CZ-CA80_DFP.1.6.163.atpack
https://packs.download.microchip.com/Microchip.PIC32CZ-CA90_DFP.1.7.168.atpack
https://packs.download.microchip.com/Microchip.PIC32CZ-CA91_DFP.1.4.23.atpack

Signed-off-by: Niyas Hameed <[email protected]>

Author: NhMchp

README.md

@@ -14,32 +14,45 @@ The directory is composed of:
 │   └── microchip
 │       └── mec5
 │           ├── MEC5 PINCTRL DTSI files
+│
 ├── include
 │   └── dt-bindings
 │       ├── sam
 |       |   └── sam_d5x_e5x — dt-binding header files for the SAM_D5X_E5X family devices
 │       └── pinctrl
 │           ├── PIC32CX PINCTRL C header files
+│
 ├── mec
 │   ├── Legacy MEC150x/2x C chip and peripheral header files
+│
 ├── mec5
 │   ├── CMakeLists.txt
 │   ├── devices
 │   │   ├── MEC5 HAL chip and peripheral header files
 │   └── drivers
 │       ├── MEC5 HAL peripheral C source files
+│
 ├── mpfs
 │   ├── PolarFire board and HAL files
+│
 ├── pic32c
+│   ├── CMakeLists.txt
+│   ├── pic32cm_jh — DFP header files for PIC32CM JH family devices
 │   ├── PIC32CX chip and peripheral HAL files
+│   ├── pic32cz_ca — DFP header files for PIC32CZ CA family devices
+│
 ├── pinconfigs
 │   ├── PIC32CX pin config definition XML
+│
 ├── sam
 │   ├── CMakeLists.txt
 │   ├── sam_d5x_e5x — DFP header files for SAM_D5X_E5X family devices
+│
 ├── README.md
+│
 ├── scripts
 │   ├── PIC32C Python pin config generation scripts
+│
 └── zephyr
     └── module.yml
 
@@ -51,6 +64,7 @@ The directory is composed of:
    - devicetree bindings
  - Legacy MEC152x header files
  - MEC5 HAL chip and peripheral header and C source files
+ - Device family DFP header files of PIC32C devices
  - [PIC32C Pin definitions](pinconfigs/README.md)
  - sam device family dfp header files
  - This README file

pic32c/CMakeLists.txt

@@ -5,3 +5,4 @@
 
 add_subdirectory_ifdef(CONFIG_SOC_FAMILY_MICROCHIP_PIC32CXSG pic32cxsg)
 add_subdirectory_ifdef(CONFIG_SOC_FAMILY_MICROCHIP_PIC32CM_JH pic32cm_jh)
+add_subdirectory_ifdef(CONFIG_SOC_FAMILY_MICROCHIP_PIC32CZ_CA pic32cz_ca)

pic32c/pic32cz_ca/CMakeLists.txt

@@ -0,0 +1,6 @@
+# Copyright (c) 2025 Microchip Technology Inc.
+#
+# SPDX-License-Identifier: Apache-2.0
+#
+
+zephyr_include_directories(${CONFIG_SOC_SERIES}/include)

pic32c/pic32cz_ca/pic32cz_ca70/atdf/PIC32CZ2051CA70064.atdf

@@ -0,0 +1,56 @@
+/*
+ * Component version header file
+ *
+ * Copyright (c) 2025 Microchip Technology Inc.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+#ifndef _COMPONENT_VERSION_H_INCLUDED
+#define _COMPONENT_VERSION_H_INCLUDED
+
+#define COMPONENT_VERSION_MAJOR 1
+#define COMPONENT_VERSION_MINOR 2
+
+//
+// The COMPONENT_VERSION define is composed of the major and the minor version number.
+//
+// The last four digits of the COMPONENT_VERSION is the minor version with leading zeros.
+// The rest of the COMPONENT_VERSION is the major version.
+//
+#define COMPONENT_VERSION 10002
+
+//
+// The build number does not refer to the component, but to the build number
+// of the device pack that provides the component.
+//
+#define BUILD_NUMBER 32
+
+//
+// The COMPONENT_VERSION_STRING is a string (enclosed in ") that can be used for logging or embedding.
+//
+#define COMPONENT_VERSION_STRING "1.2"
+
+//
+// The COMPONENT_DATE_STRING contains a timestamp of when the pack was generated.
+//
+// The COMPONENT_DATE_STRING is written out using the following strftime pattern.
+//
+//     "%Y-%m-%d %H:%M:%S"
+//
+//
+#define COMPONENT_DATE_STRING "2025-04-21 21:39:04"
+
+#endif/* #ifndef _COMPONENT_VERSION_H_INCLUDED */
+