topic When USB packets are a multiple of MaxPacketSize. Any byte that happens to fall on top of a multiple of MaxPacketSize is corrupted. in MQX Software Solutions

When USB packets are a multiple of MaxPacketSize. Any byte that happens to fall on top of a multiple of MaxPacketSize is corrupted.

Jetcitycowboy — Thu, 30 Jan 2014 00:49:51 GMT

Using MQX 4.1. and 4.0.3 when the packets are a multiple of MaxPacketSize. It is ANY byte that happens to fall on top of a multiple of MaxPacketSize. Which means if you send a packet of 150 characters, the 128^th byte magically gets zeroed. Is there a fix for this?

I am seeing this on 2 different processors KL25 and Coldfire MCF52254CAF66, at 2 different customers

I see a similar posting by Paul Hunt, that has not been addressed. Please advise.

Re: When USB packets are a multiple of MaxPacketSize. Any byte that happens to fall on top of a multiple of MaxPacketSize is corrupted.

Carlos_Musich — Tue, 11 Feb 2014 22:10:00 GMT

Hi Kenneth,

I assume you are talking about USB Stack 4.1.1 and 4.0.3.

Are you using host or device?

Do you see the same behavior in the 64th byte?

Are you using one of our examples (which one)? Did you edited it? Or you are developing your own application.

Please be sure that the device maximum packet size is set to 64 for Interrupt, control or bulk transfers as indicated by the spec. Setting max packet size higher than 64 can cause unexpected behavior. Isochronous transfers can be up to 1024 but I think this is not your case.

Regards,

Carlos