Chris McClelland wrote: > Basically, the supplied FX2 firmware (in libusbx/fx2/fw/firmware.hex) > enumerates with two IN endpoints, EP1IN and EP2IN.
Endpoint 1 is the poor stepchild in the FX2. The functionality is limited, the buffering is fixed and limited, and it uses different registers from the other endpoints. As a general rule, you'll be much happier if you forget about it, and always restrict yourself to the even-numbered endpoints. Your descriptors have the max packet size set to 64 for endpoint 1. That's not valid. In a high-speed devices, bulk endpoints must ALWAYS have a max packet size of 512. That's required by the spec. Because the FX2 only has a 64-byte buffer for endpoint 1, that presents a philosophical problem, and the FX2 data sheet points this out. You have to report it as 512 bytes, but make sure you never try to do a packet larger than 64. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
