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
Removed cymetadata section from FUTURE_SEQUANA targets #10011
Conversation
This data, placed at physically not existing addresses (0x9xxxxxxx) was used only by PSoC Programmer and KitProg2 and is no longer needed, but was causing issues with standard hex file processing tools like srecord (srec_cat).
@lrusinowicz could you please also update the FUTURE_SEQUANA_PSA secure images with |
New PR or here? Just to know when to start CI for this one |
@orenc17
I might not be on proper master commit for it. Anyway, as exporters should stop failing even with old images I would rather wait for merge and then update images from clean master. |
@lrusinowicz this error is fixed in the latest master |
CI started |
Test run: SUCCESSSummary: 13 of 13 test jobs passed |
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.
Meets criteria, fix for target to support PSA. Approved.
Description
This data, placed at physically not existing addresses (0x9xxxxxxx) was used
only by PSoC Programmer and KitProg2 and is no longer needed, but was causing
issues with standard hex file processing tools like srecord (srec_cat).
@0xc0170
This should remove nightly exporter failures (#9611).
Pull request type
Reviewers
Release Notes