Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix CPD Manifest's partition offset #374

Merged
merged 1 commit into from
Aug 18, 2023

Conversation

XutaxKamay
Copy link
Contributor

The header size needs to be probably added here, maybe it was forgotten ?

This is needed in order to get the proper base address of a CPD_EXT_IFWI_PARTITION_MANIFEST structure in the image for example in that specific case.

If I don't do this, it points to a meaningless address.

Let me know if there can be any issues with this.

The header size needs to be probably added here, maybe it was forgotten ?

This is needed in order to get the proper base address of a CPD_EXT_IFWI_PARTITION_MANIFEST structure in the image for example in that specific case.

If I don't do this, it points to a meaningless address.

Let me know if there can be any issues with this.
@NikolajSchlej NikolajSchlej merged commit 29915ca into LongSoft:new_engine Aug 18, 2023
10 checks passed
@XutaxKamay XutaxKamay deleted the new_engine-1 branch August 18, 2023 17:33
@XutaxKamay
Copy link
Contributor Author

XutaxKamay commented Aug 19, 2023

Sorry, but I just noticed that it does indeed make a problem, FTPR.man does not point anymore to the right base address, I think the header size will likely be needed to be added on the offset field in the Types::CpdExtension. I'll make another pull request to revert this and fix it again

@NikolajSchlej
Copy link
Collaborator

For future similar changes let's start with a GH issue with files and screenshots demonstrating the problem, will be easier to prevent multiple fixes for the same problem this way.

@XutaxKamay
Copy link
Contributor Author

For future similar changes let's start with a GH issue with files and screenshots demonstrating the problem, will be easier to prevent multiple fixes for the same problem this way.

I'll do that, thank you.

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.

None yet

2 participants