-
Notifications
You must be signed in to change notification settings - Fork 317
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
wifi: Add storing of FW patching in external flash #1125
Merged
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
9968c76
to
fc88e44
Compare
rado17
approved these changes
Nov 15, 2023
38add2d
to
86d36e9
Compare
sachinthegreen
approved these changes
Nov 21, 2023
sachinthegreen
requested changes
Nov 21, 2023
sachinthegreen
approved these changes
Nov 21, 2023
86d36e9
to
4f1cf97
Compare
0986aef
to
2377175
Compare
This can now be used by any firmware download approach. Signed-off-by: Chaitanya Tata <[email protected]>
Introduce APIs for reset and boot that can be used by higher layers separately to the load and also the APIs take care of all processors. Signed-off-by: Chaitanya Tata <[email protected]>
This can be used by callers instead of directly exposing the addresses outside HAL. Signed-off-by: Chaitanya Tata <[email protected]>
Now that we are reading from flash, in order to have low RAM requirements we need an API to copy chunks of firmware that are read from flash directly and copied to RPU. This is basically a wrapper around HAL write, but can be extended in the future to abstract more functionality. Signed-off-by: Chaitanya Tata <[email protected]>
This makes it easier to access data. Note: Zero-length arrays are non-standard and aren't allowed in Zephyr. Signed-off-by: Chaitanya Tata <[email protected]>
For any HAL API we need to set the current processor appropriately to valid and get the respective memory addresses, but the settings was missed here. As these APIs aren't used for MCU addresses, this isn't an issue but fix it for future. Signed-off-by: Chaitanya Tata <[email protected]>
Convert to data driven programming, makes the code readable. Signed-off-by: Chaitanya Tata <[email protected]>
In order to keep the behaviour same across various firmware patch loaders, load UMAC first and then LMAC, functionally this doesn't matter but for comparing during debugging it makes it easier. Signed-off-by: Chaitanya Tata <[email protected]>
Log what is expected also. Signed-off-by: Chaitanya Tata <[email protected]>
2377175
to
a9904da
Compare
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.