Deploying to main from @ pyocd/pyocd-website-source@f729eea 🚀

Author: pyocd-bot

docs/gdb_setup.html

@@ -240,10 +240,14 @@ <h2 id="standalone-gdb-server">Standalone GDB server</h2>
 
 <h2 id="recommended-gdb-and-ide-setup">Recommended GDB and IDE setup</h2>
 
-<p>The recommended toolchain for embedded Arm Cortex-M development is <a href="https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm">GNU Arm
-Embedded</a>,
+<p>The recommended toolchain for embedded Arm Cortex-M development is <a href="https://developer.arm.com/downloads/-/gnu-rm">GNU Arm
+Embedded</a> (GNU-RM),
 provided by Arm. GDB is included with this toolchain.</p>
 
+<p>Note that the version of GDB included with the new, combined Arm GNU Toolchain as of version 11.2-2022.02
+<em>will not</em> work with pyOCD. This is because it is currently built without the required support for the XML
+target descriptions that pyOCD sends to GDB. Versions later than 11.2-2022.02 may have this bug fixed.</p>
+
 <p>For <a href="https://code.visualstudio.com">Visual Studio Code</a>, the
 <a href="https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug">cortex-debug</a> plugin is available
 that supports pyOCD.</p>

docs/target_family_notes.html

@@ -218,6 +218,11 @@ <h5 class="sidebar-header">On this page</h5>
 <li class="toc-entry toc-h3"><a href="#kinetis-family">Kinetis family</a></li>
 </ul>
 </li>
+<li class="toc-entry toc-h2"><a href="#hdsc">HDSC</a>
+<ul>
+<li class="toc-entry toc-h3"><a href="#hc32l110">HC32L110</a></li>
+</ul>
+</li>
 </ul>
                     </div>
                   </div>
@@ -270,6 +275,12 @@ <h3 id="kinetis-family">Kinetis family</h3>
 <p>Unlocking of flash security is supported for all Kinetis targets. For more, see the
 <a href="/docs/security.html">security and protection</a> documentation.</p>
 
+<h2 id="hdsc">HDSC</h2>
+
+<h3 id="hc32l110">HC32L110</h3>
+<p>The documentation for this chip states that no external pull-up resistors are required on the SWD lines due to the internal pull-up
+hardware. Testing has found this to be largely inaccurate. Most debug probes will require an external 4.7k&amp;ohm; pull-up resistor 
+between Ports P27/P31 and V+.</p>
 
 
                 </div>