Date   

Re: k_poll usage

Vakul Garg <vakul.garg@...>
 

Hi Paul

Thanks for the reply. It seems quite restrictive that most of zephyr IPC does not support k_poll. How applications can simultaneously poll on fifo, mailbox?

Any reason why kernel kept limited usage for k_poll?

Vakul


From: Paul Sokolovsky <paul.sokolovsky@...>
Sent: Tuesday, October 17, 2017 3:41:51 PM
To: Vakul Garg
Cc: zephyr-users@...
Subject: Re: [Zephyr-users] k_poll usage
 
Hello Vakul,

On Fri, 13 Oct 2017 05:48:22 +0000
Vakul Garg <vakul.garg@...> wrote:

> Hi
>
> The zephyr documentation says k_poll to operate on objects - kernel
> fifo, poll signal, semaphore. Can't it also be used on mailboxes,
> message queues etc?

Looking at the include/kernel.h, all k_poll'able object must have
a .poll_events member (either directly or via _POLL_EVENT macro).
Mailboxes and message queues don't have it. This can be confirmed by
looking at kernel/poll.c:register_event(), which handles each of the
supported pollable objects via a switch statement.

>
> Regards
>
> Vakul



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


Re: k_poll usage

Paul Sokolovsky
 

Hello Vakul,

On Fri, 13 Oct 2017 05:48:22 +0000
Vakul Garg <vakul.garg@nxp.com> wrote:

Hi

The zephyr documentation says k_poll to operate on objects - kernel
fifo, poll signal, semaphore. Can't it also be used on mailboxes,
message queues etc?
Looking at the include/kernel.h, all k_poll'able object must have
a .poll_events member (either directly or via _POLL_EVENT macro).
Mailboxes and message queues don't have it. This can be confirmed by
looking at kernel/poll.c:register_event(), which handles each of the
supported pollable objects via a switch statement.


Regards

Vakul


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


Re: TCP assert error logs

Paul Sokolovsky
 

Hello,

On Thu, 12 Oct 2017 07:55:48 +0000
Vakul Garg <vakul.garg@nxp.com> wrote:

Hi Paul

On the latest code on master branch, UDP send() on loopback address
fails.
I submitted https://github.com/zephyrproject-rtos/zephyr/issues/4347 on
this. Feel free to submit such reports directly to the bugtracker too.


Regards

Vakul
[]

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


request of information.

novello
 

I would like to develope a simple application for zephyr using stm32f4.
There ia an  IDE with debuger that I can use?
A plugin for eclipse should help.
Best Regards
Novello G


New flashing scripts merged, please report any issues

Marti Bolivar <marti.bolivar@...>
 

Hi,

Last night, a pull request of mine was merged which uses a Python script to flash binaries ("make flash"):


If you run into any problems, you can fall back on the shell scripts by setting USE_ZEPHYR_FLASH_DEBUG_SHELL in your environment for now:

export USE_ZEPHYR_FLASH_DEBUG_SHELL=1

I'd really appreciate reports of any issues you may find. I tested on all the boards I have, but I wasn't able to test everything.

In your report, please include the output of this command, run from samples/hello_world:

KBUILD_VERBOSE=1 BOARD=your_board make flash

Known issues (and proposed fixes) for  quark_se_c1000_devboard and arduino_101 are tracked in:


Thanks,
Marti
 


k_poll usage

Vakul Garg <vakul.garg@...>
 

Hi

 

The zephyr documentation says k_poll to operate on objects – kernel fifo, poll signal, semaphore.

Can’t it also be used on mailboxes, message queues etc?

 

Regards

 

Vakul


Re: TCP assert error logs

Vakul Garg <vakul.garg@...>
 

Hi Paul

On the latest code on master branch, UDP send() on loopback address fails.

Regards

Vakul

-----Original Message-----
From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-
bounces@lists.zephyrproject.org] On Behalf Of Vakul Garg
Sent: Wednesday, September 13, 2017 2:20 PM
To: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Cc: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] TCP assert error logs

[This sender failed our fraud detection checks and may not be who they
appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

Hi Paul

UDP loopback works and I can make progress with it for now.

(Ultimately, I need to move to some non-networking IPC such as mailbox or
pipe.
The problem I face with that now is that I cannot multiplex these zephyr IPC in
POSIX poll() along with socket descriptors.)

Thanks & Regards

Vakul


-----Original Message-----
From: Paul Sokolovsky [mailto:paul.sokolovsky@linaro.org]
Sent: Wednesday, September 13, 2017 1:08 PM
To: Vakul Garg <vakul.garg@nxp.com>
Cc: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] TCP assert error logs

Hello Vakul,

On Tue, 12 Sep 2017 09:09:10 +0000
Vakul Garg <vakul.garg@nxp.com> wrote:

Hello Paul

I have attached a test case with the given ticket.
Thanks for that! It's on my todo list to look into that issue again, the testcase
will be helpful then. In the meantime, following may be helpful for you:

1. UDP communication using a local interface works in Zephyr, we have a
testcase for that in tests/net/socket/udp/

2. If you need TCP communication, you would need to use HOST-Zephyr
communication. (Well, there is also a setup to allow 2 Zephyr QEMU instances
to communicate with each other, I didn't check it for a while though).


Regards

Vakul


-----Original Message-----
From: Paul Sokolovsky [mailto:paul.sokolovsky@linaro.org]
Sent: Monday, September 11, 2017 4:52 PM
To: Vakul Garg <vakul.garg@nxp.com>
Cc: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] TCP assert error logs

Hello Vakul,

On Sat, 9 Sep 2017 09:31:14 +0000
Vakul Garg <vakul.garg@nxp.com> wrote:

I just open a TCP server socket and let it listen for new
connections on 127.0.0.1 on a given server port.
Right, that might work, thanks to
https://gerrit.zephyrproject.org/r/#/c/7007/ , and if you verified, it
apparently does (I don't remember if I ever using 127.0.0.1 address, I
usually tried to use a local interface address in such cases, i.e.
192.0.2.1 by default). But just to get terminology right, there's no
explicit loopback interface in Zephyr, it's just an adhoc check for
the conventional loopback address (though this note is probably
irrelevant for your usecase, so feel free to ignore it [for now]).

