Memory read operation timed out, LCD and 1788

Comments

4 comments

  • Avatar
    Jeff Shires

    I have a similar issue with a custom Atmel ARM SAM3U4E design.  When RAM sections (e.g., bss, , .data, .stack) are placed in processor internal RAM, everything works.  But when RAM sections are placed in external RAM starting at address 0x61000000, the debugger eventually disconnects with the error "Memory read operation timed out" or "Cannot write processor state".  The software continues to run (i.e., it has not crashed) even though the debugger disconnected. 

     

    At this point, I don't know what's causing this issue. 

    0
    Comment actions Permalink
  • Avatar
    Jeff Shires

    The issue I described above occurs with CrossWorks for ARM, Release 2.3.1. 

    0
    Comment actions Permalink
  • Avatar
    Shyan Jenq

    I ran into this issue too while trying to run long iterations on my EMC SRAM. Where I did a write to the SRAM by copying data over from Flash, then I did a modification in SRAM, which at this point of time ran into "Memory read operation timed out" or "Cannot write processor state". No real way to debug this because do not know where or what trip this particular condition. The only clue I got from my side is when I totally stop the SRAM pointer from moving will this problem stop occuring. Having said that, my SRAM pointer is only moving 16 bytes  in the SRAM back and forth, continuing looping and not even going anyway further. 

    0
    Comment actions Permalink
  • Avatar
    Shyan Jenq

    Oh and I am using JTAG adapter USB CrossConnect for ARM. 

    0
    Comment actions Permalink

Please sign in to leave a comment.