|
Re: How to build external drivers
Sebastian Boe
Yes,
you can add out-of-tree directories that contain CMakeLists.txt files that define zephyr libraries (like drivers), by doing west build -b board_name . -- -DZEPHYR_EXTRA_MODULES<path_to_driver> ________________________________________ From: devel@... <devel@...> on behalf of Joris Offouga via Lists.Zephyrproject.Org <offougajoris=gmail.com@...> Sent: Thursday, September 5, 2019 5:39:37 PM To: devel@... Cc: devel@... Subject: [Zephyr-devel] How to build external drivers Hi all, How to build external drivers with zephyr, like board with example : west build -b board_name . -- -DBOARD=board_name -DBOARD_ROOT=<path_to_board>. is there a similar command for drivers? Best regards, Joris Offouga -- Best Regards, Joris Offouga
|
|||||||||||||
|
|
|||||||||||||
|
How to build external drivers
Hi all,
How to build external drivers with zephyr, like board with example : west build -b board_name . -- -DBOARD=board_name -DBOARD_ROOT=<path_to_board>. is there a similar command for drivers? Best regards, Joris Offouga -- Best Regards, Joris Offouga
|
|||||||||||||
|
|
|||||||||||||
|
Re: Dev-Review Meeting Agenda (Sept 5)
Peter A. Bigot
Discussing individual issues doesn't seem like an effective use of time, though discussing how issue assessments can be done offline and reviewed in summary form might be helpful.
But I'd like to get an understanding of what's going to be in 2.1 first. E.g. updated GPIO is, updated controlled delay (timeout) API is. Pinmux? Other API changes? Devicetree improvements? Knowing the overall vision of how 2.1 improves the life of Zephyr users would impact what issues and existing PRs should be dusted off in order to reach that goal. Peter
|
|||||||||||||
|
|
|||||||||||||
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 09/05/2019 8:00am-9:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 5 September 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
|
|||||||||||||
|
|
|||||||||||||
|
Re: NRF52810
Miguel Wisintainer <tcpipchip@...>
It can run on SKYLAB VG01
De: Miguel Wisintainer <tcpipchip@...>
Enviado: quarta-feira, 4 de setembro de 2019 21:37 Para: Bolivar, Marti <Marti.Bolivar@...>; Brett Preston <bpreston@...>; devel@... <devel@...> Assunto: RE: [Zephyr-devel] NRF52810
Solved tks!
De: Bolivar, Marti <Marti.Bolivar@...>
Enviado: quarta-feira, 4 de setembro de 2019 20:30 Para: tcpipchip@... <tcpipchip@...>; Brett Preston <bpreston@...>; devel@... <devel@...> Cc: devel@... <devel@...> Assunto: Re: [Zephyr-devel] NRF52810 Hi,
" via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@...> writes: > Thank you Preston > > See attached team It looks like Carles helped you out on Slack and your question was answered. (Posting this just to track the status on this for people only watching the ML.) Marti > > After i compile successfully the beacon sample, i tried to burn with J-LINK to NRF52810 and nothing is detected in my scanner! > > [cid:4cf00658-f2bb-40c7-88b4-f51242b96dec] > I choose the HEX > > Is there anything else that i forgot ? > > It´s a SKYLAB VG01 beacon that i am replacing the code! > > Thank you so much! > > > ________________________________ > De: Brett Preston <bpreston@...> > Enviado: quarta-feira, 4 de setembro de 2019 17:12 > Para: tcpipchip@... <tcpipchip@...> > Cc: Team <info@...> > Assunto: Re: New submission from Contact Us > > Hi Miguel, > > Please direct technical questions for Zephyr to devel@...<mailto:devel@...> > > Thank you, > > > Brett > > On Wed, Sep 4, 2019 at 10:09 AM Zephyr Project - General Contact Form <webmaster@...<mailto:webmaster@...>> wrote: > Name > Miguel Wisintainer > tcpipchip@...<mailto:tcpipchip@...> > Comment > Sir, > Did you test Zephyr on NRF52810 ? > Does it works ? > I am testing on Beacon example! Btw, will i need to use a softdevice (wich version) ? Or not necessary! > Thanks! > > > -- > Brett Preston > Sr. Program Manager > The Linux Foundation > +1 (971) 303-9030 > bpreston@...<mailto:bpreston@...> > > >
|
|||||||||||||
|
|
|||||||||||||
|
Re: NRF52810
Miguel Wisintainer <tcpipchip@...>
Solved tks!
De: Bolivar, Marti <Marti.Bolivar@...>
Enviado: quarta-feira, 4 de setembro de 2019 20:30 Para: tcpipchip@... <tcpipchip@...>; Brett Preston <bpreston@...>; devel@... <devel@...> Cc: devel@... <devel@...> Assunto: Re: [Zephyr-devel] NRF52810 Hi,
" via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@...> writes: > Thank you Preston > > See attached team It looks like Carles helped you out on Slack and your question was answered. (Posting this just to track the status on this for people only watching the ML.) Marti > > After i compile successfully the beacon sample, i tried to burn with J-LINK to NRF52810 and nothing is detected in my scanner! > > [cid:4cf00658-f2bb-40c7-88b4-f51242b96dec] > I choose the HEX > > Is there anything else that i forgot ? > > It´s a SKYLAB VG01 beacon that i am replacing the code! > > Thank you so much! > > > ________________________________ > De: Brett Preston <bpreston@...> > Enviado: quarta-feira, 4 de setembro de 2019 17:12 > Para: tcpipchip@... <tcpipchip@...> > Cc: Team <info@...> > Assunto: Re: New submission from Contact Us > > Hi Miguel, > > Please direct technical questions for Zephyr to devel@...<mailto:devel@...> > > Thank you, > > > Brett > > On Wed, Sep 4, 2019 at 10:09 AM Zephyr Project - General Contact Form <webmaster@...<mailto:webmaster@...>> wrote: > Name > Miguel Wisintainer > tcpipchip@...<mailto:tcpipchip@...> > Comment > Sir, > Did you test Zephyr on NRF52810 ? > Does it works ? > I am testing on Beacon example! Btw, will i need to use a softdevice (wich version) ? Or not necessary! > Thanks! > > > -- > Brett Preston > Sr. Program Manager > The Linux Foundation > +1 (971) 303-9030 > bpreston@...<mailto:bpreston@...> > > >
|
|||||||||||||
|
|
|||||||||||||
|
Dev-Review Meeting Agenda (Sept 5)
Kumar Gala
This week we are going to use the dev-review meeting to work on the backlog of issues/enhancements/feature requests.
The idea here is to triage issues, close out one’s that we aren’t going to handle, try and see if there are some common areas we need to focus on for the 2.1 release. I’ve asked Maureen to lead the call as I will not be able to make it. Thanks - k
|
|||||||||||||
|
|
|||||||||||||
|
Re: NRF52810
Bolivar, Marti
Hi,
" via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@...> writes: Thank you PrestonIt looks like Carles helped you out on Slack and your question was answered. (Posting this just to track the status on this for people only watching the ML.) Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Marc Herbert
it seems extremely serious, considering that west basically has one job (versioning).One of those jobs that everyone needs but no one wants to do? PS: versioning plus a bit more https://docs.zephyrproject.org/latest/guides/west/why.html
|
|||||||||||||
|
|
|||||||||||||
|
NRF52810
Miguel Wisintainer <tcpipchip@...>
Thank you Preston
See attached team
After i compile successfully the beacon sample, i tried to burn with J-LINK to NRF52810 and nothing is detected in my scanner!
I choose the HEX
Is there anything else that i forgot ?
It´s a SKYLAB VG01 beacon that i am replacing the code!
Thank you so much!
De: Brett Preston <bpreston@...>
Enviado: quarta-feira, 4 de setembro de 2019 17:12 Para: tcpipchip@... <tcpipchip@...> Cc: Team <info@...> Assunto: Re: New submission from Contact Us On Wed, Sep 4, 2019 at 10:09 AM Zephyr Project - General Contact Form <webmaster@...> wrote:
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
"Youse, Charles via Lists.Zephyrproject.Org"
<charles.youse=intel.com@...> writes: Hi Marti,I agree that it is a serious bug (see "high impact", below), and again, I'm sorry for the lack of test coverage that led to it happening in the first place. I'm grateful to the reporter for bringing it up. Now that the hotfix is out in the 0.6.x branch, I'm going to be adding regression testing. I do my best to make sure fixes get regression tests. Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
"Youse, Charles" <charles.youse@...> writes:
Marti,Of course. We have a process in place. It failed here due to lack of coverage, which unfortunate oversight and I'm very sorry for it, especially for those who ran into it. However, it was lack of coverage, and not lack of process, that was to blame. West has a test suite that works at both API and functional levels. The repository CI runs it on each commit (on Linux, via shippable). We also run it on supported platforms before cutting a release. In this case, that's Windows 10 and macOS. (This is in addition to informal testing that people are doing on the code in the master branch, which isn't relevant to this point since you are asking about process.) More testers and attention to testing are always welcome, so feel free to make any concrete suggestions for how we can improve our QA. Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Youse, Charles
Hi Marti,
toggle quoted messageShow quoted text
In spite of the fact that it doesn't cause data loss, it seems extremely serious, considering that west basically has one job (versioning). Thanks, Charles
-----Original Message-----
From: devel@... [mailto:devel@...] On Behalf Of Bolivar, Marti Sent: Wednesday, September 4, 2019 12:39 PM To: users@...; devel@... Subject: Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2 Marti Bolivar <marti.bolivar@...> writes: Hi,I was requested to add a link to the bug: https://github.com/zephyrproject-rtos/west/issues/298 It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases. Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
Marti Bolivar <marti.bolivar@...> writes:
Hi,I was requested to add a link to the bug: https://github.com/zephyrproject-rtos/west/issues/298 It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases. Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Youse, Charles
Marti,
toggle quoted messageShow quoted text
Thanks for letting us know. Perhaps, since 'west' has been made practically essential to Zephyr, we should investigate some kind of QA process for west releases. Thanks Charles
-----Original Message-----
From: devel@... [mailto:devel@...] On Behalf Of Bolivar, Marti Sent: Wednesday, September 4, 2019 9:48 AM To: users@...; devel@... Subject: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2 Hi, West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected. If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process: Linux: pip3 install -U --user west macOS and Windows: pip3 install -U west Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
Hi,
West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected. If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process: Linux: pip3 install -U --user west macOS and Windows: pip3 install -U west Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Error in NRF SoC flash memory compilation
#nrf52840
giriprasad@...
When Iam trying to include flash.h file in my application noticed below compilation error.
Can you help me to resolve the issue
ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ EPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api;
|
|||||||||||||
|
|
|||||||||||||
|
Zephyr 2.0.0-rc3 tagged
Glaropoulos, Ioannis
Hi Zephyr developers,
We have now tagged Zephyr 2.0.0-rc3!
All major external dependencies and components, are now up-to-date. All high-priority bugs (including last-minute high-priority issues) have been addressed, and the corresponding PRs are merged to master. We, currently have 16 medium-priority bugs, which is below the threshold required for release.
We are now in the release testing phase. Master branch is now open only for documentation updates and patches that contribute to the release notes for 2.0. Everything else should wait until after we open the merge window, again.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc3
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
We expect to release Zephyr 2.0 after the release testing completes successfully.
Thanks to everybody who has contributed to this release!
Ioannis Glaropoulos
Från: Glaropoulos, Ioannis
Hi Zephyr developers,
We have now tagged Zephyr 2.0.0-rc2!
All major external dependencies and components, are now up-to-date. All high-priority bugs have been addressed, and the corresponding PRs are merged to master.
We still have a (relatively short) list of bug-fix PRs that need to be reviewed and merged, in order to drop the bug count below the threshold that is required for the release.
Besides that, documentation updates and patches that contribute to the release notes for 2.0 may be merged to master.
Everything else should wait until after we open the merge window, again.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc2
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
The final release is tentatively scheduled for August 30th.
Thanks to everybody who has contributed to this release!
Ioannis Glaropoulos
Från: Glaropoulos, Ioannis
Hi Zephyr developers,
We have just tagged Zephyr 2.0.0-rc1.
All required features scheduled for 2.0 release are now merged into master. As of now we are in the stabilization phase for 2.0 release; the merge window is closed for new features and enhancements, and will remain closed until the release date. We will also start working on filling in the existing skeleton for the release notes.
During the stabilization period bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for 2.0 release will need to be approved by TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers. Testing Zephyr release candidate branches is also highly appreciated; please, test the code base and file bug reports so they can be addressed before the release deadline.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc1
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
The final release is tentatively scheduled for August 30th.
Thanks to everybody who contributed to this release!
Ioannis Glaropoulos
|
|||||||||||||
|
|
|||||||||||||
|
Upcoming Event: Zephyr Project: APIs - Tue, 09/03/2019 9:00am-10:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 3 September 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 Live meeting minutes: https://docs.google.com/
|
|||||||||||||
|
|
|||||||||||||
|
API meeting: agenda
Carles Cufi
Hi all,
This week we will look at: Agenda: - Sensor API: Potential sharing between V4Z and rtio - GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it 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
|
|||||||||||||
|
|
|||||||||||||
