Search found 429 matches

by snahmad75
Sun Apr 14, 2019 1:02 pm
Forum: ESP32 IDF
Topic: WiFi scanning
Replies: 1
Views: 120

WiFi scanning

Hi, I understood wifi scan for all channels from 1-13 by default for active scanning as our product needs to work in all countries. I would like it scan only from 1-11 for active scanning and 12 and 13 channel as passive scanning. I now set esp_wifi_set_country to usa with channel range(1-11) This w...
by snahmad75
Sat Apr 13, 2019 9:39 pm
Forum: ESP32 IDF
Topic: Internal fastfs file gets corrupt some time after re-power.
Replies: 13
Views: 477

Re: Internal fastfs file gets corrupt some time after re-power.

jcsbanks wrote:
Sat Apr 13, 2019 9:34 pm
My only comment is that I often do FATFS operations in between OTS completion and reset into the new OTS app.
Thanks for sharing.
by snahmad75
Sat Apr 13, 2019 3:16 pm
Forum: ESP32 IDF
Topic: Internal fastfs file gets corrupt some time after re-power.
Replies: 13
Views: 477

Re: Internal fastfs file gets corrupt some time after re-power.

I found out interesting results. After OTA complete/end If I perform internal fatfs operation like check file exist and delete file. It fails. Can you some check and verify please. I now move my internal fatfs operation before ota begin. I still do NVS write and commit after ota end/complete. Is thi...
by snahmad75
Fri Apr 12, 2019 10:39 pm
Forum: ESP32 IDF
Topic: Internal fastfs file gets corrupt some time after re-power.
Replies: 13
Views: 477

Re: Internal fastfs file gets corrupt some time after re-power.

Internal flash writes during large partition updates from OTA, or sometimes even small files with FATFS can cause problems with the CAN driver and high resolution timer callbacks resulting in interrupt watchdog timeouts, so I've preferred to refactor my work to use a form of RAM disk where a map of...
by snahmad75
Fri Apr 12, 2019 5:46 pm
Forum: ESP32 IDF
Topic: Internal fastfs file gets corrupt some time after re-power.
Replies: 13
Views: 477

Re: Internal fastfs file gets corrupt some time after re-power.

Sometime fwrite fails. It writes zero bytes so generate emty file.

I am using fopen(, "wb")

Is this correct flags for file write.

I am using few months old master branch of version =3.2

now I downloaded official release of version=3.2
I will try it again.
by snahmad75
Thu Apr 11, 2019 6:45 am
Forum: ESP32 IDF
Topic: Is this stack overflow or watch dog trigger
Replies: 2
Views: 132

Re: Is this stack overflow or watch dog trigger

The task watchdog timer is triggering because some task has not yielded CPU: https://docs.espressif.com/projects/esp-idf/en/stable/api-reference/kconfig.html#envvar-CONFIG_TASK_WDT_PANIC https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/system/wdts.html ok, thanks. just verifying ...
by snahmad75
Wed Apr 10, 2019 9:05 pm
Forum: ESP32 IDF
Topic: heap corruption any idea?
Replies: 9
Views: 307

Re: heap corruption any idea?

It looks like related with hardware time not stop properly.

I will investigate
by snahmad75
Wed Apr 10, 2019 3:33 pm
Forum: ESP32 IDF
Topic: Is this stack overflow or watch dog trigger
Replies: 2
Views: 132

Is this stack overflow or watch dog trigger

I (1322) W2K: Beginning-Of-Flash Vector: 0x3F400020 -> 0x3F404D10 I (1338) W2K: HardwareTimer::start I (1341) mcast-ipv4: Configured IPV4 Multicast address 224.0.0.251 I (1479) W2K: __builder_init notify I (1480) W2K: __builder_init completed I (1481) W2K: Thread_Application I (1481) W2K: Internal H...
by snahmad75
Wed Apr 10, 2019 2:40 pm
Forum: ESP32 IDF
Topic: heap corruption any idea?
Replies: 9
Views: 307

Re: heap corruption any idea?

Still hardware timer crash. ore 0 register dump: PC : 0x40096645 PS : 0x00060430 A0 : 0x80096253 A1 : 0x3ffbc840 0x40096645: uxListRemove at C:/Work/library/esp32/master/esp-idf/components/freertos/list.c:214 A2 : 0x3ffed928 A3 : 0x00000000 A4 : 0x3ffbb7a0 A5 : 0x00000000 A6 : 0x3ffbb858 A7 : 0x0000...
by snahmad75
Wed Apr 10, 2019 10:34 am
Forum: ESP32 IDF
Topic: heap corruption any idea?
Replies: 9
Views: 307

Re: heap corruption any idea?

This looks to be related with hardware timer I am using hardware timer and start and stop it and delete it. I do stop ARLErrorCode_e HardwareTimer::stop () { ACDTRACEF(ES_NoError, "HardwareTimer::stopping"); std::lock_guard<std::mutex> lock(_observer_mutex_); for (s32 i = 0; i < size_; i++) { observ...

Go to advanced search