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.

Sign up for GitHub

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

Jump to bottom

Add TE0714-03-50-2l #97

Merged
merged 1 commit into from
Nov 24, 2020
Merged

Add TE0714-03-50-2l #97

merged 1 commit into from
Nov 24, 2020

Conversation

rroohhh
Copy link
Contributor

@rroohhh rroohhh commented Aug 4, 2020 •
edited
Loading

The SPIFlashResource defined for this board is connected to the configuration interface, this means one cannot drive the clock directly, but one has to use the USRCCLKO primitive. Any guidance on how to reflect this in the platform file?

@rroohhh rroohhh force-pushed the master branch 2 times, most recently from 0bf6c92 to 5bb39c7 Compare August 5, 2020 15:22
@rroohhh rroohhh marked this pull request as ready for review August 5, 2020 15:25
@whitequark
Copy link
Member

The SPIFlashResource defined for this board is connected to the configuration interface, this means one cannot drive the clock directly, but one has to use the USRCCLKO primitive. Any guidance on how to reflect this in the platform file?

We can't do this yet, but I have plans to fix this in near future.

whitequark
whitequark requested changes Nov 24, 2020
View reviewed changes
Copy link
Member

@whitequark whitequark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide an URL for the board documentation?

Does the board have no way to program it?

Even if the answer to the above is "yes", having blinky with do_program=False would still be quite useful for smoke testing.

@rroohhh
Copy link
Contributor Author

rroohhh commented Nov 24, 2020 •
edited
Loading

Can you provide an URL for the board documentation?

The schematic can be found here.
Looking it up again made me notice that the last letter is not a small L but a capital i instead :)

Does the board have no way to program it?

The board has the JTAG only on the expansion connector, so the programming method depends on how you break that out.

Even if the answer to the above is "yes", having blinky with do_program=False would still be quite useful for smoke testing.

Sure makes sense.

@whitequark whitequark merged commit ad9408d into amaranth-lang:master Nov 24, 2020
@whitequark
Copy link
Member

Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@whitequark whitequark whitequark approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rroohhh @whitequark