Date   

C++ compile error

miem@...
 

Hi,

I am getting the following error while I want to compile my c++ project.

The CMAKE_CXX_COMPILER:
 
    c:/gccarmemb/bin/arm-none-eabi-g++
 
  is not a full path to an existing compiler tool.
 
  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.

Does anyone knows how to solve it?

Regards,
Mina


Re: Zephyr IPv6 default router / prefix networking options

Jukka Rissanen
 

Hi Michael,

On Fri, 2018-08-17 at 12:15 -0700, Michael Scott wrote:
Hello Devs,

I'd like to discuss some different approaches to a simple setup for
BLE
and iwpan 802.15.4 nodes connected to a gateway via 6lowpan (in a
star
pattern). No mesh involved.

On the gateway side, I'm running a NAT64 container which picks up
traffic destined for the 64:ff9b::/96 network and translates it to
IPv4
before sending it out. On the return path it gets re-translated
back
from IPv4 to the 64:ff9b::/96 IP and sent back to the original node
that
sent the data. Paired with that I'm also running a DNS64 container
on
the gateway which accepts DNS queries from the connected nodes (BLE
and
802.15.4 6lowpan) and if an IPv4 address would normally be returned
it
translates it to the 64:ff9b::/96 prefix (DNS64).

Using this setup, each node *should* have basic access to the
internet
even on home networks where there is no IPv6 available.

On each Zephyr node, we currently only have a link-local address
configured.

Enter the complications:

If I ask Zephyr to send a packet to a 64:ff9b::/96-based address
(via
the gateway IP) it gets denied because link-local addresses are not
"proper" according to RFCs and the function here:
https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/i
p/net_if.c#L1689

Here are some of my proposed changes to solve this:

1. First solution was to setup RADVD on the gateway to present a
"proper" IPv6 network to the connected nodes. Here we encounter
initial
connection failures due to the RA packets not being received prior
to
the application choosing to communicate via the network. Looks like
@jukkar's L4 notifications would come in handy here if we can craft
the
right requirements for the "UP" and "DOWN" notifications. Also, I
think
that RADVD is overkill in this scenario. We are talking about a
hand
full of nodes on 1 subnet w/ 1 statically configured router IP. It
will
never change and if the gateway goes down, the nodes would never be
connected in the first place.
This would be most standard configuration but as you said, if the
network is very tiny it is kind of overkill to use radvd. But if you
are moving the device around, then this is definitely the best option
as then the prefix is set properly in different subnets automatically.



2. Second solution was to add a Kconfig option to
subsys/net/ip/net_if.c
which would change the behavior of is_proper_ipv6_address(). In
effect
saying "go ahead and use the link-local address" we know what we're
doing. I'm not sure how the networking maintainers feel about that
as
it does contradict RFC. Seems like a one-off fix.
This is a bit too hackish imho.



3. A third solution was to add Kconfig options to
subsys/net/lib/config
for NET_APP_MY_IPV6_ROUTER, NET_APP_MY_IPV6_PREFIX and
NET_APP_MY_IPV6_PREFIX_LEN. These would effectively configure the
nodes
at boot-time as if the related RA packets had been received (no
lifetime
expiration). These changes might allow us to modify all of our IPv6
samples so that multiple nodes can be running at the same time.
We have a lot of static configuration already so probably it would not
harm too much to add these too. IPv6 is suppose to be auto configured
so setting these at compile time would contradict this idea. Currently
the static IPv6 address configuration in Zephyr is meant for testing
purposes and setting also prefix and router statically would help
testing effort in this front. IMHO it does not make much sense to use
statically set IPv6 addresses in real networks.

In real life scenarios and devices, I would definitely prefer the
option 1. as then everything would work just fine in every network
setup and there would be no need re-compile if you want to use
different IPv6 configuration and subnet. This is how IPv6 is suppose to
work anyway.


So a summary of these imho would be:
* Option 1. is the best bet for real life devices
* Option 2. is no-go
* Option 3. we could add the static prefix and router info. This should
only be used for testing purposes with a big disclaimer about loosing
dynamic configuration of the device if done this way.



Question to @jukkar or other network maintainers: What's the
preferred
setup? I know there is movement on this front but I'm not sure of
the
specifics.

- Mike

Cheers,
Jukka


Re: Enable SPI driver on nrf52840

Chettimada, Vinayak Kariappa
 

Hi,

 

The drivers are not experimental, you can use both I2C and SPI. Have you tried different instances of the peripherals?

i.e. I2C_0 and SPI_1 ?

 

If you are facing an issue, do provide details of your configuration, we will be glad to address defects, if any.

 

Regards,

Vinayak

 

From: devel@... [mailto:devel@...] On Behalf Of cpmcparland@...
Sent: Sunday, August 19, 2018 2:14 AM
To: devel@...
Subject: [Zephyr-devel] Enable SPI driver on nrf52840

 

