From 89904dc35603f04619e20a50d0f563d46074204b Mon Sep 17 00:00:00 2001
From: Bassam Husain <bassam.husain@gmail.com>
Date: Thu, 2 Jan 2025 22:43:53 -0500
Subject: [PATCH] Add mcu timer too close error to special considerations.

---
 .vscode/settings.json | 3 +--
 README.md             | 6 ++++++
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/.vscode/settings.json b/.vscode/settings.json
index 46bdbfe..06f81c1 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -1,7 +1,5 @@
 {
 	"editor.tabSize": 4,
-	// "editor.formatOnSave": false,
-	// "editor.defaultFormatter": null,
 	"editor.insertSpaces": true,
 	"editor.detectIndentation": false,
 	"git.mergeEditor": false,
@@ -20,6 +18,7 @@
 		"Klipper",
 		"Klipperized",
 		"lrwxrwxrwx",
+		"microsteps",
 		"moonraker",
 		"normalsize",
 		"octahedroflake",
diff --git a/README.md b/README.md
index d8a1031..0ffcae4 100644
--- a/README.md
+++ b/README.md
@@ -318,6 +318,12 @@ In PrusaSlicer, please see Printer Settings > Notes, for extruder clearances.
 
 Renamed to `_BED_MESH_CALIBRATE`.
 
+### Errors
+
+#### MCU 'mcu' shutdown: Timer too close
+
+This error often occurs when the `mcu` is unable to generate the required `microsteps`. Lower power Klipper hosts might be especially susceptible. Reducing `microsteps` to `64`, or even `32` can resolve the issue.
+
 [🔼 Back to top](#outline)
 
 ## FAQ