Open
Conversation
sequencer
requested changes
Feb 22, 2023
ZenithalHourlyRate
force-pushed
the
usb
branch
from
b03bb73 to
cdc24c8
Compare
A USB 1.1 Full speed device is implemented. Actually it is USB 2.0 compliant as additional requests can be handled in software, but to make things less confusing we say it is USB 1.1. It is an end-to-end solution, as it can be easily attached to the tilelink/axi4 bus and in the end it outputs two top io for RX/TX. The controller and PHY is not strictly separated, and it does not have a standard UTMI/ULPI port. The MMIO port is also custom. The architecture for it may be found in slides of RVSC22[1]. The driver for it may be found in [2]. Some part of the driver is quite similar to tinyUSB so it may get ported there. It has been verified in an Arty100t FPGA, capable of running the required USB stack of canokey (a yubikey alternative) [1]. The control, bulk and interrupt transfer types worked, but the support of isoc transfer is not added. [1] https://github.com/OpenRigil/rvsc22 [2] https://github.com/OpenRigil/openrigil-firmware
|
Do you consider adding UTMI(+) IO support? |
Author
I wanted to add them a long time ago but I'm afraid there is no ETA for it |
Member
|
We have sent out the first PCB board to JLC today, I'll approve the RTL after the FPGA test. |
Author
It works with such FMC board. Great thanks to @vowstar for designing the board! I've tested USB enumeration and USB reset and they worked. I will test bulk transfer with large payload and interrupt transfer later once I get an SPI flash installed on the FMC. Will update the PR with minor fixes so do not merge yet. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The info about the device itself is in the commit message.
I have personally tested it to be working, but unfortunately, there is no vigorous test for it. A vigorous test for this means substantial work and I did not have that bandwidth at that time and now.
As for the merge policy, as far as I can tell there is no merge policy for this repo. I'm willing to contribute this RTL to chipsalliance as this eases the burden of maintenance, but I have no clue what else should be done.
This PR may not get merged and anyone interested may test it and report the status here.