Hi Matt, Just looked at the code, it seems OK at first sight (the Mass Storage Device) is recognized by Windows without installing any drivers which is what I would expect. Regarding the buffers it depends on how you want to manage them. If you want to avoid copies, you have to allocate the buffers in the USB/ CPU shared memory region (dual port memory), but be aware that some devices (e.g. 13/14k50) have only 256 bytes of USB memory, in addition you need to add buffer descriptors in order to manage the ownership of the buffers. So maybe it is easier to start with shadow buffers in non shared memory and copy the data upon transmit/receive, I would not recommend holding the USB buffers for a longer period (>1ms) because this will cause USB timout problems Albert
On May 23, 5:32 am, mattschinkel <[email protected]> wrote: > It seems that I have to manage/create buffers myself via callbacks > usb_ep_data_out_callback() and usb_ep_data_in_callback() > usb_ep_data_out_callback() - data out from host > usb_ep_data_out_callback() - data in to host > > I also assume my buffer size should be > 64 since the host will send > up to 64 bytes at a time. In the previous code I have const byte > USB_MSD_TX_BUFFER_SIZE = 64 > > Is this correct? > > Matt. > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/jallib?hl=en. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
