-
Notifications
You must be signed in to change notification settings - Fork 3k
Update uVisor with new page allocator #2558
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 |
@@ -352,6 +347,7 @@ SECTIONS | |||
} | |||
|
|||
/* Initializes stack on the end of block */ | |||
__StackTop = ORIGIN(m_data_2) + LENGTH(m_data_2); |
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.
Looks like the stack was moved to the end of RAM. This should increase the heap size so +1.
Also, the GCC specific tweaks can now be removed in RTX_CM_Lib.h:
#if defined(__GNUC__) && !defined(__CC_ARM) /* GCC */
extern uint32_t __StackTop[];
#define INITIAL_SP (__StackTop)
#else
#define INITIAL_SP (0x20030000UL)
#endif
@meriac You aren't currently on the white list for the morph bot, sorry about that! I have to do some maintenance on the test boxes today, so when that's done I'll add you to the whitelist. I'll trigger your PR as well. |
@bridadan Thanks a lot! Can you please trigger a new test? I updated my pull request. |
@sg- @c1728p9 @0xc0170 As recommended we reverted the K64F-specific StackTop-reference. Please trigger a test and merge. |
Looks good to me! |
/morph test |
Result: ABORTEDYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 726 Build Prep failed! |
I had to abort the test temporarily as some infrastructure changes are going through right now, I'll retrigger them after I've verified things are ready to go. |
/morph test |
@mbed-bot: TEST HOST_OSES=ALL |
[Build 853] |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 733 Test failed! |
Morph tests look ok, all failing due to a known issue measuring timing-based tests on host PCs. 👍 |
@mbed-bot: TEST HOST_OSES=ALL |
[Build 855] |
@sg- LGTM 👍 |
@sg- @AlessandroA @0xc0170 @c1728p9