Incorrect port definitions in SDK for (at least) MPC5745R

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Incorrect port definitions in SDK for (at least) MPC5745R

784 Views
joost_sannen
Contributor I

I believe I have found a problem with the port definitions in the SDK for the MPC5745R.
From port PTK all pointers actually reference PTJ...

After applying the patch below things seem better. Could someone please confirm this is a bug and that my fix is correct and complete?

Patch:

Index: MPC5745R_features.h
===================================================================
--- MPC5745R_features.h (revision 1053)
+++ MPC5745R_features.h (revision 1082)
@@ -1752,27 +1752,27 @@
/** Peripheral PTK base address */
#define PTK_BASE (0xFFFC1714u)
/** Peripheral PTK base pointer */
-#define PTK ((GPIO_Type *)PTJ_BASE)
+#define PTK ((GPIO_Type *)PTK_BASE)
/** Peripheral PTL base address */
#define PTL_BASE (0xFFFC1716u)
/** Peripheral PTL base pointer */
-#define PTL ((GPIO_Type *)PTJ_BASE)
+#define PTL ((GPIO_Type *)PTL_BASE)
/** Peripheral PTW base address */
#define PTW_BASE (0xFFFC1718u)
/** Peripheral PTW base pointer */
-#define PTW ((GPIO_Type *)PTJ_BASE)
+#define PTW ((GPIO_Type *)PTW_BASE)
/** Peripheral PTX base address */
#define PTX_BASE (0xFFFC171Au)
/** Peripheral PTX base pointer */
-#define PTX ((GPIO_Type *)PTJ_BASE)
+#define PTX ((GPIO_Type *)PTX_BASE)
/** Peripheral PTY base address */
#define PTY_BASE (0xFFFC171Cu)
/** Peripheral PTY base pointer */
-#define PTY ((GPIO_Type *)PTJ_BASE)
+#define PTY ((GPIO_Type *)PTY_BASE)
/** Peripheral PTZ base address */
#define PTZ_BASE (0xFFFC171Eu)
/** Peripheral PTZ base pointer */
-#define PTZ ((GPIO_Type *)PTJ_BASE)
+#define PTZ ((GPIO_Type *)PTZ_BASE)

/** Array initializer of GPIO peripheral base addresses */
#define GPIO_BASE_ADDRS { PTA_BASE, PTB_BASE, PTC_BASE, PTD_BASE, \

Labels (1)
0 Kudos
1 Reply

598 Views
cezardobromir
NXP Employee
NXP Employee

Hello Joost,

Indeed, it seems to be an issue in the SDK pointers definitions.

Thank you for reporting the issue. We will have it fixed for the next release.

Until then please use the fixed patch that you mentioned.

Best regards,

Cezar

0 Kudos