Closed WGR7 closed 1 month ago
Host does not support too slow msc, so stop using it, and your code is incorrect because write api is in isr.
BL616 is used as a MSC device, insn't a host. MSC is a blocking protocol as I know, so the write can be slow. I'm using FreeRTOS.
BL616 is used as a MSC device, insn't a host. MSC is a blocking protocol as I know, so the write can be slow. I'm using FreeRTOS.
i have said, cherryusb write api is in isr,and host is pc.
usbd_msc_sector_write is in isr thanks.Please give up if your flash is too slow, it is not cherryusb problem.
I'll take my time and port TinyUSB. your library is a waste of time. Tks.
So jokes, you should study freertos first and know freertos api cannot be used in interrupt api
I can patch your code to deal with this issue, but I need to know how can I do NAKs to host when the MCU is writing to slow memory. Is there any specific SCSI status to return that can I inform host that device is busy?
Hi,
I'm using a BL616 with USB HS mode. I've updated component to more recent master CherryUSB branch.
I have a very slow media: a NOR Flash SPI. I'm getting a issue while writing to the media. In the middle of transfer I get a type of reconfig of interfaces with these messages. They are the same message when the USB cable is plugged in USB port. The file to write is large, about 40MBytes.
To isolate the problem I did take the example of the composite device cdc_mscram and in the final of the write function I've added a vTaksDelay(200).
The issue is still the same, the device is reconfigured and the transfer stops.