DMA may not transfer the complete bitlists from input DPM Image into host memory

The firmware internal length calculation for Input data DMA length does not take into account the alignment of Bitlists in Input DPM Image.

In case the input data length is not 4-byte aligned there may be up to 3 padding bytes between the end if Input data and start of Bitlists (to ensure 4-byte alignment of Bitlist).

If DMA is used and the input process data length is uneven the calculated DMA length may be up to 3 byte to small.

The issue can not be detected from outside, looking at DPM Input Area or Host input DMA buffer everything is working as expected. This is due to the fact that the rcX operating system always sets up DMA with a 4-byte aligned length. Thus the missing padding bytes are "fixed" by rcX.