cancel
Showing results for 
Search instead for 
Did you mean: 

Documentation error for STM32MP215-DK

ADunc.1
Senior II

I spotted that the documentation and code examples do not match for port pin assignments for LED2 and LED 4.

The user manual manual does not match the schematics:

image.png

image.png

Code examples do match the schematics, so just a documentation error I think.

EDIT:  There is definitely some sort of misalignment here.  The Linux device tree (stm32mp215f-dk.dts) puts the blue LED on PZ3.  And when controlled on/off or heartbeat through Linux, the blue led labelled LD2 on the dev kit is controlled.  So this seems to match the user manual!

	gpio-leds {
		compatible = "gpio-leds";

		led-blue {
			function = LED_FUNCTION_HEARTBEAT;
			color = <LED_COLOR_ID_BLUE>;
			gpios = <&gpioz 3 GPIO_ACTIVE_HIGH>;
			linux,default-trigger = "heartbeat";
			default-state = "off";
		};
	};

I can only assume the LED labelled LD4 on the dev kit is wired to pin PF10?

2 REPLIES 2
PatrickF
ST Employee

Hi @ADunc.1 ,

quickly checked, I think there is no mistake, just component numbering (which is automatic I guess) that are not aligned with PCB signal naming (alignment is not mandatory although is create headache).

  • PZ3 schematic signal name is LED4, and control the blue LED labelled LD2
  • PH12 schematics signal name is LED3, and control the orange LED labelled LD3
  • PF10 schematics signal name is LED2, and control the green LED labelled LD4
  • PH4 schematics signal name is LED1, and control the red LED labelled LD5

 

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Tip of the day: Try Sidekick STM32 AI agent, see here
ADunc.1
Senior II

@PatrickF Thanks for checking.  Yeah, it's not super ideal having them labelled inconsistently, but not the end of the world.  Perhaps a note in that table in the user manual would help clarify.