Search found 18 matches
- Sat Feb 13, 2021 12:28 pm
- Forum: ESP-IDF
- Topic: nvs_set_blob issue with UART interrupt enabled
- Replies: 3
- Views: 5727
Re: nvs_set_blob issue with UART interrupt enabled
Ah, one other very likely thing I didn't spot the first time: uart_isr_register(UART_NUM_2, uart2_isr, NULL, ESP_INTR_FLAG_IRAM, &uart2_intr_handle); Are you sure that all of the code that can possibly be called from uart2_isr is in IRAM? If not, problems can occur while writing to flash and this c...
- Thu Dec 03, 2020 10:37 am
- Forum: ESP-IDF
- Topic: ESP-IDF 4.2 reset on radio
- Replies: 7
- Views: 10053
Re: ESP-IDF 4.2 reset on radio
It is the RTC watchdog causing this problem. Possible solutions: Disable RTC watchdog: Bootloader config->Use RTC watchdog in start code Increase RTC timeout Bootloader config->Timeout for RTC watchdog Feed RTC watchdog: import "soc/rtc_wdt.h" and invoke "rtc_wdt_feed();" periodically Check this thr...
- Fri Nov 27, 2020 11:49 am
- Forum: ESP-IDF
- Topic: ESP-IDF 4.2 reset on radio
- Replies: 7
- Views: 10053
Re: ESP-IDF 4.2 reset on radio
I am facing similar issue when migrated from v4.0.1 to v4.2 The device reboots almost every 10sec Attaching a very basic code with sdkconfig from original project. So, I am guessing, it's something in sdkconfig Here is the log ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_F...
- Wed Nov 11, 2020 11:15 am
- Forum: ESP-IDF
- Topic: Hash verification fails when I use ota feature, I need the bin file format。
- Replies: 5
- Views: 8743
Re: Hash verification fails when I use ota feature, I need the bin file format。
I have a similar problem. Getting following error. [0;31mE (298214) esp_image: Image hash failed - image is corrupt[0m [0;31mE (298784) esp_image: Checksum failed. Calculated 0x10 read 0x18[0m Additional details: Apart from OTA, other two taks are running but they are suspended before starting OTA B...
- Fri May 29, 2020 6:10 am
- Forum: ESP-IDF
- Topic: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
- Replies: 7
- Views: 8042
Re: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
Hi @xiaoxufeng I ran the command but I guess I am doing something wrong Following is the output esptool.py v2.8 Found 1 serial ports Serial port COM3 Connecting........_____. Detecting chip type... ESP32 Chip is ESP32D0WDQ6 (revision 1) Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efus...
- Thu May 28, 2020 6:18 am
- Forum: ESP-IDF
- Topic: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
- Replies: 7
- Views: 8042
Re: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
Additional update:
Tried same thing by updating to idf v3.3.2 as well as v4.0.1
Same issues. I can provide additional logs if required.
Basically, I would like to update to either v3.3.2 or v4.0.1 as they contain MQTT module with lot of bug fixes.
Tried same thing by updating to idf v3.3.2 as well as v4.0.1
Same issues. I can provide additional logs if required.
Basically, I would like to update to either v3.3.2 or v4.0.1 as they contain MQTT module with lot of bug fixes.
- Thu May 28, 2020 6:13 am
- Forum: ESP-IDF
- Topic: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
- Replies: 7
- Views: 8042
Re: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
Currently I am working with ESP32 S node mcu dev board. You may test with the same
- Wed May 27, 2020 12:01 pm
- Forum: ESP-IDF
- Topic: Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
- Replies: 7
- Views: 8042
Device bricked on OTA update when esp-idf is updated from v3.1 to v4.0 [IDFGH-3384]
## Environment - Development Kit: [none, custom product using wrover module.] - Module or chip used: [ESP32-WROVER 32Mbit] - Operating System: [Windows] - Power Supply: [on-board 3.3V] - IDF version: v3.1 Application uses custom partition table as follows # additional nvs data otadata, data, ota, 0x...
- Mon Apr 22, 2019 12:21 pm
- Forum: General Discussion
- Topic: i2c randombly fails
- Replies: 19
- Views: 42117
Re: i2c randombly fails
I am facing the same issue with I2C example provided in idf. ESP32 Arduino works as expected whereas esp-idf gives the following errors timeout : 0x107 (generated by I2C_STATUS_TIMEOUT) failed: -1 (generated by I2C_STATUS_ACK_ERROR) The slave is an Arduino device. ESP-idf version: v3.1 Code: #includ...
- Mon Feb 11, 2019 10:22 am
- Forum: ESP-IDF
- Topic: Using Interrupts on the UART
- Replies: 8
- Views: 20349
Re: Using Interrupts on the UART
Looking at your code a bit better, I think you're not using the driver correctly... you're supposed to either use uart_driver_install() so you can use all the nice queued read functions etc, or use uart_isr_register() to install your own ISR and handle all hardware things yourself. In your particul...