summaryrefslogtreecommitdiff
path: root/docs/faq_build.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq_build.md')
-rw-r--r--docs/faq_build.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/faq_build.md b/docs/faq_build.md
index e4e69b912d..b86f2177a0 100644
--- a/docs/faq_build.md
+++ b/docs/faq_build.md
@@ -57,8 +57,8 @@ Also see this.
https://github.com/tmk/tmk_keyboard/issues/150
You can buy a really unique VID:PID here. I don't think you need this for personal use.
-- http://www.obdev.at/products/vusb/license.html
-- http://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1
+- https://www.obdev.at/products/vusb/license.html
+- https://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1
### I just flashed my keyboard and it does nothing/keypresses don't register - it's also ARM (rev6 planck, clueboard 60, hs60v2, etc...) (Feb 2019)
Due to how EEPROM works on ARM based chips, saved settings may no longer be valid. This affects the default layers, and *may*, under certain circumstances we are still figuring out, make the keyboard unusable. Resetting the EEPROM will correct this.