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

USB speed is capped to Full Speed when using a custom UTMI PHY #276

Open
jeanthom opened this issue Sep 11, 2024 · 0 comments · May be fixed by #277
Open

USB speed is capped to Full Speed when using a custom UTMI PHY #276

jeanthom opened this issue Sep 11, 2024 · 0 comments · May be fixed by #277
Labels

Comments

@jeanthom
Copy link

Hi,

I recently noticed that when using Luna with a custom UTMI PHY, it would limit itself to USB FS. The limit is a hardcoded value:

else:
self.utmi = bus
self.bus_busy = Const(0)
self.translator = None
self.always_fs = True
self.data_clock = 12e6

There is no technical limitation preventing us from doing USB HS: we tested a modification of these constants successfully with a ULPI-UTMI translator.

Jean

jeanthom added a commit to lambdaconcept/luna that referenced this issue Sep 11, 2024
Removes Full Speed limitation when using custom UTMI PHY. Bump the
associated to 60 MHz (required for achieving 480Mbps throughput).

Fixes greatscottgadgets#276
jeanthom added a commit to lambdaconcept/luna that referenced this issue Sep 11, 2024
Removes Full Speed limitation when using custom UTMI PHY. Bump the
associated clock to 60 MHz (required for achieving 480Mbps throughput).

Fixes greatscottgadgets#276
povauboin pushed a commit to lambdaconcept/luna that referenced this issue Sep 26, 2024
Removes Full Speed limitation when using custom UTMI PHY. Bump the
associated clock to 60 MHz (required for achieving 480Mbps throughput).

Fixes greatscottgadgets#276
@martinling martinling added the bug label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants