• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 380 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DM648: how to configure the DDR2 512MB

keanu Feng
Prodigy 110 points

Hi, sir

I have a problem with the DDR 512MB in the DM648.As the SPRUEK5A,it just only supports the 256M bytes memory space.

please tell me how to configure the SDCFG Register.

thanks.

  • 0
    Genius 3400 points

    hi all,

        We also meet this problem.

        On DM647/DM648 silicon revision 1.1,  the DDR2 addressing range has been increased from 256M Bytes to 512M Bytes.

        How to configure?

       Thanks a lot.

  • 0 in reply to gomo
    TI__Expert 8260 points

    The same DDR2 configuration written in DM648 GEL file should support both ranges 256M and 512M. What error you are getting if you access DDR2 memory beyond 256 MB?

    Regards, Srirami.

     

  • 0 in reply to srirami
    Genius 3400 points

    Thanks for reply.

    The 256M board works well, but when I use the same GEL to the 512M board. It doesn't work.In the CCS memory watch, I couldn't acess the 0XF000 0000~0xFFFF FFFF. When I change the GEL with the SDCFG Register 0x00000833(IBANK = 3, PAGESIze = 3), it also doesn't work. As the SPRUEK5A, it doesn't support 512MB. On the 512M board, I set two 16bit-128Mb DDR, and add an address line.

    Thanks again.

  • 0 in reply to gomo
    Genius 3400 points

    Anybody can give us some advices?

  • 0 in reply to gomo
    Genius 3575 points

    Check your gel file for GEL_MapAddStr() line that addresses the DDR2 memory range, and make sure the size on that line is appropriate.

    GEL_MapAddStr( 0x80000000, 0, GEL_DDR2_MEMORY_SIZE, "R|W|AS4", 0);

    This function restricts the areas of memory that you can access through the debugger, with the idea to prevent a crash by attempting to access non-existing memory.

    The memory might be correctly configured, but if you still have the 256MB size in your gel mapping then you can't see it in the debugger.

  • 0 in reply to MattLipsey
    Prodigy 110 points

    Thanks a lot！！