Right. We need to do IN_DATA action along with the COMMIT action. If we don't do IN_DATA then it will generate a Zero length packet after committing the short packet. But if you do IN_DATA then there is a chance that you may see extra data for one clock cycle. Anyways, you can try adding IN_DATA action where you are doing the COMMIT action.
I think the best way to handle short packet is through CyU3PDmaMultiChannelSetWrapUp API call only.
Thank you very much. It worked.
if set IN_DATA with “no Write data into Data Sink” parameter is there no chance that may see extra data for one clock cycle？