Index: 06_features/funcmap/index.html
===================================================================
--- 06_features/funcmap/index.html	(revision 9391)
+++ 06_features/funcmap/index.html	(revision 9392)
@@ -54,6 +54,7 @@
 	<li> <a href="#cli"> CLI: actions </a>
 	<li> <a href="#gui"> GUI: dialog boxes and menus </a>
 	<li> <a href="#drc"> DRC: design rule checks </a>
+	<li> <a href="#boxsym"> boxsym-rnd aspects </a>
 	<li> <a href="#example"> Example: using the system in practice </a>
 </ul>
 
@@ -284,5 +285,21 @@
 monolithic symbol and the corresponding funcmap file. Ports Vcc and GND
 are not mentioned in the funcmap file since those ports are single-function.
 
+<H4 autotoc="yes"> boxsym-rnd aspects </H4>
+<p id="boxsym">
+The symbol for MCUs and CPUs are typically generated using a tool, such
+as boxsym-rnd. To play nicely with funcmap, the only requirement is that
+the tool generates the affected terminal labels to use dyntext
+%../a.funcmap/name%. In boxsym this is done when the funcmap property
+(without any argument) is added to a pin block.
+<p>
+Boxsym-rnd does not generate the funcmap file; the funcmap file shall be
+written manually. It is common that an MCU or CPU symbol is a heavy symbol
+thta works with only one funcmap. In that case the funcmap attribute could
+be specified on component level (in the global section of the boxsym
+input file).
+
+
+
 </body>
 </html>