-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
board: added board nucleo f401 #2601
Conversation
@@ -0,0 +1,4 @@ | |||
FEATURES_PROVIDED += cpp | |||
FEATURES_PROVIDED += periph_uart periph_gpio periph_spi periph_i2c periph_pwm \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please put one feature per row (-> see #2611)
Hi, looks good! I found some minor things. It seems you have some duplicates in your pin mapping. Could you maybe provide a document similar to this one, as this helps to make sure your pin mapping is clean. Could you also create a Wiki page for the board? Could you also split this PR and take out the changes done to |
Hi, thanks for your reply! I will look into it soon and split it. You're right that those pin assignments should not overlap, but it would be also good to have available peripherals mapped to arduino header (which can cause conflicts). Is it possible to remove commits done to |
no, keep this PR open and just remove the cleanup changes you did to the |
Hi, I made some changes in peripheral configuration and removed cleanup changes to |
9f184dd
to
45554bf
Compare
You still have pin A5 assigned for the boards LED and for SPI0 CLK... I would recommend re-mapping SPI0 CLK to some other pin! |
@haukepetersen: On the nucleo-f334 that makes the LED blink during transfers - I actually like it. :) |
Hi, sorry for the delay. |
* @file | ||
* @brief Board specific implementations for the STM32F4Discovery evaluation board | ||
* | ||
* @author Hauke Petersen <hauke.petersen@fu-berlin.de> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy&paste?
Hi, |
@adamberlinger, what's the latest here? |
@katezilla can you please have a look at this PR and if it matches our "new" gpio API and architecture? |
yes, checking it |
#define GPIO_2_PORT GPIOC /* Used for user button 1 */ | ||
#define GPIO_2_PIN 3 | ||
#define GPIO_2_CLK 2 /* 0: PORT A, 1: B ... */ | ||
#define GPIO_2_EXTI_CFG() (SYSCFG->EXTICR[0] |= SYSCFG_EXTICR1_EXTI3_PC) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in #3095 we changed the implementation and gpio interface. please adapt to that new style, for an example you can check out the stm32f4-discovery board
do you still intend to work on this pr? |
Hi, |
@adamberlinger, @katezilla, @haukepetersen, @latsku, anyone object closing this one? |
I'll close this one now in favour of #4119 . @adamberlinger sorry for the duplicate work. Hope to see an other PR from you any time in future :-) |
I also added CLOCK_USE_HSI switch to use internal oscillator if required.