Date   

New default BLE Link Layer

Carles Cufi
 

Hi all,

With the merge of PR #15781, the new "split" Link Layer is now the default for BLE-enabled applications. Extensive development and testing effort has gone into this feature, but there might be regressions that have slipped through the testing procedures. Please open issues on GitHub if you come across any issues when testing your applications with it.
You can revert back to using the previous Link Layer by enabling the CONFIG_BT_LL_SW_LEGACY Kconfig option.

https://github.com/zephyrproject-rtos/zephyr/pull/15781

Thank you to everybody involved in this feature for making it happen. New features that were not possible to implement with the old architecture will now slowly start coming to the new Link Layer.

Regards,

Carles


Re: One Questions about ZephyrOS

Jennifer M Williams
 

Welcome to Zephyr, @"Explorer! Thanks for the question – others can provide their feedback and suggestions, too. Can you elaborate on the middleware support you found was lacking? It might help to know more about your requirements.

 

Re: new to Zephyr - Have you had a chance to check out the Getting Started Guide and Application Developers Guide? There are also many Samples and Demos for a variety of supported boards.

 

Cheers!

 

From: devel@... <devel@...> On Behalf Of "Explorer
Sent: Friday, July 19, 2019 6:34 PM
To: devel <devel@...>
Subject: [Zephyr-devel] One Questions about ZephyrOS

 

Hi, 

 

I am MCU development guy and I am new to Zephyr OS, do not know if a good place to mail here, pls just ignore it if this mail is not proper to be here. 

 

I want to know if Zephyr can have a good way to seperate Driver & Kernel  and Application development in an product development lifetime?  Linux is a good example as it support elf-loader and standard Driver & Kernel model.

 

My reason:   

    High performance MCU, not MPU (Cortex M7 and 64-bit RISC-V based , STM32F7, NXP i.MX RT1052 ) , they are are becoming popular, so there are much more software development work should be done on these MCU, while there is little elegant open source RTOS with mature middleware to support such kind of high-performance MCU development.  

     eCos and  uCLinux are  maybe good but these projects are nearly dead , the popolar uCOS or FreeRTOS are just too light-weight (lack of middlerware supported). 

     If application development and low-level driver can be seperated and standarized, maybe there will be lots of  middleware can port from Linux ecosystem and ZephyrOS can benifit from it.

 

Do not know if i am right, correct me if i am wrong~

 

-------

B.R.

RockC


One Questions about ZephyrOS

"Explorer
 

Hi, 

I am MCU development guy and I am new to Zephyr OS, do not know if a good place to mail here, pls just ignore it if this mail is not proper to be here. 

I want to know if Zephyr can have a good way to seperate Driver & Kernel  and Application development in an product development lifetime?  Linux is a good example as it support elf-loader and standard Driver & Kernel model.

My reason:   
    High performance MCU, not MPU (Cortex M7 and 64-bit RISC-V based , STM32F7, NXP i.MX RT1052 ) , they are are becoming popular, so there are much more software development work should be done on these MCU, while there is little elegant open source RTOS with mature middleware to support such kind of high-performance MCU development.  
     eCos and  uCLinux are  maybe good but these projects are nearly dead , the popolar uCOS or FreeRTOS are just too light-weight (lack of middlerware supported). 
     If application development and low-level driver can be seperated and standarized, maybe there will be lots of  middleware can port from Linux ecosystem and ZephyrOS can benifit from it.

Do not know if i am right, correct me if i am wrong~

-------
B.R.
RockC


VB: Zephyr 2.0 Release - important information & dates

Glaropoulos, Ioannis
 

Hi Zephyr developers!

Polite reminder that the merge window for the Zephyr 2.0 release will remain open for three weeks more, until Friday August 9th.  Any new features or enhancements to be included in the Zephyr 2.0 release must be pushed to master by the feature freeze deadline. If you are working on such features, please, submit your pull-requests in good time, to have them properly reviewed, revised and merged before August 9.

 

Thanks!

 

Ioannis Glaropoulos

 

Från: Glaropoulos, Ioannis
Skickat: den 27 juni 2019 17:26
Till: devel@...
Ämne: Zephyr 2.0 Release - important information & dates

 