Then another thread creates a TCP client socket and connects to the
127.0.0.1 on the same server port. After connection is successful,
client sends one data message on the socket.
What can I say? With such scenario, you went farther than I. Last time
I tried, it wasn't possible to establish a TCP connection under such
conditions at all:
https://jira.zephyrproject.org/browse/ZEP-2001 .

I'd suggest to add some comments to the above ticket, describing your
usecase. And ultimately, we'd need a typical small testcase to
reproduce the issue, so feel free to post your code to make a step
towards progress in that direction. I faced that issue when testing
networking support in Zephyr.JS and MicroPython projects, so there're
no readily available minimal testcases.



Thanks,
Paul



-----Original Message-----
From: Paul Sokolovsky [mailto:paul.sokolovsky@linaro.org]
Sent: Saturday, September 09, 2017 2:57 PM
To: Vakul Garg <vakul.garg@nxp.com>
Cc: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] TCP assert error logs

Hello Vakul,

On Sat, 9 Sep 2017 06:47:35 +0000
Vakul Garg <vakul.garg@nxp.com> wrote:

Hi

I have two threads on my system communicating using TCP over
loopback interface. I am getting following errors.
To the best of my knowledge, there is (was) no loopback interface
support in Zephyr. So, I'd interested to know how to achieved the
setup above.


[net/tcp] [ERR] net_tcp_get_hdr: {assert: 'frag' failed} [net/tcp]
[ERR] net_tcp_send_pkt: Packet 0x20004664 does not contain TCP
header [net/tcp] [ERR] net_tcp_get_hdr: {assert:
'frag' failed} [net/tcp] [ERR] net_tcp_send_pkt: Packet
0x20004664 does not contain TCP header [net/tcp] [ERR]
net_tcp_get_hdr: {assert: 'frag' failed} [net/tcp] [ERR]
net_tcp_send_pkt: Packet 0x20004664 does not contain TCP header
[net/buf] [ERR] net_buf_unref_debug: net_pkt_frag_unref():826:
buf 0x200046a0 double free [net/buf] [ERR] net_buf_unref_debug:
net_pkt_frag_unref():826: buf 0x200046a0 double free [net/buf]
[ERR] net_buf_unref_debug: net_pkt_frag_unref():826: buf
0x20004830 double free

Can someone help?

Regards, Vakul

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


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


--
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
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users


Re: [1.9.0] build broken for windows

Carles Perello
 

good, this and the proper Python tolos did the trick.

Now I need to check where in the make the -no-pie option is used

( echo -nostartfiles -nodefaultlibs -nostdlib -static -no-pie -Wl,-X -Wl,-N -Wl,--gc-sections -Wl,--build-id=none; echo "-Wl,-Map=zephyr.map"; echo "-L ./include/generated"; echo "-u _OffsetAbsSyms -u _ConfigAbsSyms"; echo "-e __start"; echo "-Wl,--start-group"; echo "-Wl,--whole-archive"; echo "libapplication.a"; echo "libzephyr.a"; echo "-Wl,--no-whole-archive"; echo "kernel/lib.a"; echo "./arch/x86/core/offsets/offsets.o"; echo "-Wl,--end-group"; echo "-L /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/lib/gcc/i586-intel-elfiamcu/5.2.1 -L /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/i586-intel-elfiamcu/lib -lgcc"; ) > zephyr.lnk

/home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -T linker.cmd @zephyr.lnk -o zephyr_prebuilt.elf

i586-intel-elfiamcu-gcc.exe: error: unrecognized command line option '-no-pie'


On Mon, Oct 9, 2017 at 5:48 PM, Boie, Andrew P <andrew.p.boie@...> wrote:

I had this same problem with xtools yesterday.

In scripts/Makefile.toolchain.issm, the "export" line on like 44 needs DTC added to it. Otherwise the variable is unset and you will get the error below.

DTC used to not be used for qemu this is a recent bug.

 

Andrew

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: Monday, October 9, 2017 6:52 AM
To: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 



Re: [1.9.0] build broken for windows

Boie, Andrew P
 

I had this same problem with xtools yesterday.

In scripts/Makefile.toolchain.issm, the "export" line on like 44 needs DTC added to it. Otherwise the variable is unset and you will get the error below.

DTC used to not be used for qemu this is a recent bug.

 

Andrew

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: Monday, October 9, 2017 6:52 AM
To: zephyr-users@...
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@...
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 


Re: [1.9.0] build broken for windows

Carles Perello
 

hmm interesting..

I am still lurking with it.. one reason for fail can be that I am unable to install pip (behind a Firewall and certificate fails), but I am using python 3.6 which has pip. doh.

On Mon, Oct 9, 2017 at 4:24 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

can you run this on an MSYS2 shell:

 

$ which dtc

/usr/bin/dtc

 

You should get /usr/bin/dtc, if you don’t that means that dtc for some reason failed to install.

 

Device Tree is a hardware description language and mechanism. Instead of describing the particularities of each SoC and board through a set of header files or Makefiles, you do so by using the DT language, which is then compiled by dtc to generated the required information for the build system and source code. More information can be found here:

 

https://www.zephyrproject.org/doc/devices/dts/device_tree.html

 

Zephyr 1.8 probably did not use DT for the x86 targets, since this was introduced recently.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 09 October 2017 16:14


To: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

sure dtc was installed via pacman.

 

citrix on here is Windows..I am using ISSM toolchain.

 

 

what is dts exactly? seems it was not existing on 1.8.0....probably I can avoid it?

 

regards

 

On Mon, Oct 9, 2017 at 3:57 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

Do you have dtc installed? It looks like it could not find your Device Tree Compiler (dtc).

 

