From 0b2a1666558dbbd8d74753d2cc3f78ab6d2ae168 Mon Sep 17 00:00:00 2001
From: -Z3US- <32334634+cyberlooper@users.noreply.github.com>
Date: Mon, 21 Jun 2021 10:10:16 +0100
Subject: [PATCH] Added link to Memory Map spreadsheet

An easy to use sectioned memory map for drilling down into the issue. Blank out or colour the regions that are not at fault to result in a specific RTC blacklist for the user.
---
 misc/rtc.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/misc/rtc.md b/misc/rtc.md
index c759e617..8ea8c70a 100644
--- a/misc/rtc.md
+++ b/misc/rtc.md
@@ -61,6 +61,7 @@ Regarding splitting out chunks, what we'll be doing is omitting chunks of RTC re
 
 * Also note that the final bad spot will usually be a range and not a singular spot.
 * ie. `rtcfx_exclude=85-86` instead of one singular value
+* Cyberlooper has provided an easy to use sheet for the memory map. You can colour out the regions that are safe, you can drill down with each collums until you have found the region(s) that are at fault. You can find it here, https://docs.google.com/spreadsheets/d/1vSvhE2P0roNJFnCkfsRN0a_ZLhdLFIuEkkjPIa6IBHE/edit?usp=sharing
 
 **Pro tip**: To find a value in between 2 regions, I recommend first converting from hexadecimal to decimal, then run the below equation: