This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3517 RAM Issues

  1. If I run a ram test and access ram directly, everything seems to run ok.  I write 5’s, verify, write A’s, verify, write sequential values, and verify.  I don’t get any errors doing this.
  2. If I try to load an app that utilizes external memory in the linker command file, I get an error while the app is being loaded by the XDS510PLUS. The error is as follows:  Cortex_A8_0: File Loader: Data verification failed at address 0x82000000 Please verify target memory and memory map.
  3. If I try to load the OS from an SD card, it loads the TI XLoader app from the card then tries to load U-Boot, but it stops.  It’s like it can’t load U-Boot into RAM.

    Texas Instruments X-Loader 1.44 (Dec  8 2009 - 22:58:46)
    Starting OS Bootloader...

 

  • Is this a custom board you are working with, or are you seeing this on the EVM?

    When you get the data verification error, can you verify the RAM is functional at that point through CCS using a view memory window? You should be able to open a view memory window to 0x82000000 and double click on values to try to change them, if they remain changed when you refresh the window than you are successfully modifying the memory.

    Assuming the CCS view memory window test and your other RAM test work properly, the only difference that comes to mind would be the rate of accesses to the external memory, faster continuous accesses failing while individual accesses work, which could be a hardware problem on the board, as general DDR instability can stem from layout issues.

  • This is a custom board.  We will check into your suggestions.  Our layout was done by a very experienced and talented layout person.  He knows the ins and outs of high speed signals, T-routing, etc...  We certainly tried to follow all of the layout rules.  That being said, it COULD be a layout issue but I'm def hoping its not! 

    I'll post an update after we try your suggestion.