Date   

New HTTP Library Issue

Michael Scott
 

Hello Jukka / Paul,

We are using the legacy HTTP API's current and include a "Content-Length:" header field to denote the amount of data in the payload.

The new API is completely broken when including the Content-Length header field, as the payload is sent in a chunked format which prepends the byte count to each "chunk".  This means that the user's Content-Length value is now invalid.

I'm not really sure how to solve this issue in the new API.. I don't think we should be changing the payload of the message w/o the user opting in or knowing about it.

I can get our code running on the new API if I comment out the chunked insertion logic and apply the HTTP lib payload patch here: https://github.com/zephyrproject-rtos/zephyr/pull/4882

- Mike


Re: CMake migration complete

Carles Cufi
 

Hi Kumar, Anas,

Yes, conf is now part of the SDK on Linux. That said, and since bundling an SDK for macOS and Windows is tricky, our current plan is to switch to Python for Kconfig.

Regards,

Carles

-----Original Message-----
From: Nashif, Anas [mailto:anas.nashif@intel.com]
Sent: 09 November 2017 15:12
To: Kumar Gala <kumar.gala@linaro.org>; Cufi, Carles
<Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-
devel@lists.zephyrproject.org
Subject: RE: [Zephyr-devel] CMake migration complete

Conf is coming from SDK now (on Linux)

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-
bounces@lists.zephyrproject.org] On Behalf Of Kumar Gala
Sent: Thursday, November 9, 2017 9:09 AM
To: Cufi, Carles <Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-
devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Curious why on OS-X we need conf build before hand instead of doing what
we do on linux?

Or are we getting conf from the SDK on linux?

- k
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: CMake migration complete

Nashif, Anas
 

Conf is coming from SDK now (on Linux)

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Kumar Gala
Sent: Thursday, November 9, 2017 9:09 AM
To: Cufi, Carles <Carles.Cufi@nordicsemi.no>
Cc: zephyr-users@lists.zephyrproject.org; zephyr-devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Curious why on OS-X we need conf build before hand instead of doing what we do on linux?

Or are we getting conf from the SDK on linux?

- k
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: CMake migration complete

Kumar Gala
 

Curious why on OS-X we need conf build before hand instead of doing what we do on linux?

Or are we getting conf from the SDK on linux?

- k


Re: CMake migration complete

Carles Cufi
 

Hi Erwin,

-----Original Message-----
From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-
bounces@lists.zephyrproject.org] On Behalf Of Erwin Rol
Sent: 09 November 2017 10:56
To: Bøe, Sebastian <Sebastian.Boe@nordicsemi.no>; zephyr-
devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] CMake migration complete

Well that kind of sucks, cause the on Redhat 7.X the newest cmake is
3.6.x.

Will the needed cmake be part of the toolchain ?
No, but it's quite simple to install a recent version of CMake manually:

http://docs.zephyrproject.org/getting_started/installation_linux.html#installing-requirements-and-dependencies

$ mkdir $HOME/work_dir && cd $HOME/work_dir
$ wget https://cmake.org/files/v3.8/cmake-3.8.2-Linux-x86_64.sh
$ yes | sh cmake-3.8.2-Linux-x86_64.sh | cat
$ echo "export PATH=$PWD/cmake-3.8.2-Linux-x86_64/bin:\$PATH" >> $HOME/.zephyrrc
$ bash
$ cmake --version

Regards,

Carles



- Erwin


On Thu, 2017-11-09 at 08:57 +0000, Bøe, Sebastian wrote:
PS: Correction; install cmake 3.8.2 or later.
From: Bøe, Sebastian
Sent: Thursday, 9 November 2017 9:42:27 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrpr
oject.org
Subject: CMake migration complete

Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: CMake migration complete

Erwin Rol
 

Well that kind of sucks, cause the on Redhat 7.X the newest cmake is
3.6.x.

Will the needed cmake be part of the toolchain ?

- Erwin

On Thu, 2017-11-09 at 08:57 +0000, Bøe, Sebastian wrote:
PS: Correction; install cmake 3.8.2 or later.
From: Bøe, Sebastian
Sent: Thursday, 9 November 2017 9:42:27 AM
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrpr
oject.org
Subject: CMake migration complete
 
Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions
have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no
porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692
_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: CMake migration complete

Sebastian Boe
 

PS: Correction; install cmake 3.8.2 or later.


From: Bøe, Sebastian
Sent: Thursday, 9 November 2017 9:42:27 AM
To: zephyr-devel@...; zephyr-users@...
Subject: CMake migration complete
 

Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692


CMake migration complete

Sebastian Boe
 

Hi all,

Zephyr has finally migrated to CMake.

This migration is an important step in a larger effort to make Zephyr
easy to use for application developers working on different platforms
with different development environment needs.

Simplified, this change retains Kconfig as-is, and replaces all
Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild
offers is replaced by a set of CMake extentions. These extentions have
either provided simple one-to-one translations of KBuild features or
introduced new concepts that replace KBuild concepts.

This is a breaking change for existing test infrastructure and build
scripts that are maintained out-of-tree. But for FW itself, no porting
should be necessary.

For users that just want to continue their work with minimal
disruption the following should suffice:

Install CMake 3.8.2 exactly

Port any out-of-tree Makefiles to CMake.

Learn the absolute minimum about the new command line interface:

# To do a clean build;

$ cd samples/hello_world
$ mkdir build && cd build
$ cmake -DBOARD=nrf52_pca10040 ..

# For incremental builds;

$ cd build
$ make

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4692


RFC for: "BSD Sockets API: Offloading support"

Gil Pitney
 

See PR #4821 , and related links (if so interested ;).

This is an RFC for a solution to offload WiFi communication for SoC's (like TI CC3220SF)
which support a WiFi coprocessor and provide full TCP/IP stack offload at the BSD socket
API level.

This socket framework would fit most IoT use cases for TI SimpleLink customers
who need to get sensor/actuator data communicated over WiFi,
and it can become more valuable as Zephyr applications and protocols are
are written to the socket interface.

However, there's more work to better integrate with Zephyr networking services.

Would there be any interest in pursuing this framework?

If not, are there any better ideas to *efficiently* offload socket-based networking apps
to such vendors' *socket-based* TCP/IP offload engines?

Best Regards,
- Gil


Are we nearing a 1.10 code freeze or what?

Paul Sokolovsky
 

Hello,

Taking a hints from IRC and code review comments, it seems that there's
subj. Can we have an official reminder posted please?


P.S.
I think I didn't receive any TSC meeting notes in a while either (I
used to).

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


How to enable Bluetooth on FRDM_K64F + FRDM_KW41Z

Priyanka Rawat <priyanka.rawat@...>
 

Hello 


I am testing FRDM_KW41Z as BLE controller with FRDM_K64F board as BLE host. 

flash hci_blackbox firmware on KW41Z and 
I flash zephyr sample peripheral_hr on K64F 

I get the following on console 

Bluetooth init failed (err -5) 

Anyone has any idea how to resolve this issue?

Should I switch the UART in KW41Z code? Any changes in pinmux? 
Should I change CONFIG_BLUETOOTH_UART_ON_DEV_NAME in drivers/bluetooth/hci/h4.c ?

Thanks
Priyanka



Re: Adding support for the Arduino Zero / SAMD21

Michael Hope
 



On 6 November 2017 at 16:07, Kumar Gala <kumar.gala@...> wrote:

> On Nov 4, 2017, at 5:49 PM, Michael Hope <michaelh@...> wrote:
>
> Hi there.  I'm working on adding support for the Cortex-M0+ based SAMD21G18A used in the Arduino Zero, MKR1000, and other boards like the Adafruit Feather M0 series.
>
> I'm pretty happy with it so far - there's watchdog, GPIO, and good enough UART support that I can set up a SLIP connection and ping the board.
>
> Would you be interested in merging the port?  I'm a bit new to git but I've tried to structure it as one-commit-per-feature at https://github.com/nzmichaelh/zephyr/commits/arduino_zero.  If it looks roughly good then I'll send a pull request.

Always happy to take code if you are up to helping maintain it.

What you have on GitHub looks pretty good w/regards to submitting a PR.  I’d cleanup the 'net: fix the build rules for drivers/net’ and revert.  Otherwise looks like a reasonable state to start review feedback

Cool, PR sent!

-- Michael


Migrating to cmake

Nashif, Anas
 

Hi,

In case you have not been following discussions here and pull requests on Github, a pull request is currently under review which removes Kbuild and introduced CMake. This is a very close to be merged, pending additional reviews. Please take the time to review it and test it. This is the result of at least 6 months of work and we think it is ready to be merged now. The PR is

 

https://github.com/zephyrproject-rtos/zephyr/pull/4692

 

 

So to avoid surprises when this gets merged, please take a look ASAP and speak now before it is too late J

 

There will be another email about this transition once CMake goes into master.

 

Thanks,

Anas

 


Data Management

Tamra Oyama <tamrako@...>
 

Hello Zephyr Community,

How do I write data directly to my host computer without using Bluetooth or wifi while my application is running on my board? Any advice is appreciated!

Thank you,
Tamra


Re: Adding support for the Arduino Zero / SAMD21

Kumar Gala
 

On Nov 4, 2017, at 5:49 PM, Michael Hope <michaelh@juju.nz> wrote:

Hi there. I'm working on adding support for the Cortex-M0+ based SAMD21G18A used in the Arduino Zero, MKR1000, and other boards like the Adafruit Feather M0 series.

I'm pretty happy with it so far - there's watchdog, GPIO, and good enough UART support that I can set up a SLIP connection and ping the board.

Would you be interested in merging the port? I'm a bit new to git but I've tried to structure it as one-commit-per-feature at https://github.com/nzmichaelh/zephyr/commits/arduino_zero. If it looks roughly good then I'll send a pull request.
Always happy to take code if you are up to helping maintain it.

What you have on GitHub looks pretty good w/regards to submitting a PR. I’d cleanup the 'net: fix the build rules for drivers/net’ and revert. Otherwise looks like a reasonable state to start review feedback

- k


Adding support for the Arduino Zero / SAMD21

Michael Hope
 

Hi there.  I'm working on adding support for the Cortex-M0+ based SAMD21G18A used in the Arduino Zero, MKR1000, and other boards like the Adafruit Feather M0 series.

I'm pretty happy with it so far - there's watchdog, GPIO, and good enough UART support that I can set up a SLIP connection and ping the board.

Would you be interested in merging the port?  I'm a bit new to git but I've tried to structure it as one-commit-per-feature at https://github.com/nzmichaelh/zephyr/commits/arduino_zero.  If it looks roughly good then I'll send a pull request.

Thank you,

-- Michael


Re: bluetooth: mesh: Multi-element node - get-composition status

Steve Brown
 

Hi Johan,

On Wed, 2017-11-01 at 16:57 +0200, Johan Hedberg wrote:
Hi Steve,

On Wed, Nov 01, 2017, Steve Brown wrote:
I got a little further after registering the config model only
once. I
also had to jack up the L2CAP_TX_BUF_COUNT as all the segments are
queued up before they are transmitted.

I have a primary and 2 secondary elements. The onoff server model
(1000) is registered to all three. I receive the onoff msg on 0101,
but
find_op fetches the model from 0102 instead. This looks like the
same
issue I had with double registering of the config model.

Messages to the primary element don't have this problem.
This is purely guess-work since I haven't seen your code, but is it
possible you have the same model instance registered on two elements?
You can only give a model array once to a BT_MESH_ELEM() macro since
the
structs created using BT_MESH_MODEL() represent single instances of a
model on a single element. So if you want two instances the same
model,
each on its own element, you need two independent model arrays (one
for
each BT_MESH_ELEM macro).

Johan
That was the problem. I have the onoff server running successfully on
all 4 elements.

Thanks for your patience,

Steve


Re: bluetooth: mesh: Multi-element node - get-composition status

Johan Hedberg
 

Hi Steve,

On Wed, Nov 01, 2017, Steve Brown wrote:
I got a little further after registering the config model only once. I
also had to jack up the L2CAP_TX_BUF_COUNT as all the segments are
queued up before they are transmitted.

I have a primary and 2 secondary elements. The onoff server model
(1000) is registered to all three. I receive the onoff msg on 0101, but
find_op fetches the model from 0102 instead. This looks like the same
issue I had with double registering of the config model.

Messages to the primary element don't have this problem.
This is purely guess-work since I haven't seen your code, but is it
possible you have the same model instance registered on two elements?
You can only give a model array once to a BT_MESH_ELEM() macro since the
structs created using BT_MESH_MODEL() represent single instances of a
model on a single element. So if you want two instances the same model,
each on its own element, you need two independent model arrays (one for
each BT_MESH_ELEM macro).

