board: Initial import of stm32f4discovery board#1191
board: Initial import of stm32f4discovery board#1191haukepetersen merged 4 commits intoRIOT-OS:masterfrom
Conversation
|
Can't you feature test if |
|
That is actually a good idea, will look into this. |
|
@haukepetersen can we this PR as a goal for IOTweek? |
|
sure |
|
Ok nano-specs are now optional. Will test and make this PR ready next week. |
|
can you make the TODOs a checkbox list? |
|
Certainly |
|
great =) |
|
Rebased this branch and did some fixes - still some parts to do, though... |
There was a problem hiding this comment.
I see I see :-)
|
Adressed @Kijewski issues, fixed compiler warnings, cleaned up task-switching code and rebased. |
|
Your license header is not known - I suggest you use the old-style header and let it be fixed in #1329 . |
|
Otherwise you could also add this new pattern to |
|
Ok, I will reverse to the old header once I have time. |
|
nice, merged it into this PR. |
|
rebase! |
|
rebased. |
|
Not WIP anymore: now finally fully tested and functioning, please test! |
|
Regarding the licenses, there are two files, (i) OpenCM3 doesn't really supply an alternative, as they are using their complete own scheme for header files. This I would's like to use, as the vendor header files we use all follow the same scheme, which makes it nice when switching between ST, Frescale, NXP etc... I talked further to @StefanPfeiffer, that on the long run it would make sense for us to re-implement the So in the end, for my opinion we should be fine with these two files, or is anyone strongly disagreeing? |
|
Regarding the |
|
I'd opt for implementing our own version.. one that abides to our coding conventions ;-) |
At least in Germany. |
|
Ok, so I guess re-implementing it is. I just looked into the CubeMX configuration-generation tool from ST (some windows-based f***), and this is generating code with this license: ******************************************************************************
*
* COPYRIGHT(c) 2014 STMicroelectronics
*
* Redistribution and use in source and binary forms, with or without modification,
* are permitted provided that the following conditions are met:
* 1. Redistributions of source code must retain the above copyright notice,
* this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright notice,
* this list of conditions and the following disclaimer in the documentation
* and/or other materials provided with the distribution.
* 3. Neither the name of STMicroelectronics nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
* CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
****************************************************************************** |
|
That's a regular 3 clause BSD license if I didn't overlook something.. it's already approved by our license checker =) |
|
I implemented a version compliant to our coding conventions for #1363 in |
|
Rebase on master and throw out the license commit (was already merged via #1396) |
|
rebased. The licensing issue with the start-up code is on progress, will update as soon as this is ready. |
|
adjusted PR for the the merged #856 |
|
@haukepetersen the BSD is absolutely no problem :) great! |
There was a problem hiding this comment.
I'd throw out the comments and the empty DIRS variable
There was a problem hiding this comment.
why throw out comments, they dont hurt... The DIRS I can throw out.
|
rebased and fixed error introduced from #1398 |
|
addressed comment from @Kijewski |
|
Here we go, I implemented the clock-setup code myself, this should take care of the license issues. Also did the usual squashing/rebasing - this PR should now be ready to merge?! |
|
Again here: Who's equipped with the right hardware and willing to test? |
|
ACK - works with Launchpad ARM embedded toolchain. |
|
Wanna squash something? |
|
yapp, squash on the way |
|
and go! |
board: Initial import of stm32f4discovery board
This is still WIP, left TODOs are:cortexm_commonintocortex-m4_common