\frame{\frametitle{Associated Extras}
\begin{itemize}
- \item Design Specification
- \item Scenario analysis (whether the chip will fit "markets")
+ \item Design Specification (what markets to target)
+ \item Scenario analysis ({\bf whether} the chip will fit "markets")
\item Documentation: Summary sheet, Technical Reference Manual.
\item Test suites
\item Control Interface (AXI4 / Wishbone / TileLink / other)
}
+\frame{\frametitle{Example: 7 banks, 4-way mux, 160 pins}
+ \begin{center}
+ \includegraphics[height=1.7in]{example_pinmux.jpg}
+ \end{center}
+ \begin{itemize}
+ \item { \bf 17,500 lines of auto-generated HDL (and climbing)}
+ \item { \bf 12,500 lines of auto-generated Summary/Analysis}
+ \item Technical Reference Manual expected to be 100+ pages
+ \end{itemize}
+}
+
+
\frame{
\vspace{30pt}
\begin{center}
-\frame{\frametitle{Example: 7 banks, 4-way mux, 160 pins}
- \begin{center}
- \includegraphics[height=1.7in]{example_pinmux.jpg}
- \end{center}
- \begin{itemize}
- \item { \bf 17,500 lines of auto-generated HDL (and climbing)}
- \item { \bf 12,500 lines of auto-generated Summary/Analysis}
- \item Technical Reference Manual expected to be 100+ pages
- \end{itemize}
-}
-
-
\frame{\frametitle{Muxer cases to handle (One/Many to One/Many) etc.}
\begin{itemize}
\frame{\frametitle{Summary}
\begin{itemize}
- \item TODO
+ \item Actual muxing, like SRAM cells, is deceptively simple
+ \vspace{10pt}
+ \item Actual pinmuxes are enormous: auto-generation essential
+ \vspace{10pt}
+ \item HDLs completely unsuited to auto-generation task\\
+ (TRM, docs): { \bf Modern OO language features needed}
+ \vspace{10pt}
+ \item Scenario Analysis / Verification and auto-generation of
+ different HDLs far easier in a Modern OO language
+ \vspace{10pt}
+ \item Standardisation for RISC-V saves implementors from huge
+ duplication cost (HDL, firmware, docs, maintenance)
+ \vspace{10pt}
+ \item { \bf Ultimately it's about saving money and reducing risk }
\end{itemize}
}