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

Hi, " via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@...> writes: It looks like Carles helped you out on Slack and your question was answered. (Posting this just to track

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

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

"Youse, Charles via Lists.Zephyrproject.Org" <charles.youse=intel.com@...> writes: I agree that it is a serious bug (see "high impact", below), and again, I'm sorry for the lack

"Youse, Charles" <charles.youse@...> writes: 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

Hi Marti, 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

Marti Bolivar <marti.bolivar@...> writes: 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

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

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

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/include/drivers/flash.h: In function 'int

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

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

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

Thanks, I really appreciate the response and especially the PR reference. Will check it out.

Hi Benjamin, Sorry for late reply, I’ve just came back from holiday. See my responses inline. Regards, Robert

"Alberto Escolar Piedras (ALPI)" <ALPI@...> writes: You're right, of course. I looked at the output itself without seeing the "warning" prefix. This is building and running fine (apart from

Hi Marti, That would seem to be just a warning. (At least another developer has also reported it, and I think he was also using Arch Linux) As far as a I understand it is harmless. The binary

Dear Maureen Helm Thank for your indication.I check the dts file. then I find the upcase of letter for the dts file name is wrong. after I correct. the compile is sucessful 发件人:

I can't reproduce this exact issue, but I can confirm that with ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started