Update to upstream modm develop #12
Merged
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 channel ids were incorrectly sorted as strings and then converted to int. The conversion must happen first for the correct ordering. The bug has no practical effect since no device has more than 8 channels.
FDCAN on STM32G0 is currently not supported due to the shared interrupt handler.
The data sections were previously placed into the first memory of the contiguous section with the lowest address. The selection is changed such that the first memory of the largest contiguous ram section is used. For all supported Cortex-M devices except STM32H7 the resulting linker script will be identical. On STM32H7 .data is currently placed into the DTCM which is not accessible by peripheral DMA transfers. With the new method the D1 AXI SRAM is used for .data while .fastdata remains in the DTCM.
- Remove defunct Twitter Account. - Fix dead links. - Replace system overview graphic.
Since Python 3.6 backslash-character pairs that are not valid escape sequences are deprecated and generate a 'SyntaxWarning: invalid escape sequence' warning. This is fixed by using raw string.
* [menu] Add optional allocator for ui menu classes, used for destroying AbstractViews * [menu] remove coupling between modm gui and modm menu view and menu This is because the gui stuff requires colored menus but the menu code should not have to have colored menus. This wouldn't be an issue if we could dynamic cast but on certain devices you can't do this.
When pulling from upstream develop, AllocatorBase has been moved to utils/allocator.hpp. This commit simply re-introduces safe fail behavior into AllocatorBase.construct and AllocatorBase.destroy that was previously added by Matthew Arnold (see 3ed0768 for more details).
* [menu] Add optional allocator for ui menu classes, used for destroying AbstractViews * [menu] remove coupling between modm gui and modm menu view and menu This is because the gui stuff requires colored menus but the menu code should not have to have colored menus. This wouldn't be an issue if we could dynamic cast but on certain devices you can't do this.
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.
No description provided.