chore(Boards,MAXUSB,MiscDrivers,PeriphDrivers): Fix most IAR build errors and warnings for MAX32690 #899
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
…ings and errors for MAX32690
|
/clang-format-run |
lorne-maxim
approved these changes
Feb 1, 2024
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.
Description
This PR fixes all build errors and most build warnings. The remaining build warnings are: 1) linker file/flash loader related between IAR and GCC in the SEMA PeriphDrivers, and 2) not explicitly defining the order of volatile access.
The purpose of this PR is to prep the MAX32690 for the IAR new project package.
These changes are compatible with GCC as most warnings are due to unreachable blocks that GCC doesn't catch, or IAR's sensitivity to casts.
Checklist Before Requesting Review