add slides

diff --git a/pinmux/pinmux_chennai_2018.tex b/pinmux/pinmux_chennai_2018.tex
index 4bac34d3bb43e6b0f48d90005935fe0a69f76f39..d9d5a2dc234a7bdb52e6ecc4f06ed2faab0a4ee5 100644 (file)
--- a/pinmux/pinmux_chennai_2018.tex
+++ b/pinmux/pinmux_chennai_2018.tex
@@ -103,7 +103,7 @@
                   auto-generated\vspace{30pt}
        }
        \\
-       (i.e. it would be insanely costly to do them by hand)
+       (from the Design Specification, after Scenario Analysis)
   \end{center}
   
 }
@@ -128,6 +128,30 @@
   \end{itemize}
 }
 
+
+\frame{\frametitle{Design Spec and Scenario Analysis}
+
+ \begin{itemize}
+   \item Analyse the target markets that the chip will sell in\\
+            (multiple markets increases sales volume, reduces chip cost)
+            \vspace{4pt}
+   \item Create a formal (python-based) specification for the pinmux
+            \vspace{4pt}
+   \item Add scenarios then check that they meet the requirements\\
+            { \bf (before spending money on hardware engineers!) }
+            \vspace{4pt}
+   \item Scenarios represent target markets: ICs to be connected\\
+         (GPS, NAND IC, WIFI etc.  May require preliminary schematics
+         drawn up, or client-supplied schematics analysed).
+                \vspace{4pt}
+   \item Analyse the scenarios: if pins are missing, alter and repeat.\\
+                \vspace{4pt}
+   \item Eventually the pinmux meets all requirements...\\
+            { \bf without spending USD \$5m to \$50m to find out }
+  \end{itemize}
+}
+
+
 \frame{\frametitle{Muxer cases to handle (One/Many to One/Many) etc.}
 
  \begin{itemize}