And,
If so, is the solution for this having the build flag CONFIG_SPI_FLASH_VERIFY_WRITE set?
Search found 4 matches
- Thu Dec 10, 2020 3:14 pm
- Forum: ESP-IDF
- Topic: [SOLVED] ESP_ERR_NVS_NOT_FOUND from nvs_get_blob() due to nvs_commit() race condition
- Replies: 19
- Views: 25029
- Thu Dec 10, 2020 2:37 pm
- Forum: ESP-IDF
- Topic: [SOLVED] ESP_ERR_NVS_NOT_FOUND from nvs_get_blob() due to nvs_commit() race condition
- Replies: 19
- Views: 25029
Re: [SOLVED] ESP_ERR_NVS_NOT_FOUND from nvs_get_blob() due to nvs_commit() race condition
Hi,
Was the result of the above post (Thu Jun 04, 2020 8:30 am) indicating that the nvs commit and close may return before the data is actually written?
which can lead to changes of the source data following the commit & close may get captured by the write operation?
Thanks
Was the result of the above post (Thu Jun 04, 2020 8:30 am) indicating that the nvs commit and close may return before the data is actually written?
which can lead to changes of the source data following the commit & close may get captured by the write operation?
Thanks
- Thu Sep 26, 2019 3:18 pm
- Forum: ESP-IDF
- Topic: esp32.project.ld , changing order of data in segment
- Replies: 1
- Views: 2577
esp32.project.ld , changing order of data in segment
I want to have
.noinit (NOLOAD):
{
. = ALIGN(4);
_noinit_start = ABSOLUTE(.);
*(.noinit .noinit.*)
. = ALIGN(4) ;
_noinit_end = ABSOLUTE(.);
} > dram0_0_seg
go ahead of
.dram0.data :
{ ...
}
in the linking of my application.
I see during the build process that esp32.project.ld.in is ...
.noinit (NOLOAD):
{
. = ALIGN(4);
_noinit_start = ABSOLUTE(.);
*(.noinit .noinit.*)
. = ALIGN(4) ;
_noinit_end = ABSOLUTE(.);
} > dram0_0_seg
go ahead of
.dram0.data :
{ ...
}
in the linking of my application.
I see during the build process that esp32.project.ld.in is ...
- Fri May 17, 2019 5:20 pm
- Forum: ESP-IDF
- Topic: esp32 ble server, multiple client, one client losing comm
- Replies: 0
- Views: 2311
esp32 ble server, multiple client, one client losing comm
Question on the behavior of the BLE stack
- esp32 acting as ble server
- multiple clients are attached
- if notify messages are being sent to all the attached clients
- if one clients communication is suddenly and permanently interrupted (say it moves behind a wall totally blocking ble signal ...
- esp32 acting as ble server
- multiple clients are attached
- if notify messages are being sent to all the attached clients
- if one clients communication is suddenly and permanently interrupted (say it moves behind a wall totally blocking ble signal ...