You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue could be related to PlatformIO build, see analysis
Environment
Development Kit: ESP32-DevKitC
Kit version: v4
Module or chip used: ESP32-WROOM-32
IDF version (run git describe --tags to find it): 3.30300.190916
Build System: PlatformIO
Compiler version 1.22.0-80-g6c4433a5
Operating System: Windows
Power Supply: USB
JTAG: Segger J-Link
Problem Description
Attempting to enable SystemView with CONFIG_ESP32_APPTRACE_LOCK_ENABLE results in the following errors:
(0) cpu_start: App cpu up.
(219) heap_init: Initializing. RAM available for dynamic allocation:
(226) heap_init: At 3FFAE6E0 len 0000F480 (61 KiB): DRAM
...
(257) cpu_start: Pro cpu start user code
assertion "res == coreID || res == portMUX_FREE_VAL" failed: file "portmux_impl.inc.h", line 105, function: vPortCPUAcquireMutexIntsDisabledInternal
abort() was called at PC 0x400d32e3 on core 0
where this section repeats and eventually resets:
assertion "res == coreID || res == portMUX_FREE_VAL" failed: file
"portmux_impl.inc.h", line 105, function: vPortCPUAcquireMutexIntsDisabledInternal
Expected Behavior
SystemView should work as described in the documentation.
Actual Behavior
SystemView can only be used when CONFIG_ESP32_APPTRACE_LOCK_ENABLE is 0
Steps to repropduce
Create a new project with one endless loop task and the following settings:
At first it looked like the issue is in start_cpu0_default() where esp_apptrace_init() is not called at the correct location, but even after moving it above esp_timer_init() a different error started, I think the lock might not get released in the trax code so its causing other side effects, but I did not finish the analysis.
After disabling the AppTrace locks it seems to be working.
This issue could be related to the way PlatformIO builds esp-idf or a regression in AppTrace / SystemView implementation or inappropriate defines.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
SystemView with AppTrace Lock does not work
SystemView with AppTrace Lock does not work (IDFGH-1959)
Oct 4, 2019
@drorglCONFIG_ESP32_APPTRACE_LOCK_ENABLE is incompatible with SystemView tracing module and is disabled when SystemView is enabled.
SystemView uses its own locking mechanism.
This issue could be related to PlatformIO build, see analysis
Environment
git describe --tags
to find it): 3.30300.190916Problem Description
Attempting to enable SystemView with
CONFIG_ESP32_APPTRACE_LOCK_ENABLE
results in the following errors:where this section repeats and eventually resets:
Expected Behavior
SystemView should work as described in the documentation.
Actual Behavior
SystemView can only be used when
CONFIG_ESP32_APPTRACE_LOCK_ENABLE
is0
Steps to repropduce
Create a new project with one endless loop task and the following settings:
Analysis
At first it looked like the issue is in
start_cpu0_default()
whereesp_apptrace_init()
is not called at the correct location, but even after moving it aboveesp_timer_init()
a different error started, I think the lock might not get released in the trax code so its causing other side effects, but I did not finish the analysis.After disabling the AppTrace locks it seems to be working.
This issue could be related to the way PlatformIO builds esp-idf or a regression in AppTrace / SystemView implementation or inappropriate defines.
The text was updated successfully, but these errors were encountered: