-
Notifications
You must be signed in to change notification settings - Fork 136
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
Develop #51
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
Remove all user-specific files from the repo
- to avoid duplicate definitions when simulating the user project example - added a dummy __uprj_netlists with the wrapper includes instead to be able to run the caravel dv tests
- to distinighuish it from what is in the user project example
is split into two parts, one which loads data for I/O pads on the right, and the other which loads data for the I/O pads on the left. This is designed to be "minimally invasive", so all signal vectors remain exactly the same except for the serial load data signals.
…into serial_refactor Pull before push? What changed?
Merging in the fix from the "develop" branch.
- if not given, it defaults to <path-to-project>/mag and <path-to-project>/gds
as the upper SPI flash I/O bits. Added a testbench for running the SPI flash in quad and quad DDR modes. Updated the spiflash.v module to implement reset of continuous mode on MBR command per documentation, although it isn't clear how that is supposed to work. The testbench fails in quad + DDR + continuous mode and possibly the spimemio module needs adjusting.
bidirectional by default on startup (they are configured for input anyway because quad SPI mode is not on at startup); this avoids having to configure the GPIO pins for flash access. Corrected the connections to the registered output for those two pins, which fixes the timer2 testbench.
for tests on Raven with actual hardware, but since the spiflash module does not implement configuration registers, the latency cannot be changed from 8 and so only 8 can be used in the testbench. The qspi testbench now works properly and passes.
qspi testbench, not that it has been corrected, and passes.
- use default pdn script in OL; this removes the 0.24 difference with user project
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.
initial updates for mpw-two