-
Notifications
You must be signed in to change notification settings - Fork 3
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
docs/SoC_Gowin_GW1NSR.md: document describing Gowin SoC tests added #41
base: main
Are you sure you want to change the base?
Conversation
|
||
## SoC requirements for TPM | ||
|
||
As previously stated (and described), a TPM candidate must meet the following |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@macpijan AFAIK we don't have it described in a single place (and consistent way). We could create separate document for that a and link it here and in other places instead of repeating ourselves.
part is required, it is not possible to use this memory as RAM for the hard CPU. | ||
|
||
This fact disqualifies Gowin's SoC from the GW1NSR-4C series as a hardware TPM | ||
module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why lack of hardware controller would be a problem when we can have an equivalent on FPGA? Can't the FPGA based controller decode cycles coming from AHB and "forward" communication to/from SRAM?
The project documentation shows that, among others: | ||
|
||
+ BRAM blocks in FPGA fabric are not properly handled | ||
+ PLL clocks are not supported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What problems do arise from lack of this functionality?
Signed-off-by: Maciej Gabryelski [email protected]