Categories

{{ selectedCategory.name }}

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!

Unpredictable CPU behavior due to unintended memory reads

14-Mar-2024

If the CPU starts to behave unpredictably, make sure you are not making any unintended memory reads.


Possible solution

 Close all debug windows and see if this resolves the problem. This will help you identify which debug window is performing the problematic memory reads.


Possible causes

Memory reads to undefined memory regions may cause the CPU debug to fail. Such issues are most commonly caused by:

  • Opening Memory window in undefined memory space, eg. wrong address range, non-initialized RAM with EC.
  • Viewing SFR groups for the peripherals, which are not yet enabled.
  • Reading SFRs which affect the CPU just by being read (e.g. interrupt acknowledge registers).
  • Uninitialized pointers listed in the Watch, Locals and Callstack windows.
  • Scrolling through the disassembly window into an undefined memory region.


Was this answer helpful?

Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.

Similar topics

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No similar topics found!

Other topics in the same category

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!