• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 1493 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.

AM572x RTOS DDR diagnostic

Chethan Shetty
Intellectual 760 points
Other Parts Discussed in Thread: AM5728

Hi,

  In AM5728 sdk rtos diagnostic application supporting DDR(external RAM) test code but its not working in EVM, as i observed that pinmuxing file boardPadDelayInit.c value does not added, even though i tried manually pin muxing using TI-PINMUX tool again values not declared. Please help me with this.

Here is the boardPadDelayInit.c details for ddr

/* ddr1 - ddr1_csn0 on AH23 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_cke on AG22 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_ck on AG24 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_nck on AH24 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_odt0 on AE20 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_casn on AC18 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_rasn on AF20 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_wen on AH21 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_rst on AG21 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_ba0 on AF17 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_ba1 on AE18 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

/* ddr1 - ddr1_ba2 on AB18 - DDR1 */
     /* {NOT FOUND, 0x10000, {0x0, 0, 0}, {0x0, 0, 0}, {0x0, 0, 0}}, */

-

Chethan

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    TI__Guru* 95265 points
    Chethan,

    Can you explain what do you mean "In AM5728 sdk rtos diagnostic application supporting DDR(external RAM) test code but its not working in EVM"? Do you use the latest Processor SDK 3.1? What EVM are you using? GP or IDK EVM? In the diagnostics, you copy the MLO, app and multiple tests into a SD card, when you run the DDR test, can you provide the log?

    Regards, Eric
  • 0 in reply to lding
    Intellectual 760 points

    Hi Iding,

      AM5728 sdk has diagnostic applications which also contain DDR memory test code in it, all diag code like temp sensor, qspi, eeprom etc all these working fine on EVM except DDR code why??

    I'm using processor_sdk_rtos_am57xx_3_00_00_04 and GP EVM.


    Yes i copied MLO,app and test app into SDcard. I'm not getting any log for DDR.

    --

    Chethan

  • 0 in reply to Chethan Shetty
    TI__Guru* 95265 points

    Chethan,

    processor_sdk_rtos_am57xx_3_00_00_04 is an older release, I just tested the latest Processor SDK 3.1, pdk_am57xx_1_0_4 package, with AM572x GP EVM.

    Attached is the MLO, APP and mem_TEST: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/4401.app

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/mem_5F00_TEST

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/0272.MLO

    Below is log, there is no issue for DDR test.

    ø**** PDK SBL ****
    **** Copying Application Image to DDR ****

     SD Boot - file open completed successfully
    Jumping to MPU CPU0 Application...


    Opening framework from SD card...
    Loading framework into memory...
    Running framework

    DIAGNOSTIC TEST FRAMEWORK
    Command options:
            help - displays this help menu again
            run - run a diagnostic application
            status - prints the test status
    [Diag Menu]: run
    Diagnostic Test Status:
    --------------------------------------------------------------
    ID      Name                            Pass    # of times Ran
    1       uart_TEST                       No      0
    2       eeprom_TEST                     No      0
    3       emmc_TEST                       No      0
    4       gmac_TEST                       No      0
    5       led_TEST                        No      0
    6       mem_TEST                        No      0
    7       mmcsd_TEST                      No      0
    8       pmic_TEST                       No      0
    9       temperature_TEST                No      0

    Select test number (1 - 9): 6
    Parsing mem_TEST
    Running mem_TEST

    *********************************************
    *              DDR Memory Test              *
    *********************************************

    Testing writing and reading memory
    board_external_memory_test: Start address (0x80000000), end address (0xffffffff)
    First test started
    Writing to test area...
            Write up to 0x80000000 done
            Write up to 0x90000000 done
            Write up to 0xa0000000 done
            Write up to 0xb0000000 done
            Write up to 0xc0000000 done
            Write up to 0xd0000000 done
            Write up to 0xe0000000 done
            Write up to 0xf0000000 done
    Write finished!
    Checking values...
            Read up to 0x80000000 okay
            Read up to 0x90000000 okay
            Read up to 0xa0000000 okay
            Read up to 0xb0000000 okay
            Read up to 0xc0000000 okay
            Read up to 0xd0000000 okay
            Read up to 0xe0000000 okay
            Read up to 0xf0000000 okay
    Second test started
    Writing complementary values to test area...
            Write up to 0x80000000 done
            Write up to 0x90000000 done
            Write up to 0xa0000000 done
            Write up to 0xb0000000 done
            Write up to 0xc0000000 done
            Write up to 0xd0000000 done
            Write up to 0xe0000000 done
            Write up to 0xf0000000 done
    Write finished!
    Checking values...
            Read up to 0x80000000 okay
            Read up to 0x90000000 okay

    ....

    Regards, Eric

  • 0 in reply to lding
    Intellectual 760 points
    Hi Eric,

    Thanks for you reply!!!

    The code is working fine, evm had some hardware issue now its resolved. Thanks for your concern.

    Regarding this i have one doubt, since our application will run in DDR our MLO is responsible to put our codes into DDR, meanwhile what happens if i run this DDR test code, so the code will do Write 512MB memory and Read the same so logically thinking will it disturb memory currently utilizing code or whatever??

    Please explain me or correct me.

    Regards,
    Chethan
  • 0 in reply to Chethan Shetty
    TI__Guru* 95265 points

    For the memory test, the data/code is placed into OCMC, not DDR. You can't put anything in DDR as the R/W will corrupt it.

    In the makefile of mem_Test:

    # Linker options

    # Memory test must reside outside of DDR memory

    MEM_LINKER = $(PDK_DIAG_DIR)/diag/common/$(DEVICE)/mem_linker.cmd

    Regards, Eric