boards: add initial support for ST b-l475e-iot01a#7584
boards: add initial support for ST b-l475e-iot01a#7584kaspar030 merged 2 commits intoRIOT-OS:masterfrom
Conversation
|
That's a lot of connectivity options on one board. |
9ae9325 to
637ef5e
Compare
637ef5e to
84df78b
Compare
|
I received some gifts today with 2 of these boards in :) Just tested it and this PR seems to work: I could play with the shell and on-board LEDs. I need to go further in testing and also rebase. |
a309758 to
c5b9575
Compare
|
The initial port was not that bad. I tested configured uart, timer, rtc, rtt with success. Maybe @astralien3000 you can test the configured PWMs ? |
haukepetersen
left a comment
There was a problem hiding this comment.
Minor remarks, else looks good.
But I'd say the discussion from #8058 applies here as well -> 90% of the lines in this PR are duplicates of existing code. But I am unsure we want to go ahead as is (and cleaup later), or if we want to wait merging this PR until some more clear structure for code sharing is agreed upon.
| @@ -0,0 +1,13 @@ | |||
| ## the cpu to build for | |||
| cpu_init(); | ||
|
|
||
| /* initialize the boards LED */ | ||
| #ifdef AUTO_INIT_LED0 |
There was a problem hiding this comment.
just to make sure: is this also the case on this board or is this just a copy/paste error from the nucleo code?
There was a problem hiding this comment.
It's also the case on this board => same pin for LED_0 and SPI_0 clock
There was a problem hiding this comment.
is this just a copy/paste error from the nucleo code?
hopefully all my code is not only copy paste
I know, that's why I'm very much in favour of the proposed solutions there (whichever is chosen). See my comment talking about the introduction of a The board here and others from ST are sharing a lot of things (Arduino compatible pinout, ST-Link, etc) |
|
I would also like to have #7799 merged soon and rebase on it after |
c5b9575 to
bafbd41
Compare
Take a look at #7686 to adapt the debugger. |
|
Saul SENSE_BTN does not seem to work. EDIT: it's C13 instead of B2 |
Thanks for having a look @astralien3000 ! Will fix |
|
I also tested PWMs, D9 is working, but not D5 and D6. |
bafbd41 to
9b53809
Compare
|
@astralien3000, I fixed the wrong pin definitions and removed the 2 PWM that doesn't work as it seems to be a more general driver issue (not being able to change the timer width). |
|
@kYc0o, I addressed your comment regarding the debugger configuration. Still works ! |
f0b048e to
f703f98
Compare
b61f0e0 to
cda7355
Compare
|
@haukepetersen, @kYc0o, I think we are good with this one. I tested it again locally and it's still working. |
| FEATURES_PROVIDED += periph_timer | ||
| FEATURES_PROVIDED += periph_uart | ||
|
|
||
| # Load extra provided features |
There was a problem hiding this comment.
remove this, cpp is provided by cortex-m
b8386b9 to
1fd4ef1
Compare
|
The LED1 macros are not working due to a typo in the board.h file. They are defined with LED0_MASK instead of LED1_MASK. Thanks adding support to this board! I would like to learn RIOT and I'm with this board in hands. |
1fd4ef1 to
54b889b
Compare
Thanks for reporting @fernandoavita. I just pushed the fixed configuration. Can you test again ? |
Sure! Now they are working. Thanks @aabadie! |
|
@kaspar030 ? (now that your github notifications are fixed :) ) |
Board datasheet is here, detailed pdf is here.
This board is very interesting for IoT:
I'll create an issue to keep track of the remaining things to do to fully support it.
Thanks to @kYc0o who pointed me to it :)