Has anyone successfully enabled spi driver on the nordic nrf52840_pca10056?  I2c seems
to work great, but I need both for an upcoming project.  I see the drivers are
in place, but its not enabled in the board dts file.  I'm guessing its still a bit experimental; but
would like to give it a try.  Any hints would be helpful.

Cheers,
RTISYS


Breaking changes to network config settings

Paul Sokolovsky
 

Hello,

For the 1.13 release, networking configuration library ("net_conf") was
split from net_app library, because it always was independent from the
rest of net_app, and is useful even for apps which don't use net_app
(e.g. for apps using native low-level API, or BSD Sockets API). To
finish this refactor cleanly, one last step was to move related
Kconfig options from CONFIG_NET_APP_* namespace into separate
CONFIG_NET_CONFIG_* namespace.

All in-tree samples and tests were updated, but out of tree
networking applications will need to be updated separately by their
maintainers. Thanks to recent Kconfig improvements and behavior
tightening, there will be a clear-cut error message hinting about a
need to upgrade (instead of warning and incorrectly functioning
application like it could happen before).

For a reference on which Kconfig options need updates please see
commit
https://github.com/zephyrproject-rtos/zephyr/commit/028aae1ec9d5234a65ed4d4e99471fee3832ea7b

Alternatively, a shorter example of updating MicroPython Zephyr port:
https://github.com/pfalcon/micropython/commit/f27f79da52eae4e4ca2a89c70c711ef24249b3a5


--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog


Enable SPI driver on nrf52840

cpmcparland@...
 

Has anyone successfully enabled spi driver on the nordic nrf52840_pca10056?  I2c seems
to work great, but I need both for an upcoming project.  I see the drivers are
in place, but its not enabled in the board dts file.  I'm guessing its still a bit experimental; but
would like to give it a try.  Any hints would be helpful.

Cheers,
RTISYS


Zephyr IPv6 default router / prefix networking options

Michael Scott
 

Hello Devs,

I'd like to discuss some different approaches to a simple setup for BLE and iwpan 802.15.4 nodes connected to a gateway via 6lowpan (in a star pattern).  No mesh involved.

On the gateway side, I'm running a NAT64 container which picks up traffic destined for the 64:ff9b::/96 network and translates it to IPv4 before sending it out.  On the return path it gets re-translated back from IPv4 to the 64:ff9b::/96 IP and sent back to the original node that sent the data.   Paired with that I'm also running a DNS64 container on the gateway which accepts DNS queries from the connected nodes (BLE and 802.15.4 6lowpan) and if an IPv4 address would normally be returned it translates it to the 64:ff9b::/96 prefix (DNS64).

Using this setup, each node *should* have basic access to the internet even on home networks where there is no IPv6 available.

On each Zephyr node,  we currently only have a link-local address configured.

Enter the complications:

If I ask Zephyr to send a packet to a 64:ff9b::/96-based address (via the gateway IP) it gets denied because link-local addresses are not "proper" according to RFCs and the function here:
https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/ip/net_if.c#L1689

Here are some of my proposed changes to solve this:

1. First solution was to setup RADVD on the gateway to present a "proper" IPv6 network to the connected nodes.  Here we encounter initial connection failures due to the RA packets not being received prior to the application choosing to communicate via the network.  Looks like @jukkar's L4 notifications would come in handy here if we can craft the right requirements for the "UP" and "DOWN" notifications.  Also, I think that RADVD is overkill in this scenario.  We are talking about a hand full of nodes on 1 subnet w/ 1 statically configured router IP.  It will never change and if the gateway goes down, the nodes would never be connected in the first place.

2. Second solution was to add a Kconfig option to subsys/net/ip/net_if.c which would change the behavior of is_proper_ipv6_address().  In effect saying "go ahead and use the link-local address" we know what we're doing.  I'm not sure how the networking maintainers feel about that as it does contradict RFC.  Seems like a one-off fix.

3. A third solution was to add Kconfig options to subsys/net/lib/config for NET_APP_MY_IPV6_ROUTER, NET_APP_MY_IPV6_PREFIX and NET_APP_MY_IPV6_PREFIX_LEN.  These would effectively configure the nodes at boot-time as if the related RA packets had been received (no lifetime expiration). These changes might allow us to modify all of our IPv6 samples so that multiple nodes can be running at the same time.

Question to @jukkar or other network maintainers: What's the preferred setup?  I know there is movement on this front but I'm not sure of the specifics.

- Mike


Re: Flash configuration in dts file

David Leach
 

In some work that I’m doing I had to do the same thing. I haven’t posted a PR for this work so I’m not sure how the community will react but here is what I did to add the file system partition with a single slot partition:

 

 

In my DTS file I have the following:

 

