Hi Daniel, It’s listed in the Getting Started guides as one of the packages you need to install on all 3 OSs (Linux, macOS,

Hi Dan, I can find it at http://docs.zephyrproject.org/getting_started/installation_linux.html under "Installing Requirements and Dependencies" : Tim -- Tim Kielan Registered Linux User #239184 vim

Hi there, I’ve not used zephyr for a few weeks and in the meantime Zephyr-SDK 0.9.2 was released and the CMake migration happened. After pulling the latest zephyr/arm branch, installing

Hi Vikrant, I assume you built the bluez 5.47 from source. The json files live in bluez/mesh. You either have to run meshctl in that directory or point to it with the "-c" option. Once in meshctl,

PR: https://github.com/zephyrproject-rtos/zephyr/pull/4984 cmake: s/CONFIG_I2C_STM32_V1x/CONFIG_I2C_STM32_V1/ by SebastianBoe · Pull Request #4984 · zephyrproject-rtos/zephyr ·

Hello, I to want build Zephyr based lighting system & for testing I have 3 nRF52840-PDK boards. I've flashed zephyr/samples/bluetooth/mesh firmware on all three board. They are advertising themselves

Hi, tinytile has only one USB connector. After connecting to PC first couple of seconds it waits in DFU mode after that it loads Zephyr and in the default configuration enables USB UART console,

I want build Zephyr based lighting system & for testing I have 3 nRF52840-PDK boards. I've flashed zephyr/samples/bluetooth/mesh firmware on all three board. They are advertising themselves as any

Hi Dmitry, Thanks for catching this. It is a typo. Could you create a PR on github to fix it? Yannis <zephyr-devel@...> wrote:

Jie, If you flashed your Zephyr application over USB, it should now be in the device’s flash memory and should be loaded and run on every reboot. If you are not seeing the application load when

Hi Mike, I'll investigate on the vin/gnd battery. I also have the flyswatter, but I remember having trouble with flashing with it, so I sticked with the FTDI but will check that out too. Eventually, I

Jie, Curie boards generally flash in one of two ways: over JTAG or over USB. In typical uses, they actually flash over the Curie USB interface (using the USB DFU protocol; via dfu-util). That’s

Hi all, I'm flashing my tinyTILE using DFU over FTDI cable. My computer, that has the zephyr applications, is connected to tinyTILE via a FTDI cable as TX & RX and a usb cable as power to the

Hello, Change for cmake build: commit 12f8f7616567f224b920512b6f81a65421e30bae Author: Sebastian Bøe <sebastian.boe@...> Date: Fri Oct 27 15:43:34 2017 +0200 Introduce cmake-based

Thanks Marti. Will get back to you if I have any more questions. Regards, Raj From: Marti Bolivar [mailto:marti@...] Sent: Tuesday, November 14, 2017 8:02 PM To: Gundi, Rajavardhan

Hi Raj, Sure thing, happy to help. Currently, by creating a subclass of ZephyrBinaryRunner that provides a create_for_shell_script() method which claims compatibility with 'xt-gdb.sh'. (See link to

Hi Marti, I see that you have modified the “debug”, “debugserver” and “flash” scripts to make it OS agnostic. I am working on an xtensa board and I have a dedicated script for this

Hi. I’ve ported boot serial recovery feature which had been originally provided for mynewt targets. Tools needed for create the image and transfer it to the FWU target are the same as for

Hi Steve, That's a good catch. Thanks for investigating this. It seems also the scan parameters suffer of the same issue. I've uploaded a pull request that should fix both

Hi All, It looks like set_param.filter_policy isn't initialized in hci_core.c:bt_le_adv_start. With the mesh sample, it has 0x02 in it, which is "connectable only from whitelist". If I initialize