Hi Andrei, If block wait is mandated, we can call usb_write() only on one endpoint at a time which will hamper performance. Although USB bus transactions are sequential we can however queue the write

Hi, As defined by the documentation, write is asynchronous, you can only be sure write is complete when usb_ep_callback is called. In practice, there are some hacks in current drivers to make

Hi Vikrant, Yes, we would like the sample to be merged, but you need to send a Pull Request using GitHub. Please read through the Contribution

Hi, I think we do not have now this requirement not to block-wait. When working with sending fragmented packets you would prefer to block until all fragments are sent. Best regards Andrei

https://github.com/vikrant8051/zephyr-samples-boards-nrf52-nffs Are you want this ? Thank You !!

Hi Johann, Thanks, will take a look at it. Thanks, will look into this. I need to understand the transfer method. So after it's been pulled, does the driver need to support it by default? Since

Hi Andrei, Yes, it does support both of them. So new drivers should support both of them to be inline with the API definition? As Paul pointed out, some old drivers might need to be modified since

Hi Paul,

On Tue, 30 Jan 2018 14:36:40 +0000 "Cufi, Carles" <Carles.Cufi@...> wrote: [] > > I'd suggest to look at this as a generic problem, not specific to > > USB subsystem (e.g., there's the

Hi, This sample was written for the DW driver, there was no other device driver recently. Please use subsys/usb/class for testing and as reference. The IN endpoint callback just informs that a

Hi, I think API states it supports both methods: https://github.com/zephyrproject-rtos/zephyr/blob/master/include/usb/usb_device.h#L209 Fragmentation to USB packets is done on a higher level, in

> I request Zephyr OS maintainer to create & add following attached main.c under $zephyr_base/samples/boards/nrf52/nffs/src & prj.conf under $zephyr_base/samples/boards/nrf52/nffs/ on Github.

Hi Paul,

+ Andrei Carles

Hello Sundar,

As per this document .... nrf5_SDK_for_Mesh_v1.0.1_src/doc/introduction/mesh_hw_resources.md (I've attached this file for reference......very informative) The mesh stack uses flash to store the

Hi, While developing a USB device controller driver for the Nordic nRF52840 SoC, I ran into the problem of handling chunked/partial write() while coding the usb_dc_ep_write() function. From what I

After testing I found that it is necessary to add __attribute__((packed)) after structure definationWhy ?? This will be helpful --> http://www.avabodh.com/cin/structure.html So I edit above mentioned

Hello World !! By including NFFS support into #BluetoothMesh project, now I can access flash of nRF52. { Some useful links: http://docs.zephyrproject.org/api/file_system.html

Hi Paul, I'm unable to reproduce this. Is this your own app and a custom configuration, or a sample from the Zephyr tree? If it's your custom app, could you provide the output of the