Trap 1 still happening after all memory sections ranges are permitted

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User19424
Level 3
Level 3
First solution authored First like received
Hello Community,
I ran into a very weird issue.

I have authorized all sections to run/read/write in my Memory Protection Set, but a certain line still causes Trap 1 (TIN 2, meaning read protection) 😞

I would very appreciate if someone could help me take a look at this, I'll add screenshots from my debugger:

Line the causes the Trap Jump
4751.attach

Register State before Trap:
4752.attach


Here is the Register State after the Trap is activated + The DEADD Register:
4753.attach

And Here is the Memory Protection Set With upper and lower bounds:
4754.attach
4755.attach

*PROTEN is enabled and PRS is Set0

Many Thanks for your help!
0 Likes
2 Replies
NeMa_4793301
Level 6
Level 6
10 likes received 10 solutions authored 5 solutions authored
But isn't A5=8000E4B7 before the trap? That looks outside of your ranges. Odd that DEADD is something else though.
0 Likes
MoD
Employee
Employee
50 likes received 500 replies posted 100 solutions authored
DPR2 section is defined only until 0x8000E498 therefore 0x8000E4B7 is out of this range and not defined in another range. This result in the protection trap. After change this there will be occur an alignment trap if the address is not corrected to a 16 bit aligned address.
0 Likes