Hi Jehudi, I'd bet the recv thread stack overflowed. It's already at 97% with only 32 unused bytes based on the above log. Try increasing its size to something bigger. The Kconfig variable is called

Hi, Running the bluetooth mesh example (samples/bluetooth/mesh/) on a nrf51822 results in a Hard Fault. The provisioner is meshctl (bluez). After successful provisioning I disconnect from the mesh,

Hello, a quick thought - did you try to write in Hello World example the following lines? $ make help $ make BOARD=<board_name> $ make BOARD=<board_name> flash $ make BOARD=<board_name> debug Try to

Hi, You need to install the SDK, it seems line you are missing this step. Please follow the instructions in the getting started guide to install the SDK, then point the variables to the directory

Perhaps we should change the API to add the truncate option to fs_open(), at least provided at least one underlying implementation supports this. Only if the fs_truncate() for 0 offset can be

Hi David, ​I'm not really sure if ​this needs to be POSIX compliant - the Jira ticket for adding filesystem APIs states that it is designed after POSIX but is not POSIX compliant. For example,

Hi, The Kconfig options (macro) you define need to be included (sourced) in the overall Kconfig structure of zephyr, just adding an option to prj.conf does not give you what you want. This is

Fixed, blame form auto-complete. Anas

Hi Anas, Thanks for preparing the release. Just a minor remark, after opening the link the page title seems to be incorrect. It states: "Zephyr SDK 0.9.2-rc3" Regards, Piotr

Hi, We have just tagged RC3, please see the changes since RC2 here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v1.9.0-rc3 If no major issues are found, we are expected to

I have updated Watchdog API RFC. I am waiting for feedback! Michał Kruszewski Sent with ProtonMail Secure Email.

If your goal is posix compliance, this isn't going to be right anyway. truncate is required to be atomic. The POSIX truncate call is also allowed to be used to extend the size of a file. I think it

Hi, According to stm32f412zg datasheet, usart2_pin_c is actually supported on stm32f412zg, so I don't see issue to populate it in stm32f4-pinctrl.dtsi. Besides, as mentioned by Andy, it's not a

0.9.2 RC2 is now available from https://github.com/zephyrproject-rtos/meta-zephyr-sdk/releases/tag/0.9.2-rc2 with the following changes: Changes since 0.9.2-rc1: Update to Qemu 2.10.0

Hi Johan, With the patch applied I am getting still getting the warning every 10 seconds. Kind regards, Jehudi 2017-09-03 8:57 GMT+02:00 Johan Hedberg <johan.hedberg@...>:

@Bobby I missed that it is a pointer to const u32_t. It is fine. <giannis.damigos@...> wrote:

Hi Maciej and Bobby, you can collaborate on Maciej github repository and push this commit as a PR there and then to Zephyr's repo. @Booby You declare vector_table_src as constant and the you change

Hello, "Li, Jun R" <jun.r.li@...> wrote: Well, that's not specific enough. It's not enough to define a config option "in a Kconfig file somewhere" for it to be actually available in Zephyr

Hello Bobby, amazing, thank you for doing this! Yes, it works on my Nucleo-F030R8, hello world and blinky, both are fine. Try to emphasize that this is related to my patch, so these should be released

Hello, Andrzej Kaczmarek <andrzej.kaczmarek@...> wrote: ENOTSUP is your friend (except Linux thinks it should be EPERM, see below). POSIX has