WIP: Migration from ESP Journal #78
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
@pedrominatel @f-hollow Here's the initial test of porting one of articles.
|
f-hollow
reviewed
Aug 14, 2024
Collaborator
There was a problem hiding this comment.
Improved readability of the initial paragraphs. The rest of the article can be improved after we migrate all other relevant articles.
Another suggestion: URL slugs (article folder name) shouldn't be this long. Suggest maybe boiling it down to custom-partition-tables-esp32.
| authors: | ||
| - "pedro-minatel" | ||
| --- | ||
| # How to use custom partition tables on ESP32 |
Collaborator
There was a problem hiding this comment.
Shouldn't forget to remove this heading.
|
|
||
| # Introduction | ||
|
|
||
| When we create a new project using **ESP32** , sometimes we need to store data in the flash to persist even after a restart or power down. In the past, the most common way to do that was by using EEPROM, with just a few bytes of storage ability which limited it for larger amount of data. |
Collaborator
There was a problem hiding this comment.
Suggested change
| When we create a new project using **ESP32** , sometimes we need to store data in the flash to persist even after a restart or power down. In the past, the most common way to do that was by using EEPROM, with just a few bytes of storage ability which limited it for larger amount of data. | |
| While creating an embedded project, we usually need way to store data that can persist even after a restart or power-down. In the past, the most common way to achieve that was by using EEPROM with just a few bytes of storage ability. Persistently storing larger amounts of data was problematic. |
|
|
||
| When we create a new project using **ESP32** , sometimes we need to store data in the flash to persist even after a restart or power down. In the past, the most common way to do that was by using EEPROM, with just a few bytes of storage ability which limited it for larger amount of data. | ||
|
|
||
| On the other hand, the **ESP32** uses a flash memory to store the firmware, including the bootloader and other relevant data. The flash memory size may vary from version to version, but it’s enough for most of the application code and you still can manage to have some spare storage area. |
Collaborator
There was a problem hiding this comment.
Suggested change
| On the other hand, the **ESP32** uses a flash memory to store the firmware, including the bootloader and other relevant data. The flash memory size may vary from version to version, but it’s enough for most of the application code and you still can manage to have some spare storage area. | |
| These days, the ESP32 has flash memory onboard that allows storing firmware, including the bootloader and application, as well as other relevant data. The flash memory size may vary from version to version, but it’s enough for most application binaries with yet some spare storage on top. |
|
|
||
| On the other hand, the **ESP32** uses a flash memory to store the firmware, including the bootloader and other relevant data. The flash memory size may vary from version to version, but it’s enough for most of the application code and you still can manage to have some spare storage area. | ||
|
|
||
| But not only the firmware, (your application) is stored in the flash memory. There is some other important data to keep in the flash, including the partitions map, RF calibration data, WiFi data, Bluetooth pairing information, Over-the-air updates and many other data important enough to be kept in the flash. |
Collaborator
There was a problem hiding this comment.
Suggested change
| But not only the firmware, (your application) is stored in the flash memory. There is some other important data to keep in the flash, including the partitions map, RF calibration data, WiFi data, Bluetooth pairing information, Over-the-air updates and many other data important enough to be kept in the flash. | |
| However, apart from the bootloader and application, other important data needs to be stored in flash, including the partition map, RF calibration data, Wi-Fi data, Bluetooth pairing information, Over-the-air (OTA) updates and many other types. |
|
|
||
| But not only the firmware, (your application) is stored in the flash memory. There is some other important data to keep in the flash, including the partitions map, RF calibration data, WiFi data, Bluetooth pairing information, Over-the-air updates and many other data important enough to be kept in the flash. | ||
|
|
||
| To see all ESP32 family variants, see this ordering information [**link**](https://www.espressif.com/sites/default/files/documentation/espressif_products_ordering_information_en.pdf). |
Collaborator
There was a problem hiding this comment.
Suggested change
| To see all ESP32 family variants, see this ordering information [**link**](https://www.espressif.com/sites/default/files/documentation/espressif_products_ordering_information_en.pdf). | |
| The ESP32 has multiple variants with different flash memory sizes which can be conveniently browsed in the [ESP Product Selector](https://products.espressif.com/#/product-selector?names=). |
|
|
||
| To see all ESP32 family variants, see this ordering information [**link**](https://www.espressif.com/sites/default/files/documentation/espressif_products_ordering_information_en.pdf). | ||
|
|
||
| > Important note: This article uses the [ESP-IDF v4.2](https://docs.espressif.com/projects/esp-idf/en/v4.2/esp32/) and all references use this version. |
Collaborator
There was a problem hiding this comment.
Suggested change
| > Important note: This article uses the [ESP-IDF v4.2](https://docs.espressif.com/projects/esp-idf/en/v4.2/esp32/) and all references use this version. | |
| > Important note: This article and all references in it refer to [ESP-IDF v4.2](https://docs.espressif.com/projects/esp-idf/en/v4.2/esp32/). |
|
|
||
| The default partition scheme is defined by two different major partitions: | ||
|
|
||
| ## **nvs** |
Collaborator
There was a problem hiding this comment.
As suggested by Juraj, bold typeface should be removed from all heading titles.
Suggested change
| ## **nvs** | |
| ## nvs |
f-hollow
reviewed
Aug 14, 2024
| # How to use custom partition tables on ESP32 | ||
|
|
||
|
|
||
| # Introduction |
Collaborator
There was a problem hiding this comment.
Apparently, this heading and all the other ones below should be deeper by one level respectively.
Suggested change
| # Introduction | |
| ## Introduction |
Member
|
Regarding the page URL, can we create an alias from This will allow us to point blog.espressif.com to the new location later. |
Collaborator
Author
|
Closing. This is handled by #105 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate articles from ESP Journal.