|
Updated Event: Zephyr Project: Dev Meeting
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
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
________________________________________________________________________________
|
|
|
|
Zephyr Project: Dev Meeting - Thu, 10/29/2020 3:00pm-4:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 29 October 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 Oct 28
Kumar Gala
Here’s the agenda topics for this week:
* samples: drivers: adc: add demo and fix STM32 sequence configuration: - https://github.com/zephyrproject-rtos/zephyr/pull/25590 * Any PR/issues w/dev-review tag https://github.com/zephyrproject-rtos/zephyr/labels/dev-review * Any topics anyone else has. - k
|
|
|
|
Re: [Zephyr-users] Adding an out of tree driver
Bolivar, Marti
Hi,
toggle quoted messageShow quoted text
You should just need to add it to the build system's Kconfig and CMakeLists.txt hierarchy like any other file in your module. There are worked examples in https://github.com/nrfconnect/sdk-nrf/tree/master/drivers. HTH, Martí "Lawrence King via lists.zephyrproject.org" <lawrence.king=irdeto.com@lists.zephyrproject.org> writes:
Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.zephyrproject.org%2Flatest%2Fapplication%2Findex.html%23boards&;amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659844236%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HLSJWOCIo1bmNd7toN8PiWy4yPKgDoKUSgwu4dc6HMY%3D&reserved=0
|
|
|
|
Adding an out of tree driver
Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here: https://docs.zephyrproject.org/latest/application/index.html#boards
Now I want to do the same for my_custom_sensor_driver. Is there a variable I can set (like SENSOR_ROOT) that will find my out of tree sensor driver? Unfortunately the documentation at https://docs.zephyrproject.org/2.3.0/samples/application_development/out_of_tree_driver/README.html is a little sparse.
How do I include an out of tree sensor driver?
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.
|
|
|
|
Updated Event: Zephyr Project: APIs
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
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
________________________________________________________________________________
|
|
|
|
Zephyr Project: APIs - Tue, 10/27/2020 4:00pm-5:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 27 October 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
Carles Cufi
Hi all,
Agenda for today. - Kernel headers - PR: https://github.com/zephyrproject-rtos/zephyr/pull/29359#issuecomment-713598116 - API and component naming conventions - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/29569 and then, time permitting we'd like to follow-up on pinctrl: - Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748 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
|
|
|
|
Updated Event: Zephyr: Networking Forum
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr: Networking Forum When: Where: Organizer: tsc@... An RSVP is requested. Click here to RSVP Description: Live Agenda/Minutes: https://docs.google.com/document/d/1qFsOpvbyLzhflJbbv4Vl__497pKHDoUCy9hjAveyCX0/edit?usp=sharing
Shared Folder: https://drive.google.com/drive/folders/1j6d0FLeOjiMil1Ellb59AsfHdzuWdAAc?usp=sharing ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 458 216 365#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Updated Event: Zephyr: Toolchain Working Group
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr: Toolchain Working Group When: Where: Organizer: Maureen Helm An RSVP is requested. Click here to RSVP 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
________________________________________________________________________________
|
|
|
|
Re: Runtime pin remapping on STM32F103
Thomas Hobson <thomas@...>
Hi, The use case is for this is could be considered as a intelligent GPIO expander for a much larger project, which offloads peripheral tasks to this chip, but so far GPIO/PWM/ADC has been the most problematic We would have a pin, say A1 which could be mapped to GPIO or PWM by someone unplugging say a button, and plugging in a servo, running a few commands on the chip and it should be ready to control the servo. Only 5 of the pins need ADC connection, and
there are only 8 different combinations of pin "types" I should
need to support, with the majority being GPIO input with various
different pull up/down and callback configurations. My problem only arises when I want to switch the pin between, as stated before, a button and a servo where I need to switch between GPIO and PWM. There are a total of 10 pins I should be controlling, A1-A5 - GPIO/PWM and B1-B5 - GPIO/PWM/ADC.
Hopefully that sums up my use case. Thanks,
On 10/24/20 3:18 AM, Erwan Gouriou
wrote:
|
|
|
|
Re: Runtime pin remapping on STM32F103
Erwan Gouriou
Hi Thomas, Would you mind giving us some details on your use case ? Do you expect to be able to change only the affectation of the pin and apply preconfigured settings ? For instance PIN X is: ALT FUNC 5, pull up, open drain for PWM Analog for ADC Input when GPIO And then you switch between those config in the application? Or do you expect to be able to be able to program the pin at run time to any kind of function ?
On Fri, 23 Oct 2020 at 15:07, Carles Cufi <carles.cufi@...> wrote:
|
|
|
|
Re: Runtime pin remapping on STM32F103
Carles Cufi
Hi Thomas,
This is currently not possible, but under active discussion: https://github.com/zephyrproject-rtos/zephyr/issues/11918
Carles
From: devel@... <devel@...>
On Behalf Of Thomas Hobson via lists.zephyrproject.org
Sent: 23 October 2020 12:16 To: devel@... Subject: [Zephyr-devel] Runtime pin remapping on STM32F103
Hi, I'm looking for how I would switch a physical pin between ADC, PWM and GPIO, all without the chip being reprogrammed. I have found pinmux, but I can't tell exactly what it does as documentation is lacking.
Thanks a bunch,
|
|
|
|
STM32: Generic HAL LL API headers
Gerard Marull Paretas
To all STM32 users and developers, We're in the final step of reviewing the following PRs:
The aim of these changes is to improve the usage of STM32 LL HAL in both Zephyr drivers and out-of-tree applications by providing generic LL API headers. These generic headers are auto-generated and stored in the STM32 HAL repository. They just include the right series header depending on what SoC is being used in the Zephyr build, so there is no actual abstraction involved. Some advantages of this approach include:
I would like to highlight that these headers are an additional way of using the LL API, so existing code will not be affected. In-tree drivers will be gradually moved to the generic LL headers. Additional reviewers are welcome! Regards, Gerard Gerard Marull-Paretas Teslabs Engineering S.L. teslabs.com T. +34 622 321 312 CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
|
|
|
|
Runtime pin remapping on STM32F103
Thomas Hobson <thomas@...>
Hi, I'm looking for how I would switch a physical pin between ADC, PWM and GPIO, all without the chip being reprogrammed. I have found pinmux, but I can't tell exactly what it does as documentation is lacking.
Thanks a bunch,
|
|
|
|
Zephyr Project: Dev Meeting - Thu, 10/22/2020 3:00pm-4:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 22 October 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 Oct 22
Kumar Gala
Here’s the agenda topics for this week:
* [RFC]: Macro for defining file system API with default function assigned: - https://github.com/zephyrproject-rtos/zephyr/pull/29396 * Revert "shell: support floating point output..." https://github.com/zephyrproject-rtos/zephyr/pull/29203 * Any PR/issues w/dev-review tag https://github.com/zephyrproject-rtos/zephyr/labels/dev-review * Any topics anyone else has. - k
|
|
|
|
Zephyr SDK 0.12.0-beta-1 available for testing
Kumar Gala
Hi,
Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-beta-1 Please download and try things out and report any issues. Please report issues here: https://github.com/zephyrproject-rtos/sdk-ng/issues Known issues (these are on the Zephyr side): * some xtensa platforms may need updating w/regards to Zephyr & Xtensa HAL [ https://github.com/zephyrproject-rtos/zephyr/pull/23142 ] * known issue with arm64 and linking C++ & newlib: [ https://github.com/zephyrproject-rtos/zephyr/issues/28650 ] Changes since the last release (alpha-1): • Fix for running SDK on CentOS • change to install scripts to allow automated install • RiscV PMP fixes backported from upstream qemu • Bossa support for SAM4L - k
|
|
|
|
RFC: API Change: Bluetooth: Update indication callback parameters
Jordan Yates
Hi All,
I am proposing an update to the callback signature of the Bluetooth GATT indication function.
This change would bring the callback in-line with the other GATT callbacks (read, write, notify) by providing the original parameter struct as an argument.
Cheers,
Jordan Yates DATA61 / CSIRO E Jordan.Yates@... www.csiro.au
|
|
|
|
Re: zephyr: Getting GPIOs from DTS file without aliases
Kumar Gala
Can you do:
toggle quoted messageShow quoted text
grep DT_N_NODELABEL zephyr/include/generated/devicetree_unfixed.h - k
On Oct 20, 2020, at 1:22 PM, Hiremath, Vijay P <vijay.p.hiremath@intel.com> wrote:
|
|
|
