Search found 834 matches

by ESP_igrr
Mon Oct 16, 2017 1:23 am
Forum: General Discussion
Topic: Diagnosing heap corruption
Replies: 8
Views: 94

Re: Diagnosing heap corruption

Several suggestions are given here: http://esp-idf.readthedocs.io/en/latest ... corruption
by ESP_igrr
Mon Oct 16, 2017 12:56 am
Forum: General Discussion
Topic: single core freertos and tasks
Replies: 7
Views: 157

Re: single core freertos and tasks

Is there a way to check if how much of the system tasks are run on each core? For example, I would like all ethernet, wifi and system event tasks to be running on PRO_CPU only. You can also use FreeRTOS uxTaskGetSystemState API to get information about tasks. BTW, Using the example blink app, even ...
by ESP_igrr
Sun Oct 15, 2017 11:20 am
Forum: ESP32 SDK
Topic: Is it possible to log the time between deep sleep wake up stubs function calls?
Replies: 5
Views: 151

Re: Is it possible to log the time between deep sleep wake up stubs function calls?

Leveraging which timer? Did I get that right that you want to measure time between wakeups? If so, then note that only the RTC controller remains powered on in deep sleep, and it has only one counter which applications can use — that's the one queried by rtc_time_get. Perhaps you could post the code...
by ESP_igrr
Sun Oct 15, 2017 11:17 am
Forum: ESP32 SDK
Topic: rtc_clk_cpu_freq_set() lockups
Replies: 11
Views: 106

Re: rtc_clk_cpu_freq_set() lockups

permal: I'll talk to hardware colleagues to see if they can offer a way to diagnose this issue by running some code on your side. Even if this is a hardware issue, we would like to understand the failure mode better.
by ESP_igrr
Sun Oct 15, 2017 11:14 am
Forum: General Discussion
Topic: single core freertos and tasks
Replies: 7
Views: 157

Re: single core freertos and tasks

Well, from IDF perspective the default is to have dual core mode enabled. But the template app has single core mode config option set, which is why it runs in single core mode. If you start with a project which doesn't have an sdkconfig or sdkconfig.defaults, you will get dual core mode by default. ...
by ESP_igrr
Sun Oct 15, 2017 5:11 am
Forum: ESP32 SDK
Topic: Is it possible to log the time between deep sleep wake up stubs function calls?
Replies: 5
Views: 151

Re: Is it possible to log the time between deep sleep wake up stubs function calls?

You can read the RTC counter values, by adding code similar to this one: components/soc/esp32/rtc_time.c#L129-L136 This counter runs from RTC_SLOW_CLK, which is 160kHz if the internal oscillator is used or 32kHz if external 32k XTAL is used. You can get the calibration value (period of RTC_SLOW_CLK ...
by ESP_igrr
Sun Oct 15, 2017 5:02 am
Forum: ESP32 SDK
Topic: rtc_clk_cpu_freq_set() lockups
Replies: 11
Views: 106

Re: rtc_clk_cpu_freq_set() lockups

W (55) rtc_clk: Possibly invalid CONFIG_ESP32_XTAL_FREQ setting (26MHz). Detected 26 MHz.


Yes, that's a bug in the code printing the warning. We have a fix for this sitting somewhere in the merge queue.
by ESP_igrr
Sat Oct 14, 2017 6:45 pm
Forum: ESP32 SDK
Topic: rtc_clk_cpu_freq_set() lockups
Replies: 11
Views: 106

Re: rtc_clk_cpu_freq_set() lockups

I guess if anyone else who has a 26MHz board can do a test with 80/160 MHz and chime in here, that would be very helpful. 320MHz PLL is the PLL from which 80 and 160MHz clocks are derived. When you use 240MHz CPU frequency, a different PLL (480MHz) is used. They have different parameters, and it loo...
by ESP_igrr
Sat Oct 14, 2017 6:22 pm
Forum: General Discussion
Topic: single core freertos and tasks
Replies: 7
Views: 157

Re: single core freertos and tasks

1. By default, dual core mode is enabled. However if you choose"run FreeRTOS on single core only", then APP_CPU will be clock gated and only PRO_CPU will be used by FreeRTOS. 2. Empty app: IDLE task (one per CPU), FreeRTOS timer task, IPC task (one per CPU), esp_timer task, main task. 3. W...
by ESP_igrr
Sat Oct 14, 2017 5:05 pm
Forum: ESP32 SDK
Topic: rtc_clk_cpu_freq_set() lockups
Replies: 11
Views: 106

Re: rtc_clk_cpu_freq_set() lockups

This probably indicates that 320M PLL is failing to get a lock. I wonder why you haven't been seeing this issue in the past and then it suddenly appeared. There haven't been any changes to PLL configuration code recently... Could you please add a log to rtc_clk to verify what value is returned by rt...

Go to advanced search