Skip to content
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

Closed
wants to merge 10 commits into from
Closed

board: added board nucleo f401 #2601

wants to merge 10 commits into from

Conversation

adamberlinger
Copy link

I also added CLOCK_USE_HSI switch to use internal oscillator if required.

@OlegHahm OlegHahm added Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: new feature The issue requests / The PR implemements a new feature for RIOT labels Mar 18, 2015
@@ -0,0 +1,4 @@
FEATURES_PROVIDED += cpp
FEATURES_PROVIDED += periph_uart periph_gpio periph_spi periph_i2c periph_pwm \
Copy link
Contributor

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)

@haukepetersen
Copy link
Contributor

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 cpu/stm32f4/startup.c and put them in a separate PR, as these are unrelated to this PR.

@haukepetersen haukepetersen added the CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable label Mar 18, 2015
@adamberlinger
Copy link
Author

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).
Maybe the best solution would be to allow remapping those pins. E.g. if SPI1_REMAP is defined in Makefile those pins would be remapped. But maybe it is too complicated and confusing.

Is it possible to remove commits done to cpu/stm32f4/startup.c or should I create two new PR (one for CPU and one for borad) and close this one?

@haukepetersen
Copy link
Contributor

no, keep this PR open and just remove the cleanup changes you did to the startup.c.

@adamberlinger
Copy link
Author

Hi, I made some changes in peripheral configuration and removed cleanup changes to startup.c. I also created pinmap spreadsheet here.

@haukepetersen
Copy link
Contributor

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!

@kaspar030
Copy link
Contributor

@haukepetersen: On the nucleo-f334 that makes the LED blink during transfers - I actually like it. :)

@OlegHahm OlegHahm modified the milestone: Release 2015.06 Apr 29, 2015
@adamberlinger
Copy link
Author

Hi, sorry for the delay.
I created wiki page for the board here (I was not sure if I can place it on RIOT wiki since it is not yet merged).
Should I squash all the changes into one commit (or more)?

* @file
* @brief Board specific implementations for the STM32F4Discovery evaluation board
*
* @author Hauke Petersen <hauke.petersen@fu-berlin.de>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

copy&paste?

@adamberlinger
Copy link
Author

Hi,
@kaspar030 thanks for the notice. I updated the copyright headers. Is this alright? Because some parts are copied/derived from STM32F4 Discovery BPS.
I also refactored I2C error handling.
EDIT: I fixed the copyright once more (to include other contributors).

@OlegHahm
Copy link
Member

@adamberlinger, what's the latest here?

@PeterKietzmann
Copy link
Member

@katezilla can you please have a look at this PR and if it matches our "new" gpio API and architecture?

@katezilla
Copy link
Contributor

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)
Copy link
Contributor

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

@OlegHahm OlegHahm modified the milestones: Release 2015.08, Release NEXT MAJOR Sep 2, 2015
@katezilla
Copy link
Contributor

do you still intend to work on this pr?
otherwise i would like to merge #4119

@adamberlinger
Copy link
Author

Hi,
sorry for no response in long time. This PR requires some improvements to be compatible with new GPIO API and maybe there are some other issues. If the other PR is ready to be merged, then it probably makes no sense to work on this.

@OlegHahm OlegHahm removed this from the Release 2015.12 milestone Nov 28, 2015
@OlegHahm
Copy link
Member

@adamberlinger, @katezilla, @haukepetersen, @latsku, anyone object closing this one?

@PeterKietzmann
Copy link
Member

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 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants