8 byte stack alignment and some definition changes for RAM on L4 devices #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The two SRAM address spaces aren't contiguous on devices from L471 to L486. This led to run time errors (hard fault) on the first call in the start up file.
For the use of printf and scanf it is mandatory, that the stack is 8 byte aligned.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Edited the linker script for stack alignment. It is a problem with newlib, that printf and scanf only works fine for floats if the stack is aligned to 8 bytes. See also RIOT-OS/RIOT#1891.
Some L4 devices have a non-contiguous RAM address space. These definitions for memory size were changed to avoid run time errors.