12 Dec
2018
12 Dec
'18
1:59 p.m.
On Wed, Dec 12, 2018 at 12:48:54PM +0000, Mike Leach wrote:
[...]
+/* ETMv4 exception number */ +enum {
CS_ETMV4_EXC_RESET,CS_ETMV4_EXC_DEBUG_HALT,CS_ETMV4_EXC_CALL,CS_ETMV4_EXC_TRAP,CS_ETMV4_EXC_SYSTEM_ERROR,CS_ETMV4_EXC_INST_DEBUG,CS_ETMV4_EXC_DATA_DEBUG,CS_ETMV4_EXC_ALIGNMENT,CS_ETMV4_EXC_INST_FAULT,CS_ETMV4_EXC_DATA_FAULT,CS_ETMV4_EXC_IRQ,CS_ETMV4_EXC_FIQ,+};
This enum needs correcting to cover the reserved values so that the enum values match up for the actual exception number value.
Oops, thanks for pointing out this, good catching!
Will fix it.
Additionally there are implementation defined exceptions after FIQ that could occur on custom devices.
As I saw in another email "5 bit exception number in ETMv4", so exception numbers 16 ~ 31 also are valid value. If so, we just assume they are normal exception (not async exception).
If you disagree with this, please let me know.
Thanks for reviewing. Leo Yan