From ac5cbc9b5277913c5a67bb6a1a2bd31664025a23 Mon Sep 17 00:00:00 2001 From: whatmough <pwhatmough@seas.harvard.edu> Date: Mon, 20 Jan 2020 16:31:16 -0500 Subject: [PATCH] Update README.md --- tools/vgen/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/vgen/README.md b/tools/vgen/README.md index 243badc..80d54d9 100644 --- a/tools/vgen/README.md +++ b/tools/vgen/README.md @@ -22,6 +22,8 @@ Maintaining and validating all of this is extremely time consuming and error-pro TODO add figure +.pdf "VGEN") + Fig.~\ref{fig:vgen} gives an outline of the VGEN flow, which operates in two stages. The first step is to update a CSR database with signals from the design, which can be done periodically as the RTL is developed. The VGEN tool automatically updates the database (\texttt{vgen -update}) by parsing RTL modules to find signal names with a matching prefix or postfix that indicates a CSR should be attached to the signal. -- GitLab