Hi Zephyr developers,

 

The next major Zephyr release, 2.0, is scheduled for Friday, 30 August 2019.

 

We are now in the development phase for 2.0; merge window is open for all features until feature freeze, which is scheduled for Friday 9 August, 2019. This is in 6 weeks from today. Major features should, ideally, be up for review by mid-July 2019.

 

Any new features / enhancements to be included in the Zephyr 2.0 release must be pushed to master by the feature freeze deadline. If you are working on such features / enhancements, please, submit your pull-requests in good time, to have them properly reviewed, revised and merged before August 9.

 

After feature freeze only bug-fixes, documentation and stabilization-related updates may be merged; the merge window will remain closed until the release date.

 

 

More details can be found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management

 

Roadmap: https://github.com/zephyrproject-rtos/zephyr/projects/9

 

Thanks in advance for all your contributions!

 

Ioannis Glaropoulos


Re: Name of new Driver API

Carles Cufi
 

Hi Tom,

 

Thanks for asking here, we can also have a quick vote in the API call next week if you can attend.

 

RTIO, with an rtio_ prefix being used in the code, sounds sensible to me, +1 on the name.

 

Regards,

 

Carles

 

From: devel@... <devel@...> On Behalf Of Tom Burdick via Lists.Zephyrproject.Org
Sent: 09 July 2019 19:07
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Name of new Driver API

 

Hi Zephyr Devs,

 

I've been working on an updated driver API that intends to encompass a wide array of devices including sensors and some signal output devices. Very similar in nature to what Linux provides in its IIO driver API. The intention is create a way of efficiently moving and processing streams of data in a DMA friendly way on small devices.

 

I started off with the name ZIO as an abbreviation of Zephyr IO, quickly realizing that Linux had a similar in purpose driver API already written for it. I thought this was a large enough conflict in naming to warrant renaming things.

 

 

I've since been using the prefix of RTIO, short for Real-Time IO, which I think very much relates to what I'm doing. I've already gotten some positive feedback from a fellow zephyr developer on the name but I think its important the wider community has their say.

 

I don't think the name sensor really helps to encompass what this API does in its entirety, or its goals. I do think something along the lines of IO is appropriate. Real-Time IO does better encompass what it does in my opinion.

 

I'd like the communities opinion on this name, and if you are not thrilled with it, one good name suggestion.

 

Any new suggested names should be short, there's an 80 character line limit after all and much that needs to go to non-prefix stuff.

 

I'm happy to go with what the community feels is a good name. But again, I do not think sensor/sensor2/etc would really do what this is justice. It would pigeon hole the work.

 

Thanks!

 

Tom

 

 


Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 18 July 2019 #cal-cancelled

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

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 18 July 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles

Where:
https://zoom.us/j/993312203

Organizer:
devel@...

Description:
Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        +1 877 369 0926 US Toll-free
        +1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf


Upcoming Event: Zephyr Project: APIs - Tue, 07/16/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 16 July 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY


 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing


API meeting: Agenda

Carles Cufi
 

Hi all,

While a lot of folks are off on vacation, there are a few items pending discussion.

Agenda:

- New proposal: RFC for driver-specific APIs
- GPIO: Update on progress, discussion on function naming
- Sensor API: Update on progress if contributors present

Additional items in the "Triage" column in the GitHub project may be discussed if time permits.
If you want an item included in the meeting, please add it to the GitHub project.

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


PWM as a buzzer tone generator

Alexey Papkovskiy <alexey.papkovskiy@...>
 

Hi,

I try to use PWM to drive a buzzer. But it seems impossible now (version 14.0) to change the PWM period for tone changing. I just call pwm_pin_set_usec() to set period and pulse width, but it works only once.

Best,
Alexey Papkovskiy


Upcoming Event: Zephyr Project: Dev Meeting - Thu, 07/11/2019 8:00am-9:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 11 July 2019, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/993312203

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        +1 877 369 0926 US Toll-free
        +1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf


Summer 2019 Zephyr Project Newsletter

Zephyr Project
 

