summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_arm/host_missing/accel_missing/2279
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-01 21:35:14 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-06-01 21:35:14 +0200
commit3e4c5a6261770bced301b5e74233e7866166ea5b (patch)
tree9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_arm/host_missing/accel_missing/2279
parente5634e2806195bee44407853c4bf8776f7abfa4f (diff)
downloadqemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz
qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_arm/host_missing/accel_missing/2279')
-rw-r--r--gitlab/issues_text/target_arm/host_missing/accel_missing/227925
1 files changed, 0 insertions, 25 deletions
diff --git a/gitlab/issues_text/target_arm/host_missing/accel_missing/2279 b/gitlab/issues_text/target_arm/host_missing/accel_missing/2279
deleted file mode 100644
index c43e4e439..000000000
--- a/gitlab/issues_text/target_arm/host_missing/accel_missing/2279
+++ /dev/null
@@ -1,25 +0,0 @@
-Debugging with Lauterbach Trace32 -> Cortex-A76, no SP register update
-Description of problem:
-We do not see changes in the SP_EL1 register value when debugging the QEMU application with Lauterbach Trace32.
-Steps to reproduce:
-1. Compile bare metal code that uses push and pop instructions (stack).
-2. Run QEMU with bare metal code.
-3. Connect via Lauterbach Trace32 and check the displayed SP register value.
-Additional information:
-![T32_badA76_SP_reg_display](/uploads/e6af1ac3e32072274089e6dc0cdf0266/T32_badA76_SP_reg_display.png)
-This is a screenshot from QEMU 8.0.0, but updating to QEMU 8.2.0 does not resolve the problem.
-
-I have discussed this with Lauterbach Trace32 support with these results:
-- Trace32 uses RSP protocol `p` packets to read some registers, including SP_EL1. GDB seems to use `g` packet.
-- QEMU responds to `p` packet with an invalid value, which causes Trace32 to display invalid value.
-
-Some related RSP protocol logs from Trace32.
-![T32_sp_1](/uploads/cbe34d19d3ede30549e6c4d781bb6630/T32_sp_1.png)
-![T32_sp_2](/uploads/73e22dbf83ec00b939077dfeb7bfa208/T32_sp_2.png)
-
-Different part of RSP protocol log:
-```
-Sending packet: $p20#d2 ...
-receiving packet: ec00004000000000
-```
-So it looks like Trace32 can receive different values that zero as response to `p` packet.