Most BLE applications with nrf52 boards are broken on Version 2.1
Li, Jun R
Hey, I’ve tried to build a couple of BLE applications, like “beacon” , “peripheral_hr” with several nRF52 boards such as “nrf52_pca10040”, “nrf52840_pca10056” on the version 2.1. All building process is broken at the link stage with the following errors:
/opt/zephyr-sdk-0.10.3/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/8.3.0/../../../../arm-zephyr-eabi/bin/ld: subsys/bluetooth/host/libsubsys__bluetooth__host.a(hci_core.c.obj): in function `le_set_private_addr': /home/uwb/projects/iid_device/zephyr/subsys/bluetooth/host/hci_core.c:581: undefined reference to `bt_rand' /opt/zephyr-sdk-0.10.3/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/8.3.0/../../../../arm-zephyr-eabi/bin/ld: subsys/bluetooth/host/libsubsys__bluetooth__host.a(hci_core.c.obj): in function `create_random_addr': /home/uwb/projects/iid_device/zephyr/subsys/bluetooth/host/hci_core.c:4658: undefined reference to `bt_rand' collect2: error: ld returned 1 exit status zephyr/CMakeFiles/zephyr_prebuilt.dir/build.make:104: recipe for target 'zephyr/zephyr_prebuilt.elf' failed make[2]: *** [zephyr/zephyr_prebuilt.elf] Error 1 CMakeFiles/Makefile2:579: recipe for target 'zephyr/CMakeFiles/zephyr_prebuilt.dir/all' failed make[1]: *** [zephyr/CMakeFiles/zephyr_prebuilt.dir/all] Error 2 Makefile:83: recipe for target 'all' failed make: *** [all] Error 2
I’m not sure if the CI process still covers the tests for most applications.
Regards, Jun
--
|
|
ZEBRA RFC source tree location
#ble
Dean Gereaux
The ZEBRA RFC (see RFC: https://github.com/zephyrproject-rtos/zephyr/issues/23465) is a feature proposal for a simple way to add secure authentication between two Bluetooth devices. ZEBRA is not part of the Bluetooth stack, it uses the Bluetooth stack via the firmware application to authenticate. There are several places where the ZEBRA code could potentially resided within the Zephyr code base:
Good option. The subsys directory contains key components of Zephyr. While you can use Zephyr without a sub system, say networking, these components are often critical and used in an embedded system. The subsys/auth subdirectory would contain ZEBRA and other authentication methods such as Google Fast Pair. As security becomes more important to real time systems, it makes sense to make authentication a key component of Zephyr. A subsys/auth would also enable code sharing between different authentication methods.
Looking for suggestions and comments on which option would work the best. I personally prefer option #1. Thanks, Dean Gereaux
|
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 03/26/2020 8:00am-9:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 26 March 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Join Zoom Meeting
|
|
Dev-Review Meeting Agenda Mar 25
Kumar Gala
Here’s the agenda topics for this week:
* Review PR’s tagged with dev-review * use of PRE_KERNEL_1/PRE_KERNEL_2... * Pinmux/pinctrl (Piotr/Erwan) * Any topics anyone else has - k
|
|
Zephyr crypto APIs and mbed TLS
Carles Cufi
Hi all,
I was wondering about the state of crypto APIs in Zephyr and whether it makes sense to move them forward or instead we should consider simply using the mbed TLS set of APIs as Zephyr's crypto API. The reason I say this is that today we have include/crypto/cipher.h which abstracts ciphers, but that's about it. Most users in the code seem to use mbed TLS APIs directly when they require crypto functionality (with the exception of Bluetooth which can use TinyCrypt or mbed TLS and has its own abstraction) with only the IEEE 802.15.4 stack using cipher.h. mbed TLS is a recognized crypto API that (as far as I know) can be used with or without the actual mbed TLS implementation, so I question the need to define our own in this particular case, although I might be missing key information. Unless I am mistaken one can implement hardware-accelerated or custom or proprietary implementations of crypto functions and shim them so that they expose the mbed TLS API. In any case I do believe this is something that needs discussion since the current usage in the tree is inconsistent and the subset of APIs defined in include/crypto is very small. If we did decide to use mbed TLS as an API we would then also need to discuss how to go about it, since mbed TLS is today an (optional) module and therefore the header files themselves are not included in the main zephyr tree. Input welcome! Regards, Carles
|
|
Narendar Malepu
Yes previously I posted same issue, but iam not creating any threads in my application
On Tue, 24 Mar, 2020, 2:14 PM Chettimada, Vinayak Kariappa, <vinayak.kariappa.chettimada@...> wrote:
|
|
Upcoming Event: Zephyr Project: APIs - Tue, 03/24/2020 9:00am-10:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 24 March 2020, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878 Live meeting minutes: https://docs.google.com/
|
|
Re: net_buf: non-atomic reference counting
Paul Sokolovsky
Hello,
On Tue, 24 Mar 2020 11:25:48 +0200 "Jukka Rissanen" <jukka.rissanen@linux.intel.com> wrote: Hi Darryl,Perhaps it could be rephrased differently: net_buf is more like Zephyr's internal system object. Where it's used currently, thread synchronization is expected(*) to happen on different level(s), and net_buf itself is kept lightweight and optimized. Perhaps that can be changed, but effects on existing subsystems using net_buf should be considered. (*) That doesn't mean there're no bugs, so reproducible bugreports are welcome.
-- 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
|
|
API meeting: agenda
Carles Cufi
Hi all,
Note: This is the last week where the meeting takes place at 17h CET. Next week we go back to 18h CET. Today's topics: - How to document standalone drivers like the enc28j60 (Piotr) - Upgrade the hwinfo API to stable - PR: https://github.com/zephyrproject-rtos/zephyr/pull/23661 - RTC API proposal - PR: https://github.com/zephyrproject-rtos/zephyr/pull/23526/commits/2880ee02b0f2fd91d897d8a11a4cbdefe87a19b0 - Naming in the async_notify module - PR: https://github.com/zephyrproject-rtos/zephyr/pull/23601 Additional items in the "Triage" column in the GitHub project may be discussed if time permits. If you want an item included in the meeting, please add it to the GitHub project. https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion https://github.com/zephyrproject-rtos/zephyr/projects/18 https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|
Re: net_buf: non-atomic reference counting
Jukka Rissanen
Hi Darryl,
toggle quoted messageShow quoted text
I think it is more of a historical relic than a purpose design. There has not been any reports that this have caused issues. Patches are welcome of course. Cheers, Jukka
On Sun, 2020-03-22 at 17:39 -0700, Darryl Gamroth wrote:
Hi all,
|
|
Chettimada, Vinayak Kariappa
Please create a github issue with details of building your application and steps to reproduce the issue. Do specify the commit hash, and if you have a branch, do mention that too.
I see you have re-sent this mail again to mailing list, did you try measuring the stack usage of threads using the PR mentioned in previous email threads?
Regards, Vinayak
From: devel@... <devel@...>
On Behalf Of Narendar Malepu via Lists.Zephyrproject.Org
Sent: 24 March 2020 07:20 To: devel@... Cc: devel@... Subject: [Zephyr-devel] nrf52840 ble error #ble #nrf52840
Hi, [00:01:36.902,862] <inf> os: prio recv thread stack : unused 336 usage 112 / 448 (25 %) [00:01:36.902,893] <err> os: ***** BUS FAULT ***** [00:01:36.902,893] <err> os: Imprecise data bus error [00:01:36.902,923] <err> os: r0/a1: 0x00000029 r1/a2: 0x00000004 r2/a3: 0x00000000 [00:01:36.902,923] <err> os: r3/a4: 0x20004a0c r12/ip: 0x00000000 r14/lr: 0x000388fb [00:01:36.902,923] <err> os: xpsr: 0x61000000 [00:01:36.902,923] <err> os: Faulting instruction address (r15/pc): 0x000390ee [00:01:36.902,923] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0 [00:01:36.902,923] <err> os: Current thread: 0x20000eec (unknown) [00:01:37.159,637] <err> os: Halting system
|
|
Narendar Malepu
Hi,
Iam using nrf52840 development board, developing software using zephyr. In software development iam using bluetooth as a peripheral and uart in interrupt mode(to get data from other module), when iam trying to run both interfaces the getting below errors and iam included watchdog timer so after sometime it is restarting. [00:01:36.902,862] <inf> os: prio recv thread stack : unused 336 usage 112 / 448 (25 %)
[00:01:36.902,893] <err> os: ***** BUS FAULT *****
[00:01:36.902,893] <err> os: Imprecise data bus error
[00:01:36.902,923] <err> os: r0/a1: 0x00000029 r1/a2: 0x00000004 r2/a3: 0x00000000
[00:01:36.902,923] <err> os: r3/a4: 0x20004a0c r12/ip: 0x00000000 r14/lr: 0x000388fb
[00:01:36.902,923] <err> os: xpsr: 0x61000000
[00:01:36.902,923] <err> os: Faulting instruction address (r15/pc): 0x000390ee
[00:01:36.902,923] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:01:36.902,923] <err> os: Current thread: 0x20000eec (unknown)
[00:01:37.159,637] <err> os: Halting system When i checked with above address error is at zephyr/include/sys/dlist.h:211 can someone help with above error Thanks
|
|
net_buf: non-atomic reference counting
Darryl Gamroth
Hi all,
I was looking at using net_bufs for an application broadcasting reference counted buffers to multiple threads and I noticed the reference counting is not atomic. I'm curious, is this by design? Thanks.
|
|
[API stability change] Request to change the stability of HWINFO from unstable to stable
Alexander Wachter <alexander@...>
Dear all,
This email is a request to change the stability of the Hardware Information API from "unstable" to "stable". Pull-request: #23661 Discussion in the API meeting takes place on Tuesday, March 24th. If there are any objections, please comment on the PR or attend to the API meeting. Kind regards, -- Alexander Wachter The guy who introduced this API
|
|
Zephyr Toolchain Working Group Meeting – 19 March 2020
Rasmussen, Torsten
Hi,Today’s meeting minutes:https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/
Notes/MinutesStatus updates
expect to hit same include files issue, as with using IAR IDE.
This will be hard to solve.
There are attributes set per target regarding memory: read-only read-write Settings are specified in an xml file
AP:
Short term goals:
Could be completely different test system with focus on:
Toolchain abstraction:
Linker
Best regards
Torsten T. Rasmussen
|
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 03/19/2020 8:00am-9:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 19 March 2020, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Join Zoom Meeting
|
|
Zephyr Toolchain Working Group - Thu, 03/19/2020
#cal-notice
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr Toolchain Working Group When: Where: Description:
Topic: Zephyr Toolchain Working Group Time: Mar 19, 2020 07:00 AM Pacific Time (US and Canada) Every 2 weeks on Thu, until Jul 23, 2020, 10 occurrence(s) Mar 19, 2020 07:00 AM Apr 2, 2020 07:00 AM Apr 16, 2020 07:00 AM Apr 30, 2020 07:00 AM May 14, 2020 07:00 AM May 28, 2020 07:00 AM Jun 11, 2020 07:00 AM Jun 25, 2020 07:00 AM Jul 9, 2020 07:00 AM Jul 23, 2020 07:00 AM Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://zoom.us/meeting/tJIqcu2hrD4id0z59MlGQgtjfduqRH_iTA/ics?icsToken=98tyKuCuqT4uE9aQuF39e7cqA97lbN-1i3UesPYEsRPCMidHaAXyI_NwGo12JPmB
Join Zoom Meeting https://zoom.us/j/967549258
Meeting ID: 967 549 258
One tap mobile +16699006833,,967549258# US (San Jose) +16465588656,,967549258# US (New York)
Dial by your location +1 669 900 6833 US (San Jose) +1 646 558 8656 US (New York) 855 880 1246 US Toll-free 877 369 0926 US Toll-free +1 647 558 0588 Canada 855 703 8985 Canada Toll-free Meeting ID: 967 549 258 Find your local number: https://zoom.us/u/abfRKTHWtN
|
|
Dev-Review Meeting Agenda Mar 19 2020
Kumar Gala
Agenda:
* Review any open PR / issues with dev-review label * Device Tree update / next steps (Kumar & Marti) * Power Management thoughts / initial ideas / plans (Peter) * Pinmux / DT (Piotr) If you have anything you’d like to add let me know Thanks - k
|
|
Upcoming Event: Zephyr Toolchain Working Group - Thu, 03/19/2020 7:00am-8:00am
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Toolchain Working Group When: Thursday, 19 March 2020, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/967549258 Organizer: Maureen Helm Description: Zephyr Working Group is inviting you to a scheduled Zoom meeting.
Topic: Zephyr Toolchain Working Group Time: Mar 19, 2020 07:00 AM Pacific Time (US and Canada) Every 2 weeks on Thu, until Jul 23, 2020, 10 occurrence(s) Mar 19, 2020 07:00 AM Apr 2, 2020 07:00 AM Apr 16, 2020 07:00 AM Apr 30, 2020 07:00 AM May 14, 2020 07:00 AM May 28, 2020 07:00 AM Jun 11, 2020 07:00 AM Jun 25, 2020 07:00 AM Jul 9, 2020 07:00 AM Jul 23, 2020 07:00 AM Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://zoom.us/meeting/tJIqcu2hrD4id0z59MlGQgtjfduqRH_iTA/ics?icsToken=98tyKuCuqT4uE9aQuF39e7cqA97lbN-1i3UesPYEsRPCMidHaAXyI_NwGo12JPmB
Join Zoom Meeting https://zoom.us/j/967549258
Meeting ID: 967 549 258
One tap mobile +16699006833,,967549258# US (San Jose) +16465588656,,967549258# US (New York)
Dial by your location +1 669 900 6833 US (San Jose) +1 646 558 8656 US (New York) 855 880 1246 US Toll-free 877 369 0926 US Toll-free +1 647 558 0588 Canada 855 703 8985 Canada Toll-free Meeting ID: 967 549 258 Find your local number: https://zoom.us/u/abfRKTHWtN
|
|
Re: Socket Poll functionality in case of socket is closed
Ravi kumar Veeramally
Hi,
toggle quoted messageShow quoted text
Thanks for clarification. Ravi
On 19/03/2020 14.30, Paul Sokolovsky wrote:
Hello,
|
|