Welcome to the Zephyr Project Newsletter! As the Zephyr community continues to grow and innovate we've added this update to the list of resources and tools available to our ecosystem to stay connected. In this edition, we are excited to bring you updates on what's in store for ZephyrOS this summer and fall, provide a glimpse into some of the work currently underway in the community and share ways you can get involved in the Zephyr Project. 

 

About the Zephyr Project

Zephyr Project Welcomes it's 500th Contributor!

Community is core to a successful open source project. In addition to improving and expanding the code base, a vibrant and diverse community brings new perspectives, energy and opportunity. Over the last year the Zephyr community has grown dramatically and the project is stronger because of these new voices. This month, the Zephyr Project is thrilled to welcome it's 500th contributor. On behalf of the entire community, we would like to welcome each and every one of the new contributors. 

If you are interested in joining the Zephyr Project as a member or contributor please reach out. We are here to help.
How to Contribute
Become a Member

The Zephyr Project Announces Major Technical Milestone with Release of Zephyr OS 1.14 LTS. 

Earlier this spring, Zephyr Project introduced the first long term support (LTS) release of Zephyr OS, Zephyr 1.14.0 LTS. This release is an important technical milestone for the community and is intended to be a more stable, certifiable option for product makers and developers. Major enhancements include:
  • Support for over 160 different board configurations spanning 8 architecture configurations. 
  • Enhancement of the native POSIX port by adding UART, USB, and display drivers. Based on this port, we added a simulated NRF52832 SoC which enables running full system, multi-node simulations, without the need of real hardware.
  • Application of MISRA-C code guideline on the kernel and core components of Zephyr. 
  • Addition of an experimental BLE split software Controller with Upper Link Layer and Lower Link Layer for supporting multiple BLE radio hardware architectures.
  • Introduction of the west tool for management of multiple repositories and enhanced support for flashing and debugging.
  • Support for the x86_64 architecture. It is currently implemented only for QEMU targets, supports arbitrary numbers of CPUs, and runs in SMP mode by default, our first platform to do so.
  • Added support for application user mode, application memory partitions, and hardware stack protection in ARMv8m
This release marks the culmination of one of the largest and most ambitious efforts undertaken by the Zephyr Project to date. This release would not have been possible without the hard work and skill of the 250 developers who contributed code over the last 6 months. Read more here.
Get Zephyr OS

Winners of Zephyr OS 1.14 LTS Bug Fixing Contest Announced

As part of the celebration of the ZephyrOS 1.14 LTS release the TSC hosted their first ever bug fixing contest. Sponsored by Zephyr Project member NXP, this contest awarded an i.MX RT1050 to eligible developers who helped close bugs and issues in this release. We are thrilled to announce the winners of the contest: Jukka Rissanen, Vikrant More, Aaron Tsui and Tavish Naruka. We thank you for your contributions to the Zephyr Project! Enjoy the boards and happy hacking!

Products Powered by ZephyrOS

The Zephyr Project is proud to promote the incredible products and services created by our community of product makers, innovators and entrepreneurs. If you would like to have your product featured in the Zephyr Quarterly newsletter please contact us.
 

The HiFive1 Rev B is Here

HiFive1 Rev B is an upgrade to SiFive's low-cost development board featuring the Freedom E310. It’s the best way to start prototyping and developing your RISC‑V applications. Order yours today.


Laird Connectivity Pinnacle 100

Laird Connectivity has a new multi-wireless modem that combines the advantages of low-power cellular LTE connectivity and Bluetooth 5 technology into an integrated solution. This unique combination allows new use cases employing low-cost, long-range Bluetooth sensors all attached to the next generation LTE network in simpler and less costly solution architecture.

 

hereO CORE

hereO Core is the world's first plug and play IoT platform developed from the ground up for companies looking to smarten up their consumer product offerings and mobile assets.

 

Ruuvi Node

Developed by Finnish open-source electronics specialist, Ruuvi Innovations, the Ruuvi Node is a highly robust, maintenance-free, 100 per cent open-source node solution that combines a Nordic Semiconductor nRF9160 System-in-Package (SiP) cellular IoT module and an ultra-low power Nordic nRF52840 multi-protocol Bluetooth System-on-Chip (SoC).

Phantom ELDA

Phantom's End-device Level Distributed Automation (ELDA) is a Bluetooth LE home automation system which allows wall switches to wirelessly control lights in mesh network. The system uses two devices employing Nordic’s nRF52832 SoC for mesh networking between wall switch and LED drivers. Learn more here.

Zephyr Project Face to Face Meeting Brings Together Community for Strategic Planning

With the successful release of ZephyrOS 1.14 LTS complete it is now time for the community to begin looking ahead to what's next for Zephyr Project. In addition to safety certifications, the Zephyr Project is currently working towards:

  • Improving our processes and transparency
  • Revamping our website and online presence
  • The release of Zephyr 2.0 and Zephyr 1.14.1
  • Enabling product makers and users through guides and training materials

Thank you to the team at Intel for hosting this incredible, intensive 3 day workshop. You can read the full recap of the event in this blog by Zephyr Project Board Chairperson Amy Occhialino (Intel).

A Message From Linux Foundation Strategic Programs Director Kate Stewart: Welcome New Zephyr Project Leadership

The Zephyr Project would like to extend a warm welcome to the following contributors who have taken leadership roles within the community.  
  • Maureen Helm (NXP) TSC Chairperson
  • Mark Merizan (Intel) Marketing Committee Chairperson
  • David Brown (Linaro) Security Architect
  • Flávio Ceolin (Intel) Security Chair
  • Amber Hibberd (Intel) Interim Safety Chair
We would like to thank Anas Nashif (Intel) for his service to the community as TSC Chairperson from 2016 - 2019, Andy Gross (Linaro) for his work as the Security Chairperson and Ebba Simpson (Linaro) for her leadership as the Chairperson of the Marketing Committee. Thank you! 

New Developer Guides and Resources

RISC-V Getting Started Guide

The RISC-V Getting Started Guide shows users how to get started developing for the free and open RISC-V ISA. The Guide focuses on running Zephyr and Linux – on popular RISC-V platforms with minimum effort. Learn more here.
 
The Bluetooth LE Developer Study Guide is the perfect way to learn about Bluetooth LE, GATT and GAP and Zephyr with hands-on experience. Download the Bluetooth LE Developer Study Guide today and get coding with Zephyr and Bluetooth! Learn more here.
 
Thank you to our friends at Fit IoT-Lab for sharing a fantastic guide with the community that shows users how to quickly setup a Zephyr development environment and how to compile a Zephyr firmware.
 
Antmicro has recently released Renode 1.7 and 1.7.1, one of the largest updates yet of the open source multi-node simulation framework that has been gaining popularity in both the RISC-V ecosystem and Zephyr Project.
 

The Zephyr Project Technical Newsletter

Back by popular demand, we are thrilled to share the latest changes and ongoing initiatives within the Zephyr repos in this monthly recap published by Marti Bolivar (Nordic Semiconductors). View the May and June updates.
 

Upcoming Events 

For the full listing of events, workshops and speaking engagements, please visit our event page.

Get Involved


Zephyr Project is a diverse and inclusive community dedicated to building a vendor neutral ecosystem around Zephyr OS. We welcome contributions of all types as we build a truly open source RTOS to meet the needs of developers and users inventing, building and connecting the Internet of Things. Join us.
Join the Slack Channel
Contribute to Zephyr OS
Contact Us
LinkedIn
Twitter
Website
YouTube
GitHub
Copyright © 2019 Zephyr Project, All rights reserved.

Our mailing address is:
1 Letterman Drive
Building D, Suite D4700
San Francisco, CA 94129
Phone/Fax: +1 415 723 9709
https://www.linuxfoundation.org/

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

 






This email was sent to devel@...
why did I get this?    unsubscribe from this list    update subscription preferences
Zephyr Project · 1702 Bauerle Ave · Austin, TX 78704-3304 · USA

Email Marketing Powered by Mailchimp


Re: Zephyr kernel compatibility with POSIX standard

Nashif, Anas
 

Gabrielle,

Right now Zephyr only supports a subset of the POSIX embedded profile (PSE52). It will depend on your application needs and the level of POSIX support your application depends on.

 

Anas

 

From: <devel@...> on behalf of Gabriele Morgante <gabriele.morgante@...>
Date: Wednesday, 10 July 2019 at 06:49
To: "devel@..." <devel@...>
Subject: [Zephyr-devel] Zephyr kernel compatibility with POSIX standard

 

