cancel
Showing results for 
Search instead for 
Did you mean: 

Assignment bug in I-Cube_EMBOS, BSP drivers steal pin assignments with no options

Harvey White
Senior III

 Investigating I-Cube_EMBOS.  Using latest version of CubeMXIDE.
Hardware is Nucleo-144 F767 with custom board piggybacked.

Custom board has pins assigned to LEDS, pins are

#define BLUE_LED_Pin GPIO_PIN_10
#define BLUE_LED_GPIO_Port GPIOD
#define RED_LED_Pin GPIO_PIN_4
#define RED_LED_GPIO_Port GPIOG
#define GREEN_LED_Pin GPIO_PIN_7
#define GREEN_LED_GPIO_Port GPIOG
#define AMBER_LED_Pin GPIO_PIN_8
#define AMBER_LED_GPIO_Port GPIOG

 as assigned by the IOC file.

In the Platform settings, all four BSP LEDS must be assigned.

The default assignments take the LED pin and definitions (as above in the main.h file) and remove them.  Since the pins MUST be defined or the code will not generate, selecting the appropriate pins force encoding in the BSP drivers.  This require rewriting code and forces the use of the BSP drivers.  This is not desirable.

Assigning the LEDS to unused pins includes the LED pins (as above) in the main.h file.

The appropriate action would be to have a "do not use" option which would free up the pin for use in existing drivers.

Since this is an experimental project, to see if I-Cube_EMBOS works properly, this particular problem is not critical, but likely will need to be fixed in a future release.

 

 

0 REPLIES 0