CFDP setup between two cFS projects about cf

[ashrafalhajjeh]

After doing a little digging into this issue, here's what I found:
In pdu.c, the PDU length is packed on lines (269->272) as big-endian:

In pdu.c, the received file data packet struct generation also interprets PDU length as big-endian:


which is good.

The reason I was having issues now come from the following two pieces of code:
In cf_app.c:

In pdu.c:

Where the length is interpreted as a struct parameter assuming the machine's endianness (in my case little-endian). In the cf_app.c case, this forced me to create a very large incoming packet buffer (>60k bytes) for file chunks of just 200-500 bytes. In the pdu.c case, I ended up running into the "Incoming Nak truncated to fit in storage" message due to the pdu length indicating a large memory size for the NAK struct creation.

I think the two areas that use the length in an endianness dependent manner should be changed to accommodate running on a little-endian machine.

[moafandi0]

I had the same issue. When I changed the code at cf_app.c line 1030 and added the CFE_MAKE_BIG16 macro it worked. I could get class 1 transactions working but I'm having issues with class 2 transactions. Did you have any success with class 2 transactions? @ashrafalhajjeh

[skliper]

I realize this isn't immediate help, but just a heads up that there is a major update to CF in the works that we plan to release open source.

[moafandi0]

@skliper I guess I'm just gonna wait for the new update then and work on other stuff for now.

[skliper]

Closing as obsolete (applies to v2.X)