Johan


Re: bluetooth: mesh: Multi-element node - get-composition status

Steve Brown
 

Hi Johan,

On Tue, 2017-10-31 at 20:07 +0200, Johan Hedberg wrote:
Hi Steve,

On Tue, Oct 31, 2017, Johan Hedberg wrote:
On Tue, Oct 31, 2017, Steve Brown wrote:
I have a node with 2 elements. The get-composition msg is sent to
the
primary element (0100), but the return status msg is sent from
the
secondary element (0101).

Is this expected behavior?
No, it's not. The response should be from the same element that
handled
it (which in the case of the Configuration Server Model is always
the
primary element).
You're not by chance registering the configuration model on both
elements? According to the specification (section 4.4.1.1) it's only
supposed to exist on the primary element, and I think putting it on
others may confuse some parts of the stack.

Johan
I got a little further after registering the config model only once. I
also had to jack up the L2CAP_TX_BUF_COUNT as all the segments are
queued up before they are transmitted.

I have a primary and 2 secondary elements. The onoff server model
(1000) is registered to all three. I receive the onoff msg on 0101, but
find_op fetches the model from 0102 instead. This looks like the same
issue I had with double registering of the config model.

Messages to the primary element don't have this problem.

Below is a debug snippet of both. I'm not sure where to start looking.

Steve

Message to first secondary element
[bt] [DBG] filter_add: (0x20001ad8) addr 0x77
[bt] [DBG] bt_mesh_trans_recv: (0x20001ad8) src 0x0077 dst 0x0101 seq 0x00000009
[bt] [DBG] bt_mesh_trans_recv: (0x20001ad8) Payload 5fa67131f044f23761
[bt] [DBG] trans_unseg: (0x20001ad8) AFK 1 AID 0x1f
[bt] [DBG] sdu_recv: (0x20001ad8) MIC_SIZE 4 ASZMIC 0 AKF 1 AID 0x1f
[bt] [DBG] sdu_recv: (0x20001ad8) len 8: a67131f044f23761
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) EncData (len 4) a67131f0
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) AppKey 2aa2a6ded5a0798ceab5787ca3ae39fc
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) Nonce 01000000090077010100000005
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) app_idx 0x0001 src 0x0077 dst 0x0101
^^^^^^
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) len 4: 82020101
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) OpCode 0x00008202
[bt] [DBG] find_op: (0x20001ad8) model_count:3 i:0 app_idx:0x0001 model:0x200064e4 src:0x0102
^^^^^^
[bt] [DBG] gen_onoff_set: (0x20001ad8)
[bt] [DBG] gen_onoff_set_unack: (0x20001ad8) elem: 0x02 state: 0x01 trans_id: 0x01
[bt] [DBG] gen_onoff_get: (0x20001ad8)
[bt] [DBG] bt_mesh_model_send: (0x20001ad8) net_idx 0x0000 app_idx 0x0001 dst 0x0077
[bt] [DBG] bt_mesh_model_send: (0x20001ad8) len 3: 820401
[bt] [DBG] bt_mesh_trans_send: (0x20001ad8) net_idx 0x0000 app_idx 0x0001 dst 0x0077
[bt] [DBG] bt_mesh_trans_send: (0x20001ad8) len 3: 820401


