cancel
Showing results for 
Search instead for 
Did you mean: 

Inconsistent generated Pin and Port names

Andrew Neil
Super User

See Inconsistent pin naming for CubeMX - does the same apply to CubeMX2 ?

 

(Cross-posting at the request of @Ghofrane GSOURI; again, no label available for "Suggestions")

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
1 ACCEPTED SOLUTION

Accepted Solutions
MorkBeck
ST Employee

Hi

We have checked the generated code, and it should be solved in CubeXM2. The defines is now called:

/** Primary aliases for RCC_OSC_IN pin */
#define PH0_OSC_IN_PORT                       HAL_GPIOH
#define PH0_OSC_IN_PIN                        HAL_GPIO_PIN_0
 
/** Primary aliases for RCC_OSC_OUT pin */
#define PH1_OSC_OUT_PORT                      HAL_GPIOH
#define PH1_OSC_OUT_PIN                       HAL_GPIO_PIN_1

 

So there is consistency in the naming. If you find any non consistent naming schemes, please let us know, so we can get them fixed!

View solution in original post

1 REPLY 1
MorkBeck
ST Employee

Hi

We have checked the generated code, and it should be solved in CubeXM2. The defines is now called:

/** Primary aliases for RCC_OSC_IN pin */
#define PH0_OSC_IN_PORT                       HAL_GPIOH
#define PH0_OSC_IN_PIN                        HAL_GPIO_PIN_0
 
/** Primary aliases for RCC_OSC_OUT pin */
#define PH1_OSC_OUT_PORT                      HAL_GPIOH
#define PH1_OSC_OUT_PIN                       HAL_GPIO_PIN_1

 

So there is consistency in the naming. If you find any non consistent naming schemes, please let us know, so we can get them fixed!