When using a sample application like MCSPI Loopback DMA, we see a problem of FORCE bit not being set properly.

The default application of MCSPI Loopback DMA works fine.

Problem occurs when all the transactions are set as csDisable = FALSE and for the last transaction we set csDisable = TRUE.

From second transaction onwards, we see that the FORCE field sets from 1 to 0 in the API 
MCSPI_setChDataSize, which is incorrect.