&flash0 {

                /*

                * For more information, see:

                * http://docs.zephyrproject.org/devices/dts/flash_partitions.html

                */

                partitions {

                                compatible = "fixed-partitions";

                                #address-cells = <1>;

                                #size-cells = <1>;

                               

#if defined(CONFIG_FS_FLASH_STORAGE_PARTITION)

                                slot0_partition: partition@c000 {

                                                label = "image-0";

                                                reg = <0x00000000 0x7d000>;

                                };

 

                                storage_partition: partition@7a000 {

                                                label = "storage";

                                                reg = <0x0007d000 0x00003000>;

                                };

#else

                                slot0_partition: partition@c000 {

                                                label = "image-0";

                                                reg = <0x00000000 0x80000>;

                                };

#endif

                };

};

 

Then I needed to change subsys/storage/flash_map/flash_map_default.c to conditionally include partitions based on whether that partition’s SIZE define is defined:

 

 

const struct flash_area default_flash_map[] = {

#ifdef FLASH_AREA_MCUBOOT_SIZE

                /* FLASH_AREA_BOOTLOADER */

                {

                                .fa_id = 0,

                                .fa_device_id = SOC_FLASH_0_ID,

                                .fa_off = FLASH_AREA_MCUBOOT_OFFSET,

                                .fa_size = FLASH_AREA_MCUBOOT_SIZE,

                },

#endif

                /* FLASH_AREA_IMAGE_0 */

                {

                                .fa_id = 1,

                                .fa_device_id = SOC_FLASH_0_ID,

                                .fa_off = FLASH_AREA_IMAGE_0_OFFSET,

                                .fa_size = FLASH_AREA_IMAGE_0_SIZE,

                },

#ifdef FLASH_AREA_IMAGE_1_SIZE

                /* FLASH_AREA_IMAGE_1 */

                {

                                .fa_id = 2,

                                .fa_device_id = SOC_FLASH_0_ID,

                                .fa_off = FLASH_AREA_IMAGE_1_OFFSET,

                                .fa_size = FLASH_AREA_IMAGE_1_SIZE,

                },

#endif

#ifdef FLASH_AREA_IMAGE_SCRATCH_SIZE

                /* FLASH_AREA_IMAGE_SCRATCH */

                {

                                .fa_id = 3,

                                .fa_device_id = SOC_FLASH_0_ID,

                                .fa_off = FLASH_AREA_IMAGE_SCRATCH_OFFSET,

                                .fa_size = FLASH_AREA_IMAGE_SCRATCH_SIZE,

                },

#endif

#ifdef CONFIG_FS_FLASH_STORAGE_PARTITION

                /* FLASH_AREA_STORAGE */

                {

                                .fa_id = 4,

                                .fa_device_id = SOC_FLASH_0_ID,

                                .fa_off = FLASH_AREA_STORAGE_OFFSET,

                                .fa_size = FLASH_AREA_STORAGE_SIZE,

                },

#endif

};

 

 

From: devel@... <devel@...> On Behalf Of Laurence Pasteau
Sent: Friday, August 17, 2018 10:35 AM
To: zephyr-devel@...
Subject: Re: [Zephyr-devel] Flash configuration in dts file

 

The solution below is not available since I need to start the fimrware at 0x0 without bootloader.

 

So I would really appreciate if someone could help me.

I compile with a nrf52_pca10040 board.

 

Regards,

Laurence

 


De : devel@... <devel@...> de la part de Laurence Pasteau <laurence.pasteau@...>
Envoyé : vendredi 17 août 2018 16:51
À : zephyr-devel@...
Objet : [Zephyr-devel] Flash configuration in dts file

 

Hi everybody,

 

I have a question regarding dts file, and more specifically the flash partition.

I would like to have a project without bootloader, but with a partition for the code and another for the file system.

 

At compilation time I would like to be warned if the code partition is overlapping the flash partition.

 

First I tried to set CONFIG_FLASH_LOAD_SIZE. As I have no bootloader, I still need CONFIG_FLASH_LOAD_OFFSET to 0.

Unfortunately as CONFIG_HAS_DTS is set in this project, these values are not taken into account.

 

However in the script that generates the generated_dts_board files from dts, it seems that :

if CONFIG_FLASH_LOAD_OFFSET is set to 0

then

CONFIG_FLASH_LOAD_SIZE is set to 0.

 

The only successfull but not pretty solution I found was this one :

 

        boot_partition: partition@0 {
            label = "noboot";
            reg = <0x00000000 0x4>;
        };
        code_partition: partition@4 {
            label = "code-partition";
            reg = <0x00000004 0x40000>;
        };
#if defined(CONFIG_FS_FLASH_STORAGE_PARTITION)
        storage_partition: partition@40004 {
            label = "storage";
            reg = <0x00040004 0x0003FFFC>;
        };
#endif

 

Is there a better way to solve this issue ?

 

Thanks in advance,

Regards,

Laurence

 


Re: Flash configuration in dts file

Laurence Pasteau
 

