port other projects to Zephyr
KAY LI NG <kayli0109@...>
Hi there, Is it possible to port FreeRTOS project to Zephyr project? Seems like both of them works differently. Regards, Kay Li
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: west build broken?
Marc Herbert
My bad, can you please try this revert https://github.com/zephyrproject-rtos/zephyr/pull/17549 ?
Marc
From:
<users@...> on behalf of Lawrence King <lawrence.king@...>
Dear All:
Today I did a ‘west update’, and a ‘git pull’ in the zephyr directory.
After fixing the things in my code that have become deprecated I have found an issue with west that can easily be replicated.
cd zephyr/samples/basic/blinky west build -b mdk52840_mdk # west happily builds the west code and it works fine touch src/main.c west build -b mdk52840_mdk # this time the build fails with a link error
Before today ‘west build’ happily compiles just src/main.c and successfully relinked your project, all was good.
Same issue exists with my code instead of blinky, and with any board I have tried….
Lawrence King Principal Developer Connected Transport Market Unit +1(416)627-7302
CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
west build broken?
Dear All:
Today I did a ‘west update’, and a ‘git pull’ in the zephyr directory.
After fixing the things in my code that have become deprecated I have found an issue with west that can easily be replicated.
cd zephyr/samples/basic/blinky west build -b mdk52840_mdk # west happily builds the west code and it works fine touch src/main.c west build -b mdk52840_mdk # this time the build fails with a link error
Before today ‘west build’ happily compiles just src/main.c and successfully relinked your project, all was good.
Same issue exists with my code instead of blinky, and with any board I have tried….
Lawrence King Principal Developer Connected Transport Market Unit +1(416)627-7302
CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #hci_uart with board nrf52_pca10040 build fail
#hci_uart
Carles Cufi
Hi there,
You have several options:
More information here: https://docs.zephyrproject.org/latest/guides/west/build-flash-debug.html#building-west-build
Carles
From: users@... <users@...>
On Behalf Of deeve ma via Lists.Zephyrproject.Org
Sent: 13 July 2019 16:27 To: users@... Cc: users@... Subject: [Zephyr-users] #hci_uart with board nrf52_pca10040 build fail
can anyone help me: deeve@debian:~/zephyrproject/zephyr$ git log commit 9fac66ca540a7c1221d17e20ac903a647b1a0184 Author: Nicolas Pitre <npitre@...> Date: Tue Jul 9 17:19:12 2019 -0400
tests: usb: make 64-bit compatible
Let's use the PTR_DIFF() helper which performs pointer difference in a 64-bit compatible way, and use %zu for printing sizeof() results.
Signed-off-by: Nicolas Pitre <npitre@...> deeve@debian:~/zephyrproject/zephyr$ west build -b nrf52_pca10040 samples/bluetooth/hci_uart -- west build: build configuration: source directory: /home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart build directory: /home/deeve/zephyrproject/zephyr/build BOARD: nrf52_pca10040 (origin: command line) -- west build: generating a build system CMake Error: The source "/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart/CMakeLists.txt" does not match the source "/home/deeve/zephyrproject/zephyr/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory. ERROR: command exited with status 1: /usr/local/bin/cmake -B/home/deeve/zephyrproject/zephyr/build -S/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart -GNinja -DBOARD=nrf52_pca10040 run as "west -v build -b nrf52_pca10040 samples/bluetooth/hci_uart" for a stack trace
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: DTLS over CoAP for the Zephyr project
Carles Cufi
Hi Nikos,
toggle quoted messageShow quoted text
Copying a couple of people that might not be on this mailing list and may be able to help you. Carles
-----Original Message-----
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: flag for board type issue
Carles Cufi
If you switch to using west to build instead of invoking cmake and ninja directly, then you can add:
[build] pristine = auto
in your ~/.westconfig and then west will clean the build folder for you whenever you switch apps or boards.
More info here: https://docs.zephyrproject.org/latest/guides/west/build-flash-debug.html#building-west-build
Carles
From: users@... <users@...>
On Behalf Of Marc Herbert via Lists.Zephyrproject.Org
Sent: 09 July 2019 17:10 To: KAY LI NG <kayli0109@...>; users@... Cc: users@... Subject: Re: [Zephyr-users] flag for board type issue
I'm afraid that's the way CMake's cache works:
https://stackoverflow.com/questions/26145865/confused-about-cmakes-cached-variable-setting-priority
There are at least two "workarounds":
cmake -Be70build -DBOARD=sam_e70_xplained ...
or:
rm -rf build; cmake -Bbuild ...
From:
<users@...> on behalf of KAY LI NG <kayli0109@...>
Hi there,
I have a question. I specified the flag for board type to build, it works. But when i specify the flag for another board type, it still targets to the previous board.
$ cmake -Bbuild -GNinja -DBOARD=sam_e70_xplained samples/hello_world
$ cmake -Bbuild -GNinja -DBOARD=qemu_x86 samples/hello_world
If i delete the build directory and specified the board type again, it works. Is that a problem? Or any other ways to simplify this?
Regards, Kay Li
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: DTC version unsupported error
#west
Carles Cufi
Hi Eric,
Can you try replacing $HOME in the ZEPHYR_SDK_INSTALL_DIR with the full path? I know I’ve seen issues with that in the past.
For example in my case I use:
ZEPHYR_SDK_INSTALL_DIR="/home/carles/bin/zephyr-sdk"
From: users@... <users@...>
On Behalf Of Eric via Lists.Zephyrproject.Org
Sent: 06 July 2019 06:01 To: users@... Cc: users@... Subject: [Zephyr-users] DTC version unsupported error #west
On a new Ubuntu install, I'm having this issue with Zephyr using West. It's also referenced in this issue, but the fix mentioned there didn't work for me:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: cant perform west init
Carles Cufi
Hi Kay,
toggle quoted messageShow quoted text
Can you make sure you have the latest colorama version? pip3 install --user -U colorama Carles
-----Original Message-----
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #hci_uart with board nrf52_pca10040 build fail
#hci_uart
Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>
Hi Deeve,
I use the following steps (when not using west):
$ cd ${ZEPHYR_BASE} $ mkdir -p build/hci_uart $ cd build/hci_uart $ cmake -GNinja -DBOARD=nrf52_pca10040 ../../samples/bluetooth/hci_uart/ $ ninja
Hope this may help.
Regards, Vinayak
From:
<users@...> on behalf of "deeve ma via Lists.Zephyrproject.Org" <deeve.ma=gmail.com@...>
can anyone help me: deeve@debian:~/zephyrproject/zephyr$ git log commit 9fac66ca540a7c1221d17e20ac903a647b1a0184 Author: Nicolas Pitre <npitre@...> Date: Tue Jul 9 17:19:12 2019 -0400
tests: usb: make 64-bit compatible
Let's use the PTR_DIFF() helper which performs pointer difference in a 64-bit compatible way, and use %zu for printing sizeof() results.
Signed-off-by: Nicolas Pitre <npitre@...> deeve@debian:~/zephyrproject/zephyr$ west build -b nrf52_pca10040 samples/bluetooth/hci_uart -- west build: build configuration: source directory: /home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart build directory: /home/deeve/zephyrproject/zephyr/build BOARD: nrf52_pca10040 (origin: command line) -- west build: generating a build system CMake Error: The source "/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart/CMakeLists.txt" does not match the source "/home/deeve/zephyrproject/zephyr/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory. ERROR: command exited with status 1: /usr/local/bin/cmake -B/home/deeve/zephyrproject/zephyr/build -S/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart -GNinja -DBOARD=nrf52_pca10040 run as "west -v build -b nrf52_pca10040 samples/bluetooth/hci_uart" for a stack trace
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#hci_uart with board nrf52_pca10040 build fail
#hci_uart
deeve ma
can anyone help me:
I get the latest zephyr code, but build fail: deeve@debian:~/zephyrproject/zephyr$ git log
commit 9fac66ca540a7c1221d17e20ac903a647b1a0184
Author: Nicolas Pitre <npitre@...>
Date: Tue Jul 9 17:19:12 2019 -0400
tests: usb: make 64-bit compatible
Let's use the PTR_DIFF() helper which performs pointer difference in a
64-bit compatible way, and use %zu for printing sizeof() results.
Signed-off-by: Nicolas Pitre <npitre@...>
--------------------------------------------------------------------------------------------- build command and error message: deeve@debian:~/zephyrproject/zephyr$ west build -b nrf52_pca10040 samples/bluetooth/hci_uart
-- west build: build configuration:
source directory: /home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart
build directory: /home/deeve/zephyrproject/zephyr/build
BOARD: nrf52_pca10040 (origin: command line)
-- west build: generating a build system
CMake Error: The source "/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart/CMakeLists.txt" does not match the source "/home/deeve/zephyrproject/zephyr/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
ERROR: command exited with status 1: /usr/local/bin/cmake -B/home/deeve/zephyrproject/zephyr/build -S/home/deeve/zephyrproject/zephyr/samples/bluetooth/hci_uart -GNinja -DBOARD=nrf52_pca10040
run as "west -v build -b nrf52_pca10040 samples/bluetooth/hci_uart" for a stack trace
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Mesh publish message to proxy node
Venkat Rao Vallapaneni <vallapaneni@...>
Hi Johan, I have noticed the following and I think this is not expected
behavior. I have a mesh network with two nodes with addresses 0x0100 and
0x0106. I have connected to the mesh network from my android
device over 0x0100. I also have set proxy filtering to blacklist
filter without any addresses added to the filter. Now I am sending config message to the node 0x0106 from android
device. I see that node 0x0100 receives this PDU over GATT but it
does not relay over advertisement barrier. It relays this message
back to android device over GATT. I looked at the code and bt_mesh_proxy_relay is returning true
and with destination address being unicast address (0x0106),
bt_mesh_net_relay is not calling bt_mesh_adv_send. I suppose this
is not correct behavior. Please let me know. With whitelist filter, everything works fine (bt_mesh_proxy_relay returns false as destination address is not there in filtered addresses). Rgds,Venkat.
On 18/06/19 11:38 PM, Venkat Rao
Vallapaneni wrote:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: DTLS over CoAP for the Zephyr project
Nikos Karamolegkos
Any ideas guys?
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Summer 2019 Zephyr Project Newsletter
Zephyr Project <taldrich@...>
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: flag for board type issue
Marc Herbert
I'm afraid that's the way CMake's cache works:
https://stackoverflow.com/questions/26145865/confused-about-cmakes-cached-variable-setting-priority
There are at least two "workarounds":
cmake -Be70build -DBOARD=sam_e70_xplained ...
or:
rm -rf build; cmake -Bbuild ...
From:
<users@...> on behalf of KAY LI NG <kayli0109@...>
Hi there,
I have a question. I specified the flag for board type to build, it works. But when i specify the flag for another board type, it still targets to the previous board.
$ cmake -Bbuild -GNinja -DBOARD=sam_e70_xplained samples/hello_world
$ cmake -Bbuild -GNinja -DBOARD=qemu_x86 samples/hello_world
If i delete the build directory and specified the board type again, it works. Is that a problem? Or any other ways to simplify this?
Regards, Kay Li
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
flag for board type issue
KAY LI NG <kayli0109@...>
Hi there, I have a question. I specified the flag for board type to build, it works. But when i specify the flag for another board type, it still targets to the previous board. $ cmake -Bbuild -GNinja -DBOARD=sam_e70_xplained samples/hello_world $ cmake -Bbuild -GNinja -DBOARD=qemu_x86 samples/hello_world If i delete the build directory and specified the board type again, it works. Is that a problem? Or any other ways to simplify this? Regards, Kay Li
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: BLE mesh message advertising interval
Venkat Rao Vallapaneni <vallapaneni@...>
Hi, I also have a follow-up question, more related to the
specification. This is regarding Publish Retransmit Count. I
suppose this increases the number of mesh messages advertised. Can
we have "Model Publication" state for configuration server model
also? In the specification, it is mentioned that: "models defined
by higher layer specifications use instances of the model
publication state to control the publishing of messages". Not sure
if we can have this state for base model such as configuration
server. Venkat.
On 08/07/19 8:30 PM, Venkat Rao
Vallapaneni wrote:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BLE mesh message advertising interval
Venkat Rao Vallapaneni <vallapaneni@...>
Hi, I am trying BLE mesh on-off app on nrf52840 USB dongle. I have
provisioned two devices. Sometimes, I see that I don't get response (No response could be
first message or any message in between or sometimes even I am
successful in binding app keys to all models, but rarely). This mesh message is missed by node1. I am trying to understand more on why this mesh message advertising packet was missed by node1. I noticed that in mesh/adv.c, I see that min interval and max interval are same. In the specifications, it is mentioned that: "The Advertising_Interval_Min shall be less than or equal to the Advertising_Interval_Max. The Advertising_Interval_Min and Advertising_Interval_Max should not be the same value to enable the Controller to determine the best advertising interval given other activities." param.interval_min = ADV_SCAN_UNIT(adv_int); Why these two values are set same? I have tried making interval_max as ADV_SCAN_UNIT(adv_int+5) but
didn't help. I have used default settings in mesh on-off sample app: /* 3 transmissions with 20ms
interval */
.net_transmit = BT_MESH_TRANSMIT(2, 20), I increased the transmissions to 6 (along with max interval
greater than min interval) and it improved (3/5 times successful
in sending 25 configuration messages back to back). Any other recommended approaches to minimize mesh message advertising packet losses? Thanks, Venkat.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DTC version unsupported error
#west
Eric
On a new Ubuntu install, I'm having this issue with Zephyr using West. It's also referenced in this issue, but the fix mentioned there didn't work for me:
https://github.com/zephyrproject-rtos/zephyr/issues/15246 $ west build -b nrf51_pca10031 -- west build: build configuration: source directory: /home/hp1/zephyrproject/zephyr/samples/hello_world build directory: /home/hp1/zephyrproject/zephyr/samples/hello_world/build BOARD: nrf51_pca10031 (origin: command line) -- west build: generating a build system Zephyr version: 1.14.99 -- Selected BOARD nrf51_pca10031 -- Found west: /home/hp1/.local/bin/west (found suitable version "0.5.7", minimum required is "0.5.6") CMake Error at /home/hp1/zephyrproject/zephyr/cmake/extensions.cmake:1324 (message): Assertion failed: The detected dtc version is unsupported. The version was found to be 1.4.5 But the minimum supported version is 1.4.6 See https://docs.zephyrproject.org/latest/getting_started/ for how to use the SDK's dtc alongside a custom toolchain. Call Stack (most recent call first): /home/hp1/zephyrproject/zephyr/cmake/host-tools.cmake:69 (assert) /home/hp1/zephyrproject/zephyr/cmake/app/boilerplate.cmake:412 (include) CMakeLists.txt:5 (include) -- Configuring incomplete, errors occurred! I did try the two environmental variables, which are now part of the Zephyr instructions, but the problem persists.
I'm unsure how to go about fixing the DTC version issue.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
gnfranco@...
Thanks Andrei
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Zephyr kernel compatibility with POSIX standard
Gabriele Morgante
Hi,
we are interested to know the compatibility degree of Zephyr kernel with the POSIX standard. For instance, could we execute a C program POSIX compliant, written for an x86 linux kernel, on a Zephyr board as a Zephyr Application? Thanks, regards!
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|