Date   

API meeting: agenda

Carles Cufi
 


Now: Zephyr: Toolchain Working Group - 03/07/2022 #cal-notice

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr: Toolchain Working Group

When:
03/07/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

Description:

Live meeting minutes: https://docs.google.com/document/d/11ENuzr2oDsHXa2FrHf0S3AQ2HncQbGBCU9F5sjTZUnI________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Event: Zephyr: Toolchain Working Group - 03/07/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr: Toolchain Working Group

When:
03/07/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

An RSVP is requested. Click here to RSVP

Description:

Live meeting minutes: https://docs.google.com/document/d/11ENuzr2oDsHXa2FrHf0S3AQ2HncQbGBCU9F5sjTZUnI________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Zephyr SDK 0.14.0-beta1 Release

Stephanos Ioannidis
 

Hi,

 

Zephyr SDK 0.14.0-beta1 has been released.

 

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.14.0-beta1

 

This is the first Zephyr SDK release to support all three major host operating systems:

 

  • Linux (AArch64, x86-64)
  • macOS (AArch64, x86-64)
  • Windows (x86-64)

 

Please refer to the following preliminary “Getting Started Guide” for the instructions on how to

install and use the multi-platform Zephyr SDK:

 

https://stephanosio.github.io/zephyr-mpsdk-doc-test/getting_started/index.html#install-a-toolchain

 

Please try it out and report if you find any issues.

 

Thanks,

 

Stephanos


Event: Zephyr: Power Management Sync - 03/03/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr: Power Management Sync

When:
03/03/2022
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,677440320# United States, Orlando
Phone Conference ID: 677 440 320#
 
________________________________________________________________________________


Event: Zephyr Project: Dev Meeting - 03/03/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: Dev Meeting

When:
03/03/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Deadline to Submit March 4

Maemalynn Meanor <maemalynn@...>
 

Hi All: 

This is a reminder to submit your talks for the Zephyr Developer Summit by this Friday, March 4


Thanks,
Mae

Maemalynn Meanor
Senior PR Manager
The Linux Foundation 
ELISA, Open Mainframe Project, Zephyr Project
(602) 541-0356
@Maemalynn




On Feb 25, 2022, at 9:29 AM, Maemalynn Meanor <maemalynn@...> wrote:

Members of the Zephyr Community:

This year, we’re hosting the Zephyr Developer Summit on June 8-9 at the Computer History Museum in Mountain View, CA. 

We’re currently accepting speaking proposals in several categories including micro-conferences, presentations, demos and tutorials. We’d love to hear from you - please submit your proposals by next Friday, March 4



We hope to see you there!
Maemalynn

