Skip to content

stm32f4discovery/periph_conf: Changing pin configuration#2022

Closed
PeterKietzmann wants to merge 1 commit intoRIOT-OS:masterfrom
PeterKietzmann:change_periph_conf_stm32f4discovery
Closed

stm32f4discovery/periph_conf: Changing pin configuration#2022
PeterKietzmann wants to merge 1 commit intoRIOT-OS:masterfrom
PeterKietzmann:change_periph_conf_stm32f4discovery

Conversation

@PeterKietzmann
Copy link
Copy Markdown
Member

This PR changes the pin configuration for the stm32f4discovery board so that #2018 can use PA4 and PA5. Be aware that some applications may have to be connected differently after merging this.

@OlegHahm OlegHahm added Area: drivers Area: Device drivers Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation labels Nov 18, 2014
@haukepetersen
Copy link
Copy Markdown
Contributor

NACK. Changing the ports of SPI_1 is a bad idea, as SPI_1 is internally connected to the accelerometer that is soldered onto the board...

@haukepetersen
Copy link
Copy Markdown
Contributor

As the DAC has only these two pins available, I would vote (as I wrote in #2018) for leaving the pin-config as is and closing this PR.

@PeterKietzmann
Copy link
Copy Markdown
Member Author

Oh I overlooked this. Then you are right with NACK and we'll discuss in #2018 while closing this PR.

@PeterKietzmann PeterKietzmann deleted the change_periph_conf_stm32f4discovery branch June 5, 2015 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: drivers Area: Device drivers Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants