-
Notifications
You must be signed in to change notification settings - Fork 3k
Updates to Maxim Integrated targets. #2832
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
Conversation
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 973 Build failed! |
Looks like both MAXWSNENV and MAX32600MBED are running out of RAM for the STL test when compiling with GCC:
@jeremybrodt Can you reproduce this locally when you merge with master? |
Yes. After rebasing, I am getting this compile error. I will adjust the stack size and push another commit. |
This appears to be a side effect of the moving of the 'targets' directory. I moved the library files that I added to the new location. |
e733fd9
to
f56f5dc
Compare
I reran the mbed test suite with these new commits. All tests pass. |
a300352
to
a8de1d1
Compare
retest uvisor |
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
@jeremybrodt Can you please rebase? A cmsis restructure was just merged |
a8de1d1
to
2dc78be
Compare
Ok. I have rebased and addressed the merge conflicts. |
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 1083 Build failed! |
@jeremybrodt Maxim targets fail to compile. One of the failures: MAXWSNENV: ARM and GCC_ARM |
@0xc0170 I have resolved the issue with MAXWSNENV. I am rerunning mbed tests now. I do not see a build failure on MAX32600MBED, and hci_drv.c does not exist for that platform. Is there a different compile error you are seeing for that platform? |
2dc78be
to
1d2d743
Compare
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 1094 Build failed! |
Getting this error:
We use this command in CI to turn on some extra metrics:
Can you reproduce this error locally? |
All tests compile successfully for me using this command. Perhaps we are using different GCC versions. |
1d2d743
to
b4e2339
Compare
/morph test |
retest uvisor |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 0 All builds and test passed! |
Clean up, updates and fixes for issues uncovered during further testing. All mbed tests pass with one exception. The MAX32620HSP platform only has one LED, causing failure on the two tests that use LED2. Test results are attached.
max32620hsp_test_results_20160927.txt
max32600mbed_test_results_20160927.txt
maxwsnenv_test_results_20160927.txt