I'm going back to this topic because this problem occurs more and more often (I see several similar reports even outside this forum) and so far no one has indicated a possible recovery solution or at least a procedure that works to rewrite the entire flash (reverting to factory default)...
rst ...
Search found 208 matches
- Wed May 24, 2023 6:18 am
- Forum: General Discussion
- Topic: 1150 mmu set XXXX
- Replies: 2
- Views: 5382
- Fri Nov 19, 2021 11:21 am
- Forum: General Discussion
- Topic: 1150 mmu set XXXX
- Replies: 2
- Views: 5382
Re: 1150 mmu set XXXX
Hi,
I have the same issue here:
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xeefe1a61,len:-1657528432
1150 mmu set 00010000, pos ...
I have the same issue here:
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xeefe1a61,len:-1657528432
1150 mmu set 00010000, pos ...
- Tue Feb 23, 2021 7:59 am
- Forum: ESP-IDF
- Topic: NimBLE memory leak?
- Replies: 10
- Views: 14953
Re: NimBLE memory leak?
The same works fine on v4.2 release as well (ESP-IDF Github head: c40f2590bf759ff60ef122afa79b4ec04e7633d2 esp-nimble head: 95bd8644abf4a410dd3fb914468d3a23ac9bbec2 nimble-1.2.0-idf branch) Logs:
I (30) boot: ESP-IDF v4.2 2nd stage bootloader
I (30) boot: compile time 22:39:39
I (30) boot: chip ...
- Mon Feb 22, 2021 5:05 pm
- Forum: ESP-IDF
- Topic: NimBLE memory leak?
- Replies: 10
- Views: 14953
Re: NimBLE memory leak?
Hello @ESP_Hrishi,
I'm on TAG" v4.2" ( https://github.com/espressif/esp-idf/tree/v4.2/ ) not branch "release/v4.2":
I guess the correct way is to use the TAG which is associated to stable and "verified" version.
Anyway I will try to update submodule "nimble" to the commit you specifed.
Thanks!
I'm on TAG" v4.2" ( https://github.com/espressif/esp-idf/tree/v4.2/ ) not branch "release/v4.2":
I guess the correct way is to use the TAG which is associated to stable and "verified" version.
Anyway I will try to update submodule "nimble" to the commit you specifed.
Thanks!
- Mon Feb 22, 2021 4:05 pm
- Forum: ESP-IDF
- Topic: NimBLE memory leak?
- Replies: 10
- Views: 14953
Re: NimBLE memory leak?
@davdav
You don't need to file an issue. It is now tracked internally.
Quick fix: Can you please add the following line (in green) below ble_npl_callout_stop in the file esp-idf/components/bt/host/nimble/nimble/nimble/host/src/ble_hs_stop.c:
ble_npl_callout_stop(&ble_hs_stop_terminate_tmo ...
- Sun Feb 21, 2021 4:49 pm
- Forum: ESP-IDF
- Topic: NimBLE memory leak?
- Replies: 10
- Views: 14953
Re: NimBLE memory leak?
@davdav
Thank you for reporting the issue and for providing a simplistic code to recreate the same. Yes, this looks like a problem.
Just to give you some background, the NimBLE upstream does not yet have the stop/deinit support integrated. We have added this functionality to our port (esp-nimble ...
- Tue Feb 16, 2021 3:55 pm
- Forum: ESP-IDF
- Topic: NimBLE memory leak?
- Replies: 10
- Views: 14953
NimBLE memory leak?
Hi everybody,
I'm trying to port our application which used Bluedroid to nimBLE. I'm working with esp-idf-v4.2.
In my opinion there is a memory leak when nimble is init and deinit if GAP advertizing is used.
I have written a simple code to test it (derived from "bleprph" example). Please find ...
I'm trying to port our application which used Bluedroid to nimBLE. I'm working with esp-idf-v4.2.
In my opinion there is a memory leak when nimble is init and deinit if GAP advertizing is used.
I have written a simple code to test it (derived from "bleprph" example). Please find ...
- Thu Feb 11, 2021 2:02 pm
- Forum: ESP-IDF
- Topic: [SOLVED]Porting from esp-idf v3.3.4 to v4.2 increase bin size
- Replies: 6
- Views: 8724
Re: Porting from esp-idf v3.3.4 to v4.2 increase bin size
Thanks @WiFive. That's OK to have 3% of increase.libmbedtls.a also decreased by that amount.
So you are down to around 50k which is probably expected for new features. A 3% increase.Total image size:~1650794 bytes (.bin may be padded larger) 1598298 +52496
- Wed Feb 10, 2021 12:05 pm
- Forum: ESP-IDF
- Topic: [SOLVED]Porting from esp-idf v3.3.4 to v4.2 increase bin size
- Replies: 6
- Views: 8724
Re: Porting from esp-idf v3.3.4 to v4.2 increase bin size
Have a look at this too:
https://www.esp32.com/viewtopic.php?t=15477
Thanks @boarchuz. I have checked difference and, although there is an increase in some of my source code(this is strange but could be related to change from "tcpip_adpater" to "esp-netif"? ), the main and relevant difference ...
- Wed Feb 10, 2021 7:39 am
- Forum: ESP-IDF
- Topic: [SOLVED]Porting from esp-idf v3.3.4 to v4.2 increase bin size
- Replies: 6
- Views: 8724
Re: Porting from esp-idf v3.3.4 to v4.2 increase bin size
idf.py size-components should give you more info
Thanks @WiFive. I have worked on menuconfig and removed some BLE features (in particular debug to save .bin size), so now I have a difference of 100KB. Below is size-components:
esp-idf-V3.3.4
Total sizes:
DRAM .data size: 18392 bytes
DRAM ...