• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 103 subscribers
  • Views 1750 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6678: Dose anyone check my gel file for DDR3 ECC Error Verification for C6678?

j-breeze
Mastermind 7560 points
Part Number: TMS320C6678

Hi Champs,

I made a gel script for c6678 DDR3 ECC error verification for one of my customers who are planning to use the DDR3 ECC.
I attached the file.  So, dose anyone check the script whether it can verify the ECC error?

c6678_ecc_test_draft.gel

Regards,
j-breeze

  • 0
    TI__Guru**** 161600 points
    Hi,

    I've notified the SW team. Their feedback will be posted here.

    Bet Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    TI__Guru* 95265 points
    Hi,

    The TI 6678 EVM has 512MB DDR, there is no ECC RAM chip on the board so there is no ECC test reference code or GEL file available. Do you use the customized board with ECC chip? I am looking for ECC test routine and will update you.

    Regards, Eric
  • 0 in reply to lding
    Mastermind 7560 points

    Hi Eric,

    Your prompt reply would be greatly appreciated.

    Regards,
    j-breeze

  • 0 in reply to j-breeze
    TI__Guru* 95265 points
    Hi,

    I looked at your GEL file:

    1, The ddr3_setup_ecc(): the Non-ECC part setting I assume you followed our TI C6678 EVM GEL file. If you used a different DDR3 chip, the timing information needs to be re-calculated for your chip.

    2. How to enable ECC? You did it by Enable_ECC_1(). This looks right by enabling one region

    3. Where to enable ECC? You did it by before starting line leveling, it looks right.

    4. How to configure ECC range, you did it in Set_ECC_Address_Range_1(), looks OK

    5. How to test it? BB_REG_FIELD_WRITE(DDR3EMIF_IRQ_STATUS_SYS,31,0,0x00000018); // Clear ===> this clear R/W interrupt, looks OK. Then a non 64-bit aligned write should generate a write interrupt.

    Overall, the code looks OK. You can also see this E2E for some disscussion: e2e.ti.com/.../280814

    Regards, Eric
  • 0 in reply to lding
    Mastermind 7560 points

    Hi Eric,

    Thank you for your support and I'd like to ask you one more thing.
    Could you give me some advice on how I can verify a read ECC error?

    Regards,
    j-breeze