The solution below is not available since I need to start the fimrware at 0x0 without bootloader.


So I would really appreciate if someone could help me.

I compile with a nrf52_pca10040 board.


Regards,

Laurence



De : devel@... <devel@...> de la part de Laurence Pasteau <laurence.pasteau@...>
Envoyé : vendredi 17 août 2018 16:51
À : zephyr-devel@...
Objet : [Zephyr-devel] Flash configuration in dts file
 

Hi everybody,


I have a question regarding dts file, and more specifically the flash partition.

I would like to have a project without bootloader, but with a partition for the code and another for the file system.


At compilation time I would like to be warned if the code partition is overlapping the flash partition.


First I tried to set CONFIG_FLASH_LOAD_SIZE. As I have no bootloader, I still need CONFIG_FLASH_LOAD_OFFSET to 0.

Unfortunately as CONFIG_HAS_DTS is set in this project, these values are not taken into account.


However in the script that generates the generated_dts_board files from dts, it seems that :

if CONFIG_FLASH_LOAD_OFFSET is set to 0

then

CONFIG_FLASH_LOAD_SIZE is set to 0.


The only successfull but not pretty solution I found was this one :


        boot_partition: partition@0 {
            label = "noboot";
            reg = <0x00000000 0x4>;
        };
        code_partition: partition@4 {
            label = "code-partition";
            reg = <0x00000004 0x40000>;
        };
#if defined(CONFIG_FS_FLASH_STORAGE_PARTITION)
        storage_partition: partition@40004 {
            label = "storage";
            reg = <0x00040004 0x0003FFFC>;
        };
#endif

Is there a better way to solve this issue ?

Thanks in advance,
Regards,
Laurence


Flash configuration in dts file

Laurence Pasteau
 

Hi everybody,


I have a question regarding dts file, and more specifically the flash partition.

I would like to have a project without bootloader, but with a partition for the code and another for the file system.


At compilation time I would like to be warned if the code partition is overlapping the flash partition.


First I tried to set CONFIG_FLASH_LOAD_SIZE. As I have no bootloader, I still need CONFIG_FLASH_LOAD_OFFSET to 0.

Unfortunately as CONFIG_HAS_DTS is set in this project, these values are not taken into account.


However in the script that generates the generated_dts_board files from dts, it seems that :

if CONFIG_FLASH_LOAD_OFFSET is set to 0

then

CONFIG_FLASH_LOAD_SIZE is set to 0.


The only successfull but not pretty solution I found was this one :


        boot_partition: partition@0 {
            label = "noboot";
            reg = <0x00000000 0x4>;
        };
        code_partition: partition@4 {
            label = "code-partition";
            reg = <0x00000004 0x40000>;
        };
#if defined(CONFIG_FS_FLASH_STORAGE_PARTITION)
        storage_partition: partition@40004 {
            label = "storage";
            reg = <0x00040004 0x0003FFFC>;
        };
#endif

Is there a better way to solve this issue ?

Thanks in advance,
Regards,
Laurence


Cpp support on Zephyr #gettingstartedguide

miem@...
 

Hi,

Does anyone tried to compile a project written in C++ or knows how powerful is Zephyr in supporting C++ applications? 

Regards,
Mina


Re: about synchronization of remote forked master, local master & local branches

vikrant8051 <vikrant8051@...>
 

Hi Li,

I tried your trick. But it was not fulfill my requirements.

Following is my way ....... It is lengthy but works !!

(PART-A)

// This is to sync forked local master (repo on PC/Laptop) with Zephyr Master

cd /home/user_name/

git clone https://github.com/developer_user_name/zephyr.git

cd zephyr

git remote add upstream https://github.com/zephyrproject-rtos/zephyr.git

git fetch upstream

git pull upstream master

// This is to sync GitHub forked master with Zephyr master

git push -f origin master

---------------------------------------------------------------------------------------------------------------------------------

(PART-B)

// This is to sync local branch with master

1)

cd /home/user_name/Desktop

git clone -b fix_branch https://github.com/developer_user_name/zephyr.git

cd zephyr

git pull --all

git checkout master

git pull

git checkout -

git rebase master

---------------------------------------------------------------------------------------------------------------------------------

OR

2)
(After following PART-A instructions)

cd /home/user_name/zephyr

git pull --all

git checkout fix_branch

git rebase master


I'm looking for even better sequence of instructions than this.

Thank You !!

On Thu, Aug 16, 2018 at 10:09 PM, Li, Jun R <jun.r.li@...> wrote:

Let’s say the PR’s number is $PR, run the follow commands:

 

  1. git pull origin master
  2. git fetch origin +refs/pull/$PR/merge
  3. git checkout FETCH_HEAD -b my_branch_with_fix

 

 

 

