-
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
Add support for MIMXRT1170_EVK #14394
Conversation
…own folder and generic in IMX folder
This PR cannot be merged due to conflicts. Please rebase to resolve them. |
@s-bruce13, thank you for your changes. |
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.
Please describe your changes in the first section in your first comment (Summary of changes
).
How was this tested, can you paste logs to confirm this run all tests?
targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MIMXRT1170/CMakeLists.txt
Outdated
Show resolved
Hide resolved
targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MIMXRT1170/CMakeLists.txt
Outdated
Show resolved
Hide resolved
targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MIMXRT1170/TARGET_EVK/CMakeLists.txt
Outdated
Show resolved
Hide resolved
I am trying to do pull request by pieces, so I am submitting the serial and timers first. Based on Porting Guide online I did these two tests.
Build successes:
Memory map breakdown for built projects (values in Bytes):
Build successes:
Is there a different test I should be running? |
@s-bruce13 you have modified the default header template by removing sections, please put them back and do not remove in the future - thanks. |
@adbridge, i apologize i didnt realize i deleted sections. How can I retrieve the original template? |
@s-bruce13 just click on create new PR and copy from there :) OR I can fix it for you this time |
Fixed |
Thank you!! |
@0xc0170 Hello, I posted my test results. I am not sure if I should be running a different test than the ones mentioned in the porting guide. Could you please advice what I need to check? |
CI started |
Yes, run all the tests, do not specify |
@0xc0170 @hugueskamba @gpsimenos ok, thank you so should the last test "continuous-integration/jenkins/pr-head " be able to pass as is? or what needs to happen next for this pull request to be merged? |
Please rebase your branch as soon as #14457 is merged (should be very soon), and then your PR will be able to pass Jenkins CI. |
@gpsimenos @0xc0170 @adbridge @hugueskamba |
@adbridge @0xc0170 @hugueskamba Hello all hope you are well. Is it possible to start the CI? |
@s-bruce13 unfortunately we are having some CI issues currently and the CI team are on Easter vacation so we are restricted to running one PR at a time (this is in the queue). |
@adbridge thank you for letting me know! |
@adbridge Hello Anna, hope you are doing well. I just wanted to ask if you had a rough estimate as to a timeline on when the CI will be run based on the queue you mentioned? |
CI started |
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.
@s-bruce13 Looking at the history, can you rebase to fix some commits ("same" for instance could be squashed, and add better description to some commits). As this is a new target, this could be consolidated into couple of commits.
Jenkins CI Test : ❌ FAILEDBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
@0xc0170 Do I have to rebase with the latest release(5..15.7, is that correct)? also how can I confirm why it failed these 4 tests? There is no "failed" folder in the logs for the CI tests. for cloud example, there is a log for the mimxrt1170 in the "PASS" folder. Is this correct? I am and have been running all tests on my end and are passing, did I miss something? |
Cmake error:
Please fix. To rebase, just use interactive rebase to squash some commits. |
@0xc0170 I've been attempting to rebase with the interactive rebase. However it presents merge conflicts and shows commits that are not part of my pull request, so I am unable to squash the commits properly. Should I close this PR and open a new one, with the latest fix? |
A new PR might be easier if you can't resolve the conflicts (there are couple of merges on your master that should not be there). |
got it will do! |
Summary of changes
Adding Support for the MIMXRT1170_EVK
Impact of changes
Migration actions required
Documentation
Pull request type
Test results
Reviewers