Hi supriti, I think you are missing to set environment variable Best Regards Rahul

Hello , I am facing trouble while setting up the toolchain into my system. While running cmake command for nrf52 I have encountered an error "Are permission set correctly ?" for below

No sure, but probably can ask on https://github.com/Shippable/support - k

@Andy Ross Thanks for the perspective. This is interesting. It does currently live under \zephyr\drivers with i2c, spi, gpio, etc. and is developed following a general driver API. Also, the Zephyr

Inertia, probably, and maybe a lack of somewhere better to put them. Properly "sensors" are an abstract subsystem and the related peripherals would be things like "accelerometers",

Hello Zephyr developers! This is a (final) polite reminder that the merge window for Zephyr 2.0 release will close on Friday August 9th. If you are currently working on features for the 2.0

Hi, When I call adc_read_async to start adc sampling on nrf52832 board, the hardware exception happened. I have use the debuger to trace the fault, it happened after call adc_read_async function. But

... or the reason why I wish I could smash my keyboard with a 12-foot H-beam. Accessibility wise, this shipable web interface thingy is a complete abomination. Every of my attempts to get to test

Reminder: Zephyr Project: APIs When: Tuesday, 30 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

Hi all, This week we are focusing on finalizing the GPIO API which has been under discussion for a few weeks already. Agenda: - GPIO: Settle on API * See:

Hi, I’ve just tagged RC3. This includes some bug fixes and related features: An optional “repo-path” project attribute to allow override the project’s “name” when forming the fetch

Hi all, What is the rationale for ‘Sensors’ being under ‘Peripherals’ in theAPI Reference with the ADC, Counter, I2C, SPI, etc.? Is it because the Peripheral APIs are for hardware-related

I forgot to add: it would be nice if any issues could be reported via the west bug tracker (https://github.com/zephyrproject-rtos/west/issues) rather than email, if possible. Thanks again.

Hi, West version 0.6.0rc1 has been tagged. Release notes are in this pull request: https://github.com/zephyrproject-rtos/zephyr/pull/17714 Testing and feedback are welcome; I’d like this

As discussed in various meetings: there is an ongoing need for Zephyr to support peripherals that have features beyond what is supported in the generic driver class, e.g. calibration APIs for specific

All, Just a heads up on some changes to the generation path for handling of DT. Ulf and I have been working on a replacement for the DT parsing and Code Generation code. The replacement is in this

Hi, Thank you for your help. I have tried the commands given in the documentation and yours as well. My Python VersionPython 2.7.15+. I am getting the following errors after executing the commands

Reminder: Zephyr Project: Dev Meeting When: Thursday, 25 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

Here’s the issues/PRs on the agenda so far for this week’s Dev Review Meeting: * Proposed development plan for Zephyr's POSIX subsystem:

Hi Rockc: Essentially, app code and kernel code will be combined into one image. Then that image will be flashed into target board. There is no support for program loader.