[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1812091] Re: gdbstub memory accesses performed with wr
[Qemu-devel] [Bug 1812091] Re: gdbstub memory accesses performed with wrong attributes
Thu, 17 Jan 2019 13:11:08 -0000
Hello Peter and thanks a lot for your quick response.
I have tested the patch and it seems to work! Looks like my testing code
was buggy, apologies for the inaccurate bug description.
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
gdbstub memory accesses performed with wrong attributes
Status in QEMU:
The ARMv8-M architecture (with security extensions) contains a SAU, the
Security Attribution Unit. After booting the mps2-an505 and immediately halting
(`-S`), I attempt to read the SAU_TYPE register, located at 0xE000EDD4, using
gdb (x 0xE000EDD4). The returned value is 0, while the expected value is 8
(number of regions).
On further investigation, it seems that `attrs.secure` is set to false
(armv7m_nvic.c - nvic_readl, line 1167). Commenting out the check will
return the correct value.
As the CPU should be in 'secure' mode after reset, I think this
behavior is wrong.
Steps to reproduce:
Example code that loads an endless loop into the beginning of secure memory:
Commandline: qemu-system-arm -machine mps2-an505 -cpu cortex-m33 \
-m 4096 \
-nographic -serial mon:stdio \
-kernel $(IMAGE) -s -S
Attach with arm-none-eabi-gdb, and run x 0xE000EDD4.
To manage notifications about this bug go to: