The Cfdp engine uses Big Endian byte order.
The test InPDU Packet data was converted to Big Endian byte order. And Cfdp engine extracted the right data.
But when CF app received a Input PDU,
it extracted the PDU Data length from the PDU header(CF_PDU_Hdr_t) with Little Endian in function, "CF_SendPDUToEngine".
(PduHdrPtr->PDataLen)
This caused too small/big data length information was sent to Cfdp engine.
Test case : Test_CF_SendPDUToEngine_InPDUInvalidDataLenTooBig, Test_CF_AppPipe_HousekeepingCmdUpFreezeWarn
The Cfdp engine uses Big Endian byte order. The test InPDU Packet data was converted to Big Endian byte order. And Cfdp engine extracted the right data. But when CF app received a Input PDU, it extracted the PDU Data length from the PDU header(CF_PDU_Hdr_t) with Little Endian in function, "CF_SendPDUToEngine". (PduHdrPtr->PDataLen)
This caused too small/big data length information was sent to Cfdp engine.