I am not sure if Citrix and Works is Windows (MSYS2) or not, but if you are building on Linux then you need to install the Zephyr SDK, which includes dtc.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 09 October 2017 15:52
To: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 

 



Re: [1.9.0] build broken for windows

Carles Cufi
 

Hi Carles,

 

can you run this on an MSYS2 shell:

 

$ which dtc

/usr/bin/dtc

 

You should get /usr/bin/dtc, if you don’t that means that dtc for some reason failed to install.

 

Device Tree is a hardware description language and mechanism. Instead of describing the particularities of each SoC and board through a set of header files or Makefiles, you do so by using the DT language, which is then compiled by dtc to generated the required information for the build system and source code. More information can be found here:

 

https://www.zephyrproject.org/doc/devices/dts/device_tree.html

 

Zephyr 1.8 probably did not use DT for the x86 targets, since this was introduced recently.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 09 October 2017 16:14
To: zephyr-users@...
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

sure dtc was installed via pacman.

 

citrix on here is Windows..I am using ISSM toolchain.

 

 

what is dts exactly? seems it was not existing on 1.8.0....probably I can avoid it?

 

regards

 

On Mon, Oct 9, 2017 at 3:57 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

Do you have dtc installed? It looks like it could not find your Device Tree Compiler (dtc).

 

I am not sure if Citrix and Works is Windows (MSYS2) or not, but if you are building on Linux then you need to install the Zephyr SDK, which includes dtc.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 09 October 2017 15:52
To: zephyr-users@...
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@...
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 

 


Re: [1.9.0] build broken for windows

Carles Perello
 

sure dtc was installed via pacman.

citrix on here is Windows..I am using ISSM toolchain.


what is dts exactly? seems it was not existing on 1.8.0....probably I can avoid it?

regards

On Mon, Oct 9, 2017 at 3:57 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

Do you have dtc installed? It looks like it could not find your Device Tree Compiler (dtc).

 

I am not sure if Citrix and Works is Windows (MSYS2) or not, but if you are building on Linux then you need to install the Zephyr SDK, which includes dtc.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 09 October 2017 15:52
To: zephyr-users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 



Re: [1.9.0] build broken for windows

Carles Cufi
 

Hi Carles,

 

Do you have dtc installed? It looks like it could not find your Device Tree Compiler (dtc).

 

I am not sure if Citrix and Works is Windows (MSYS2) or not, but if you are building on Linux then you need to install the Zephyr SDK, which includes dtc.

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 09 October 2017 15:52
To: zephyr-users@...
Subject: Re: [Zephyr-users] [1.9.0] build broken for windows

 

Ok. msys2 on Windows 7 Enterprise is BSOD.

 

So I tried it under citrix and Works but still have the same error:

 

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@...
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards

 


Re: [1.9.0] build broken for windows

Carles Perello
 

Ok. msys2 on Windows 7 Enterprise is BSOD.

So I tried it under citrix and Works but still have the same error:

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=scripts/basic

make -f /home/perelloc/zephyr/scripts/Makefile.build obj=dts/x86

echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay; then echo '#include "Z:/perelloc/msys32/home/perelloc/zephyr/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /home/perelloc/issm-toolchain-windows-2017-01-25/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/home/perelloc/zephyr/kernel/include -I/home/perelloc/zephyr/arch/x86/include -I/home/perelloc/zephyr/arch/x86/soc/intel_quark/quark_se -I/home/perelloc/zephyr/boards/x86/arduino_101 -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/include -I/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated -include /home/perelloc/zephyr/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h -I/home/perelloc/zephyr/ext/hal/qmsi/include -I/home/perelloc/zephyr/ext/hal/qmsi/drivers/include -I/home/perelloc/zephyr/ext/hal/qmsi/soc/quark_se/include/ -I/home/perelloc/zephyr/lib/libc/minimal/include -I/home/perelloc/zephyr/arch/x86/soc -I/home/perelloc/zephyr/dts/common -I/home/perelloc/zephyr/dts -I/home/perelloc/zephyr/dts/x86 -I/home/perelloc/zephyr/drivers/of/testcase-data -I/home/perelloc/zephyr/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ; -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /home/perelloc/zephyr/dts/x86/ -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d

/bin/sh: -O: command not found

make[3]: *** [scripts/Makefile.lib:307: dts/x86/arduino_101.dts_compiled] Error 127

make[2]: *** [/home/perelloc/zephyr/Makefile:1008: include/generated/generated_dts_board.h] Error 2

make[2]: Leaving directory '/home/perelloc/zephyr/samples/hello_world/outdir/arduino_101'

make[1]: *** [Makefile:178: sub-make] Error 2

make[1]: Leaving directory '/home/perelloc/zephyr'

make: *** [/home/perelloc/zephyr/Makefile.inc:82: all] Error 2

 

On Fri, Oct 6, 2017 at 10:35 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@lists.zephyrproject.org [mailto:zephyr-users-bounces@lists.zephyrproject.org] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards



Re: [1.9.0] build broken for windows

Carles Cufi
 

Hi Carles,

 

MinGW is no longer supported as a build environment for Zephyr, it was removed from the documentation accordingly.

 

Could you try using MSYS2 instead, as per the instructions here:

https://www.zephyrproject.org/doc/getting_started/installation_win.html#using-msys2

 

Regards,

 

Carles

 

From: zephyr-users-bounces@... [mailto:zephyr-users-bounces@...] On Behalf Of Carles Perello
Sent: 06 October 2017 10:28
To: zephyr-users@...
Subject: [Zephyr-users] [1.9.0] build broken for windows

 

Hi

 

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

 

Seems this got broken on 1.9.0

 

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

 

any hint?

 

regards


[1.9.0] build broken for windows

Carles Perello
 

Hi

I was able to buil zephyr under Windows/MinGW until versión 1.8.0 (targets quemu and arduino_101)

Seems this got broken on 1.9.0

