Hi, Current API already supports multiple instances of a given device driver, so that's fine. That is missing indeed. Or, more precisely, the only current way to support this is to have a struct

Would be a great idea. Especially useful to bring to the surface RNGs that have been interfaced to the system without a whitening filter... Daniel.

Seems like a pretty worth while thing to work on. We have some support for a few random number generators in the tree already (drivers/random). So I think a test app as you described shouldn’t be

Do you think we will have systems with multiple RTC in them? I’m generally for supporting multiples of a given device type, just wonder about RTCs. We need to have a standard view of time

<andrei.emeltchenko.news@...> wrote: IIRC, last time I tried this (5 or so years ago), composite devices required custom drivers on Windows. That may not work for a factory line test

Interesting product indeed but beware of the "100% open" on the front page. ugfx is not open source... merely "open". Daniel.

Hi Bill, I'm not sure if ugfx has been ported to Zephyr but you can check it anyway. I've heard good things about it. https://ugfx.io/ Od: zephyr-devel-bounces@... <zephyr-devel-bounces@...> w

Hi, You can combine those descriptors together to have multifunction device. http://www.beyondlogic.org/usbnutshell/usb5.shtml (I have not tried it myself) Best regards Andrei Emeltchenko

This is a great topic to bring up. In addition to an MPU policy to protect threads for debugging, we do need to specify a system-level policy that get applied at boot, even if we are not protecting

Yet another example that shows the importance of laying out early what the different MPU regions will be used for, as stated in the top comment in my original reply to the RFC.

I had planned on checking user pointers unconditionally, I think it's a common programming mistake. When running in supervisor mode on behalf of a user thread, we should make sure any buffers passed

I would like to add one more point to the discussion. It is maybe not directly related to the topic but should likely be considered when designing MPU support. Occasionally, mainly in

Ben, Thanks for the explanation! It is very clear now. Regards, Jun

Agreed, but I think this can be made optional if the application is trusted and user-space is used more as a debugging aid. Although, that's Yet Another Kconfig configuration to verify.

Hi Jun, <duration> is the time before the first timer expiry, and <period> is the period at which it will expiry subsenquently. If you specify a <period> of 0, the timer only fire once. e.g. If the

Hi Thanks for the reply But as of now with the available zephyr, the USB can work either as DFU flashing or as UART over USB (CDC) and not both functionalities together. We have a requirement at End

And validation of all the arguments passed into each function call. No point going to all this trouble if userspace code can pass in dodgy pointers or lengths etc. to the kernel. -- Tixy

Hi Vishal, The button example was originally created for the nucleo_f103rb board, and then expanded for others. However, looking at the latest README.rst, galileo is not in the supported list.

Hi there, I’m trying to use the “k_timer” in my project, and get confused by the parameters in the function “k_timer_start(struct k_timer *timer, int32_t duration, int32_t period)”. How

I'm looking around for RTOSs that support graphics and while I don't see any references to graphics support in Jira or schedules I'm hoping someone knows of a 3rd party library that would