You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,10 @@ You will require the following to get started:
32
32
- An ESP32 development kit: ESP32-DevKitC (Available on [DigiKey](https://www.digikey.com/?_ga=2.24343738.1493252097.1552534720-1988497184.1552534720), [Mouser](https://www.mouser.com/_/?Keyword=ESP32-DevKitC), [Amazon](https://www.amazon.com/s?k=esp32-devkitc&crid=34ZPSBVQ3ZVZK&sprefix=esp32-devt%2Caps%2C738&ref=nb_sb_ss_i_1_9). You could also use any other ESP32 development boards if you already have one.)
33
33
- Follow the step-by-step guide at [ESP-Jumpstart Getting Started](https://docs.espressif.com/projects/esp-jumpstart/en/latest/index.html).
34
34
35
-
Please ensure to use ESP-IDF v4.0 from either the tagged release or the following command,
35
+
Please ensure to use ESP-IDF v4.4 from either the tagged release or the following command,
Please follow the steps in this documentation for setting up IDF: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/get-started/index.html}. Please complete all the steps on this page.
31
+
Please follow the steps in this documentation for setting up IDF: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/get-started/index.html}. Please complete all the steps on this page.
32
32
33
33
Before proceeding, please ensure that you have setup your development host, and have built the first application as indicated in this page. Now that you have done that, let's look at some additional details about IDF.
Since we are building a production-ready firmware here, we would want to base our development on a stable release of IDF. Currently, ESP-Jumpstart uses the stable version 4.0 of ESP-IDF. Let us first switch to that version of ESP-IDF.
72
+
Since we are building a production-ready firmware here, we would want to base our development on a stable release of IDF. Currently, ESP-Jumpstart uses the stable version 4.4 of ESP-IDF. Let us first switch to that version of ESP-IDF.
The following components are offered as part of the provisioning infrastructure:
87
87
\begin{itemize}
88
-
\item\textbf{Unified Provisioning Specification:} A specification to \textit{securely} transfer Wi-Fi credentials to the device, independent of the transport (SoftAP, BLE). More details can be found here: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/provisioning/provisioning.html}.
89
-
\item\textbf{IDF Components:} Software modules that implement this specification in the device firmware, available through ESP-IDF. More details can be found here: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/provisioning/wifi_provisioning.html}.
88
+
\item\textbf{Unified Provisioning Specification:} A specification to \textit{securely} transfer Wi-Fi credentials to the device, independent of the transport (SoftAP, BLE). More details can be found here: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/provisioning/provisioning.html}.
89
+
\item\textbf{IDF Components:} Software modules that implement this specification in the device firmware, available through ESP-IDF. More details can be found here: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/provisioning/wifi_provisioning.html}.
90
90
\item\textbf{Phone apps:} Android: BLE Provisioning(\url{https://play.google.com/store/apps/details?id=com.espressif.provble}), SoftAP Provisioning(\url{https://play.google.com/store/apps/details?id=com.espressif.provsoftap}). iOS: BLE Provisioning(\url{https://apps.apple.com/in/app/esp-ble-provisioning/id1473590141}), SoftAP Provisioning(\url{https://apps.apple.com/in/app/esp-softap-provisioning/id1474040630})
91
91
\item\textbf{Phone App sources:} Sources for the phone apps for Android (\url{https://github.com/espressif/esp-idf-provisioning-android}) and iOS (\url{https://github.com/espressif/esp-idf-provisioning-ios}) are available for testing during your development, or for skinning with your brand's elements.
92
92
\end{itemize}
@@ -191,7 +191,7 @@ \subsubsection{Proof of Possession}\index{Proof of Possession}
More details about Unified provisioning and the Wi-Fi provisioning abstraction layer are available at: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/provisioning/provisioning.html} and \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/provisioning/wifi_provisioning.html}
194
+
More details about Unified provisioning and the Wi-Fi provisioning abstraction layer are available at: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/provisioning/provisioning.html} and \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/provisioning/wifi_provisioning.html}
In the Unified Provisioning section above, we mentioned in passing that the Wi-Fi credentials are stored in the NVS. The NVS is a software component that maintains a persistent storage of key-value pairs. Since the storage is persistent this information is available even across reboots and power shutdowns. The NVS uses a dedicated section of the flash to store this information.
More details about NVS are available at: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/storage/nvs_flash.html}
214
+
More details about NVS are available at: \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/storage/nvs_flash.html}
215
215
216
216
\section{Reset to Factory}\index{Reset to Factory}
217
217
Another common behaviour that is expected of products is \textit{Reset to Factory Settings}. Once the user configuration is stored into the NVS as discussed above, reset to factory behaviour can be achieved by simply erasing the NVS partition.
As you might have noticed, you will have to perform some additional steps for enabling secure boot on your devices. Please head over to the detailed information about Secure Boot (\url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/security/secure-boot.html}{Secure Boot}) to understand further.
74
+
As you might have noticed, you will have to perform some additional steps for enabling secure boot on your devices. Please head over to the detailed information about Secure Boot (\url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/security/secure-boot.html}{Secure Boot}) to understand further.
The flash encryption support ensures that any application firmware, that is stored in the flash of the ESP32, stays encrypted. This allows manufacturers to ship encrypted firmware in their devices.
For more information about enabling flash encryption, you can head over to additional documentation of Flash Encryption (\url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/security/flash-encryption.html}).
88
+
For more information about enabling flash encryption, you can head over to additional documentation of Flash Encryption (\url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/security/flash-encryption.html}).
For more information about using NVS encryption, you can head over to the additional documentation at \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.0/api-reference/storage/nvs_flash.html#nvs-encryption}.
112
+
For more information about using NVS encryption, you can head over to the additional documentation at \url{https://docs.espressif.com/projects/esp-idf/en/release-v4.4/api-reference/storage/nvs_flash.html#nvs-encryption}.
0 commit comments