Message to primary element
[bt] [DBG] bt_mesh_trans_recv: (0x20001ad8) src 0x0077 dst 0x0100 seq 0x0000000b
[bt] [DBG] bt_mesh_trans_recv: (0x20001ad8) Payload 5f03df10f8a4e89abc
[bt] [DBG] trans_unseg: (0x20001ad8) AFK 1 AID 0x1f
[bt] [DBG] sdu_recv: (0x20001ad8) MIC_SIZE 4 ASZMIC 0 AKF 1 AID 0x1f
[bt] [DBG] sdu_recv: (0x20001ad8) len 8: 03df10f8a4e89abc
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) EncData (len 4) 03df10f8
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) AppKey 2aa2a6ded5a0798ceab5787ca3ae39fc
[bt] [DBG] bt_mesh_app_decrypt: (0x20001ad8) Nonce 010000000b0077010000000005
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) app_idx 0x0001 src 0x0077 dst 0x0100
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) len 4: 82020003
[bt] [DBG] bt_mesh_model_recv: (0x20001ad8) OpCode 0x00008202
[bt] [DBG] find_op: (0x20001ad8) model_count:5 i:0 app_idx:0x0001 model:0x20006458 src:0x0100
[bt] [DBG] find_op: (0x20001ad8) model_count:5 i:1 app_idx:0x0001 model:0x20006474 src:0x0100
[bt] [DBG] find_op: (0x20001ad8) model_count:5 i:2 app_idx:0x0001 model:0x20006490 src:0x0100
[bt] [DBG] gen_onoff_set: (0x20001ad8)
[bt] [DBG] gen_onoff_set_unack: (0x20001ad8) elem: 0x00 state: 0x00 trans_id: 0x03
[bt] [DBG] gen_onoff_get: (0x20001ad8)


Re: Kconfig like menu in out of tree app

Sebastian Boe
 

"Is there a special reason why it is APPLICATION_BASE and not
PROJECT_BASE ?"


I don't know, I have been confused about that myself, I suspect you could

s/APPLICATION_BASE/PROJECT_BASE/


Great that you got it working!


From: Erwin Rol <mailinglists@...>
Sent: Wednesday, 1 November 2017 12:34:09 PM
To: Bøe, Sebastian; Zephyr Devel List
Subject: Re: [Zephyr-devel] Kconfig like menu in out of tree app
 
Hey Sebastian,

Thanks for the hint, now I got it working after a bit of tuning.

I do have a question;

the test Kconfig has the following code

config ZEPHYR_BASE
        string
        option env="ZEPHYR_BASE"

config APPLICATION_BASE
        string
        option env="PROJECT_BASE"

Is there a special reason why it is APPLICATION_BASE and not
PROJECT_BASE ?


The "tuning" I did was in the Makefile;

KBUILD_KCONFIG = $(CURDIR)/Kconfig
export KBUILD_KCONFIG

without that change it just presents the normal Zephyr menu, with it it
uses my application menu.

and in Kconfig;

source "$APPLICATION_BASE/src/Kconfig"

Because without it it doesn't find my Kconfig in the src/ dir.

simply source "src/Kconfig" doesn't work, interestingly it does not
give any errors, just the menu is missing.

- Erwin


On Wed, 2017-11-01 at 10:48 +0000, Bøe, Sebastian wrote:
> Hi,
>
> "But the Kconfig in ~erwin/zephyr/ is the root of the menuconfig
> tree, and that knows nothing about my application in ~erwin/app/"
>
> This is what KBUILD_KCONFIG is for, as you seem to have noticed,
> it changes what the root KConfig file will be.
>
> "I tried to play with KBUILD_KCONFIG env variable but couldn't get it
> to
> work. "
>
> Have a look at how tests/benchmarks/object_footprint uses
> KBUILD_KCONFIG to change the root
> KConfig, I verified that it works as intended. Of course, it might be
> that using KBUILD_KCONFIG
> out-of-tree is broken, if so I would report a bug.
>
> From: zephyr-devel-bounces@... <zephyr-devel-boun
> ces@...> on behalf of Erwin Rol <mailinglists@erw
> inrol.com>
> Sent: Wednesday, 1 November 2017 10:45:44 AM
> To: Zephyr Devel List
> Subject: [Zephyr-devel] Kconfig like menu in out of tree app
>  
> Hello all,
>
> is there a way to add menuconfig entries from outside the Zephyr
> source
> tree? 
>
> For example having zephyr in  ~erwin/zephyr/  and an application in
> ~erwin/app/. Compiling and configuring zephyr works fine, but I would
> like to add configuration options to my app and use menuconfig for
> that. But the Kconfig in ~erwin/zephyr/ is the root of the menuconfig
> tree, and that knows nothing about my application in ~erwin/app/
>
> I tried to play with KBUILD_KCONFIG env variable but couldn't get it
> to
> work. 
>
> Any ideas on how to do this ?
>
> TIA,
>
> Erwin
>
> _______________________________________________
> Zephyr-devel mailing list
> Zephyr-devel@...
> https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel

4601 - 4620 of 8204