-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Checksum the vector table of the LPC546XX #8319
Conversation
CC @studavekar @0xc0170 @kjbracey-arm |
@c1728p9 Thank you. Can you please make the same change for LPC54114. |
f0307b6
to
04113df
Compare
Updated for the LPC54114 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is better than implementing verify in flash algo just to skip the checksum area.
Everyone else seems to do be doing this via |
@mmahadevan108 you added this target. Is there a reason this didn't inherit from LPCTarget? Should I update this PR so the targets inherit from LPCTarget? |
Please do. I was not aware of the availability of this feature inside mbed-os at the time I added these targets. Thank you. |
04113df
to
8a23fcb
Compare
I rebased this PR to master and updated it to inherit from LPCTarget |
/morph build |
Build : FAILUREBuild number : 3345 |
LPC devices require a checksummed vector table to boot. To ensure this most programmers automatically compute the checksum when programming flash. This causes problems with verification if the original image does not have a checksummed vector table. This is because when reading the data back the checksum location differs from the original image. To fix this verification failure this patch adds a post build hook to checksum the vector table of the LPC54XXX. This fixes flash verification failures due to the checksum not matching.
8a23fcb
to
06c825f
Compare
Reverted this PR to the previous implementation which just adds the post build hook. When these targets inherit from LPCTarget a second EMAC driver is pulled in and causes build errors: |
/morph build |
Build : SUCCESSBuild number : 3453 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 3075 |
Test : SUCCESSBuild number : 3245 |
Description
LPC devices require a checksummed vector table to boot. To ensure this most programmers automatically compute the checksum when programming flash. This causes problems with verification if the original image does not have a checksummed vector table. This is because when reading the data back the checksum location differs from the original image.
To fix this verification failure this patch adds a post build hook to checksum the vector table of the LPC546XX. This fixes flash verification failures due to the checksum not matching.
Pull request type