From: <devel@...> on behalf of vikrant8051 <vikrant8051@...>
Date: Thursday, August 16, 2018 at 05:43
To: "devel@..." <devel@...>, "users@..." <users@...>
Subject: [Zephyr-devel] about synchronization of remote forked master, local master & local branches

 

Hi,

 

Assume a person create one PR (to solve already present issues) & it take some time to get approval from reviewers.

 

Meanwhile Zephyr master get upgrad as usual.

 

Then how to properly sync

 

1) forked Zephyr master branch on GitHub

2) local master branch

3) local branch (which is actually responsible to fix issues)

 

periodically without disturbing own commits architecture?

 

Thank You !!

 



Re: about synchronization of remote forked master, local master & local branches

Yasushi SHOJI
 

Hi,

# I don't think it's a good idea to multi-post.
# make sure not to do so next time.

On Thu, Aug 16, 2018 at 9:43 PM, vikrant8051 <vikrant8051@...> wrote:
Then how to properly sync

1) forked Zephyr master branch on GitHub
$ git fetch --all
$ git pull $YOUR_REMOTE origin/master:master

2) local master branch
$ git fetch --all
$ git checkout master
$ git merge origin/master

or, if you haven't fetched.

$ git checkout master
$ git pull

or, if you are sure you don't have anything on your local master,
there are other ways:

https://stackoverflow.com/q/5471174/640650

3) local branch (which is actually responsible to fix issues)
$ git checkout $YOUR_FIX_BRANCH
$ git rebase master

and make sure to test your branch again.

periodically without disturbing own commits architecture?
If you have some modification which is not commited yet. Do

$ git stash

then

$ git checkout $WHATEVER

There is "auto stash" config if you prefer.
--
yashi


Re: about synchronization of remote forked master, local master & local branches

Li, Jun R
 

Let’s say the PR’s number is $PR, run the follow commands:

 

  1. git pull origin master
  2. git fetch origin +refs/pull/$PR/merge
  3. git checkout FETCH_HEAD -b my_branch_with_fix

 

 

 

From: <devel@...> on behalf of vikrant8051 <vikrant8051@...>
Date: Thursday, August 16, 2018 at 05:43
To: "devel@..." <devel@...>, "users@..." <users@...>
Subject: [Zephyr-devel] about synchronization of remote forked master, local master & local branches

 

Hi,

 

Assume a person create one PR (to solve already present issues) & it take some time to get approval from reviewers.

 

Meanwhile Zephyr master get upgrad as usual.

 

Then how to properly sync

 

1) forked Zephyr master branch on GitHub

2) local master branch

3) local branch (which is actually responsible to fix issues)

 

periodically without disturbing own commits architecture?

 

Thank You !!

 


about synchronization of remote forked master, local master & local branches

vikrant8051 <vikrant8051@...>
 

Hi,

Assume a person create one PR (to solve already present issues) & it take some time to get approval from reviewers.

Meanwhile Zephyr master get upgrad as usual.

Then how to properly sync

1) forked Zephyr master branch on GitHub
2) local master branch
3) local branch (which is actually responsible to fix issues)

periodically without disturbing own commits architecture?

Thank You !!


Re: Renaming the RISC-V FE310 SoC in Zephyr

Nashif, Anas
 

I do not think the FRDM in Freedom board is something Zephyr specific, this is part of the branding/product naming AFAIK. So I would not abbreviate it, SiFive Freedom is just fine.

Anas

-----Original Message-----
From: devel@... [mailto:devel@...] On Behalf Of Cufi, Carles
Sent: Wednesday, August 15, 2018 5:19 PM
To: Nathaniel Graff <nathaniel.graff@...>; zephyr-devel@...
Subject: Re: [Zephyr-devel] Renaming the RISC-V FE310 SoC in Zephyr

Hi Nate,

No objections, I only want to point out that we already abbreviate "Freedom" as "frdm" in the NXP Freedom board series, for example:

https://github.com/zephyrproject-rtos/zephyr/tree/master/boards/arm/frdm_k64f

So I wonder if we should consider "sifive_frdm" as the folder name.

Regards,

Carles

On 15/08/2018, 22:47, "devel@... on behalf of Nathaniel Graff" <devel@... on behalf of nathaniel.graff@...> wrote:

Hi Zephyr Developers,

At the moment, Zephyr support for SiFive’s Freedom line of SoCs is named FE310. Since the FE310 is just one of our products which is compatible with this port, we’d like to change the name of the SoC in Zephyr.

We’re proposing renaming the “FE310” SoC to "SiFive Freedom”.

If there are any concerns about this particular choice, let me know, otherwise I’ll submit a PR and we can hash out the minutiae there.

Thanks,
Nate Graff


Re: Renaming the RISC-V FE310 SoC in Zephyr

Carles Cufi
 

Hi Nate,

No objections, I only want to point out that we already abbreviate "Freedom" as "frdm" in the NXP Freedom board series, for example:

https://github.com/zephyrproject-rtos/zephyr/tree/master/boards/arm/frdm_k64f

So I wonder if we should consider "sifive_frdm" as the folder name.

Regards,

Carles

On 15/08/2018, 22:47, "devel@... on behalf of Nathaniel Graff" <devel@... on behalf of nathaniel.graff@...> wrote:

Hi Zephyr Developers,

At the moment, Zephyr support for SiFive’s Freedom line of SoCs is named FE310. Since the FE310 is just one of our products which is compatible with this port, we’d like to change the name of the SoC in Zephyr.

We’re proposing renaming the “FE310” SoC to "SiFive Freedom”.

If there are any concerns about this particular choice, let me know, otherwise I’ll submit a PR and we can hash out the minutiae there.

Thanks,
Nate Graff


Renaming the RISC-V FE310 SoC in Zephyr

Nathaniel Graff
 

Hi Zephyr Developers,

At the moment, Zephyr support for SiFive’s Freedom line of SoCs is named FE310. Since the FE310 is just one of our products which is compatible with this port, we’d like to change the name of the SoC in Zephyr.

We’re proposing renaming the “FE310” SoC to "SiFive Freedom”.

If there are any concerns about this particular choice, let me know, otherwise I’ll submit a PR and we can hash out the minutiae there.

Thanks,
Nate Graff


Re: Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

Carles Cufi
 

Hi Kai,

 

Thanks for confirming this solves the issue.

Note that the installation path does *not* need to be called “gnuarmemb” since Zephyr simply uses the location set in GNUARMEMB_TOOLCHAIN_PATH. That said, using paths with spaces might break the scripts so c:\gnuarmemb makes a lot of sense.

 

Thanks,

 

Carles

 

From: Kai Ren <kren@...>
Date: Wednesday, 15 August 2018 at 15:57
To: "Cufi, Carles" <Carles.Cufi@...>, "zephyr-devel@..." <zephyr-devel@...>
Cc: vikrant8051 <vikrant8051@...>, Johan Hedberg <johan.hedberg@...>
Subject: RE: Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

 

Hello Carles,

 

This sample is just created by myself, I git clone from my private repo, not Zephyr public repo.

 

Just solved this problem that:

·         Install gnu arm embedded to c:\gnuarmemb

·         set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb

·         set GNUARMEMB_TOOLCHAIN_PATH=c:\gnuarmemb

·         switch the source code to latest commit.

 

Thanks for the help!

 

Regards,

Kai

 

From: Cufi, Carles <Carles.Cufi@...>
Sent: Wednesday, August 15, 2018 5:12 PM
To: Kai Ren <kren@...>; zephyr-devel@...
Cc: vikrant8051 <vikrant8051@...>; Johan Hedberg <johan.hedberg@...>
Subject: RE: Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

 

Hi Kai,

 

I don’t think that sample exists: samples/microbit/generic_onoff_svr.

Maybe you have updated your Zephyr tree and that sample has been moved or renamed? Unless of course this is your own sample that is not part of Zephyr.

 

Furthermore, please follow the instructions in this email to switch to the new naming conventions for GNU Arm Embedded:

https://lists.zephyrproject.org/g/users/topic/gcc_arm_embedded_is_now_gnu/24238396

 

I just tested building the hello_world  and bluetooth/mesh_demo samples for bbc_microbit on Windows 10 with the latest master had no issues.

 

Regards,

 

Carles

 

 

 

From: devel@... <devel@...> On Behalf Of Kai Ren
Sent: 15 August 2018 10:40
To: zephyr-devel@...
Subject: [Zephyr-devel] Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

 

Hello,

I had set the dev environment up on my Windows computer by “Option 1: Windows Command Prompt”, but suddenly, it can NOT work, below is the error log, when I type cmake -GNinja -DBOARD=bbc_microbit .. , there are some errors, how can I solve this problem?

 

 

C:\Users\xxxxxx\zephyr\samples\microbit\generic_onoff_svr\build>cmake -GNinja -DBOARD=bbc_microbit ..

CMake Deprecation Warning at C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):

  The OLD behavior for policy CMP0000 will be removed from a future version

  of CMake.

 

  The cmake-policies(7) manual explains that the OLD behaviors of all

  policies are deprecated and that a policy should be set to OLD only under

  specific short-term circumstances.  Projects should be ported to the NEW

  behavior and not rely on setting a policy to OLD.

Call Stack (most recent call first):

  CMakeLists.txt:3 (include)

 

 

-- Found PythonInterp: C:/Python37/python.exe (found suitable version "3.7", minimum required is "3.4")

-- Selected BOARD bbc_microbit

