- Packs
- SAMV71-RT_DFP
SAMV71-RT_DFP
1.3.152-
Pack Type
Device Support
Microchip SAMV71-RT Series Device Support
-
Add to CMSIS Solution
packs:- pack: Microchip::SAMV71-RT_DFP@1.3.152
Add with cpackget
> cpackget add Microchip::SAMV71-RT_DFP@1.3.152
Download
Microchip.SAMV71-RT_DFP.1.3.152.packOverview
The Microchip SAMV71-RT Series Device Family Pack (DFP) is a CMSIS-Pack that:
- Enables compatible tools with device support.
- Contains support files for the MPLAB XC32 Compiler.
- Contains support files for the GCC compiler.
- Contains support files for the Arm Compiler for Embedded.
- Contains support files for the IAR Embedded Development Tools.
- Contains System View Description (SVD) descriptions of the peripherals.
- Flash algorithms for the on-chip flash memory.
Related packs
- pack: ARM::CMSISDevices
ATSAMV71Q21RT
MISRA-C:2023 Compliance Deviations List
Deviation ID: MFWCG-40
- Rule 5.5: Identifiers shall be distinct from macro names.
- Use case: Identifiers corresponding to register names.
Example:
```C typedef union { struct { uint32_t GPIO:29; uint32_t :3; } vec; uint32_t reg; } ECIA_SRC8_Type;
#define GPIO (0x40081000) ```
- Reason: Access to hardware.
The macros expand into the same identifiers, which allow users to detect for the presence of specific registers during preprocessing.
- Scope: Device headers for the DEC15xx and MEC15xx family
(
<device-name>.h).
Deviation ID: MFWCG-42
- Rule 20.9: All identifiers used in the controlling expression of
#ifor#elifpreprocessing directives shall be#define'd before evaluation. - Use case: Use of compiler builtin macros.
Example:
C #ifdef (__ARM_FP == 14) || (__ARM_FP == 4) fpu_enable(); #endif- Reason: Access to hardware.
Headers may rely on builtin macros from the compiler and are written under the assumption that if the macro is not defined, its value is zero.
- Scope: All device headers (
<device-name>.h).
Deviation ID: MFWCG-43
- Rule 21.1:
#defineand#undefshall not be used on a reserved identifier or reserved macro name. - Use case: Reserved names, beginning with
_followed by a capital letter or__followed by a lower-case are within the compiler's namespace.
Example:
C #define __IO volatile- Reason: Access to hardware; Code Quality (Usability: Accessibility).
Within these headers originate many reserved names that are within the compiler's namespace.
- Scope: All device headers (
<device-name>.h).
Deviation ID: MFWCG-44
- Rule 21.2: A reserved identifier or reserved macro name shall not be declared.
- Use case: Reserved names, beginning with
_followed by a capital letter or__followed by a lower-case are within the compiler's namespace.
Example:
C extern const VECTOR_TABLE_Type __VECTOR_TABLE;- Reason: Access to hardware; Code Quality (Usability: Accessibility).
Within these headers originate many reserved names that are within the compiler's namespace.
- Scope: All device headers (
<device-name>.h).
Support
For support questions, contact Microchip Support through https://www.microchip.com/en-us/support.