|
API meeting: agenda
Carles Cufi
Hi all,
Special agenda for today: - In order to help with the 2.4 release we will go through bugs labeled API or drivers and try to clean up or assign as many as we can. Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d 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
|
|
|
|
Zephyr 2.4.0-rc1 tagged
Maureen Helm
Hi everyone, The first release candidate for Zephyr 2.4.0 has been tagged (v2.4.0-rc1).
The merge window for features and enhancements is now closed for this release, and it will remain closed until 2.4.0 is released; the stabilization period is now open. During the stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for the 2.4 release require approval by the TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers.
Testing Zephyr master branch during the stabilization period is also requested; please test the code base and file bug reports so they can be addressed before the release deadline.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.4.0-rc1 More details about Zephyr releases can found on the pages below: https://docs.zephyrproject.org/latest/development_process/release_process.html https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management The final release is tentatively scheduled for 25 Sep.
Note 1: You may continue to send Pull Requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the largest extent possible, so that we can release 2.4.0 on time and in the best shape possible.
Note 2: If you have a feature or enhancement you would like to submit to the TSC, please tag the Pull Request with the "TSC" label, make sure it is approved and passing CI, and attend the next TSC meeting.
A big Thank You to everyone that contributed to this release so far, be it with code, reviews, documentation or any other type of contribution!
Maureen
|
|
|
|
double free detected in bfree_recombine
George Kumar
Hi all, I am running zephyr 2.2.0 on my board and while developing a multi-threading application, running into a double free at ZEPHY_BASE/lib/os/mempool.c:163. /*Detect common double-free occurrences */ __ASSERT(alloc_bit_is_set(p, level, bn), "mempool double free detected at %p", block); My question is does Zephyr have any tools like valgrind that can help me pinpoint the issue. Thanks. George
|
|
|
|
Timeout in NCS (nRF Connect SDK) by Nordic Semiconductors using Zephyr OS
Lavingia, Raj
Hello,
I am using the default Zephyr BLE stack while using the NCS SDK with nrf52840 development board by Nordic.
My setup is as follows Board1 – Running a Peripheral_Uart demo code which is advertising. Board2 – Running a Central_Uart demo code which is scanning.
When the scan starts on board 2, I am filling the advertising address of the devices which are advertising, in a buffer. When I started the printing the buffer, the addresses repeat at a certain time period. For example, if I see 01:01:01:01:01:01 address at time X sec, I see the same address at X + (120-180)sec again. So I am wondering if the data coming from the callback is getting refreshed at a certain time interval? If so, which parameters are controlling this refresh rate? Is it possible to change this time which is 120-180 sec approximately right now to whatever value I want?
Thanks Raj Lavingia I Embedded Software Engineer Shure Incoporated 5800 W. Touhy Avenue Niles, Illinois 60714-4608 USA T +1.847.600.6276 shure.com
This e-mail message (including any attachments) contains confidential, non-public information. It also may be protected by the attorney/client or other applicable privileges. It is intended to be communicated only to the designated recipient(s). Unauthorized use, reproduction, dissemination, or communication of this message or any information contained in this message is strictly prohibited and may be unlawful. If you are not an intended recipient of this message, please notify the sender promptly by e-mail or contact Shure Incorporated at info@... or 800-25-SHURE (800-257-4873).
|
|
|
|
Zephyr Project: Dev Meeting - Thu, 09/03/2020 3:00pm-4:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 3 September 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Re: RFC: API change - make all device instance constant
Tomasz Bursztyka
Hello,
toggle quoted messageShow quoted text
The PR was merged. Now ALL device instances are constant. Along with this change: all isr handlers take a const void pointer. To all relevant stakeholders that this may affect: !!! PLEASE REBASE YOUR PR(s) ACCORDINGLY !!! Thank you, Tomasz
Hello,
|
|
|
|
Zephyr Project: APIs - Tue, 09/01/2020 4:00pm-5:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 1 September 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18 ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
API meeting agenda: 2020-09-01
Peter A. Bigot
Carles has asked me to stand in for him in coordinating this
week's API telecon.
Topics include: - #26516 add MODBUS RTU subsystem - Anything else added to the Triage column of the API Project - Anything else raised in the slack #api channel or at the meeting Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d 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
|
|
|
|
v2.4.0 merge window closes friday
Maureen Helm
Hi everyone, This is a reminder that the v2.4.0 merge window for new features closes this Friday, 4 September. After that, only bug fixes and documentation will be merged until the final release is tagged, which is targeted for 25 September. Exceptions require TSC approval. New feature PRs may still be submitted while the merge window is closed, but please keep in mind that maintainers will have less time to review them during the release stabilization period.
Please add the v2.4.0 milestone to PRs that need to be included in the release, and do not wait until Friday to submit them. https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+milestone%3Av2.4.0
Please try to help fix bugs, test release candidates, and write release notes to minimize the time the merge window is closed so we can all quickly get back to adding fun new things to Zephyr!
Thank you for your contributions!
Your v2.4.0 release manager, Maureen
|
|
|
|
Re: Reg: Installing and Running with windows laptop.
Carles Cufi
Hi Deepa,
From your question it seems you are using the nRF Connect SDK, and not vanilla Zephyr. You should therefore direct your question to the Nordic DevZone instead: https://devzone.nordicsemi.com/
Regards,
Carles
From: users@... <users@...>
On Behalf Of Deepalakshmi RR via lists.zephyrproject.org
Sent: 31 August 2020 12:33 To: users@... <users@...>; devel@... Subject: [Zephyr-users] Reg: Installing and Running with windows laptop.
Hello team,
Greetings From Deepa. I need an manual installation procedure and building, compiling and Running the zephyr -OS with my laptop for learning purpose. I browsed and compiled via cmd prompt, but still I need an Editor support for running this OS with nrf9160 controller. In addition to that, I tried running with web browser as well. I also willing to run with an IDE(any IDE which supports for NC sdk) for creating my own projects and running with NC sdk.
Please, suggest some options along with sample projects running procedure at the earliest.
Thanks & Regards, Deepa.R +91-9486308286/ 8072608604
Sent from Mail for Windows 10
=====================================================
|
|
|
|
Reg: Installing and Running with windows laptop.
Deepalakshmi RR <deepalakshmi.rr@...>
Hello team,
Greetings From Deepa. I need an manual installation procedure and building, compiling and Running the zephyr -OS with my laptop for learning purpose. I browsed and compiled via cmd prompt, but still I need an Editor support for running this OS with nrf9160 controller. In addition to that, I tried running with web browser as well. I also willing to run with an IDE(any IDE which supports for NC sdk) for creating my own projects and running with NC sdk.
Please, suggest some options along with sample projects running procedure at the earliest.
Thanks & Regards, Deepa.R +91-9486308286/ 8072608604
Sent from Mail for Windows 10
Please refer to https://northamerica.altran.com/email-disclaimer for important disclosures regarding this electronic communication. =====================================================
|
|
|
|
Re: Zephyr Toolchain Working Group Meeting – 27 August 2020
Thomas Törnblom
Good morning Torsten,
toggle quoted messageShow quoted text
As a followup on yesterdays meeting I verified that one can use #include in a preinclude file with the IAR compiler, and that works fine, so a workaround for the limit of only one --preinclude directive, one could create a file that #include all the files and preinclude that. Thomas Den 2020-08-27 kl. 14:27, skrev
Rasmussen, Torsten:
--
Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom@... Website: www.iar.com Twitter: www.twitter.com/iarsystems
|
|
|
|
Zephyr Project: Dev Meeting - Thu, 08/27/2020 3:00pm-4:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 27 August 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Dev-Review Meeting Agenda Aug 27
Bolivar, Marti
Hi,
Kumar is out this week, so I'm sending the dev-review agenda. * Open PRs with the dev-review label: * Emulator framework and example I2C emulator #27300 * lib: hawkbit: Add Hawkbit FOTA Support #24107 * Open issues anyone would like to discuss Thanks, Martí
|
|
|
|
Zephyr: Toolchain Working Group - Thu, 08/27/2020
#cal-notice
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr: Toolchain Working Group When: Where: Description: Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r
________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Zephyr: Toolchain Working Group - Thu, 08/27/2020 2:00pm-3:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr: Toolchain Working Group When: Thursday, 27 August 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: Maureen Helm Description: Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r
________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Zephyr Toolchain Working Group Meeting – 27 August 2020
Rasmussen, Torsten
Call for today’s Toolchain WG.
Agenda
PR: https://github.com/zephyrproject-rtos/zephyr/pull/24851 now ready for review.
Feel free to send a mail, if you would like additional topics to be discussed.
Best regards
Torsten T. Rasmussen
Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll) Conference ID: 682 738 030# Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Re: BLE Controller Core Spec 5.2 Power Control Feature
Chettimada, Vinayak Kariappa
> I think it will integrate better with the new design but let me continue with the current master for the time being.
Current master has not accepted any new control procedure code except for bug fixes and conformance related changes since November 2019.
The strategy has been to restrain from any control procedure related changes in the current master and all focus be on the new work in the topic branch.
You should switch to integrating on the topic branch as the current control procedure code will be deleted in the very next release version after one release with new control procedure code merged.
- Vinayak
Get Outlook for iOS
From: Khaled Elsayed <khaled.elsayed@...>
Sent: Wednesday, August 26, 2020 9:10:42 PM To: Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> Cc: devel@... <devel@...> Subject: Re: [Zephyr-devel] BLE Controller Core Spec 5.2 Power Control Feature
Hi Vinayak
Thanks for sharing the sample Min used channels procedure.
I had a quick look and the new design seems to be very elegant. Good to see the req/ack logic gone and using explicit states. I actually used explicit states in the draft LE PC feature implementation and tried to plug it in with the current master. I think
it will integrate better with the new design but let me continue with the current master for the time being.
BR,
Khaled
On Wed, Aug 26, 2020 at 3:04 PM Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
The information contained in this message is privileged, confidential or otherwise protected from use and disclosure. If you are not the
intended recipient, you are hereby notified that any review, disclosure, copying or dissemination of this message or the taking of any action in reliance on its contents, or other use is strictly prohibited. If you received this message in error, please notify
us immediately by replying to the message and deleting it from your computer. Thank you.
Si-Vision,
LLC.
|
|
|
|
Re: BLE Controller Core Spec 5.2 Power Control Feature
Khaled Elsayed
Hi Vinayak Thanks for sharing the sample Min used channels procedure. I had a quick look and the new design seems to be very elegant. Good to see the req/ack logic gone and using explicit states. I actually used explicit states in the draft LE PC feature implementation and tried to plug it in with the current master. I think it will integrate better with the new design but let me continue with the current master for the time being. BR, Khaled On Wed, Aug 26, 2020 at 3:04 PM Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
The information contained in this message is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying or dissemination of this message or the taking of any action in reliance on its contents, or other use is strictly prohibited. If you received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Si-Vision, LLC.
|
|
|
|
RFC: remove w25qxxdv flash driver from Zephyr as of 2.4.0
Peter A. Bigot
The spi_flash_w25qxxdv driver has been superseded by the generic
spi_nor driver for over a year. The only non-refactoring change to
the W25Q driver in the last 18 months was done to support a
backport to 1.14.
All devices supported by spi_flash_w25qxxdv driver are expected to be supported by the spi_nor driver, using the standard jedec,spi-nor devicetree compatible. No in-tree devicetree files make use of this driver. To reduce confusion about which driver is expected to be used for JEDEC-standard SPI NOR serial flash memories pull request 27802 proposes to remove the redundant driver from Zephyr 2.4. (It's not practical to deprecate a driver, and the existing one will work only for winbond,w25q16 if anything. Please raise any concerns you have with this proposal as comments/reviews on the pull request. Peter
|
|
|