|
TinyCrypt end of life - Help needed
Flavio Ceolin
Hello,
Recently Intel notify us about TinyCrypt end of life because Zephyr is one major project still using it. In order to respond it properly, the Zephyr PSIRT team needs to understand how TinyCrypt is currently used on Zephyr. An initial research shows that only the Bluetooth subsystem depends (exclusively) on this library for hashing and elliptic curves. We need the community feedback to know which other places are using TinyCrypt, which features are being used and finally what is the most constraint platform currently supported that is using TinyCrypt. Based on the answers we will come up with some proposals to mitigate this problem. Regards, Flavio Ceolin
|
|
|
|
Re: Dev-Review Meeting Agenda Sept 30
Bolivar, Marti
We did not have quorum to discuss the labeled issues, so the meeting time was used for v2.7 release preparation.
From: Bolivar, Marti
Sent: Thursday, September 30, 2021 6:55 AM To: devel@... <devel@...> Subject: Dev-Review Meeting Agenda Sept 30
Hi,
Kumar is on vacation, so I'm running today's meeting.
Pinctrl, if we have quorum (we seem to be settling on 37572, but 37621 still has the dev-review tag, so I'm including it):
new pinctrl api
drivers: pinctrl: new state based API proposal
This regulator issue has dev-review but has been postponed for quite some time; we may continue to postpone:
drivers: regulator: convert to gpio_dt_spec
https://github.com/zephyrproject-rtos/zephyr/pull//37689
Martí
|
|
|
|
Event: Zephyr Project: Dev Meeting - 09/30/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Project: Dev Meeting When: Where: 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
________________________________________________________________________________
|
|
|
|
Dev-Review Meeting Agenda Sept 30
Bolivar, Marti
Hi,
Kumar is on vacation, so I'm running today's meeting.
Pinctrl, if we have quorum (we seem to be settling on 37572, but 37621 still has the dev-review tag, so I'm including it):
new pinctrl api
drivers: pinctrl: new state based API proposal
This regulator issue has dev-review but has been postponed for quite some time; we may continue to postpone:
drivers: regulator: convert to gpio_dt_spec
https://github.com/zephyrproject-rtos/zephyr/pull//37689
Martí
|
|
|
|
custom externel module
Omar Morceli
Hi We have added a custom zephyr module in zephyrproject\zephyr\modules The module consists of a static library and Kconfig parameters Module and library worked as expected, but we get warnings in just four parameters of Kconfig: [122/257] Building C object zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj zephyr/misc/generated/configs.c: In function '_ConfigAbsSyms': zephyr/misc/generated/configs.c:56: warning: "CONFIG_TEST_MODEL_TESTNode_sign" redefined 56 | #define CONFIG_TEST_MODEL_TESTNode_sign 101; | In file included from <command-line>: C:/Users/OMAR/zephyrproject/zephyr/samples/bluetooth_models_static_libV1/build/zephyr/include/generated/autoconf.h:46: note: this is the location of the previous definition 46 | #define CONFIG_TEST_MODEL_TESTNode_sign 101 | zephyr/misc/generated/configs.c:57: warning: "CONFIG_TEST_MODEL_sign" redefined 57 | #define CONFIG_TEST_MODEL_sign 0x99; | In file included from <command-line>: C:/Users/OMAR/zephyrproject/zephyr/samples/bluetooth_models_static_libV1/build/zephyr/include/generated/autoconf.h:47: note: this is the location of the previous definition 47 | #define CONFIG_TEST_MODEL_sign 0x99 | zephyr/misc/generated/configs.c:61: warning: "CONFIG_addrs_RSSI_list_SIZE" redefined 61 | #define CONFIG_addrs_RSSI_list_SIZE 50; | In file included from <command-line>: C:/Users/OMAR/zephyrproject/zephyr/samples/bluetooth_models_static_libV1/build/zephyr/include/generated/autoconf.h:51: note: this is the location of the previous definition 51 | #define CONFIG_addrs_RSSI_list_SIZE 50 | zephyr/misc/generated/configs.c:65: warning: "CONFIG_TEST_SRV_MODEL_sign" redefined 65 | #define CONFIG_TEST_SRV_MODEL_sign 0x79; | In file included from <command-line>: C:/Users/OMAR/zephyrproject/zephyr/samples/bluetooth_models_static_libV1/build/zephyr/include/generated/autoconf.h:55: note: this is the location of the previous definition 55 | #define CONFIG_TEST_SRV_MODEL_sign 0x79a thanks
|
|
|
|
Re: Custom driver Power Management in Zephyr
Flavio Ceolin
Hi Srinivasan,
Hi,There are some ways to do this. Which one is better will depend on what you are doing. - You can register a notification with a callback to be called when the system is about suspend/resume and handle your devices there. Be aware of the imposed constraints (IRQ lockeds). See: void pm_notifier_register(struct pm_notifier *notifier) int pm_notifier_unregister(struct pm_notifier *notifier) - If you are implementing the hook to set the SoC state in our application (implementing the method pm_power_state_set(struct pm_state_info info)) you can suspend your devices there are resume them in pm_power_state_exit_post_ops(struct pm_state_info info) Note that in both cases, your application will be called after Zephyr has handled all "know" devices. There are other hacks that you can do, but these two (mainly the first) are the best options IMHO. Regards, Flavio Ceolin
|
|
|
|
Re: Unknown origin of error
markus.prager@...
Thanks for the directions, Jamie. &spi2 {
pinctrl-0 = <&spi2_sck_pb13
&spi2_miso_pb14 &spi2_mosi_pb15>;/*PIN34,PIN35,PIN36*/
cs-gpios = <&gpioc 6 GPIO_ACTIVE_LOW>;/* PC6, Acc_CS */
status = "okay";
};
This is based on the information found in "spi-device.yaml". &spi2 {
lis3dhh: lis3dhh@0 {
compatible = "st,lis3dhh","st,spi_lis3dhh";
status = "okay";
reg = <0>;
label = "LIS3DHH";
spi-max-frequency = <1000000>;
irq-gpios = <&gpioc 7 GPIO_ACTIVE_HIGH>, <&gpioc 8 GPIO_ACTIVE_HIGH>; //INT1, PC7 & INT2, PC8
};
};
int lis3dhh_spi_init(const struct device *dev)
{
struct lis3dhh_data *lis3dhh_drv_data = dev->data;
const struct lis3dhh_config *cfg = dev->config;
const struct lis3dhh_spi_cfg *spi_cfg = cfg->bus_cfg.spi_cfg;
LOG_ERR("config->cs: %p", spi_cfg->spi_conf.cs);
LOG_ERR("config->cs->gpio_dev: %p", spi_cfg->spi_conf.cs->gpio_dev);
lis3dhh_drv_data->hw_tf = &lis3dhh_spi_transfter_fn;
if (spi_cfg->cs_gpios_label != NULL)
{
lis3dhh_drv_data->cs_ctrl.gpio_dev = device_get_binding(spi_cfg->cs_gpios_label);
if (!lis3dhh_drv_data->cs_ctrl.gpio_dev)
{
LOG_ERR("unable to get GPIO SPI CS device");
return -ENODEV; //no such device
}
LOG_DBG("SPI GPIO CS configured on %s:%u", spi_cfg->cs_gpios_label, lis3dhh_drv_data->cs_ctrl.gpio_pin);
}
if (spi_cfg->cs_gpios_label == NULL) {LOG_ERR("spi_cfg cs_gpios_label is NULL");}
return 0;
}
int lis3dhh_init(const struct device *dev)
{
struct lis3dhh_data *lis3dhh_drv_data = dev->data;
const struct lis3dhh_config *cfg = dev->config;
int status;
uint8_t id;
lis3dhh_drv_data->bus = device_get_binding(
cfg->bus_name);
if (!lis3dhh_drv_data->bus)
{
LOG_ERR("master not found: %s", cfg->bus_name);
return -EINVAL; // error: invalid value
}
cfg->bus_init(dev); //spi bus initialization
status = lis3dhh_drv_data->hw_tf->read_reg(
dev, LIS3DHH_REG_WAI,
&id);
if (status < 0)
{
LOG_ERR("failed to read chip id.");
return status;
}
if (id != LIS3DHH_CHIP_ID)
{
LOG_ERR("invalid chip id: %02x (hex)\n", id);
return -EINVAL; // error: invalid value
}
LOG_INF("bus=%s", cfg->bus_name);
status = lis3dhh_drv_data->hw_tf->write_reg(dev, LIS3DHH_CTRL_REG1,
(LIS3DHH_CTRL_REG1_NORM_MODE_EN |
LIS3DHH_CTRL_REG1_IF_ADD_INC |
LIS3DHH_CTRL_REG1_BOOT));
if (status < 0)
{
LOG_ERR("failed to configure ctrl reg 1");
printk("failed to configure ctrl reg 1");
return status;
}
status = lis3dhh_drv_data->hw_tf->write_reg(dev, LIS3DHH_CTRL_REG4, LIS3DHH_CTRL_REG4_ONE_1);
return status;
}
|
|
|
|
Event: Zephyr Project: APIs - 09/28/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Project: APIs When: Where: 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
________________________________________________________________________________
|
|
|
|
API meeting: agenda
Carles Cufi
Hi all,
Agenda for today: - Pinctrl: Now focusing on #37572 as the single PR to target our efforts - PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572 - Updates by Gerard and Kumar on the state of the PR - Discussion, specifically Devicetree layout format: https://github.com/zephyrproject-rtos/zephyr/discussions/35077#discussioncomment-1201394 If you have additional items please let me know. 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://lists.zephyrproject.org/g/devel/calendar https://github.com/zephyrproject-rtos/zephyr/projects/18 Minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|
|
|
Zephyr v2.7.0-rc3
Christopher Friedt
Hi Zephyr community!
Just a heads up that we have tagged v2.7.0-rc3 \o/ [1] At the request of some other community members, I am opting to continue code-naming release candidates, and this one will be codenamed “Math Contest”, for … reasons. There will be one last release candidate before the final v2.7.0 LTS release is made. For this LTS release, we will be doing things slightly differently. Namely, we will * create v2.7-branch * allow merges to main to resume * merge bug-fixes to the v2.7 branch as backports The purpose of this approach is to ensure that merging new features and enhancements can continue even while the final v2.7.0 LTS release stabilizes. All changes targeting Zephyr v2.7 (LTS) need to be submitted to the main branch and marked with the backport v2.7-branch label. A bot will create a backport pull-request when the changes are merged into the main branch. In case a change only targets the LTS release, it must be submitted against the v2.7-branch. Please note, that there may be some selectivity about backporting fixes to v2.7-branch. Specifically, we cannot backport any fixes that may introduce any additional risk or instability. Thanks for your patience and we hope to see some incredible features in main again soon! C Respect and enjoy the peace.[1] https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.7.0-rc3
|
|
|
|
Event: Zephyr Memory Footprint - biweekly discussion - 09/27/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Memory Footprint - biweekly discussion When: Where: 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 meetingOr call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
______________________________
|
|
|
|
Re: Zephyr Memory Footprint - biweekly discussion
Rob Woolley
I don’t have any agenda items for today. I propose that we cancel today's meeting and meet in 2 weeks.
I have put together a proposed agenda for October 4th to follow up on the items we have discussed: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit# Additional agenda items are warmly welcomed. Have a great day, Rob -----Original Appointment----- From: devel@... Group <devel@...> Sent: April 16, 2021 4:15 PM To: devel@... Group Subject: Zephyr Memory Footprint - biweekly discussion When: Occurs every 2 week(s) on Monday effective 2021-04-26 from 3:00 PM to 4:00 PM (UTC-05:00) Eastern Time (US & Canada). Where: Microsoft Teams Meeting 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 ( https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWNkNzZmOGMtMjExZC00ODEwLWI5OTktMTg1MjMyZDk1NjBk%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 ) Or call in (audio only) +1 321-558-6518,,546018126# ( tel:+13215586518,,546018126# ) United +States, Orlando Phone Conference ID: 546 018 126# Find a local number ( https://dialin.teams.microsoft.com/325d775d-c910-441e-90d0-353ebaa56cdd?id=546018126 ) | Reset PIN ( https://mysettings.lync.com/pstnconferencing ) Learn More ( https://aka.ms/JoinTeamsMeeting ) | Meeting options ( https://teams.microsoft.com/meetingOptions/?organizerId=841a7c92-7816-4faf-9887-5e334e88f6d8&tenantId=af0096d9-700c-411a-b795-b3dd7122bad2&threadId=19_meeting_NWNkNzZmOGMtMjExZC00ODEwLWI5OTktMTg1MjMyZDk1NjBk@thread.v2&messageId=0&language=en-US ) ______________________________ ______________________________ ____________________
|
|
|
|
Cancelled Event: Zephyr Project: Dev Meeting - Thursday, September 23, 2021
#cal-cancelled
devel@lists.zephyrproject.org Calendar <noreply@...>
Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Where: 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
________________________________________________________________________________
|
|
|
|
19 Coverity issues
Christopher Friedt
We currently have 19 coverity issues, so please ensure that any issues
assigned to you are fixed in the near term. https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aopen+is%3Aissue+label%3ACoverity
|
|
|
|
Re: Attn: Maintainers - LTS Release Notes v2.7.0
Christopher Friedt
For any strictly new maintainers, feel free to request to join the
maintainers team on GitHub. Thanks to Erwan for the reminder. https://github.com/orgs/zephyrproject-rtos/teams/maintainers/members On Wed, Sep 22, 2021 at 12:56 PM Christopher Friedt <chrisfriedt@...> wrote: Also, I would like to welcome the following new / added maintainers
|
|
|
|
Attn: Maintainers - LTS Release Notes v2.7.0
Christopher Friedt
Hi everyone!
It's that time of the release cycle, and I would like to invite all maintainers to make PR's for the v2.7.0 LTS release notes [1]. There have been a number of additions already [2] so thanks to those who have already made changes. For reference, please have a look at previous release notes [3]. This release cycle is undoubtedly the largest ever. As such, I expect that the release notes will be quite extensive, so please ensure that you have sufficient time to make the necessary changes. Also, I would like to welcome the following new / added maintainers since v2.6.0. * Stephanos Ioannidis, C Library, CMSIS-DSP Integration, C++ * Robert Lubos, Networking * Felipe Neves, Espressif Platforms * Glauber Maroto Ferreira, Espressif Platforms * Mulin Chao, Nuvoton_NPCX Platforms * Jun Lin, Nuvoton_NPCX Platforms * Wealian Liao, Nuvoton_NPCX Platforms * Enjia Mai, Intel Platforms (X86) * Tomasz Bursztyka, Drivers: PTP Clock * David Leach, NXP Platforms * Ryan Erickson, Drivers: Modem Please excuse me if I have forgotten anyone. Thank you for all of your contributions! C [1] doc/releases/release-notes-2.7.rst [2] https://docs.zephyrproject.org/latest/releases/release-notes-2.7.html [3] https://docs.zephyrproject.org/latest/releases/index.html
|
|
|
|
Minimum required Zephyr SDK version update to 0.13.1
Stephanos Ioannidis
Hi all,
The Zephyr SDK 0.13.1 will be required to build the Zephyr main branch after #38733 is merged (to be merged in a day or so).
Please download and install the Zephyr SDK 0.13.1 from the following link: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.13.1
Regards,
Stephanos
|
|
|
|
Event: Zephyr Project: APIs - 09/21/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Project: APIs When: Where: 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
________________________________________________________________________________
|
|
|
|
Re: API meeting: Agenda
Carles Cufi
Additional item, as per the Stable API Change procedure:
toggle quoted messageShow quoted text
- RFC: API Change: IPM - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/38609 - PR: https://github.com/zephyrproject-rtos/zephyr/pull/38523 Carles
-----Original Message-----
|
|
|
|
Re: API meeting: Agenda
Carlo Caione
On 20/09/2021 22:07, Carles Cufi wrote:
Hi all,Hey Carles, can we talk about https://github.com/zephyrproject-rtos/zephyr/issues/38609 as well? Thank you, -- Carlo Caione
|
|
|