Hi,

we are interested to know the compatibility degree of Zephyr kernel with the POSIX standard.

For instance, could we execute a C program POSIX compliant, written for an x86 linux kernel, on a Zephyr board as a Zephyr Application?

Thanks, regards!


Zephyr kernel compatibility with POSIX standard

Gabriele Morgante <gabriele.morgante@...>
 

Hi,

we are interested to know the compatibility degree of Zephyr kernel with the POSIX standard.

For instance, could we execute a C program POSIX compliant, written for an x86 linux kernel, on a Zephyr board as a Zephyr Application?

Thanks, regards!


Name of new Driver API

Tom Burdick
 

Hi Zephyr Devs,

I've been working on an updated driver API that intends to encompass a wide array of devices including sensors and some signal output devices. Very similar in nature to what Linux provides in its IIO driver API. The intention is create a way of efficiently moving and processing streams of data in a DMA friendly way on small devices.

I started off with the name ZIO as an abbreviation of Zephyr IO, quickly realizing that Linux had a similar in purpose driver API already written for it. I thought this was a large enough conflict in naming to warrant renaming things.


I've since been using the prefix of RTIO, short for Real-Time IO, which I think very much relates to what I'm doing. I've already gotten some positive feedback from a fellow zephyr developer on the name but I think its important the wider community has their say.

I don't think the name sensor really helps to encompass what this API does in its entirety, or its goals. I do think something along the lines of IO is appropriate. Real-Time IO does better encompass what it does in my opinion.

I'd like the communities opinion on this name, and if you are not thrilled with it, one good name suggestion.

Any new suggested names should be short, there's an 80 character line limit after all and much that needs to go to non-prefix stuff.

I'm happy to go with what the community feels is a good name. But again, I do not think sensor/sensor2/etc would really do what this is justice. It would pigeon hole the work.

Thanks!

Tom



Upcoming Event: Zephyr Project: APIs - Tue, 07/09/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 9 July 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY


 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing


API meeting agenda for 9 Jul 2019

Maureen Helm
 

API meeting agenda for 9 Jul 2019:

  • Sensors (Maureen/Kevin/Tom)

 

Discussion is postponed on the following. Please review and submit feedback in GitHub before next week:

  • GPIO #15611 (Piotr M)
  • Driver-specific functions #17072 (Peter B)

 

Additional items in the "Triage" column in the GitHub project may be discussed if time permits.

If you want an item included in the meeting, please add it to the GitHub project.

 

https://github.com/zephyrproject-rtos/zephyr/projects/18

 


Upcoming Event: Zephyr Project: APIs - Tue, 07/02/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 2 July 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY


 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing


DTS deprecated defines

Kumar Gala
 

All,

We’ve made some recent changes to DTS generated defines to make this more consistent:

* _GPIO_ and _PWM_ defines are now _GPIOS_ and _PWMS_ (to match the property in dts)
* LED/SW defines used in samples are now DT_ALIAS_ prefixed

As such we are marking the old defines as deprecated. Its possible that some driver or sample got missed, so please let me know or submit a PR to fixup any such cases.

Here’s the PR that will mark the old style defines as deprecated:

https://github.com/zephyrproject-rtos/zephyr/pull/17254

Thanks

- k


Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 4 July 2019 #cal-cancelled

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

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 4 July 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles

Where:
https://zoom.us/j/993312203

Organizer:
devel@...

Description:
Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        +1 877 369 0926 US Toll-free
        +1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf


Re: nrf52 hw pwm 1 enabled and compile failed on sample code #builds #ninja

lairdjm
 

Hi Jeremy

The reason is that hardware is static and defined as part of the device tree, so for the nRF52840 this will be in the boards\arm\nrf52840_pca10056 directory and is nrf52840_pca10056.dts, if you open this file in a text editor and search for PWM you will find this code:

&pwm0 {

                status = "ok";

                ch0-pin = <13>;

                ch0-inverted;

};

There is no pwm1 section, so to utilise a second PWM channel you would need to create another section for it named &pwm1.

Thanks,
Jamie

1941 - 1960 of 8033