make -f d:/zephyr-1.9.0/scripts/Makefile.build obj=dts/x86
  echo '#include "arduino_101.dts"' > dts/x86/arduino_101.dts_pre_compiled ; if test -e d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay; then echo '#include "d:/zephyr-1.9.0/samples/hello_world/arduino_101.overlay"' >> dts/x86/arduino_101.dts_pre_compiled ; fi ; /d/IntelSWTools/ISSM_2016.1.067/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc -E -Wp,-MD,dts/x86/.arduino_101.dts_compiled.d.pre.tmp -nostdinc -I/d/zephyr-1.9.0/kernel/include -I/d/zephyr-1.9.0/arch/x86/include -I/d/zephyr-1.9.0/arch/x86/soc/intel_quark/quark_se -I/d/zephyr-1.9.0/boards/x86/arduino_101  -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/include -I/d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated -include /d/zephyr-1.9.0/samples/hello_world/outdir/arduino_101/include/generated/autoconf.h  -I/d/zephyr-1.9.0/ext/hal/qmsi/include -I/d/zephyr-1.9.0/ext/hal/qmsi/drivers/include -I/d/zephyr-1.9.0/ext/hal/qmsi/soc/quark_se/include/ -I/d/zephyr-1.9.0/lib/libc/minimal/include -I/d/zephyr-1.9.0/arch/x86/soc -I/d/zephyr-1.9.0/dts/common -I/d/zephyr-1.9.0/dts -I/d/zephyr-1.9.0/dts/x86 -I/d/zephyr-1.9.0/drivers/of/testcase-data -Id:/zephyr-1.9.0/samples/hello_world -undef -D__DTS__ -x assembler-with-cpp -o dts/x86/.arduino_101.dts_compiled.dts.tmp dts/x86/arduino_101.dts_pre_compiled ;  -O dts -o dts/x86/arduino_101.dts_compiled -b 0 -i /d/zephyr-1.9.0/dts/x86/  -d dts/x86/.arduino_101.dts_compiled.d.dtc.tmp dts/x86/.arduino_101.dts_compiled.dts.tmp ; cat dts/x86/.arduino_101.dts_compiled.d.pre.tmp dts/x86/.arduino_101.dts_compiled.d.dtc.tmp > dts/x86/.arduino_101.dts_compiled.d
/bin/sh: -O: command not found
make[3]: *** [dts/x86/arduino_101.dts_compiled] Error 127

any hint?

regards


Re: Problem with echo_server / echo_client samples running in QEMU (No rule to make target 'qemu' ?)

Priyanka
 

Hi Paul


Thanks for the patch.

I tested again  /samples/net/ieee802154/qemu


Probably the issue comes from qemu <---> qemu set up and this might work on kw41z (as suggested by David).

My kernel version is 4.4.0-96-generic.


For the test with QEMU at least, echo-server / Qemu crashes (Fatal fault in ISR! Spinning...) as soon as echo-client is launched.

Need to check what is wrong at echo-server app end . 

Terminal 2 echo-client (Qemu)
-------------------------------------------
zephyr/samples/net/echo_client$ make CONF_FILE=prj_qemu_802154.conf client
[QEMU] CPU: qemu32

[echo-client] [INF] init_app: Run echo client
[echo-client] [ERR] wait_reply: Data packet not received
[echo-client] [ERR] wait_reply: Data packet not received


Terminal 1 echo-server ( Qemu)
-----------------------------------------
zephyr/samples/net/echo_server$ make CONF_FILE=prj_qemu_802154.conf server

[QEMU] CPU: qemu32
qemu-system-i386: warning: Unknown firmware file in legacy mode: genroms/multiboot.bin

***** CPU Page Fault (error code 0x00000002)
Supervisor thread wrote address 0x00000000
PDE: 0x025 Present Read-only User
PTE: 0x000 Non-present Read-only Supervisor
Current thread ID = 0x00401000
Faulting segment:address = 0x0008:0x00001d5c
eax: 0x00413033, ebx: 0x00000000, ecx: 0x00000000, edx: 0x000002f8
esi: 0x004137ec, edi: 0x0040c0b0, ebp: 0x004107d8, esp: 0x004107d0
eflags: 0x202
Fatal fault in ISR! Spinning...
Terminate emulator due to fatal kernel error
/zephyr/scripts/Makefile.qemu:26: recipe for target 'run' failed
make[2]: *** [run] Error 1
make[2]: Leaving directory 'zephyr/samples/net/echo_server/outdir/qemu_x86'
Makefile:178: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory 'zephyr-LTI/zephyr'

Thanks
Priyanka


From: Paul Sokolovsky <paul.sokolovsky@...>
Sent: Tuesday, October 3, 2017 9:09 PM
To: Priyanka Rawat
Cc: Nashif, Anas; zephyr-users@...
Subject: Re: [Zephyr-users] Problem with echo_server / echo_client samples running in QEMU (No rule to make target 'qemu' ?)
 
On Tue, 3 Oct 2017 14:24:10 +0000
Priyanka Rawat <priyanka.rawat@...> wrote:

> Hello Nashif
>
>
> Thanks for the fix.
>
> This might resolve the issue related to 'target QEMU", however
> another issue is that echo_client fails to compile with errors like
> (even with the 3 week older zephyr version).
>
> undefined reference to `net_app_send_pkt'

Thanks for the report. In future cases, feel free to open a bug at
https://github.com/zephyrproject-rtos/zephyr/issues .

I posted a patch to solve this issue:
https://github.com/zephyrproject-rtos/zephyr/pull/4166


> This is why I had today switched to the most recent version of zephyr.
>
> Any idea, what am I missing here? Thanks.
>
>
> Terminal 2 echo_client
>
> --------------------------------
>
> zephyr/samples/net/echo_client$ make CONF_FILE=prj_qemu_802154.conf
>
> In function `prepare_send_pkt':
> /zephyr/samples/net/echo_client/src/echo-client.c:111: undefined
> reference to `net_app_get_net_pkt' src/built-in.o: In function
> `send_udp_data': zephyr/samples/net/echo_client/src/udp.c:160:
> undefined reference to `net_app_send_pkt' src/built-in.o: In function
> `connect_udp': /zephyr/samples/net/echo_client/src/udp.c:262:
> undefined reference to `net_app_init_udp_client'
> zephyr/samples/net/echo_client/src/udp.c:273: undefined reference to
> `net_app_set_cb' /zephyr/samples/net/echo_client/src/udp.c:302:
> undefined reference to `net_app_connect' src/built-in.o: In function
> `stop_udp': zephyr/samples/net/echo_client/src/udp.c:360: undefined
> reference to
> `net_app_close' /zephyr/samples/net/echo_client/src/udp.c:361:
> undefined reference to `net_app_release'
>
>
> Best,
> Priyanka

