Add support for 128KB flash MCUs #25
Draft
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
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.
When porting AM32 to the STM32G0B1 I noticed that the configurator actually doesn't work with MCUs that have 128KB of flash for multiple reasons.
The first reason is because there is no target with that signature. The second reason is because the eeprom memorry addressing for
0x1F800didn't work. It failed when trying to get the ESC filename because it was subtracting 32 bytes from the already shifted address instead of the real address.I had it working previously, but I made some changes and I haven't tested in the latest form.