Update UART fabric

[AwesomeTornado]

Closes #505 & #502
@elsevers

Notes

This has been tested on my single AMDS setup and through simulation. It has not been run on anyone else's hardware yet.

The testbench code is unfortunately messy due to me restarting this project three times.

Self-Review

1. Are all images < 40 kB and other files < 300 kB (if not, please carefully assess whether it is worth committing them)? Yes
2. Are all files named according to the appropriate naming convention, i.e., dash-case, camelCase, snake case? Yes
3. Do all Markdown files follow the CONTRIBUTING article template? Yes
4. Do all links work in the material that the PR is adding? Yes
5. Is the PR configured to close the correct issue(s)? Yes
6. Did the PR fully address the Approach section of the issue(s) it is closing? Yes

Reviewer Instructions

Reviewers, please copy and paste a suitable review checklist into your review and answer all questions.

Appendix

This section should be the same for all PRs. Do not edit this section when creating a PR.

Review Checklists

Checklists maintained by the eLev lab for research repositories include:

• Report checklist
• Publication archive checklist (select a checklist from the Approach that corresponds to the step this PR seeks to complete).
• Standard checklist (if none of the above apply).

Standard checklist

1. Are all images < 40 kB and other files < 300 kB (if not, please carefully assess whether it is worth committing them)? **Yes or No**
2. Are all files named according to the appropriate [naming convention](https://github.com/Severson-Group/research-repo-template?tab=readme-ov-file#file-naming), i.e., dash-case, camelCase, snake case? **Yes or No**
3. Do all Markdown files follow the [CONTRIBUTING article template](https://github.com/Severson-Group/.github/blob/main/CONTRIBUTING.md#markdown-documentation-template)? **Yes or No**
4. Do all links work in the material that the PR is adding? **Yes or No**
5. Is the PR configured to close the correct issue(s)? **Yes or No**
6. Did the PR fully address the `Approach` section of the issue(s) it is closing? **Yes or No**

Please work on addressing any **No** items.

[elsevers]

Excellent @AwesomeTornado! I understand it passes the verilog testbench. Do we also have test validation in hardware (i.e., on @knvprasad-dr's hardware)?

[AwesomeTornado]

Half of these edits are confirmed working on @knvprasad-dr’s hardware, I will be testing everything again today,

…

On Tue, Jun 9, 2026 at 7:03 AM Eric Severson ***@***.***> wrote: *elsevers* left a comment (Severson-Group/AMDC-Firmware#514) <#514 (comment)> Excellent @AwesomeTornado <https://github.com/AwesomeTornado>! I understand it passes the verilog testbench. Do we also have test validation in hardware (i.e., on @knvprasad-dr <https://github.com/knvprasad-dr>'s hardware)? — Reply to this email directly, view it on GitHub <#514?email_source=notifications&email_token=ARNJIU7ATSTFFHYSRTOT2VT4674KBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRVHE2TCMZVHE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4659513596>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARNJIU6YQMS4BQF3O7MN75L4674KBAVCNFSM6AAAAACZ7Z7EC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNJZGUYTGNJZGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AwesomeTornado]

@elsevers I have tested this and confirmed it to be working on @knvprasad-dr's hardware.

I believe the Jupyter notebook is a bit out of date, but the graphs look the same between this branch and the previous one.

[elsevers]

Looks good. Let's merge!

1. Are all images < 40 kB and other files < 300 kB (if not, please carefully assess whether it is worth committing them)? Yes
2. Are all files named according to the appropriate naming convention, i.e., dash-case, camelCase, snake case? Yes
3. Do all Markdown files follow the CONTRIBUTING article template? Yes
4. Do all links work in the material that the PR is adding? Yes
5. Is the PR configured to close the correct issue(s)? Yes
6. Did the PR fully address the Approach section of the issue(s) it is closing? Yes