-
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
Improve the startup code on the STM32F070 #4525
Conversation
This reduces the number of loads inside of the .data copy loop by 3 by using one more register. It should work on any STM32 with at least 5 general-purpose registers. If only 4 are available, then 1 load could still be removed from the original implementation.
retest uvisor |
I don't have the ability to do that, nor can I even see the details |
@fahhem Hello - have you developed this code from scratch in the context of MBED or has this already been exercised before in another context ? |
I first used it in my custom board with the same chip as the nucleo f070rb
board. It's working for me and I figured it would be useful to upstream it.
It seems the original version was developed for a chip with only 4
registers available and was copied to bigger chips without redesign?
…On Jun 13, 2017 12:12 AM, "Laurent Meunier" ***@***.***> wrote:
@fahhem <https://github.com/fahhem> Hello - have you developed this code
from scratch in the context of MBED or has this already been exercised
before in another context ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4525 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASrtIb-TKn0NLOerbf9MR3iNTetQbzcks5sDjZLgaJpZM4N3BiA>
.
|
ST_INTERNAL_REF 34824 |
@bcostm Will you be updating this in the ST SDK? Should we close this PR? |
We are going to launch some tests first and we'll let you know if ok to merge. |
All tests are OK |
Glad I could help! |
CLA checked, signed ;) Waiting for CI |
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
That looks like it failed due to a totally untouched processor timing out, so it seems like it's just flaky? https://mbedosci.cloudapp.net/results/pr/4525/645/FAIL/NCS36510/IAR/test_report_NCS36510-IAR.html |
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
Seems like it's another different board that's failing. Is morph normally this flaky? |
/morph test |
Ah, we limit the users who can trigger our CI. We don't want it DDOSed after all. Let me get that for you. /morph test |
Is it normal for the CI to be this flaky? |
Nope. We just merged a few robustness improvements for the CI. I think this run should be more stable. |
retest uvisor |
It failed to update the status :( |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Looks like ram usage went up since the last release for stm32 boards, but not just this one. |
Can you elaborate? |
retest uvisor |
Description
This reduces the number of loads inside of the .data copy loop by 3 by using one more register. It should work on any STM32 with at least 5 general-purpose registers. If only 4 are available, then 1 load could still be removed from the original implementation.
Status
READY
Migrations
NO
Steps to test or reproduce
Run any program with a non-empty
.data
section (globals, for instance).