STM32MP1 Primer – Day 2

STM32CubeMXwhich front ends STM32CubeIDEdoes not allow us to directly assign STM32MP157x GPIO pins to the Cortex-A7 or Cortex-M4 cores. Thus, blinking LEDs is simply a matter of manually configuring the desired core's GPIO pins that drive the discovery kit's on-board LEDs. HoweverSTM32CubeMX does allow us to assign communications peripherals such as I2C to a specific core. To accomplish this peripheral assignment, we must use the resources provided by the kernel device tree. The device tree describes almost every aspect of a peripheral as it relates to the host STM32MP157x hardware. The level of detail contained within the device tree makes it a difficult thing for us to manually create. FortunatelySTM32CubeMX in conjunction with STM32CubeIDE generates a detailed device tree automatically based on our inputs to STM32CubeMX during the initial project development process. Today we will generate an STM32MP1 embedded Linux project aimed at driving an Accel6 click using the STM32MP157D's I2C peripheral I2C5. We will use STM32CubeMX to generate a device tree that includes our desired I2C5 peripheral. The Accel 6 click's physical interface to the STM32MP157D's I2C peripheral is realized using a Pi 4 click shield attached to the STM32MP157D-DK1's on-board Raspberry Pi compatible pin set.