Skip to content
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

Fomu platform definition updates #1

Merged
merged 2 commits into from
Jun 10, 2019

Conversation

TomKeddie
Copy link
Owner

Update @mithro fomu platform defs from @xobs foboot and try to make them all match the litex style a little more. Working towards resolving im-tomu/foboot#2

all match the litex style a little more
@xobs
Copy link

xobs commented Jun 6, 2019

You should rename fomu_dvt.py to fomu_pvt.py. There ended up being exactly one DVT board in existence that worked. Production boards go by the moniker pvt.

@TomKeddie TomKeddie requested a review from mithro June 6, 2019 04:09
@TomKeddie
Copy link
Owner Author

TomKeddie commented Jun 6, 2019

@xobs or perhaps rename just plain fomu.py? I added you as a collaborator, lets do a local review here make sure the definitions are what you want and I'll work to move it upstream from here.

@mithro
Copy link
Collaborator

mithro commented Jun 6, 2019

@TomKeddie I think fomu-hacker and fomu-pvt make sense.

@xobs
Copy link

xobs commented Jun 7, 2019

Likewise, neither the hacker nor production boards have serial pins connected.

- rename dvt to pvt
- remove serial from both pvt and hacker
- remove NC spi wp and hold pins from hacker
- remove spiflash4x as pins are NC
Added links to schematic/cad data
@TomKeddie TomKeddie merged commit ac9d013 into tomk_20190605_fomu_reviewed Jun 10, 2019
@TomKeddie TomKeddie deleted the tomk_20190605_platform_fomu branch June 10, 2019 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants