Skip to content

Commit 672390c

Browse files
krzychbkrzychb
committed
Mass replacement of http with https urls, fixed broken urls
1 parent 604308f commit 672390c

24 files changed

+69
-69
lines changed

‎components/bootloader/Kconfig.projbuild

+4-4
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ config SECURE_BOOT_ENABLED
5858

5959
When enabling secure boot, JTAG and ROM BASIC Interpreter are permanently disabled by default.
6060

61-
Refer to http://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
61+
Refer to https://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
6262

6363
choice SECURE_BOOTLOADER_MODE
6464
bool "Secure bootloader mode"
@@ -122,7 +122,7 @@ config SECURE_BOOT_VERIFICATION_KEY
122122
PEM formatted private key using the espsecure.py
123123
extract_public_key command.
124124

125-
Refer to http://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
125+
Refer to https://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
126126

127127
config SECURE_BOOT_INSECURE
128128
bool "Allow potentially insecure options"
@@ -133,7 +133,7 @@ config SECURE_BOOT_INSECURE
133133

134134
Only enable these options if you are very sure.
135135

136-
Refer to http://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
136+
Refer to https://esp-idf.readthedocs.io/en/latest/security/secure-boot.html before enabling.
137137

138138
config FLASH_ENCRYPTION_ENABLED
139139
bool "Enable flash encryption on boot (READ DOCS FIRST)"
@@ -144,7 +144,7 @@ config FLASH_ENCRYPTION_ENABLED
144144
Note: After first boot, the system will be permanently encrypted. Re-flashing an encrypted
145145
system is complicated and not always possible.
146146

147-
Read http://esp-idf.readthedocs.io/en/latest/security/flash-encryption.html before enabling.
147+
Read https://esp-idf.readthedocs.io/en/latest/security/flash-encryption.html before enabling.
148148

149149
config FLASH_ENCRYPTION_INSECURE
150150
bool "Allow potentially insecure options"

‎docs/COPYRIGHT.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -103,10 +103,10 @@ Copyright (C) 2011, ChaN, all right reserved.
103103
.. _Newlib: https://sourceware.org/newlib/
104104
.. _FreeRTOS: http://freertos.org/
105105
.. _esptool.py: https://github.com/espressif/esptool
106-
.. _LWIP: http://savannah.nongnu.org/projects/lwip/
106+
.. _LWIP: https://savannah.nongnu.org/projects/lwip/
107107
.. _TinyBasic: https://github.com/BleuLlama/TinyBasicPlus
108108
.. _miniz: https://code.google.com/archive/p/miniz/
109-
.. _wpa_supplicant: http://w1.fi/wpa_supplicant/
109+
.. _wpa_supplicant: https://w1.fi/wpa_supplicant/
110110
.. _FreeBSD net80211: https://github.com/freebsd/freebsd/tree/master/sys/net80211
111111
.. _TJpgDec: http://elm-chan.org/fsw/tjpgd/00index.html
112112
.. _JSMN: http://zserge.com/jsmn.html

‎docs/Doxyfile

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
# Make sure that correct warnings are generated to flag issues with documented code
1111
#
1212
# For the complete list of configuration statements see:
13-
# http://www.stack.nl/~dimitri/doxygen/manual/config.html
13+
# https://www.stack.nl/~dimitri/doxygen/manual/config.html
1414

1515

1616
PROJECT_NAME = "ESP32 Programming Guide"

‎docs/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Documentation Source Folder
22

3-
This folder contains source files of [ESP-IDF documentation](http://esp-idf.readthedocs.io/).
3+
This folder contains source files of [ESP-IDF documentation](https://esp-idf.readthedocs.io/).
44

55
The sources do not render well in GitHub and some information is not visible at all.
66

77
Use actual documentation generated instantly on each commit:
88

9-
* Main server: http://esp-idf.readthedocs.io/ or http://esp-idf.rtfd.io/
9+
* Main server: https://esp-idf.readthedocs.io/ or http://esp-idf.rtfd.io/
1010
* Mirror: https://dl.espressif.com/doc/esp-idf/latest/
1111

‎docs/api-guides/jtag-debugging/debugging-examples.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ Checking and setting memory
152152

153153
To display or set contents of memory use "Memory" tab at the bottom of "Debug" perspective.
154154

155-
With the "Memory" tab, we will read from and write to the memory location ``0x3FF44004`` labeled as ``GPIO_OUT_REG`` used to set and clear individual GPIO's. For more information please refer to `ESP32 Technical Reference Manual <http://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf>`__, chapter IO_MUX and GPIO Matrix.
155+
With the "Memory" tab, we will read from and write to the memory location ``0x3FF44004`` labeled as ``GPIO_OUT_REG`` used to set and clear individual GPIO's. For more information please refer to `ESP32 Technical Reference Manual <https://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf>`__, chapter IO_MUX and GPIO Matrix.
156156

157157
Being in the same ``blink.c`` project as before, set two breakpoints right after ``gpio_set_level`` instruction. Click "Memory" tab and then "Add Memory Monitor" button. Enter ``0x3FF44004`` in provided dialog.
158158

@@ -512,7 +512,7 @@ Checking and setting memory
512512

513513
Displaying the contents of memory is done with command ``x``. With additional parameters you may vary the format and count of memory locations displayed. Run ``help x`` to see more details. Companion command to ``x`` is ``set`` that let you write values to the memory.
514514

515-
We will demonstrate how ``x`` and ``set`` work by reading from and writing to the memory location ``0x3FF44004`` labeled as ``GPIO_OUT_REG`` used to set and clear individual GPIO's. For more information please refer to `ESP32 Technical Reference Manual <http://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf>`__, chapter IO_MUX and GPIO Matrix.
515+
We will demonstrate how ``x`` and ``set`` work by reading from and writing to the memory location ``0x3FF44004`` labeled as ``GPIO_OUT_REG`` used to set and clear individual GPIO's. For more information please refer to `ESP32 Technical Reference Manual <https://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf>`__, chapter IO_MUX and GPIO Matrix.
516516

517517
Being in the same ``blink.c`` project as before, set two breakpoints right after ``gpio_set_level`` instruction. Enter two times ``c`` to get to the break point followed by ``x /1wx 0x3FF44004`` to display contents of ``GPIO_OUT_REG`` memory location::
518518

‎docs/api-guides/jtag-debugging/index.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The key software and hardware to perform debugging of ESP32 with OpenOCD over JT
5757

5858
Under "Application Loading and Monitoring" there is another software and hardware to compile, build and flash application to ESP32, as well as to provide means to monitor diagnostic messages from ESP32.
5959

60-
Debugging using JTAG and application loading / monitoring is integrated under the `Eclipse <http://www.eclipse.org/>`_ environment, to provide quick and easy transition from writing, compiling and loading the code to debugging, back to writing the code, and so on. All the software is available for Windows, Linux and MacOS platforms.
60+
Debugging using JTAG and application loading / monitoring is integrated under the `Eclipse <https://www.eclipse.org/>`_ environment, to provide quick and easy transition from writing, compiling and loading the code to debugging, back to writing the code, and so on. All the software is available for Windows, Linux and MacOS platforms.
6161

6262
If the :doc:`ESP32 WROVER KIT <../../hw-reference/modules-and-boards>` is used, then connection from PC to ESP32 is done effectively with a single USB cable thanks to FT2232H chip installed on WROVER, which provides two USB channels, one for JTAG and the second for UART connection.
6363

‎docs/contribute/documenting-code.rst

+6-6
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The purpose of this description is to provide quick summary on documentation sty
77
Introduction
88
------------
99

10-
When documenting code for this repository, please follow `Doxygen style <http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html#specialblock>`_. You are doing it by inserting special commands, for instance ``@param``, into standard comments blocks, for example: ::
10+
When documenting code for this repository, please follow `Doxygen style <https://www.stack.nl/~dimitri/doxygen/manual/docblocks.html#specialblock>`_. You are doing it by inserting special commands, for instance ``@param``, into standard comments blocks, for example: ::
1111

1212
/**
1313
* @param ratio this is oxygen to air ratio
@@ -21,7 +21,7 @@ Typical comment block, that contains documentation of a function, looks like bel
2121
:align: center
2222
:alt: Sample inline code documentation
2323

24-
Doxygen supports couple of formatting styles. It also gives you great flexibility on level of details to include in documentation. To get familiar with available features, please check data reach and very well organized `Doxygen Manual <http://www.stack.nl/~dimitri/doxygen/manual/index.html>`_.
24+
Doxygen supports couple of formatting styles. It also gives you great flexibility on level of details to include in documentation. To get familiar with available features, please check data reach and very well organized `Doxygen Manual <https://www.stack.nl/~dimitri/doxygen/manual/index.html>`_.
2525

2626

2727
Why we need it?
@@ -125,7 +125,7 @@ There is couple of tips, how you can make your documentation even better and mor
125125
5. Use markdown to make your documentation even more readable. You will add headers, links, tables and more. ::
126126

127127
*
128-
* [ESP32 Technical Reference](http://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf)
128+
* [ESP32 Technical Reference](https://espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf)
129129
*
130130

131131
.. note::
@@ -171,7 +171,7 @@ OK, but I am new to Sphinx!
171171

172172
3. You will likely want to see how documentation builds and looks like before posting it on the GitHub. There are two options to do so:
173173

174-
* Install `Sphinx <http://www.sphinx-doc.org/>`_, `Breathe <https://breathe.readthedocs.io/>`_ and `Doxygen <http://www.stack.nl/~dimitri/doxygen/>`_ to build it locally, see chapter below.
174+
* Install `Sphinx <http://www.sphinx-doc.org/>`_, `Breathe <https://breathe.readthedocs.io/>`_ and `Doxygen <https://www.stack.nl/~dimitri/doxygen/>`_ to build it locally, see chapter below.
175175

176176
* Set up an account on `Read the Docs <https://readthedocs.org/>`_ and build documentation in the cloud. Read the Docs provides document building and hosting for free and their service works really quick and great.
177177

@@ -183,12 +183,12 @@ Setup for building documentation locally
183183

184184
You can setup environment to build documentation locally on your PC by installing:
185185

186-
1. Doxygen - http://www.stack.nl/~dimitri/doxygen/
186+
1. Doxygen - https://www.stack.nl/~dimitri/doxygen/
187187
2. Sphinx - https://github.com/sphinx-doc/sphinx/#readme-for-sphinx
188188
3. Docment theme "sphinx_rtd_theme" - https://github.com/rtfd/sphinx_rtd_theme
189189
4. Breathe - https://github.com/michaeljones/breathe#breathe
190190

191-
The package "sphinx_rtd_theme" is added to have the same "look and feel" of `ESP32 Programming Guide <http://esp-idf.readthedocs.io/en/latest/index.html>`_ documentation like on the "Read the Docs" hosting site.
191+
The package "sphinx_rtd_theme" is added to have the same "look and feel" of `ESP32 Programming Guide <https://esp-idf.readthedocs.io/en/latest/index.html>`_ documentation like on the "Read the Docs" hosting site.
192192

193193
Installation of Doxygen is OS dependent:
194194

‎docs/get-started/eclipse-setup.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,5 +105,5 @@ Related Documents
105105
eclipse-setup-windows
106106

107107

108-
.. _eclipse.org: http://www.eclipse.org/
108+
.. _eclipse.org: https://www.eclipse.org/
109109

‎docs/get-started/establish-serial-connection.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Connect the ESP32 board to the PC using the USB cable. If device driver does not
1111

1212
Below are the links to Windows and MacOS drivers for ESP32 boards produced by Espressif:
1313

14-
* ESP32 Core Board - `CP210x USB to UART Bridge VCP Drivers <http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers>`_
14+
* ESP32 Core Board - `CP210x USB to UART Bridge VCP Drivers <https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers>`_
1515

1616
* ESP32 WROVER KIT and ESP32 Demo Board - `FTDI Virtual COM Port Drivers <http://www.ftdichip.com/Drivers/D2XX.htm>`_
1717

‎docs/get-started/get-started-devkitc.rst

+5-5
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ What You Need
1515
Overview
1616
--------
1717

18-
ESP32-DevKitC is a small-sized ESP32-based development board produced by `Espressif <http://espressif.com>`_. Most of the I/O pins are broken out to the pin headers on both sides for easy interfacing. Developers can connect these pins to peripherals as needed. Standard headers also make development easy and convenient when using a breadboard.
18+
ESP32-DevKitC is a small-sized ESP32-based development board produced by `Espressif <https://espressif.com>`_. Most of the I/O pins are broken out to the pin headers on both sides for easy interfacing. Developers can connect these pins to peripherals as needed. Standard headers also make development easy and convenient when using a breadboard.
1919

2020

2121
Functional Description
@@ -24,7 +24,7 @@ Functional Description
2424
The following list and figure below describe key components, interfaces and controls of ESP32-DevKitC board.
2525

2626
ESP-WROOM-32
27-
Standard `ESP-WROOM-32 <http://www.espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ module soldered to the ESP32-DevKitC board.
27+
Standard `ESP-WROOM-32 <https://www.espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ module soldered to the ESP32-DevKitC board.
2828
EN
2929
Reset button: pressing this button resets the system.
3030
Boot
@@ -58,6 +58,6 @@ To start development of applications, proceed to section :doc:`index`, that will
5858
Related Documents
5959
-----------------
6060

61-
* `ESP32-DevKitC schematic <http://dl.espressif.com/dl/schematics/ESP32-Core-Board-V2_sch.pdf>`_ (PDF)
62-
* `ESP32 Datasheet <http://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
63-
* `ESP-WROOM-32 Datasheet <http://espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ (PDF)
61+
* `ESP32-DevKitC schematic <https://dl.espressif.com/dl/schematics/ESP32-Core-Board-V2_sch.pdf>`_ (PDF)
62+
* `ESP32 Datasheet <https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
63+
* `ESP-WROOM-32 Datasheet <https://espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ (PDF)

‎docs/get-started/get-started-wrover-kit-v2.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ What You Need
1717
Overview
1818
^^^^^^^^
1919

20-
The ESP-WROVER-KIT is a development board produced by `Espressif <http://espressif.com>`_ built around ESP32. This board is compatible with ESP32 modules, including the ESP-WROOM-32 and ESP32-WROVER. The ESP-WROVER-KIT features support for an LCD and MicroSD card. The I/O pins have been broken out from the ESP32 module for easy extension. The board carries an advanced multi-protocol USB bridge (the FTDI FT2232HL), enabling developers to use JTAG directly to debug the ESP32 through the USB interface. The development board makes secondary development easy and cost-effective.
20+
The ESP-WROVER-KIT is a development board produced by `Espressif <https://espressif.com>`_ built around ESP32. This board is compatible with ESP32 modules, including the ESP-WROOM-32 and ESP32-WROVER. The ESP-WROVER-KIT features support for an LCD and MicroSD card. The I/O pins have been broken out from the ESP32 module for easy extension. The board carries an advanced multi-protocol USB bridge (the FTDI FT2232HL), enabling developers to use JTAG directly to debug the ESP32 through the USB interface. The development board makes secondary development easy and cost-effective.
2121

2222
.. note::
2323

@@ -173,9 +173,9 @@ Related Documents
173173
-----------------
174174

175175
* `ESP-WROVER-KIT V2 schematic`_ (PDF)
176-
* `ESP32 Datasheet <http://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
176+
* `ESP32 Datasheet <https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
177177
* `ESP-WROOM-32 Datasheet <http://www.espressif.com/sites/default/files/documentation/esp_wroom_32_datasheet_en.pdf>`_ (PDF)
178-
* `ESP32-WROVER Datasheet <http://espressif.com/sites/default/files/documentation/esp32-wrover_datasheet_en.pdf>`_ (PDF)
178+
* `ESP32-WROVER Datasheet <https://espressif.com/sites/default/files/documentation/esp32-wrover_datasheet_en.pdf>`_ (PDF)
179179
* :doc:`../api-guides/jtag-debugging/index`
180180
* :doc:`../hw-reference/modules-and-boards`
181181

@@ -189,4 +189,4 @@ Related Documents
189189
.. |jp11-rx-tx| image:: ../_static/wrover-jp11-tx-rx.png
190190
.. |jp14| image:: ../_static/wrover-jp14.png
191191

192-
.. _ESP-WROVER-KIT V2 schematic: http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf
192+
.. _ESP-WROVER-KIT V2 schematic: https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf

‎docs/get-started/get-started-wrover-kit.rst

+5-5
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ What You Need
1717
Overview
1818
^^^^^^^^
1919

20-
The ESP-WROVER-KIT is a development board produced by `Espressif <http://espressif.com>`_ built around ESP32. This board is compatible with ESP32 modules, including the ESP-WROOM-32 and ESP32-WROVER. The ESP-WROVER-KIT features support for an LCD and MicroSD card. The I/O pins have been broken out from the ESP32 module for easy extension. The board carries an advanced multi-protocol USB bridge (the FTDI FT2232HL), enabling developers to use JTAG directly to debug the ESP32 through the USB interface. The development board makes secondary development easy and cost-effective.
20+
The ESP-WROVER-KIT is a development board produced by `Espressif <https://espressif.com>`_ built around ESP32. This board is compatible with ESP32 modules, including the ESP-WROOM-32 and ESP32-WROVER. The ESP-WROVER-KIT features support for an LCD and MicroSD card. The I/O pins have been broken out from the ESP32 module for easy extension. The board carries an advanced multi-protocol USB bridge (the FTDI FT2232HL), enabling developers to use JTAG directly to debug the ESP32 through the USB interface. The development board makes secondary development easy and cost-effective.
2121

2222
.. note::
2323

@@ -324,9 +324,9 @@ Related Documents
324324
-----------------
325325

326326
* `ESP-WROVER-KIT V3 schematic`_ (PDF)
327-
* `ESP32 Datasheet <http://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
328-
* `ESP32-WROVER Datasheet <http://espressif.com/sites/default/files/documentation/esp32-wrover_datasheet_en.pdf>`_ (PDF)
329-
* `ESP-WROOM-32 Datasheet <http://espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ (PDF)
327+
* `ESP32 Datasheet <https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf>`_ (PDF)
328+
* `ESP32-WROVER Datasheet <https://espressif.com/sites/default/files/documentation/esp32-wrover_datasheet_en.pdf>`_ (PDF)
329+
* `ESP-WROOM-32 Datasheet <https://espressif.com/sites/default/files/documentation/esp-wroom-32_datasheet_en.pdf>`_ (PDF)
330330
* :doc:`../api-guides/jtag-debugging/index`
331331
* :doc:`../hw-reference/modules-and-boards`
332332

@@ -339,7 +339,7 @@ Related Documents
339339
.. |jp11-rx-tx| image:: ../_static/wrover-jp11-tx-rx.png
340340
.. |jp14| image:: ../_static/wrover-jp14.png
341341

342-
.. _ESP-WROVER-KIT V3 schematic: http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf
342+
.. _ESP-WROVER-KIT V3 schematic: https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf
343343

344344
.. toctree::
345345
:hidden:

‎docs/get-started/idf-monitor.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -114,4 +114,4 @@ Issues Observed on Windows
114114
.. _addr2line: https://sourceware.org/binutils/docs/binutils/addr2line.html
115115
.. _gdb: https://sourceware.org/gdb/download/onlinedocs/
116116
.. _pySerial: https://github.com/pyserial/pyserial
117-
.. _miniterm: http://pyserial.readthedocs.org/en/latest/tools.html#module-serial.tools.miniterm
117+
.. _miniterm: https://pyserial.readthedocs.org/en/latest/tools.html#module-serial.tools.miniterm

‎docs/get-started/index.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ To develop applications for ESP32 you need:
2121
* **PC** loaded with either Windows, Linux or Mac operating system
2222
* **Toolchain** to build the **Application** for ESP32
2323
* **ESP-IDF** that essentially contains API for ESP32 and scripts to operate the **Toolchain**
24-
* A text editor to write programs (**Projects**) in C, e.g. `Eclipse <http://www.eclipse.org/>`_
24+
* A text editor to write programs (**Projects**) in C, e.g. `Eclipse <https://www.eclipse.org/>`_
2525
* The **ESP32** board itself and a **USB cable** to connect it to the **PC**
2626

2727
.. figure:: ../_static/what-you-need.png

‎docs/get-started/macos-setup-scratch.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Compile the Toolchain from Source
2121

2222
- Install either MacPorts_ or homebrew_ package manager. MacPorts needs a full XCode installation, while homebrew only needs XCode command line tools.
2323

24-
.. _homebrew: http://brew.sh/
24+
.. _homebrew: https://brew.sh/
2525
.. _MacPorts: https://www.macports.org/install.php
2626

2727
- with MacPorts::

0 commit comments

Comments
 (0)