[]

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
www.facebook.com
Log into Facebook to start sharing and connecting with your friends, family, and people you know.

http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
twitter.com
1,745 tweets • 616 photos/videos • 3,063 followers. Check out the latest Tweets from Linaro (@LinaroOrg)


Re: IPSP bluetooth sample with QEMU (ping fails)

David Leach
 

Priyanka,

 

I have a branch on my fork that compiles the 802.15.4 echo client/server without any errors. It really is just a couple of project files though so I’m not sure what is happening with your setup. You can check what I did here:

 

https://github.com/dleach02/zephyr/tree/kw41z

 

I’m still playing around with things to get a better understanding of how things are laid out. Anas had suggested that we consider cleaning up the config files in the client/server echo sample … plus I’m not so convinced things are working that well.

 

David Leach

 

From: Priyanka Rawat
Sent: Tuesday, October 03, 2017 9:15 AM
To: Paul Sokolovsky <paul.sokolovsky@...>
Cc: zephyr-users@...; Vakul Garg <vakul.garg@...>; Maureen Helm <maureen.helm@...>; David Leach <david.leach@...>
Subject: Re: [Zephyr-users] IPSP bluetooth sample with QEMU (ping fails)

 

Hi Paul

 

Thank you for the details and suggestions. 

Sure, I am going to add "+1" to the PR :-)

 

In fact, what we are interested in is not really BLE, but having IPv6 over KW41Z communicating with a peer board.

So we had been exploring and testing different connectivity options.

 

1) I tested IPv6 over BLE (IPSP sample) with QEMU and it works finally :-). However, Maureen informed us about some legal issues related to enabling BLE on KW41Z. So I understand we won't be able to use the BLE connectivity option on real hardware.

 

2) Now as a possible alternative option, I started with testing "IPv6 over IEEE802.15.4" with QEMU first and then we will test with kw41z.

 

However,  with the most recent zephyr master branch (after I did "git pull" today), echo_server / echo_client failed for target QEMU. 

Nashif, Anas  has just provided a fix for this, I will test again with the fix. Thanks.

 

The fix might resolve "target 'qemu'" issue, however, another issue is that echo_client fails to compile with errors like 

