Hey Paul, time() was just the first thing I tried to see how well newlib works, and the results was it doesn't. And that it compiles without warning and than hangs in an endless loop sounds like a

Hello, I am developing an I2C driver based on the stm32cube LL API. The driver can be found here: https://github.com/ydamigos/zephyr/tree/i2c_ll_stm32f4 The driver supports both polling and

Hey All, I rewrote it by using CONTAINER_OF() and it works fine and is lot cleaner. Tanks for the hint. - Erwin

Hi Andy, Erwan, Anas, I will send an RFC when I have some free time for it and thanks for the hints. Neil

Hello Erwin, Erwin Rol <mailinglists@...> wrote: When you want time(NULL), what are your expectations? Because as you know, what it's supposed to do is to return number of seconds

Hey all (yeah there he is again), I was wondering what the status and planning is for the C-library? I tried a simple example and I guess I directly hit a problem. The "buildin" mini C-lib doesn't

No problem, I understand it is not easy to jump in. And agreed we might miss some material to make all this clear. Great! We look forward to see it upstreamed Seems right!

Hey Neil, Erwan, thanks for the infos. I guess the confusions are largely because Zephyr is still such a young project. Under Linux there are so many drivers to look at as examples and if 10 use HAL

Indeed, for the little story I was trying to test the sensor (to upstream support for it) on the stm32f4discovery board, but when I hoocked up everything (driver, ...) to test the driver, I realized

Hi Erwin, LL based version was initiated without knowing Neil had a HAL based driver, and from what I am aware of (unless I missed this information), Neil never proposed to upstream it. I let him

Hey Erwan, Yes, I will rewrite it to use CONTRAINER_OF. So the I2C driver is being rewritten even though there is a working version (I assume Neil's HAL version is working)? Now you are making

Hi Erwin, As mentioned by Neil, CONTAINER_OF is a good solution that is used in other projects using STM32Cube. About your last point: There won't be any branching from STM32Cube for Zephyr. Generic

Hi Baohong, thanks for the clarification. I suppose: source_transfer_width should be source_data_size ? dest_transfer_width should be dest_data_size ? It is a little redundant, what is the

Hey Neil, Thanks, somehow just didn't think about that. Will rewrite the eth driver to use the CONTAINER_OF() construct. BTW is that i2c driver going to be included in mainline? :-) - Erwin

Hi Erwin, You can use CONTAINER_OF() to get the parent structure like https://github.com/superna9999/zephyr/blob/stm32f4_i2c/drivers/i2c/i2c_stm32.c#L93 Neil

Hey Erwan, like you say some things are subjective when it comes to HAL's, but somethings really bother me with the STM32 HAL. The most important is how to deal with IRQ's. In Zephyr I have to

Hi Prasad, Mostly driver dedicated public functions used by the system or by some specific board configuration. Just talking about those I know: Console ones for

Folks, Could you please tell me why “include” directory is organized like this? I mean to say there is “drivers” folder and driver API header files are outside this directory(e.g. dma.h,

Hi, The DMA API describes the source_burst_length and dest_burst_length of the struct dma_config as: ... * source_burst_length [ 0 : 15 ] - number of source data units *