-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Merge supervisor firmware tree into mainline #42
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
…ing embedded code, I swear.
… they're needed by other things and can't always be inlined. Also had to tell GCC to *not* replace the implementation of these functions with calls to them, because we are, in fact, the implementation of said calls, thanks GCC
…re-link if it changes
…rgs to the linker also gets them
…slation units, seizing the means of production
…d pin needed pin initialization to `setup_io`
…rs, and disambiguated the names
…ing into an SPI specific implementation. Also, set up the framework for reading and writing from the on-board configuration flash, along with validating the link by checking the ID
This is due to the fact that the ARM Cortex-M0+ does not have any atomic instructions, and we're not able to link against any stdlibs, ***AND*** libatomic isn't even included with the compiler for this platform anyway.
… for things for a set amount of time
…from a span of bytes
…should have been done
…ove it in line with the other naming conventions
… entries causing the SysTick handler to be in the wrong spot, i'm surprised anything worked
… to be in config mode (with the appropriate delay)
…FLASH into the FPGA
… would have caused due to calling a naked function
…to set the LEDs to a known state
…lash and FPGA id failure, relying on just the new fault system
…ning despite other interrupts to ensure when we hit the fault handler we can still blink out an error code
…n't do a full JEDEC compliant ID read, only enough for our onboard flash
…e extra whitespace
… to the PSRAM from the firmware end
…we brown-out rather than lose all power causing the peripherals to stay configured causing a lockup state on power on from reset
…at least there now
…ermine if we're restarting due to a brownout or not
…ng the core if we browned out
…n advanced address after read for later use
…tstream loading from PSRAM to FPGA
…m out of the PSRAM
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.