(undefined reference to `net_app_send_pkt'....)

 

Thanks

Priyanka

 


From: Paul Sokolovsky <paul.sokolovsky@...>
Sent: Tuesday, October 3, 2017 3:15 PM
To: Priyanka Rawat
Cc: zephyr-users@...; Vakul Garg; Maureen Helm; David Leach
Subject: Re: [Zephyr-users] IPSP bluetooth sample with QEMU (ping fails)

 

Hello Priyanka,

Sorry for the delay with response, I was at Linaro Connect with pretty
packed local program. But we touched some questions you posed
below with Maureen Helm and David Leach of NXP (both are in cc:), so
hopefully I can bring some info.

Another note is that I appreciate that you use Zephyr "user" mailing
list - we have also the "devel" mailing, and some posts there would be
better suited for the user lists. But your posts are actually the
opposite, as they touch Zephyr development matters, so given there're
not many responses, I may suggest to post there too, maybe people
monitor it better.

See also below for more comments.


On Wed, 27 Sep 2017 20:27:05 +0000
Priyanka Rawat <priyanka.rawat@...> wrote:

> Hi
>
> Thank you Paul for the suggestions.
> We are waiting for the real hardware (KW41Z board), meanwhile I
> should test IPSP with QEMU.
>
> Unfortunately, I do not have a 96b_carbon board. Does anyone know if
> IPv6 over BLE, IPSP work on FRDM boards?

Not that I know of. And work done by Linaro on KW41Z/KW40Z revolves
around 802.15.4 instead. For example, there's a Zephyr driver
already in the tree, and 15.4-over-FSCI driver in the review:
https://github.com/zephyrproject-rtos/zephyr/pull/868 . I found a bit
strange there was no talk about BLE support, as "native" Hexiwear
support is all about BLE (and communication with smartphones), and
vice-versa, there's no sign of 15.4 support.

At the Connect, David mentioned that BLE controller/stack might have
been licensed from 3rd party vendor, and that poses additional
organizational complications to its support in Zephyr.

However, if you have a two-core system, like Hexiwear, where KW40Z is
used completely as a block box BLE controller, you might be able to run
it, if it uses the standard HCI protocol. At least we have couple of
boards in Zephyr which use a similar arrangement.

> Eventually, we would like to test the following scenario;
> KW41Z running Zephyr + 6loble (IPv6 over BLE) with a x86 Linux +
> KW41Z-FRDM / USB.

Same here at Linaro, except we want to do it over 15.4 ;-).

> Any idea if IPv6 over BLE / 6lowpan works over KW41Z running Zephyr?
> Has anyone tested IPv6 over BLE with Zephyr over KW41Z board?

David (re)tested 6lowpan over 15.4 with KW41Z, it mostly works.
Reproducing that is my immediate TODO once I finish with post-travel
backlog.

> What is the current status on IPv6 over BLE?

Well, it works (as an "experimental technology" would, with various
requirements and caveats).

>
> I found some links on IPv6 over BLE, but couldn't figure out much
> from them. Is there any other link I should look at?

I mention previously
https://github.com/zephyrproject-rtos/zephyr/pull/1185 , which
documents steps I went thru to get IPv6 over BLE running. I'd like to
extend an invitation to add a "+1" style comment to it if you find it
useful and would like to see it in the official documentation
(otherwise, the reviewers of that patch are people who also maintain
Linux kernel side of BLE and Bluez, and they assume that everyone runs
the latest kernel and Bluez, which is of course not true ;-) ).

>
> https://github.com/zephyrproject-rtos/zephyr/pull/1151
> net: l2: bt: Make 6lowpan/BLE be compatible with Linux by default
> #1151
>
> https://github.com/zephyrproject-rtos/zephyr/issues/3111

github.com

Reported by James Prestwood: Running using Zephyr's IPv6 over BLE seems to have been broken recently. I have tested with iotivity-constrained and do see some data but things are not working correct...


> IPv6 over BLE no longer works after commit 2e9fd88 #3111
>
>
> Update on IPSP sample with QEMU  (ping works, but there are errors
> like fatal kernel error etc., )

Well, great news! What kernel version do you use? The latest news is
that kernel 4.12 finally should fix all the issues (known issues) with
6lowpan/ble support:
https://github.com/zephyrproject-rtos/zephyr/commit/a4e176b6a33ebbb0732e4a1d8cb174bb57a6f510

github.com

Since 4.12 Linux kernel has fixes required to comply to RFC 7668. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@...>



If you have below that, might as well be not too surprised with errors,
etc. ;-). I myself running 4.10, waiting while my OS vendor will issue
an (still experimental) 4.12 upgrade.

> -----------------------------------------------------------------------------------------------------------------------------------------
>
> I tested IPSP bluetooth sample with QEMU again and ping works now.
> Tests with telnet and echo-client work as well.
>
> $ ping6 2001:db8::1
> PING 2001:db8::1(2001:db8::1) 56 data bytes
> 64 bytes from 2001:db8::1: icmp_seq=1 ttl=64 time=27.2 ms
> 64 bytes from 2001:db8::1: icmp_seq=2 ttl=64 time=4.45 ms
> 64 bytes from 2001:db8::1: icmp_seq=3 ttl=64 time=2.13 ms
> 64 bytes from 2001:db8::1: icmp_seq=4 ttl=64 time=3.73 ms
> ^C
>
> s$ telnet 2001:db8::1 4242
> Trying 2001:db8::1...
> Connected to 2001:db8::1.
> Escape character is '^]'.
> hello
> hello
> okkkkkkkk
> okkkkkkkk
>
> $ sudo ./echo-client -i bt0 2001:db8::1
> Binding to 2001:db8::2
> .......
>
> However, I get warnings
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
>
> and then after a while it terminates with the following error (fatal
> kernel error and fatal fault in ISR!)
>
> ***** CPU Page Fault (error code 0x00000002)
> Supervisor thread wrote address 0x00000008
> PDE: 0x025 Present Read-only User
> PTE: 0x000 Non-present Read-only Supervisor
> Current thread ID = 0x004015e0
> Faulting segment:address = 0x0008:0x00013170
> eax: 0x00402094, ebx: 0x00403510, ecx: 0x0040200a, edx: 0x00402050
> esi: 0x00000000, edi: 0x000001f4, ebp: 0x00417774, esp: 0x00417764
> eflags: 0x202
> Fatal fault in ISR! Spinning...
> Terminate emulator due to fatal kernel error
> $zephyr/scripts/Makefile.qemu:26: recipe for target 'run' failed
> make[2]: *** [run] Error 1
> make[2]: Leaving directory
> 'zephyr/samples/bluetooth/ipsp/outdir/qemu_x86' Makefile:178: recipe
> for target 'sub-make' failed make[1]: *** [sub-make] Error 2
> make[1]: Leaving directory '...../zephyr'
> /zephyr/Makefile.inc:91: recipe for target 'run' failed
> make: *** [run] Error 2
>
> -------------------------------------------------
>
> Following is the entire output.
>
>
> [QEMU] CPU: qemu32
>
> [bt] [INF] show_dev_info: Identity: 00:aa:01:00:00:23 (public)
> [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000,
> manufacturer 0x003f [bt] [INF] show_dev_info: LMP: version 5.0 (0x09)
> subver 0x0000 [ipsp] [INF] init_app: Run IPSP sample
> [ipsp] [INF] listen: Starting to wait
> [bt] [ERR] read_payload: Not enough space in buffer
> [bt] [WRN] hci_cmd_done: pool id 4 pool 0x0041add4 != &hci_cmd_pool
> 0x0041adb4 [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 1 bytes
> [ipsp] [DBG] build_reply_pkt: Received 1 bytes, sending 1 bytes
> [ipsp] [DBG] pkt_sent: Sent 1 bytes
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 6 bytes
> [ipsp] [DBG] build_reply_pkt: Received 6 bytes, sending 6 bytes
> [ipsp] [DBG] pkt_sent: Sent 6 bytes
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 4 bytes
> [ipsp] [DBG] build_reply_pkt: Received 4 bytes, sending 4 bytes
> [ipsp] [DBG] pkt_sent: Sent 4 bytes
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 26 bytes
> [ipsp] [DBG] build_reply_pkt: Received 26 bytes, sending 26 bytes
> [ipsp] [DBG] pkt_sent: Sent 26 bytes
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 1232 bytes
> [ipsp] [DBG] build_reply_pkt: Received 1232 bytes, sending 1232 bytes
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 1 bytes
> [ipsp] [DBG] build_reply_pkt: Received 1 bytes, sending 1 bytes
> [ipsp] [DBG] pkt_sent: Sent 1 bytes
> [ipsp] [DBG] build_reply_pkt: UDP IPv6 received 256 bytes
> [ipsp] [DBG] build_reply_pkt: Received 256 bytes, sending 256 bytes
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
>
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] read_payload: Failed to allocate, deferring to rx_thread
> [bt] [WRN] hci_cmd_done: pool id 4 pool 0x0041add4 != &hci_cmd_pool
> 0x0041adb4 [bt] [WRN] hci_cmd_done: pool id 4 pool 0x0041add4 !=
> &hci_cmd_pool 0x0041adb4
>
> [ipsp] [DBG] build_reply_pkt: TCP IPv6 received 7 bytes
> [ipsp] [DBG] build_reply_pkt: Received 7 bytes, sending 7 bytes
> [ipsp] [DBG] pkt_sent: Sent 7 bytes
> [ipsp] [DBG] pkt_sent: Sent 7 bytes
> [ipsp] [DBG] pkt_sent: Sent 0 bytes
> [ipsp] [DBG] build_reply_pkt: TCP IPv6 received 11 bytes
> [ipsp] [DBG] build_reply_pkt: Received 11 bytes, sending 11 bytes
> [ipsp] [DBG] pkt_sent: Sent 11 bytes
> [ipsp] [DBG] pkt_sent: Sent 11 bytes
> [ipsp] [DBG] pkt_sent: Sent 0 bytes
> [ipsp] [DBG] build_reply_pkt: TCP IPv6 received 36 bytes
> [ipsp] [DBG] build_reply_pkt: Received 36 bytes, sending 36 bytes
> [ipsp] [DBG] pkt_sent: Sent 36 bytes
> [ipsp] [DBG] pkt_sent: Sent 36 bytes
> [ipsp] [DBG] pkt_sent: Sent 0 bytes
> [ipsp] [DBG] build_reply_pkt: TCP IPv6 received 86 bytes
> [ipsp] [DBG] build_reply_pkt: Received 86 bytes, sending 86 bytes
> [ipsp] [DBG] pkt_sent: Sent 86 bytes
> [ipsp] [DBG] pkt_sent: Sent 0 bytes
>
> [ipsp] [DBG] build_reply_pkt: TCP IPv6 received 7 bytes
> [ipsp] [DBG] build_reply_pkt: Received 7 bytes, sending 7 bytes
> ***** CPU Page Fault (error code 0x00000002)
> Supervisor thread wrote address 0x00000008
> PDE: 0x025 Present Read-only User
> PTE: 0x000 Non-present Read-only Supervisor
> Current thread ID = 0x004015e0
> Faulting segment:address = 0x0008:0x00013170
> eax: 0x00402094, ebx: 0x00403510, ecx: 0x0040200a, edx: 0x00402050
> esi: 0x00000000, edi: 0x000001f4, ebp: 0x00417774, esp: 0x00417764
> eflags: 0x202
> Fatal fault in ISR! Spinning...
> Terminate emulator due to fatal kernel error
> /zephyr/scripts/Makefile.qemu:26: recipe for target 'run' failed
> make[2]: *** [run] Error 1
> make[2]: Leaving directory
> '/zephyr/samples/bluetooth/ipsp/outdir/qemu_x86' Makefile:178: recipe
> for target 'sub-make' failed make[1]: *** [sub-make] Error 2
> make[1]: Leaving directory '/Downloads/zephyr-LTI/zephyr'
> /zephyr/Makefile.inc:91: recipe for target 'run' failed
> make: *** [run] Error 2
>
> -----------------------------------------------------------------------------------
>
> Has anyone come across similar errors?
>
> I found a link on Bluetooth: ipsp fixes
> https://github.com/zephyrproject-rtos/zephyr/pull/1537/files?diff=split

github.com

Since Linux 4.12 has been released with fixes to RFC 7668 the default configuration no longer works, so this moves CONFIG_NET_L2_BT_ZEP1656 to separate conf file so prj.conf keeps working with Linu...


> Not sure if this would fix the above issues.
>
>
> Best Regards,
> Priyanka
>
>
> > -----Original Message-----
> > From: zephyr-users-bounces@...
> > [mailto:zephyr-users- bounces@...] On Behalf Of
> > Paul Sokolovsky
> > Sent: Thursday, September 21, 2017 9:46 PM
> > To: Priyanka Rawat <priyanka.rawat@...>
> > Cc: zephyr-users@...
> > Subject: Re: [Zephyr-users] IPSP bluetooth sample with QEMU (ping
> > fails)
> >
> > Hello Priyanka,
> >
> > On Mon, 18 Sep 2017 17:04:25 +0000
> > Priyanka Rawat <priyanka.rawat@...> wrote:
> >  
> > > While testing bluetooth IPSP sample (recent master branch of
> > > zephyr) with Qemu, ping fails (no response found) and
> > >
> > > ping: sendmsg: No buffer space available (wireshark capture
> > > attached).
> > >
> > > I noticed that there are some old issues and bugs reported on the
> > > IPSP sample. However, I couldn't figure out if the bugs/issues
> > > have been resolved already.
> > >
> > > What is the current status on the IPSP bluetooth sample? Anyone
> > > tested IPSP sample with Qemu? 
> >
> > I tested it on BOARD=96b_carbon (real hardware) straight before 1.9
> > release, everything worked well, and I captured docs required to
> > set it up at
> > https://github.com/zephyrproject-rtos/zephyr/pull/1185 (if you
> > would find detailed instructions for setting up IPSP in Zephyr
> > useful, please add +1 comment to that pull request).
> >
> > What's your usecase for working with BLE in qemu_x86 in general? I
> > fully understand and support the idea of being able to run it via
> > QEMU, so everyone can test it without a real hardware, but based on
> > your own experience, not everything works smooth there. So, if
> > you're just interested in BLE and/or IPSP, I'd suggest to try them
> > on some real board as an alternative to QEMU, that's known to work
> > pretty well (across few boards).
> >
> > I myself a novice with BLE support in Zephyr (usually work on other
> > things), and would be interested to get it work with QEMU too, but
> > don't know when I'll be able to pay enough attention to it, as I'm
> > currently working on few other things keeping me pretty busy.
> >  
> > >
> > > I get the following for the IPSP test:
> > >
> > > zephyr/samples/bluetooth/ipsp$ make BOARD=qemu_x86
> > > CONF_FILE=prj_dbg.conf run
> > >
> > > [QEMU] CPU: qemu32
> > > qemu-system-i386: warning: Unknown firmware file in legacy mode:
> > > genroms/multiboot.bin
> > >
> > > [bt] [INF] show_dev_info: Identity: 00:aa:01:00:00:23 (public)
> > > [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision
> > > 0x0000, manufacturer 0x003f [bt] [INF] show_dev_info: LMP:
> > > version 5.0 (0x09) subver 0x0000 [ipsp] [INF] init_app: Run IPSP
> > > sample [ipsp] [INF]
> > > listen: Starting to wait
> > >
> > >
> > > On host PC
> > >
> > > ----------------
> > >
> > > I enabled 6lowpan and bluetooth_6lowpan
> > >
> > >
> > > # modprobe bluetooth_6lowpan
> > > # modprobe 6lowpan
> > > # echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable
> > > # echo connect "00:aa:01:00:00:23 1" 
> > > > /sys/kernel/debug/bluetooth/6lowpan_control 
> > >
> > >
> > >
> > > $ sudo hcitool lescan
> > > [sudo] password for nxf32661:
> > > LE Scan ...
> > > 00:AA:01:00:00:23 (unknown)
> > > 00:AA:01:00:00:23 Test IPSP node
> > >
> > >
> > > $ sudo ./echo-client -i bt0 2001:db8::1 Binding to 2001:db8::2
> > > Timeout while waiting idx 0 len 1 Timeout while waiting idx 1 len
> > > 6 Timeout while waiting idx 2 len 4 Timeout while waiting idx 3
> > > len 26 Timeout while waiting idx 4 len 1232 Timeout while waiting
> > > idx 5 len 1 Timeout while waiting idx 6 len 256
> > >
> > > $ ping6 -I bt0 2001:db8::1
> > > PING 2001:db8::1(2001:db8::1) from 2001:db8::2 bt0: 56 data bytes
> > > ping: sendmsg: No buffer space available
> > > ping: sendmsg: No buffer space available
> > > ping: sendmsg: No buffer space available
> > > ping: sendmsg: No buffer space available
> > >
> > > $ ifconfig bt0
> > > bt0       Link encap:UNSPEC  HWaddr
> > > 00-AA-01-FF-FE-01-00-24-00-00-00-00-00-00-00-00 inet6 addr:
> > > fe80::2aa:1ff:fe01:24/64 Scope:Link inet6 addr: 2001:db8::2/64
> > > Scope:Global UP POINTOPOINT RUNNING MULTICAST  MTU:1280  Metric:1
> > >           RX packets:76 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:91 errors:0 dropped:91 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:1
> > >           RX bytes:7128 (7.1 KB)  TX bytes:8532 (8.5 KB)
> > >
> > > Thanks
> > > Priyanka
> > > 
> >
> >
> >
> > --
> > 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
> > _______________________________________________
> > Zephyr-users mailing list
> > Zephyr-users@...
> > https://lists.zephyrproject.org/mailman/listinfo/zephyr-user 



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


Re: Problem with echo_server / echo_client samples running in QEMU (No rule to make target 'qemu' ?)

Paul Sokolovsky
 

On Tue, 3 Oct 2017 14:24:10 +0000
Priyanka Rawat <priyanka.rawat@nxp.com> wrote:

Hello Nashif


Thanks for the fix.

This might resolve the issue related to 'target QEMU", however
another issue is that echo_client fails to compile with errors like
(even with the 3 week older zephyr version).

undefined reference to `net_app_send_pkt'
Thanks for the report. In future cases, feel free to open a bug at
https://github.com/zephyrproject-rtos/zephyr/issues .

I posted a patch to solve this issue:
https://github.com/zephyrproject-rtos/zephyr/pull/4166


This is why I had today switched to the most recent version of zephyr.

Any idea, what am I missing here? Thanks.


Terminal 2 echo_client

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

zephyr/samples/net/echo_client$ make CONF_FILE=prj_qemu_802154.conf

In function `prepare_send_pkt':
/zephyr/samples/net/echo_client/src/echo-client.c:111: undefined
reference to `net_app_get_net_pkt' src/built-in.o: In function
`send_udp_data': zephyr/samples/net/echo_client/src/udp.c:160:
undefined reference to `net_app_send_pkt' src/built-in.o: In function
`connect_udp': /zephyr/samples/net/echo_client/src/udp.c:262:
undefined reference to `net_app_init_udp_client'
zephyr/samples/net/echo_client/src/udp.c:273: undefined reference to
`net_app_set_cb' /zephyr/samples/net/echo_client/src/udp.c:302:
undefined reference to `net_app_connect' src/built-in.o: In function
`stop_udp': zephyr/samples/net/echo_client/src/udp.c:360: undefined
reference to
`net_app_close' /zephyr/samples/net/echo_client/src/udp.c:361:
undefined reference to `net_app_release'


Best,
Priyanka
[]

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


Re: Projects in Zephyr v1.9.0 always rebuild even no changes in source code. How to fix this?

Carles Cufi
 

Hi Alan,

 

Unfortunately I don´t think there is a fix as of yet. The transition to CMake will of course resolve this issue but in the meantime no one has seriously looked into this since it seems like most of our current users develop on Linux. I do build on Windows regularly but have not looked into this yet. If I do I will update the GitHub issue.

 

Regards,

 

Carles

 

From: Alan Low <alanlhc@...>
Date: Tuesday, 3 October 2017 at 16:56
To: "Cufi, Carles" <Carles.Cufi@...>
Cc: "zephyr-users@..." <zephyr-users@...>
Subject: RE: [Zephyr-users] Projects in Zephyr v1.9.0 always rebuild even no changes in source code. How to fix this?

 

Hi Carles,

2481 - 2500 of 2706