Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    PC=0x96 has no relation to any lines in your source code. So, no, there's no point in looking at line 150. Line 150 is completely irrelevant here. And where exactly in the manual did you read that 0x0024 is RETI? Commented May 11, 2019 at 2:05
  • I am not understanding the situation for debugging this... Commented May 11, 2019 at 2:28
  • 1
    Where's the program? Errors like that might easily be caused by out-of-bounds local array modification. Stack damage smashes the stored function's return address, making it "return" to a completely wrong location (e.g. 0x96), hitting "invalid instructions" stored there. Commented May 11, 2019 at 2:52
  • 1
    PC=0x96 means the program counter is pointing to that memory location and it is trying to execute the instruction at that location ..... the last picture shows code at 0x1ab4 Commented May 11, 2019 at 2:54
  • 1
    I have the same problem. Would you tell me please, if you have solved the problem, and how? Commented Dec 10, 2020 at 10:39