Nucleo f030r8 #1103
Closed
Nucleo f030r8 #1103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@apodogrocki, @erwango, @ydamigos |
ydamigos
requested changes
Aug 14, 2017
dbkinder
reviewed
Aug 14, 2017
|
|
||
| Overview | ||
| ******** | ||
| STM32 Nucleo-64 development board with STM32F030R8 MCU, supports Arduino and ST morpho connectivity. |
dbkinder
reviewed
Aug 14, 2017
|
|
||
| The STM32 Nucleo board provides an affordable and flexible way for users to try out new concepts, | ||
| and build prototypes with the STM32 microcontroller, choosing from the various | ||
| combinations of performance, power consumption and features. |
There was a problem hiding this comment.
add a comma before the "and"
dbkinder
reviewed
Aug 14, 2017
| expansion of the STM32 Nucleo open development platform with a wide choice of | ||
| specialized shields. | ||
|
|
||
| The STM32 Nucleo board does not require any separate probe as it integrates the ST-LINK/V2-1 |
There was a problem hiding this comment.
recommend deleting "does not require any separate probe as it"
dbkinder
reviewed
Aug 14, 2017
| ======== | ||
|
|
||
| Nucleo F030R8 board includes an ST-LINK/V2-1 embedded debug tool interface. | ||
| This interface is supported by the openocd version included in Zephyr SDK. |
dbkinder
reviewed
Aug 14, 2017
| Flashing an application to Nucleo F030R8 | ||
| ---------------------------------------- | ||
|
|
||
| The sample application `blinky` is being used in this tutorial: |
There was a problem hiding this comment.
change to
:ref:`blinky-sample`
dbkinder
reviewed
Aug 14, 2017
| ---------------------------------------- | ||
|
|
||
| The sample application `blinky` is being used in this tutorial: | ||
|
|
There was a problem hiding this comment.
I'd recommend deleting this code block (and change the colon ":" on the previous line to end with a period.
dbkinder
reviewed
Aug 14, 2017
|
|
||
| $ make BOARD=nucleo_f030r8 flash | ||
|
|
||
| Run a serial host program to connect with your Nucleo board: |
There was a problem hiding this comment.
Just checking, do you need to connect a serial host for this app? What's written to the console?
dbkinder
suggested changes
Aug 14, 2017
galak
requested changes
Aug 14, 2017
There was a problem hiding this comment.
The hal import should separate the import of code from the adding Kconfig/Makefile for building it.
Also, the commit message should include the source (where to find the HAL)
Example:
commit 0015544
Author: Erwan Gouriou erwan.gouriou@linaro.org
Date: Wed Nov 9 15:23:39 2016 +0100
stm32cube: Introduce STM32Cube for STM32F2xx series
With this commit we provide header and HAL/LL files for all STM32F2
SoCs.
Using STM32Cube provides generic access to all families, maximizes
code reuse across different STM32 families and helps taking benefit
of a mature SDK
Origin: STM32Cube
URL: http://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-embedded-software/stm32cubef2.html
Purpose: Introduction of STM32F2xx STM32Cube definitions
and Abstraction Layers
Maintained-by: External
Original STM32Cube tree structure has been modified to a minimum
structure for a better fit into Zephyr. hal is split into 2 parts:
-driver: initially Drivers/STM32F2xx_HAL_Driver, contains HAL and LL
-soc: initially Drivers/CMSIS/Device/ST/STM32F2xx, contains stm32f2xx
socs header files
Change-Id: I78a4716d495ce3f3038a442e19a0403f0f00506c
Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
please look at CONTRIBUTING.rst or https://www.zephyrproject.org/doc/contribute/contribute_guidelines.html#identifying-contribution-origin |
galak
requested changes
Aug 14, 2017
drivers/pinmux/Makefile
Outdated
| @@ -6,20 +6,21 @@ ccflags-$(CONFIG_PINMUX_QMSI) += -I$(CONFIG_QMSI_INSTALL_PATH)/include | |||
| obj-$(CONFIG_PINMUX_MCUX) += pinmux_mcux.o | |||
| obj-$(CONFIG_PINMUX_STM32) += stm32/pinmux_stm32.o | |||
| obj-$(CONFIG_PINMUX_BEETLE) += beetle/pinmux_board_v2m_beetle.o | |||
| obj-$(CONFIG_BOARD_NUCLEO_F103RB) += stm32/pinmux_board_nucleo_f103rb.o | |||
There was a problem hiding this comment.
not sure why the changes, here. But lets put the board pinmux in boards/arm/nucleo_f030r8/pinmux.c
There was a problem hiding this comment.
The changes are just to put the nucleo boards in order.
As for pinmux, I will follow the include/dt-bindings convention, and I will leave the boards/ as it is in the rest of nucleos.
There was a problem hiding this comment.
STM32 boards pinmux code has been moved recenlty with #1301 (merged in ARM branch for now).
Please update according to this change (maybe rebase on ARM branch to do so)
There was a problem hiding this comment.
@erwango I moved the drivers/pinmux/stm32/pinmux_board_nucleo_f030r8.c to boards/arm/nucleo_f030r8/pinmux.c. Is that what you mean?
There was a problem hiding this comment.
Yes, and then you should not need to impact pinmux makefile anymore.
You could also rework commit title as this one is no more specific to nucleo f030 board
| @@ -13,6 +13,36 @@ config EXTI_STM32 | |||
| help | |||
| Enable EXTI driver for STM32 line of MCUs | |||
|
|
|||
| if SOC_SERIES_STM32F0X | |||
There was a problem hiding this comment.
why do we need this if? We dont for any other of the STM32 SoC families
| @@ -270,7 +304,6 @@ static inline void __stm32_exti_isr_15_10(void *arg) | |||
| __stm32_exti_isr(10, 16, arg); | |||
| } | |||
|
|
|||
| #ifdef CONFIG_SOC_SERIES_STM32F4X | |||
There was a problem hiding this comment.
seems like this shouldn't be removed
Seems like #if defined(CONFIG_SOC_SERIES_STM32F0X) || defined(CONFIG_SOC_SERIES_STM32F4X)
MaciejDebski
force-pushed
the
nucleo_f030r8
branch
2 times, most recently
from
359bdf4
to
416d9b6
Compare
|
@MaciejDebski is this now working for you with the pinmux/dts changes? |
|
@galak Yes, I did manage to make it work for new pinmux/dts in the end, but there were a problem on the way, totally somewhere else. Some small snippet of code concerning aliasing flash memory in my cortex, which was added recently by someone else, was messing everything up. I described it in this months zephyr-devel, in the mail named: Adding Nucleo-F030R8 support to Zephyr - runtime error. I still have to post issue on github, but I am not going to change my pull request code, it should be all good. Is it OK? |
|
@nashif Thank you for your help, it is fixed now! |
|
@galak HAL libs and Kconfig/Makefile are now separated. Thank you. |
|
@dbkinder All the recommended changes are implemented, thank you! |
|
@ydamigos The new approach to pinmux/dts is implemented, thank you! |
ydamigos
reviewed
Sep 1, 2017
arch/arm/soc/st_stm32/stm32f0/soc.h
Outdated
| #include <stm32f0xx.h> | ||
|
|
||
| /* IO pin functions */ | ||
| enum stm32f0x_pin_config_mode { |
There was a problem hiding this comment.
Do we still need this enumeration?
MaciejDebski
force-pushed
the
nucleo_f030r8
branch
from
f3adc04
to
02e99c9
Compare
|
@ydamigos enum in arch/arm/soc/st_stm32/stm32f0/soc.h was not necessary to compile. Updated. Thank you. |
erwango
reviewed
Sep 4, 2017
| @@ -223,7 +236,9 @@ static int stm32_clock_control_init(struct device *dev) | |||
|
|
|||
| /* Disable other clocks */ | |||
| LL_RCC_HSE_Disable(); | |||
| #ifndef CONFIG_SOC_SERIES_STM32F0X | |||
There was a problem hiding this comment.
Remove the #ifdef here, as you defined LL_RCC_MSI_Disable in stm32_f0_ll_clock.c file
It helps reducing the use of ifdef in this generic file (when doable)
| @@ -239,7 +254,10 @@ static int stm32_clock_control_init(struct device *dev) | |||
|
|
|||
| /* Disable other clocks */ | |||
| LL_RCC_HSI_Disable(); | |||
|
|
|||
| #ifndef CONFIG_SOC_SERIES_STM32F0X | |||
| LL_RCC_MSI_Disable(); | ||
| #endif /* CONFIG_SOC_SERIES_STM32F0X */ |
| << RCC_CFGR_PLLMUL_Pos); | ||
| #if defined(RCC_PLLSRC_PREDIV1_SUPPORT) | ||
| /* PREDIV support is a specific RCC configuration present on */ | ||
| /* following SoCs: STM32F302XE, STM32F303xE and STM32F398xx */ |
added 10 commits
September 14, 2017 17:48
The commit delivers HAL/LL static library source files for STM32F0 SoC. Using STM32Cube provides generic access to all families, maximizes code reuse across different STM32 families and helps taking benefits of a mature SDK. Origin: STM32Cube URL: http://www.st.com/en/embedded-software/stm32cubef0.html Purpose: Introduction of STM32F0xx STM32Cube definitions and Abstraction Layers Maintained-by: External Original STM32Cube tree structure has been modified to a minimum structure for a better fit into Zephyr. HAL is split into 2 parts: -driver: initially Drivers/STM32F0xx_HAL_Driver, contains HAL and LL -soc: initially Drivers/CMSIS/Device/ST/STM32F0xx, contains stm32f0xx SoCs header files. JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
JIRA: ZEP-2492 Signed-off-by: Maciej Debski <maciej.debski@rndity.com>
MaciejDebski
force-pushed
the
nucleo_f030r8
branch
from
bd12589
to
1c265be
Compare
|
@superna9999 |
Some SOCs (e.g. STM32F0) can map the flash to address 0 and the flash base address at the same time. Prevent writing to duplicate flash address which stops the SOC. Allow Cortex M SOCs to create their own vector table relocation function. Provide a relocation function for STM32F0x SOCs. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
MaciejDebski
force-pushed
the
nucleo_f030r8
branch
from
8a14cd0
to
1cca52f
Compare
|
the issue about missing memory was discusses on the mailing-list, it should be solved since all other points were solved. |
|
Hello @MaciejDebski @superna9999 the commit b0661@30e4e71 should make the pull request pass CI. @superna9999 You mentioned that the missing memory was already discussed on the mailing list and solved. I did not find the solution. Don´t we need the commit above? @MaciejDebski Do you plan to integrate the commit? If you like I can create a combined pull request that takes your pull request as the basis https://github.com/b0661/zephyr/tree/stm32f0_nucleos Regards |
|
@b0661 In was referencing the solution you provide in this commit |
|
@MaciejDebski Would you want @b0661 or me to take over this PR (while keeping your authorship) if you don't have enough time ? |
|
Hi Neil,
On behalf of Maciek I would like to ask you or Bobby to take over this PR.
In October Maciek will not have enough time to finalize this job.
Cheers,
Adam Podogrocki
2017-10-09 13:55 GMT+02:00 Neil Armstrong <notifications@github.com>:
… @MaciejDebski <https://github.com/maciejdebski> Would you want @b0661
<https://github.com/b0661> or me to take over this PR (while keeping your
authorship) if you don't have enough time ?
We have at least 2 more F0 SoCs/Boards to submit following this PR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AP5E9W_K3-G1V6SwLBWIKCNqnPORSuZ4ks5sqgmngaJpZM4O2FiW>
.
--
Adam Podogrocki
*Senior Software Engineer* of *rndity;*
+48 607 236 982 <+48+607+236+982> rndity.com
[image: facebook] <http://facebook.com/rndity> [image: twitter]
<http://twitter.com/RnDity_com> [image: linkedin]
<https://www.linkedin.com/company/rndity> [image: github]
<https://github.com/RnDity>
[image: rndity]
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended
addressee, you may neither use this message nor copy or deliver it to
anyone. In such case, you should immediately destroy this message and
kindly notify the sender by reply email. Thank you.
|
Merged
|
Hi Adam,
Should we consider this is same situation for you and
#556 ?
("iwdg: make independent watchdog driver compliant with STM32Cube LL API")
(keeping your credit of course).
There is less demand on this one than on STM32F0, but it would be nice we
don't loose the benefit of your work.
Or you already planned to resume it later on?
Cheers
Erwan
…On 9 October 2017 at 14:13, Adam Podogrocki ***@***.***> wrote:
Hi Neil,
On behalf of Maciek I would like to ask you or Bobby to take over this PR.
In October Maciek will not have enough time to finalize this job.
Cheers,
Adam Podogrocki
2017-10-09 13:55 GMT+02:00 Neil Armstrong ***@***.***>:
> @MaciejDebski <https://github.com/maciejdebski> Would you want @b0661
> <https://github.com/b0661> or me to take over this PR (while keeping
your
> authorship) if you don't have enough time ?
> We have at least 2 more F0 SoCs/Boards to submit following this PR
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1103 (comment)-
335136071>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AP5E9W_K3-
G1V6SwLBWIKCNqnPORSuZ4ks5sqgmngaJpZM4O2FiW>
> .
>
--
Adam Podogrocki
*Senior Software Engineer* of *rndity;*
+48 607 236 982 <+48%20607%20236%20982> <+48+607+236+982> rndity.com
[image: facebook] <http://facebook.com/rndity> [image: twitter]
<http://twitter.com/RnDity_com> [image: linkedin]
<https://www.linkedin.com/company/rndity> [image: github]
<https://github.com/RnDity>
[image: rndity]
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended
addressee, you may neither use this message nor copy or deliver it to
anyone. In such case, you should immediately destroy this message and
kindly notify the sender by reply email. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARtr5HAbwtjUXMPwc55RD2JRENkz1U6Tks5sqg30gaJpZM4O2FiW>
.
|
|
Hi Erwan,
I was convinced that there is no more work for me regarding mentioned PR
(iwdg). Patch for CubeMX is required, as it was discussed in separate PR,
but it doesn't cause the iwdg works incorrectly. So if you have nay
suggestions what I could add more, please let me know.
Cheers,
Adam
2017-10-11 10:53 GMT+02:00 Erwan Gouriou <notifications@github.com>:
… Hi Adam,
Should we consider this is same situation for you and
#556 ?
("iwdg: make independent watchdog driver compliant with STM32Cube LL API")
(keeping your credit of course).
There is less demand on this one than on STM32F0, but it would be nice we
don't loose the benefit of your work.
Or you already planned to resume it later on?
Cheers
Erwan
On 9 October 2017 at 14:13, Adam Podogrocki ***@***.***>
wrote:
> Hi Neil,
>
> On behalf of Maciek I would like to ask you or Bobby to take over this
PR.
> In October Maciek will not have enough time to finalize this job.
>
> Cheers,
> Adam Podogrocki
>
> 2017-10-09 13:55 GMT+02:00 Neil Armstrong ***@***.***>:
>
> > @MaciejDebski <https://github.com/maciejdebski> Would you want @b0661
> > <https://github.com/b0661> or me to take over this PR (while keeping
> your
> > authorship) if you don't have enough time ?
> > We have at least 2 more F0 SoCs/Boards to submit following this PR
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <#1103 (comment)-
> 335136071>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AP5E9W_K3-
> G1V6SwLBWIKCNqnPORSuZ4ks5sqgmngaJpZM4O2FiW>
> > .
> >
>
>
>
> --
>
> Adam Podogrocki
>
> *Senior Software Engineer* of *rndity;*
>
> +48 607 236 982 <+48%20607%20236%20982> <+48%20607%20236%20982>
<+48+607+236+982> rndity.com
>
> [image: facebook] <http://facebook.com/rndity> [image: twitter]
> <http://twitter.com/RnDity_com> [image: linkedin]
> <https://www.linkedin.com/company/rndity> [image: github]
> <https://github.com/RnDity>
>
> [image: rndity]
>
> Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
> lub poufne informacje i została wysłana wyłącznie do wiadomości i
> użytku osób, do których została zaadresowana. Jeśli wiadomość została
> otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
> osób trzecich. W takim przypadku uprasza się o natychmiastowe
> zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
> sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
>
> This message, including any attachments hereto, may contain privileged
> or confidential information and is sent solely for the attention and
> use of the intended addressee(s). If you are not an intended
> addressee, you may neither use this message nor copy or deliver it to
> anyone. In such case, you should immediately destroy this message and
> kindly notify the sender by reply email. Thank you.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1103 (comment)-
335139975>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
ARtr5HAbwtjUXMPwc55RD2JRENkz1U6Tks5sqg30gaJpZM4O2FiW>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AP5E9WoYegFMoElFBr508RyANRE_ih4aks5srIIGgaJpZM4O2FiW>
.
--
Adam Podogrocki
*Senior Software Engineer* of *rndity;*
+48 607 236 982 <+48+607+236+982> rndity.com
[image: facebook] <http://facebook.com/rndity> [image: twitter]
<http://twitter.com/RnDity_com> [image: linkedin]
<https://www.linkedin.com/company/rndity> [image: github]
<https://github.com/RnDity>
[image: rndity]
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended
addressee, you may neither use this message nor copy or deliver it to
anyone. In such case, you should immediately destroy this message and
kindly notify the sender by reply email. Thank you.
|
|
Yeah, I also considered it was ok.
So, we just miss LSI_VALUE fix to be provided aside and we're good.
And a PR from Yannis just came in. So let's try to get it merged then.
Can you rebase the patchset first?
On 11 October 2017 at 12:16, Adam Podogrocki <notifications@github.com>
wrote:
… Hi Erwan,
I was convinced that there is no more work for me regarding mentioned PR
(iwdg). Patch for CubeMX is required, as it was discussed in separate PR,
but it doesn't cause the iwdg works incorrectly. So if you have nay
suggestions what I could add more, please let me know.
Cheers,
Adam
2017-10-11 10:53 GMT+02:00 Erwan Gouriou ***@***.***>:
> Hi Adam,
>
> Should we consider this is same situation for you and
> #556 ?
> ("iwdg: make independent watchdog driver compliant with STM32Cube LL
API")
> (keeping your credit of course).
> There is less demand on this one than on STM32F0, but it would be nice we
> don't loose the benefit of your work.
> Or you already planned to resume it later on?
>
> Cheers
> Erwan
>
> On 9 October 2017 at 14:13, Adam Podogrocki ***@***.***>
> wrote:
>
> > Hi Neil,
> >
> > On behalf of Maciek I would like to ask you or Bobby to take over this
> PR.
> > In October Maciek will not have enough time to finalize this job.
> >
> > Cheers,
> > Adam Podogrocki
> >
> > 2017-10-09 13:55 GMT+02:00 Neil Armstrong ***@***.***>:
> >
> > > @MaciejDebski <https://github.com/maciejdebski> Would you want
@b0661
> > > <https://github.com/b0661> or me to take over this PR (while keeping
> > your
> > > authorship) if you don't have enough time ?
> > > We have at least 2 more F0 SoCs/Boards to submit following this PR
> > >
> > > —
> > > You are receiving this because you were mentioned.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/zephyrproject-rtos/zephyr/
pull/1103#issuecomment-
> > 335136071>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/AP5E9W_K3-
> > G1V6SwLBWIKCNqnPORSuZ4ks5sqgmngaJpZM4O2FiW>
> > > .
> > >
> >
> >
> >
> > --
> >
> > Adam Podogrocki
> >
> > *Senior Software Engineer* of *rndity;*
> >
> > +48 607 236 982 <+48%20607%20236%20982> <+48%20607%20236%20982>
<+48%20607%20236%20982>
> <+48+607+236+982> rndity.com
> >
> > [image: facebook] <http://facebook.com/rndity> [image: twitter]
> > <http://twitter.com/RnDity_com> [image: linkedin]
> > <https://www.linkedin.com/company/rndity> [image: github]
> > <https://github.com/RnDity>
> >
> > [image: rndity]
> >
> > Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
> > lub poufne informacje i została wysłana wyłącznie do wiadomości i
> > użytku osób, do których została zaadresowana. Jeśli wiadomość została
> > otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
> > osób trzecich. W takim przypadku uprasza się o natychmiastowe
> > zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
> > sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
> >
> > This message, including any attachments hereto, may contain privileged
> > or confidential information and is sent solely for the attention and
> > use of the intended addressee(s). If you are not an intended
> > addressee, you may neither use this message nor copy or deliver it to
> > anyone. In such case, you should immediately destroy this message and
> > kindly notify the sender by reply email. Thank you.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <#1103 (comment)-
> 335139975>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/
> ARtr5HAbwtjUXMPwc55RD2JRENkz1U6Tks5sqg30gaJpZM4O2FiW>
> > .
>
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1103 (comment)-
335742354>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AP5E9WoYegFMoElFBr508RyANRE_ih4aks5srIIGgaJpZM4O2FiW>
> .
>
--
Adam Podogrocki
*Senior Software Engineer* of *rndity;*
+48 607 236 982 <+48%20607%20236%20982> <+48+607+236+982> rndity.com
[image: facebook] <http://facebook.com/rndity> [image: twitter]
<http://twitter.com/RnDity_com> [image: linkedin]
<https://www.linkedin.com/company/rndity> [image: github]
<https://github.com/RnDity>
[image: rndity]
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended
addressee, you may neither use this message nor copy or deliver it to
anyone. In such case, you should immediately destroy this message and
kindly notify the sender by reply email. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARtr5KrBzLnX0Y8Ler-S1NIyT_Tc-y-rks5srJWKgaJpZM4O2FiW>
.
|
nagineni
pushed a commit
to nagineni/zephyr
that referenced
this pull request
Nov 20, 2017
…rtos#1103) Signed-off-by: Geoff Gustafson <geoff@linux.intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ZEP-2492
boards: provide support for Nucleo-64 F030R8