• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 3570 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cortext M3 Program Counter Test

Muhammad Ahsan
Note: This was originally posted on 16th March 2011 at http://forums.arm.com

I am working with Cortex M3 and want to perfrom Stuck at (To check that none of the bit of PC is stuck at 0 or 1) test of Program Counter. Can anybody give me an idea how to implement this? Thanks in advance!
Parents
  • Note: This was originally posted on 21st March 2011 at http://forums.arm.com

    How about a sequence of 16bit instructions (minimum of 16), at a 32 byte aligned address. An appropriate choice of instructions will expose stuck-at faults in the lower bits of PC. For the upper bits you might want to use MPU regions marked as NX, which cover the address you want to verify. The MemManange Fault will tell you whether you've actually tried to access that address.
    Depending on the requirements it may be sufficient if only the MPU sees the address. If you want to check actual address bits on the instruction interface, you'll have to find a more complex approach.

    Regards
    Marcus
Reply
  • Note: This was originally posted on 21st March 2011 at http://forums.arm.com

    How about a sequence of 16bit instructions (minimum of 16), at a 32 byte aligned address. An appropriate choice of instructions will expose stuck-at faults in the lower bits of PC. For the upper bits you might want to use MPU regions marked as NX, which cover the address you want to verify. The MemManange Fault will tell you whether you've actually tried to access that address.
    Depending on the requirements it may be sufficient if only the MPU sees the address. If you want to check actual address bits on the instruction interface, you'll have to find a more complex approach.

    Regards
    Marcus
Children
No data