Zephyr version: 1.12.0

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:33: warning: BT (defined at subsys/bluetooth/Kconfig:10) set more than once. Old value: "y", new value: "y".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:46: warning: BT_CTLR_LE_PING (defined at subsys/bluetooth/controller/Kconfig:150) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:47: warning: BT_CTLR_DATA_LENGTH (defined at subsys/bluetooth/controller/Kconfig:182) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:48: warning: BT_CTLR_PHY (defined at subsys/bluetooth/controller/Kconfig:199) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:49: warning: BT_CTLR_CHAN_SEL_2 (defined at subsys/bluetooth/controller/Kconfig:208) set more than once. Old value: "n"Parsing Kconfig tree in C:/Users/xxxxxx/zephyr//Kconfig

Using C:/Users/xxxxxx/zephyr/boards/arm/bbc_microbit/bbc_microbit_defconfig as base

Merging C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf

, new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:50: warning: BT_CTLR_MIN_USED_CHAN (defined at subsys/bluetooth/controller/Kconfig:215) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:51: warning: BT_CTLR_ADV_EXT (defined at subsys/bluetooth/controller/Kconfig:222) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:52: warning: BT_CTLR_PRIVACY (defined at subsys/bluetooth/controller/Kconfig:156) set more than once. Old value: "n", new value: "n".

warning: MICROBIT_DISPLAY (defined at drivers/display/Kconfig.microbit:9) was assigned the value "y" but got the value "n" -- check dependencies

warning: BT_L2CAP_RX_MTU (defined at subsys/bluetooth/host/Kconfig:163) was assigned the value "69" but got the value "" -- check dependencies

warning: BT_CTLR_LE_ENC (defined at subsys/bluetooth/controller/Kconfig:136) was assigned the value "n" but got the value "y" -- check dependencies

warning: BT_CTLR_DATA_LENGTH_MAX (defined at subsys/bluetooth/controller/Kconfig:189) was assigned the value "27" but got the value "" -- check dependencies

CMake Error at C:/Users/xxxxxx/zephyr/cmake/toolchain.cmake:35 (include):

  include could not find load file:

 

    C:/Users/xxxxxx/zephyr//cmake/toolchain/gnuarmemb.cmake

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:242 (include)

  CMakeLists.txt:3 (include)

 

 

CMake Error at C:/Users/xxxxxx/zephyr/cmake/toolchain.cmake:53 (file):

  file MD5 requires a file name and output variable

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:242 (include)

  CMakeLists.txt:3 (include)

 

 

fatal: No names found, cannot describe anything.

-- Generating zephyr/include/generated/generated_dts_board.h

CMake Error at C:/Users/xxxxxx/zephyr/cmake/dts.cmake:69 (message):

  command failed with return code: The system cannot find the file specified

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:268 (include)

  CMakeLists.txt:3 (include)

 

 

-- Configuring incomplete, errors occurred!

 

 

Regards,

Kai

 


Re: Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

Kai Ren
 

Hello Carles,

 

This sample is just created by myself, I git clone from my private repo, not Zephyr public repo.

 

Just solved this problem that:

  • Install gnu arm embedded to c:\gnuarmemb

·        set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb

·        set GNUARMEMB_TOOLCHAIN_PATH=c:\gnuarmemb

  • switch the source code to latest commit.

 

Thanks for the help!

 

Regards,

Kai

 

From: Cufi, Carles <Carles.Cufi@...>
Sent: Wednesday, August 15, 2018 5:12 PM
To: Kai Ren <kren@...>; zephyr-devel@...
Cc: vikrant8051 <vikrant8051@...>; Johan Hedberg <johan.hedberg@...>
Subject: RE: Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

 

Hi Kai,

 

I don’t think that sample exists: samples/microbit/generic_onoff_svr.

Maybe you have updated your Zephyr tree and that sample has been moved or renamed? Unless of course this is your own sample that is not part of Zephyr.

 

Furthermore, please follow the instructions in this email to switch to the new naming conventions for GNU Arm Embedded:

https://lists.zephyrproject.org/g/users/topic/gcc_arm_embedded_is_now_gnu/24238396

 

I just tested building the hello_world  and bluetooth/mesh_demo samples for bbc_microbit on Windows 10 with the latest master had no issues.

 

Regards,

 

Carles

 

 

 

From: devel@... <devel@...> On Behalf Of Kai Ren
Sent: 15 August 2018 10:40
To: zephyr-devel@...
Subject: [Zephyr-devel] Can't perform "cmake -GNinja -DBOARD=bbc_microbit .."

 

Hello,

I had set the dev environment up on my Windows computer by “Option 1: Windows Command Prompt”, but suddenly, it can NOT work, below is the error log, when I type cmake -GNinja -DBOARD=bbc_microbit .. , there are some errors, how can I solve this problem?

 

 

C:\Users\xxxxxx\zephyr\samples\microbit\generic_onoff_svr\build>cmake -GNinja -DBOARD=bbc_microbit ..

