Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

examples\system\sysview_tracing unstable openocd connection in dual core (IDFGH-9216) #10604

Closed
3 tasks done
antoDimaggio opened this issue Jan 24, 2023 · 3 comments
Closed
3 tasks done

examples\system\sysview_tracing unstable openocd connection in dual core (IDFGH-9216) #10604

antoDimaggio opened this issue Jan 24, 2023 · 3 comments
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally

Comments

@antoDimaggio
Copy link

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

IDF version.
master

Operating System used.
Windows

How did you build your project?
Command line with idf.py

If you are using Windows, please specify command line type.
ESP-IDF CMD

Hardware
ESP32-S3-DevKitC-1

Issue description
I made two very little modification to the sysview tracing example:

  1. I increased the timers frequency by 10.
    event_data[i].period = 100000 * (i + 1);
  2. I increased the number of iterations in order to let it run forever:
    if (tim_arg->count++ < INT_MAX) {

I compiled in dual core mode.

Than I flashed, started a monitor, launched openocd with:
openocd -f board/esp32s3-builtin.cfg
And after started sysvire tracing via telnet
esp sysview start pro-cpu.SVDat app-cpu.SVDat 1 -1 -1

After a while (10 to 100 seconds) openocd exits with error:

1395454
1395707
1395960
Error: Incomplete block sz 2, wr 56

I increased the verbosity of openocd but I did non find more info.

Other Info
I have the same problem on IDF v4.4.3
I changed JTAG clock frequency from default (40M) to 10M and 20MHz.
Rising the verbosity of the terminal I can see that the target is running and stacked in apptrace module code.
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 24, 2023
@github-actions github-actions bot changed the title examples\system\sysview_tracing unstable openocd connection in dual core examples\system\sysview_tracing unstable openocd connection in dual core (IDFGH-9216) Jan 24, 2023
@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: Opened Issue is new labels Jul 10, 2023
@KonssnoK
Copy link
Contributor

could you tell us when it's going to be propagated to 4.4.5 ? thanks

espressif-bot pushed a commit that referenced this issue Jul 22, 2023
@gerekon
fix(app_trace): Fix apptrace data corruption on ESP32-S3
3eacf08 
Close #10604
diff --git a/components/soc/esp32s3/include/soc/tracemem_config.h b/components/soc/esp32s3/include/soc/tracemem_config.h
index 55c9b907dd..75fd87419b 100644
--- a/components/soc/esp32s3/include/soc/tracemem_config.h
+++ b/components/soc/esp32s3/include/soc/tracemem_config.h
@@ -10,7 +10,7 @@ extern "C" {
 #endif

 #define TRACEMEM_MUX_BLK0_NUM                   22
-#define TRACEMEM_MUX_BLK1_NUM                   23
+#define TRACEMEM_MUX_BLK1_NUM                   26

 #if (TRACEMEM_MUX_BLK0_NUM < 6) || (TRACEMEM_MUX_BLK0_NUM > 29)
 #error Invalid TRAX block 0 num!
@dobairoland
Copy link
Collaborator

could you tell us when it's going to be propagated to 4.4.5 ? thanks

It will be added into the next, v4.4.6 bugfix release.

espressif-bot pushed a commit that referenced this issue Aug 9, 2023
@gerekon
fix(app_trace): Fix apptrace data corruption on ESP32-S3
865f7d6 
Close #10604
diff --git a/components/soc/esp32s3/include/soc/tracemem_config.h b/components/soc/esp32s3/include/soc/tracemem_config.h
index 55c9b907dd..75fd87419b 100644
--- a/components/soc/esp32s3/include/soc/tracemem_config.h
+++ b/components/soc/esp32s3/include/soc/tracemem_config.h
@@ -10,7 +10,7 @@ extern "C" {
 #endif

 #define TRACEMEM_MUX_BLK0_NUM                   22
-#define TRACEMEM_MUX_BLK1_NUM                   23
+#define TRACEMEM_MUX_BLK1_NUM                   26

 #if (TRACEMEM_MUX_BLK0_NUM < 6) || (TRACEMEM_MUX_BLK0_NUM > 29)
 #error Invalid TRAX block 0 num!
espressif-bot pushed a commit that referenced this issue Aug 9, 2023
@gerekon
fix(app_trace): Fix apptrace data corruption on ESP32-S3
ea3f688 
Close #10604
diff --git a/components/soc/esp32s3/include/soc/tracemem_config.h b/components/soc/esp32s3/include/soc/tracemem_config.h
index 55c9b907dd..75fd87419b 100644
--- a/components/soc/esp32s3/include/soc/tracemem_config.h
+++ b/components/soc/esp32s3/include/soc/tracemem_config.h
@@ -10,7 +10,7 @@ extern "C" {
 #endif

 #define TRACEMEM_MUX_BLK0_NUM                   22
-#define TRACEMEM_MUX_BLK1_NUM                   23
+#define TRACEMEM_MUX_BLK1_NUM                   26

 #if (TRACEMEM_MUX_BLK0_NUM < 6) || (TRACEMEM_MUX_BLK0_NUM > 29)
 #error Invalid TRAX block 0 num!
@antoDimaggio
Copy link
Author

The issue should be reopened.
I tested the bug fix and had the same bahaviour.
I also tried to update the esp-idf and to re-run the example but than I got different errors reported on this new issue
#12268
We are not yet able to reliably perform tracing on ESP32-S3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dobairoland @KonssnoK @espressif-bot @antoDimaggio