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.

Linux/66AK2H14: DDR3 memory stress testing

Part Number: 66AK2H14


Tool/software: Linux

Hi,

we are designing a custom board losely based on the Keystone II EVM (www2.advantech.com/.../EVMK2HX_sd4.aspx)

I would like to stress test all the DDR3 memories (a DIMM module attached to controller DDR3A and on-board chips attached to controller DDR3B).

I have found the 'memtester' tool which is purpose made for such test, but how do I target the individual memories?

From what I see linux appears to use only the DIMM module attached to DDR3A, so targetting the module is straight forward. But how can I also test the memory attached to DDR3B?

Thanks in advance

  • Hi,

    From what I see linux appears to use only the DIMM module attached to DDR3A, so targetting the module is straight forward

    This is because DDR3A is connected directly to ARM cores & DSP cores through MSMC and DDR3B is available to all the peripherals of the device + core packs through TeraNet. This is why the memtester works for ddr3a.

    The easiest way to test your DDR is to use GEL files, as described here:
    www.ti.com/.../sprac04.pdf

    Best Regards,
    Yordan
  • Thanks for your response Yordan.

    Ok, so a little more effort is required to implement this.

    I have already started to work on a small bare-metal app that implements the memory test.

    While doing so I also found that there are some functions in the board GEL scripts already to test both, DDR3 A and B.

    (CCS V7.2.0: <path to installation folder>\ccsv7\ccs_base\emulation\boards\xtcievmk2x\gel\xtcievmk2x_arm.gel)

    DDR3A works fine, but DDR3B does not .... is there anything specific I have to do before being able to run this test on DDR3B?

    Looking through that GEL file I would have thought that it takes care of all configuration. (My test app can't access DDR3B either (trying address 0x6000_0000))

    Regards,

    Rene