Date   

Re: Updated Event: Zephyr: Networking Forum #cal-invite

Jukka Rissanen
 

Hi all,

Tuesday (3 Nov) there is a networking forum Teams meeting. Let me know
if there are any network related topic you would like to discuss there
so I can add it to the agenda.


Cheers,
Jukka


Updated Event: Zephyr Project: Dev Meeting #cal-invite

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

Zephyr Project: Dev Meeting

When:
Thursday, 5 November 2020
4:00pm to 5:00pm
(UTC+00:00) UTC
Repeats: Weekly on Thursday

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
 
 
________________________________________________________________________________


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,

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@...> 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&amp;sdata=HLSJWOCIo1bmNd7toN8PiWy4yPKgDoKUSgwu4dc6HMY%3D&amp;reserved=0

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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.zephyrproject.org%2F2.3.0%2Fsamples%2Fapplication_development%2Fout_of_tree_driver%2FREADME.html&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=4qznVND3NnjhnL6oS0evZVz89Uqi0Tk4zIpPycsMX3I%3D&amp;reserved=0 is a little sparse.

How do I include an out of tree sensor driver?

Lawrence King
Principal Developer
Connected Transport Market Unit
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.irdeto.com%2F&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=DuktziXbXA7dDl%2BDxoD5cMHtFNUn0EtQfEKdmMK9SDI%3D&amp;reserved=0
+1(416)627-7302

[1]<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcareers.irdeto.com%2F&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Z8rh2RzZbwZp0PtsYk8Asrn2CALvLKN6B7SRKWNDR3g%3D&amp;reserved=0> [2 - linkedin] <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Firdeto%2F&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=hojClORdOoJtcW8pt162xhoVOkFpDSAlHFdpi4ixj9U%3D&amp;reserved=0> [3 - instagram] <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.instagram.com%2Flifeatirdeto%2F%3Fhl%3Den&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=SBEqwhWg5Wsp2LhpAqZh5JBYbVqaXvF6X0O1shAvBCU%3D&amp;reserved=0> [4 - youtube] <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCwgT0-wMbEqx3qLfrPIEnRg&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=a9wID1YYPeFdVXijSjIDOCdAJJ%2FcAIA7T1md1y%2FQj8o%3D&amp;reserved=0> [6 - facebook] <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FJoinIrdeto%2F&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=urIrDp3t2mZKOMMewzbWZiv6hS3v%2FYg%2FGgNGhkHzL2U%3D&amp;reserved=0> [7] <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FIrdeto%3Fref_src%3Dtwsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor&amp;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659854203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=6rPAMHp%2FoV4OnZlM8rx43YOkNtzFsD60KTLHvTwDi8E%3D&amp;reserved=0>

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.






Adding an out of tree driver

Lawrence King
 

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

https://www.Irdeto.com

+1(416)627-7302

 

1  2 - linkedin  3 - instagram  4 - youtube  6 - facebook  7

            

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:
Tuesday, 3 November 2020
5:00pm to 6:00pm
(UTC+00:00) UTC
Repeats: Weekly on Tuesday

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
 
 
________________________________________________________________________________


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
 


Updated Event: Zephyr: Networking Forum #cal-invite

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

Zephyr: Networking Forum

When:
Tuesday, 3 November 2020
4:00pm to 5:00pm
(UTC+00:00) UTC
Repeats: Monthly on the first Tuesday

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
 
 
________________________________________________________________________________


Updated Event: Zephyr: Toolchain Working Group #cal-invite

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

Zephyr: Toolchain Working Group

When:
Monday, 2 November 2020
4:00pm to 5:00pm
(UTC+00:00) UTC
Repeats: Every 2 weeks on Monday, through Thursday, 17 December 2020

Where:
Microsoft Teams Meeting

Organizer: Maureen Helm

An RSVP is requested. Click here to RSVP

Description:

________________________________________________________________________________
+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,
Thomas

On 10/24/20 3:18 AM, Erwan Gouriou wrote:
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:

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,
Thomas

 


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:

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,
Thomas

 


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,
Thomas

 


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:

  1. SoC header dependency on drivers' configuration is removed (drivers using LL API will be responsible for including the necessary headers)
  2. Only the necessary headers are included
  3. Out of tree applications will also have access to generic LL API headers, making it easier to create multi-series applications using the LL API.
For more details please, check the RFC: https://github.com/zephyrproject-rtos/zephyr/issues/28822

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,
Thomas



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
Embedded Engineer

DATA61 / CSIRO

E Jordan.Yates@...

www.csiro.au