I have a product requirement, USB AUDIO converts IIS to another chip, the second chip converts IIS to WAV buffer files, and then connects to the outside through the USB DISK interface.
*.WAV buffer file is fixed length, USB AUDIO decoded IIS data constantly updated cycle, external USB in the way of FIFO, cycle read *.WAV buffer file for recording,
1- The first chip (USB AUDIO) is easy to implement,
2- The second chip first builds a USB storage disk and then cycles IIS into WAV virtual files.
To achieve the function of 2, what way can be well implemented.
USB AUDIO converts IIS to another chip
USB AUDIO converts IIS to another chip
- Attachments
-
- DVS1010D.png (30.46 KiB) Viewed 72 times
Re: USB AUDIO converts IIS to another chip
Mass storage devices aren't very polite. You can give them your data fast and then at some point those things say "no thanks, please wait" And while you are waiting for stuff, you get more data steadily. And then you need some buffer which would need to be quite large and even external device.
And the write speed depends heavily on the storage device model
And the write speed depends heavily on the storage device model
Re: USB AUDIO converts IIS to another chip
I can share an external SRAM, exchange data with each other in the way of FIFO, or connect to the SD card
Re: USB AUDIO converts IIS to another chip
viewtopic.php?t=3017Hannu wrote: ↑Thu 2024-11-14 9:04 Mass storage devices aren't very polite. You can give them your data fast and then at some point those things say "no thanks, please wait" And while you are waiting for stuff, you get more data steadily. And then you need some buffer which would need to be quite large and even external device.
And the write speed depends heavily on the storage device model
hi, I suddenly thought of using your ADC board to change the USB AUDIO part to the USB DISK protocol, which should be easier?
Re: USB AUDIO converts IIS to another chip
LOL
That is a very strange idea. USB mass storage works basically so that USB host request disk block from device to be read or written. Bulk mode is used in 64 or 512 bytes chunks depending USB protocol version.
Doing this would give interface where you could read with something like:
dd if=/dev/something of=audiofile.pcm
And there could be doubled or missing samples. So:
Please don't even think about that. It doesn't work like that.
That is a very strange idea. USB mass storage works basically so that USB host request disk block from device to be read or written. Bulk mode is used in 64 or 512 bytes chunks depending USB protocol version.
Doing this would give interface where you could read with something like:
dd if=/dev/something of=audiofile.pcm
And there could be doubled or missing samples. So:
Please don't even think about that. It doesn't work like that.