CMake Deprecation Warning at C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:38 (cmake_policy):

  The OLD behavior for policy CMP0000 will be removed from a future version

  of CMake.

 

  The cmake-policies(7) manual explains that the OLD behaviors of all

  policies are deprecated and that a policy should be set to OLD only under

  specific short-term circumstances.  Projects should be ported to the NEW

  behavior and not rely on setting a policy to OLD.

Call Stack (most recent call first):

  CMakeLists.txt:3 (include)

 

 

-- Found PythonInterp: C:/Python37/python.exe (found suitable version "3.7", minimum required is "3.4")

-- Selected BOARD bbc_microbit

Zephyr version: 1.12.0

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:33: warning: BT (defined at subsys/bluetooth/Kconfig:10) set more than once. Old value: "y", new value: "y".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:46: warning: BT_CTLR_LE_PING (defined at subsys/bluetooth/controller/Kconfig:150) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:47: warning: BT_CTLR_DATA_LENGTH (defined at subsys/bluetooth/controller/Kconfig:182) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:48: warning: BT_CTLR_PHY (defined at subsys/bluetooth/controller/Kconfig:199) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:49: warning: BT_CTLR_CHAN_SEL_2 (defined at subsys/bluetooth/controller/Kconfig:208) set more than once. Old value: "n"Parsing Kconfig tree in C:/Users/xxxxxx/zephyr//Kconfig

Using C:/Users/xxxxxx/zephyr/boards/arm/bbc_microbit/bbc_microbit_defconfig as base

Merging C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf

, new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:50: warning: BT_CTLR_MIN_USED_CHAN (defined at subsys/bluetooth/controller/Kconfig:215) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:51: warning: BT_CTLR_ADV_EXT (defined at subsys/bluetooth/controller/Kconfig:222) set more than once. Old value: "n", new value: "n".

C:/Users/xxxxxx/zephyr/samples/microbit/generic_onoff_svr/prj_bbc_microbit.conf:52: warning: BT_CTLR_PRIVACY (defined at subsys/bluetooth/controller/Kconfig:156) set more than once. Old value: "n", new value: "n".

warning: MICROBIT_DISPLAY (defined at drivers/display/Kconfig.microbit:9) was assigned the value "y" but got the value "n" -- check dependencies

warning: BT_L2CAP_RX_MTU (defined at subsys/bluetooth/host/Kconfig:163) was assigned the value "69" but got the value "" -- check dependencies

warning: BT_CTLR_LE_ENC (defined at subsys/bluetooth/controller/Kconfig:136) was assigned the value "n" but got the value "y" -- check dependencies

warning: BT_CTLR_DATA_LENGTH_MAX (defined at subsys/bluetooth/controller/Kconfig:189) was assigned the value "27" but got the value "" -- check dependencies

CMake Error at C:/Users/xxxxxx/zephyr/cmake/toolchain.cmake:35 (include):

  include could not find load file:

 

    C:/Users/xxxxxx/zephyr//cmake/toolchain/gnuarmemb.cmake

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:242 (include)

  CMakeLists.txt:3 (include)

 

 

CMake Error at C:/Users/xxxxxx/zephyr/cmake/toolchain.cmake:53 (file):

  file MD5 requires a file name and output variable

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:242 (include)

  CMakeLists.txt:3 (include)

 

 

fatal: No names found, cannot describe anything.

-- Generating zephyr/include/generated/generated_dts_board.h

CMake Error at C:/Users/xxxxxx/zephyr/cmake/dts.cmake:69 (message):

  command failed with return code: The system cannot find the file specified

Call Stack (most recent call first):

  C:/Users/xxxxxx/zephyr/cmake/app/boilerplate.cmake:268 (include)

  CMakeLists.txt:3 (include)

 

 

-- Configuring incomplete, errors occurred!

 

 

Regards,

Kai

 


Breaking change to app build scripts

Sebastian Boe
 

Hi all,

to silence the 'policy CMP000' warning[0] we have decided to
require that all 'app' CMakeLists.txt build scripts invoke the
function 'cmake_minimum_required'.

This requirement is a breaking change, not updating will result
in an error[1]. To resolve the error this line must
be added to the top of the 'app' CMakeLists.txt file:

cmake_minimum_required(VERSION 3.8.2)

E.g. to update the 'hello_world' sample one could execute:

sed -i '1s;^;cmake_minimum_required(VERSION 3.8.2)\n;' $ZEPHYR_BASE/samples/hello_world/CMakeLists.txt

See PR https://github.com/zephyrproject-rtos/zephyr/pull/9186 for more details.

[0] The warning shown when cmake >= 3.9 is used.
CMake Deprecation Warning at boilerplate.cmake:38 (cmake_policy):
The OLD behavior for policy CMP0000 will be removed from a future version
of CMake.

The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
CMakeLists.txt:2 (include)

[1] The error shown if no 'cmake_minimum_required' line is present.
CMake Error in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as

cmake_minimum_required(VERSION 3.12)

should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".

3621 - 3640 of 8579