-
Notifications
You must be signed in to change notification settings - Fork 653
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
[WIP] Bare Metal VCU118 Capability #1892
base: main
Are you sure you want to change the base?
[WIP] Bare Metal VCU118 Capability #1892
Conversation
…TSI connection in the same way as the Arty. Issues: The non-TSI UART pins map to the same as the TSI pins, so I moved them to unused pins on the PMOD connectors, but this required modification of fpga-shells. Also, the LEDs do not work for the TSI connection yet.
Right, you'd need a separate PMOD UART for the target UART
The LEDs were a debug feature when I was setting it up on the Arty. Not require for VCU118, but still very useful. |
So would we want another PR for fpga-shells which implements a different PMOD UART which uses say the male connectors on the vcu118? There is no other spare female PMOD connector. This will definitely need to be changed as the normal Linux test harness will need the UART over the USB, whereas with the bare-metal approach it can be put on PMOD like the Arty. Is there perhaps a way to override the pins specified in fpga-shell for this?
I will see if I can add them... Anything else that needs to be done from what you can see? |
…s as status blinkers for the CPU itself but I am borrowing the VCU118 and do not have time to test it currently.
@@ -63,6 +69,37 @@ class WithVCU118Tweaks extends Config( | |||
new freechips.rocketchip.subsystem.WithNMemoryChannels(1) | |||
) | |||
|
|||
class WithVCU118TweaksBareMetal extends Config( |
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.
Can we drop the "BareMetal" naming, and name it UARTTSIVCU118
in all places. The "baremetal" terminology I feel does not accurately describe what the additional capability of these configs is.
harnessIO <> port.io.uart | ||
val packagePinsWithPackageIOs = Seq( | ||
("AW25" , IOPin(harnessIO.rxd)), | ||
("BB21", IOPin(harnessIO.txd))) |
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.
Your comment indicates that this overlaps with the UART device, which uses the UARTOverlay-generated pins in the VCU118TestHarness, but this generates its own pins. Do these overlap with the UARTOverlay pins?
Added new configs and harness binders for the VCU118 to use the UART TSI connection in the same way as the Arty
Issues: The non-TSI UART pins map to the same as the TSI pins, so I moved them to unused pins on the PMOD connectors, but this required modification of fpga-shells. Also, the LEDs do not work for the TSI connection yet.
Type of change:
Impact:
Contributor Checklist:
main
as the base branch?changelog:<topic>
label?changelog:
label?.conda-lock.yml
file if you updated the conda requirements file?Please Backport
?