Skip to content

Connect CfdpManager directly to ComQueue#10

Merged
pepepr08 merged 1 commit intocfdp_managerfrom
cfdp_commqueue
Apr 10, 2026
Merged

Connect CfdpManager directly to ComQueue#10
pepepr08 merged 1 commit intocfdp_managerfrom
cfdp_commqueue

Conversation

@pepepr08
Copy link
Copy Markdown
Collaborator


Change Description

Changes needed to connect CfdpManager directly to ComQueue.

Rationale

The packet descriptor now need to be handled at the component side, to avoid the need for a Cfdp ComQueue Adapter.

@pepepr08 pepepr08 merged commit d4b3138 into cfdp_manager Apr 10, 2026
3 checks passed
// Port mapping is the same from bufferAllocate -> dataOut -> dataReturnIn -> bufferDeallocate
FW_ASSERT(portNum < Cfdp::NumChannels, portNum, Cfdp::NumChannels);
this->bufferDeallocate_out(portNum, data);
this->bufferDeallocate_out(portNum, fwBuffer);
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typically we only deallocate out to port 0, but work if you use the specific mapping all throughout


// Shift PDU data forward to make room for descriptor
// Use memmove (not memcpy) since source and destination overlap
memmove(bufferData + descriptorSize, bufferData, static_cast<size_t>(pduSize));
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there are reason we can't offset the initial write, rather than memmove.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants