Can_VS_0_PBcfg.h 5.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118
  1. /*==================================================================================================
  2. * Project : RTD AUTOSAR 4.4
  3. * Platform : CORTEXM
  4. * Peripheral : FLEXCAN
  5. * Dependencies :
  6. *
  7. * Autosar Version : 4.4.0
  8. * Autosar Revision : ASR_REL_4_4_REV_0000
  9. * Autosar Conf.Variant :
  10. * SW Version : 1.0.0
  11. * Build Version : S32K1_RTD_1_0_0_HF01_D2109_ASR_REL_4_4_REV_0000_20210907
  12. *
  13. * (c) Copyright 2020-2021 NXP Semiconductors
  14. * All Rights Reserved.
  15. *
  16. * NXP Confidential. This software is owned or controlled by NXP and may only be
  17. * used strictly in accordance with the applicable license terms. By expressly
  18. * accepting such terms or by downloading, installing, activating and/or otherwise
  19. * using the software, you are agreeing that you have read, and that you agree to
  20. * comply with and are bound by, such license terms. If you do not agree to be
  21. * bound by the applicable license terms, then you may not retain, install,
  22. * activate or otherwise use the software.
  23. ==================================================================================================*/
  24. /*==================================================================================================
  25. ==================================================================================================*/
  26. /*
  27. @brief The consistency of the configuration must be checked by the configuration tool(s).
  28. @brief (SWS_Can_00022) The code configuration of the Can module is CAN controller specific.
  29. If the CAN controller is sited on-chip, the code generation tool for the Can module is Controller specific.
  30. If the CAN controller is an external device the generation tool must not be Controller specific.
  31. @brief (SWS_Can_00024) The valid values that can be configured are hardware dependent.
  32. Therefore the rules and constraints can't be given in the standard.
  33. The configuration tool is responsible to do a static configuration checking, also regarding dependencies between modules (i.e. Port driver, MCU driver etc.)
  34. */
  35. #ifndef CAN_VS_0_PBCFG_H
  36. #define CAN_VS_0_PBCFG_H
  37. /**
  38. * @file Can_VS_0_PBcfg.h
  39. * @version 1.0.0
  40. *
  41. * @brief AUTOSAR Can - module interface
  42. * @details Configuration settings generated by user settings.
  43. *
  44. * @addtogroup CAN_DRIVER
  45. * @{
  46. */
  47. #ifdef __cplusplus
  48. extern "C"{
  49. #endif
  50. /**
  51. * @page misra_violations MISRA-C:2012 violations
  52. *
  53. * @section [global]
  54. * Violates MISRA 2012 Required Rule 5.1, External identifiers shall be distinct.
  55. * The used compilers use more than 31 chars for identifiers.
  56. *
  57. * @section [global]
  58. * Violates MISRA 2012 Required Rule 5.2, Identifiers declared in the same scope and name space shall be distinct.
  59. * The used compilers use more than 31 chars for identifiers.
  60. *
  61. * @section [global]
  62. * Violates MISRA 2012 Required Rule 5.4, Macro identifiers shall be distinct.
  63. * The used compilers use more than 31 chars for identifiers.
  64. *
  65. * @section [global]
  66. * Violates MISRA 2012 Required Rule 5.5, Identifiers shall be distinct from macro names.
  67. * The used compilers use more than 31 chars for identifiers.
  68. *
  69. * @section Can_Cfg_h_REF_1
  70. * Violates MISRA 2012 Advisory Rule 2.5, A project should not contain unused macro declarations.
  71. * Some macro are required by ASR even they are not use in MCAL layer
  72. *
  73. * @section Can_Cfg_h_REF_2
  74. * Violates MISRA 2012 Advisory Rule 4.9, A function should be used in preference to a function-like macro where they are interchangeable.
  75. * Function like macro are used to reduce code complexity
  76. */
  77. /*==================================================================================================
  78. * INCLUDE FILES
  79. * 1) system and project includes
  80. * 2) needed interfaces from external units
  81. * 3) internal and external interfaces from this unit
  82. ==================================================================================================*/
  83. /*==================================================================================================
  84. * SOURCE FILE VERSION INFORMATION
  85. ==================================================================================================*/
  86. /*
  87. * @file Can_VS_0_PBcfg.h
  88. */
  89. #define CAN_VENDOR_ID_VS_0_PBCFG_H 43
  90. #define CAN_AR_RELEASE_MAJOR_VERSION_VS_0_PBCFG_H 4
  91. #define CAN_AR_RELEASE_MINOR_VERSION_VS_0_PBCFG_H 4
  92. #define CAN_AR_RELEASE_REVISION_VERSION_VS_0_PBCFG_H 0
  93. #define CAN_SW_MAJOR_VERSION_VS_0_PBCFG_H 1
  94. #define CAN_SW_MINOR_VERSION_VS_0_PBCFG_H 0
  95. #define CAN_SW_PATCH_VERSION_VS_0_PBCFG_H 0
  96. /*==================================================================================================
  97. * FILE VERSION CHECKS
  98. ==================================================================================================*/
  99. /*==================================================================================================
  100. * DEFINES AND MACROS
  101. ==================================================================================================*/
  102. #ifdef __cplusplus
  103. }
  104. #endif
  105. /** @} */
  106. #endif /* _CAN_VS_0_PBCFG_H_ */