Hi Paul, <paul.sokolovsky@...> wrote: When you use a presentation which says: Main benefits taking zephyr in use would come from good ble and tcp/ip stacks ... I understand it can be

Hello Piotr,

Hello Piotr,

Hi, Analysing the problem here, with a 32-bit integers, only 31-bit value range can be used to set alarms that expire after a rollover of 32-bit clock counts. This is considering that we want to

Hi all: from the dtc compiler command in Makefile.lib document, the device tree of zepher project are compiler to "DTS" file, not the blob file "DTB" type, so, and then convert to header

Hi, One more vote to set the default log level to 2 (warning) but not to enable logging by default for the reasons Jukka has mentioned. It certainly makes sense to provide sane defaults (level 2 is a

"Nashif, Anas" <anas.nashif@...> wrote: Well, just as you tried to present the issues in the net stack from the different sides, just the same I try to present an extended perspective of the

Tomasz Bursztyka <tomasz.bursztyka@...> wrote: [] Right, I had the same idea, mentioned in the other mails. [] I posted https://github.com/zephyrproject-rtos/zephyr/pull/1507

Should I assume you started replying before you read my final comment about logging? :-) Anas

Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: We can approach it from another side. Let me present some cases I faced (some of them based on other users' feedback), and you'll try to

Quick status about device tree: *Pinmux is not yet generated thanks to dts files. Only pinmux.c matters *Today, on STM32 dts files, only UART pinctrl is taken into account So related to FSMC, you

As said earlier, you can directly access HAL code in your application, no problem with that. Point is CONFIG_ flags and Kconfig files are designed to enable "typical" use of Zephyr (through Zephyr

Please ignore my previous post I am writing a demo graphic application running on STM32F412G-Discovery. For this purpose, I must set the multiplexing of some pins to use the FSMC device. I wonder if

and what about peripherals that zephyr doesn't manage, like FSMC? I am writing a demo graphic application running on STM32F412G-Discovery. For this purpose I use the pre-compiled

Sto sviluppando una pplicazione grafica che gira su STM32F412G-Discovery. For this purpose, I must set the multiplexing of some pins to use the FSMC device. I wonder if I need to edit the files

Hello Maciej, 2017-09-14 12:07 GMT+02:00 Maciej Dębski <maciej.debski@...>: Pull request now updated. Please pull and test. Thank you Bobby

Hi, This is the correct understanding, you need to modify Makefile/Kbuild to access HAL drivers. Then, if you need to use some driver in an application, you'd theoretically use zephyr HW API and

Hi. You need to provide description of how to use the description you introduced. Look at https://github.com/zephyrproject-rtos/zephyr/blob/master/dts/common/yaml/partition.yaml For details how BOT

In an application I need to use STM32 HAL driver, for example GPIO, FSMC and others. I wonder how can I have the appropriate files compiled. There are some CONFIG_* to set? I read

Hi, I would like to setup zephyr so that it can use a flash area to store data. I have added a partition description in my dts file describing the flash partitioning (for testing I used the