Connect with the Zephyr Project: 
@ZephyrIoT (#ZephyrDevSummit, #ZephyrRTOS)

Maemalynn Meanor
Senior PR Manager
The Linux Foundation 
ELISA, Open Mainframe Project, Zephyr Project
(602) 541-0356
@Maemalynn






Dev Review Agenda for Mar 3, 2022

Maureen Helm
 


Event: Zephyr Project: APIs - 03/01/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: APIs

When:
03/01/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

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
 
 
________________________________________________________________________________


Event: Zephyr: Networking Forum - 03/01/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr: Networking Forum

When:
03/01/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: tsc@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 458 216 365#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


API meeting: agenda

Carles Cufi
 


Event: Zephyr Memory Footprint - biweekly discussion - 02/28/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Memory Footprint - biweekly discussion

When:
02/28/2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:
Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Networking Forum

Lubos, Robert
 

Hi all,

 

There is a Networking Forum Tomorrow, March 1st , please let me know if there are any particular topics you’d like to discuss. Otherwise I’ll just keep the slot open to answer any questions/updates from the attendees.

 

Meeting notes:

https://docs.google.com/document/d/1qFsOpvbyLzhflJbbv4Vl__497pKHDoUCy9hjAveyCX0

 

Shared Folder:

https://drive.google.com/drive/folders/1j6d0FLeOjiMil1Ellb59AsfHdzuWdAAc?usp=sharing

 

Teams meeting:
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw%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

 

Regards,
ROBERT LUBOS | Senior Firmware Engineer
M +48 504 088 482 | Krakow, Poland
nordicsemi.com | devzone.nordicsemi.com

Nordic_logo_signature

 


Configure BLE Module on STEVAL-MKSBOX1V1

Daniele Bortoluzzi <danieleb88@...>
 

Hi,
I'm Bortoluzzi Daniele, and I'm developing, for my master's thesis with University of Turin, a project using platformio and zephyr.

I would like to use the Ble Module (SPBTLE-1S) of the STEVAL-MKSBOX1V1 (SensorTile.box) in a zephyr project. This mcu is supported by zephyr, but the .dts file doesn't configure the spi2 interface used by bluetooth.

According with the hardware specs [1], I tried to start from ST BLE sensor project example [2] and configure:

- prj.conf:

CONFIG_BT_SPI=y
CONFIG_BT_HCI=y
CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="SPBTLE-1S"
CONFIG_BT_GATT_CLIENT=y

- app.overlay:

/ {
    chosen {
           zephyr,bt-hci-spi = &zephyr_bt_hci_spi;
           zephyr,bt-hci-spi-slave = &zephyr_bt_hci_spi_slave;
    };
};

&spi2 {
    pinctrl-0 = <&spi2_nss_pd0 &spi2_sck_pd1 &spi2_miso_pd3 &spi2_mosi_pc3>;
    pinctrl-names = "default";
    status = "okay";

    cs-gpios = <&gpiod 0 GPIO_ACTIVE_LOW>;

    zephyr_bt_hci_spi: zephyr_bt_hci_spi@0 {
        compatible = "zephyr,bt-hci-spi";
        reg = <0>;
        irq-gpios = <&gpiod 4 GPIO_ACTIVE_LOW>;
        reset-gpios = <&gpioa 8 GPIO_ACTIVE_LOW>;
        spi-max-frequency = <1000000>;
        label = "SPBTLE-1S";
    };

    zephyr_bt_hci_spi_slave: zephyr_bt_hci_spi_slave@1 {
        compatible = "zephyr,bt-hci-spi-slave";
        reg = <1>;
        irq-gpios = <&gpiod 4 GPIO_ACTIVE_LOW>;
    };
};

Unfortunately, bluetooth isn't enabled correctly and the system hangs up:
in the main.c, the bt_enable waits endlessly, because the function bt_spi_rx_thread of the file https://github.com/zephyrproject-rtos/zephyr/blob/v2.7-branch/drivers/bluetooth/hci/spi.c (line 343) doesn't return, looping in the do-while.

Some infos:
- Zephyr version: 2.7.0
- Sources:
[1] https://www.st.com/resource/en/schematic_pack/steval-mksbox1v1_schematic.pdf : electric schema of the sensortile.box
[2] https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/st_ble_sensor : st ble example project
[3] https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/arm/stm32l562e_dk/stm32l562e_dk_common.dtsi : similar dtsi (SPBTLE-RF module)


Re: Changes to Review Process in Github

David Leach
 

It appears the github notification has changed where it now has the PR author as the person dismissing the stale reviews when pushing an update…

 

From: devel@... <devel@...> On Behalf Of David Leach via lists.zephyrproject.org
Sent: Wednesday, February 23, 2022 7:24 AM
To: anas.nashif@...; devel@...
Subject: Re: [Zephyr-devel] Changes to Review Process in Github

 

Update from GitHub support:

 

GitHub Support (GitHub Support)

Feb 23, 2022, 10:10 AM UTC

Hi David,

Thanks for reaching out to GitHub Support! Sorry for not getting back to you as quickly as we'd like! Please accept my apologies.

We have received a few similar reports of this issue, and the team has been investigating. I've added your report as another data point to our internal issue. While we don’t yet have a specific ETA, we’ll be sure to update you as soon as there’s any news to share.

Feel free to come back to me if there's anything else you need.

Regards,
Peter
GitHub Support

 

 

 

From: devel@... <devel@...> On Behalf Of David Leach via lists.zephyrproject.org
Sent: Friday, February 11, 2022 2:59 PM
To: anas.nashif@...; devel@...
Subject: Re: [Zephyr-devel] Changes to Review Process in Github

 

Just FYI, for reasons unknown, GitHub is attributing the dismissed approved reviews to my account, dleach02. I am not doing this and I have submitted a bug to the GitHub support to get them to look into this.

 

David Leach

 

From: devel@... <devel@...> On Behalf Of Nashif, Anas via lists.zephyrproject.org
Sent: Friday, February 11, 2022 8:42 AM
To: devel@...
Subject: [Zephyr-devel] Changes to Review Process in Github

 

Hit send too fast… fixed subject.

 

From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas


Zephyr Dev Summit - Deadline to Submit March 4

Maemalynn Meanor <maemalynn@...>
 

Members of the Zephyr Community:

This year, we’re hosting the Zephyr Developer Summit on June 8-9 at the Computer History Museum in Mountain View, CA. 

We’re currently accepting speaking proposals in several categories including micro-conferences, presentations, demos and tutorials. We’d love to hear from you - please submit your proposals by next Friday, March 4



We hope to see you there!
Maemalynn

Connect with the Zephyr Project: 
@ZephyrIoT (#ZephyrDevSummit, #ZephyrRTOS)

Maemalynn Meanor
Senior PR Manager
The Linux Foundation 
ELISA, Open Mainframe Project, Zephyr Project
(602) 541-0356
@Maemalynn





Event: Zephyr: Power Management Sync - 02/24/2022 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr: Power Management Sync

When:
02/24/2022
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:


________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,677440320# United States, Orlando
Phone Conference ID: 677 440 320#
 
________________________________________________________________________________


Re: Changes to Review Process in Github

Bolivar, Marti
 

Hi Emil,

In one PR, I was able to use the rebase button from within the GH web UI
to rebase without re-requesting reviews. YMMV.

On Fri, Feb 11 2022, Emil via lists zephyrproject org Gydesen wrote:
Hi Anas,

A question on the feature:

If I rebase a PR without changing the content, does it trigger request for new reviews?

Also a clarification:
The text says "New reviewable commits pushed" - Does that also trigger if you amend an existing commit and push that, or is it only if you add new commits?

Best regards,
Emil Gydesen
Software Developer, Nordic Semiconductor | +4528265669 | emil.gydesen@...
________________________________
From: devel@... <devel@...> on behalf of Nashif, Anas via lists.zephyrproject.org <anas.nashif=intel.com@...>
Sent: Friday, February 11, 2022 15:41
To: devel@... <devel@...>
Subject: [Zephyr-devel] Changes to Review Process in Github


Hit send too fast… fixed subject.



From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.



Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.



For reference, here is the settings screen with the option enabled:



[Graphical user interface, text, application, email Description automatically generated]



This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.



This change will go into effect immediately.



Regards,

Anas





Cancelled Event: Zephyr Project: Dev Meeting - Thursday, February 24, 2022 #cal-cancelled

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, February 24, 2022
8:00am to 9:00am
(UTC-08:00) America/Los Angeles

Where:
Microsoft Teams Meeting

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: Changes to Review Process in Github

David Leach
 

Update from GitHub support:

 

GitHub Support (GitHub Support)

Feb 23, 2022, 10:10 AM UTC

Hi David,

Thanks for reaching out to GitHub Support! Sorry for not getting back to you as quickly as we'd like! Please accept my apologies.

We have received a few similar reports of this issue, and the team has been investigating. I've added your report as another data point to our internal issue. While we don’t yet have a specific ETA, we’ll be sure to update you as soon as there’s any news to share.

Feel free to come back to me if there's anything else you need.

Regards,
Peter
GitHub Support

 

 

 

From: devel@... <devel@...> On Behalf Of David Leach via lists.zephyrproject.org
Sent: Friday, February 11, 2022 2:59 PM
To: anas.nashif@...; devel@...
Subject: Re: [Zephyr-devel] Changes to Review Process in Github

 

Just FYI, for reasons unknown, GitHub is attributing the dismissed approved reviews to my account, dleach02. I am not doing this and I have submitted a bug to the GitHub support to get them to look into this.

 

David Leach

 

From: devel@... <devel@...> On Behalf Of Nashif, Anas via lists.zephyrproject.org
Sent: Friday, February 11, 2022 8:42 AM
To: devel@...
Subject: [Zephyr-devel] Changes to Review Process in Github

 

Hit send too fast… fixed subject.

 

From: Nashif, Anas <anas.nashif@...>
Date: Friday, February 11, 2022 at 9:40 AM
To: devel@... <devel@...>
Subject: Changes to

Hi,

The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github.

 

Specifically, we will be enabling an option that will cause new reviewable commits pushed to a pull-request branch to dismiss existing pull request review approvals and asking reviewers to revisit and re-review the new changes since they last reviewed the PR.

 

For reference, here is the settings screen with the option enabled:

 

Graphical user interface, text, application, email

Description automatically generated

 

This means that you will be asked to re-review changes when new content is being added to a pull-request. Please continue to provide reviews and keep watching for changes and enhancements added to pull-requests as they evolve.

 

This change will go into effect immediately.

 

Regards,

Anas