• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 881 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.

Linux/TMS320DM8127: DM8127 CSK

Sriram V
Intellectual 955 points
Part Number: TMS320DM8127

Tool/software: Linux

Hi,

I use DM8127 CSK board. I use TI 8127 RDK 3.9.1 Release. From the documentation. This board has a DDR size of 2GB. 

The u-boot detects this board as having only 1GB and not 2GB. When i run the memory tests the portion which access 0xA0000000 to 0xC0000000 hangs.

Can anyone provide clarity on this please? The only change i have done is to enable memory commands in the config file in u-boot.

Am i using the right sources or is this the expected behaviour? 

My log:

U-Boot SPL 2016.05 (Nov 18 2017 - 20:15:17)
Trying to boot from MMC2
reading u-boot.img
reading u-boot.img


U-Boot 2016.05 (Nov 18 2017 - 20:15:17 +0530)

I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment

Net: <ethaddr> not set. Reading from E-fuse
cpsw
Hit any key to stop autoboot: 0 
DM8127-CSK# mtest 0x81000000 0xA0000000 0xaa55aa55 3
Testing 81000000 ... a0000000:
Pattern AA55AA55 Writing... Reading...Tested 3 iteration(s) with 0 errors.
DM8127-CSK# mtest 0xA0000000 0xC0000000 0xaa55aa55 3
Testing a0000000 ... c0000000:
Pattern AA55AA55 Writing...

Could you please advice me on this.

Thanks,

Sriram

  • 0
    Mastermind 8715 points
    Hi,

    DM8127 CSK has 2GB RAM. But software is not configured access complete RAM. This is in align with our idea of demonstarting that less foot print is sufficient for all the demonstrative use cases what we run.

    However, you can configure the registers such as DDR & LISA to enable complete 2GB.

    Thanks
  • 0 in reply to Ravikiran HV
    Intellectual 955 points
    Hi Ravikiran,

    Thank you for your response. The bootloader is configured for 1GB which is from 0x80000000 to 0xC0000000.

    Could you please respond to my other question which is why are the memory tests in u-boot hang with the RDK 3.9.1

    This is what i ran:

    DM8127-CSK# mtest 0xA0000000 0xC0000000 0xaa55aa55 3
    Testing a0000000 ... c0000000:
    Pattern AA55AA55 Writing...

    Thanks,
  • 0 in reply to Sriram V
    Mastermind 8715 points
    Hi Sriram V,

    While running, U-boot has loaded to the RAM. By writing 0xA5A5... pattern to the RAM, actually u-boot corrupts itself.
    You need to run mtest by excluding u-boot region in RAM.

    Does that help ?

    Thanks
  • 0 in reply to Ravikiran HV
    Intellectual 955 points
    Hi Ravikiran,

    From my understanding, The u-boot sits in the region of 0x80000000 and occupies some space from in that region. I run my command from 0xA0000000 which does not overwrite u-boot unless there are issues with the memory timings. Could you please check why we can't access the RAM region of 1GB which is configured.

    DM8127-CSK# mtest 0xA0000000 0xC0000000 0xaa55aa55 3
    Testing a0000000 ... c0000000:
    Pattern AA55AA55 Writing...

    Thanks,
  • 0 in reply to Sriram V
    Mastermind 8715 points

    Sorry, thats my mistake. I read it as 0x80000000.
    Your understanding is correct.

    Please can you confirm me that it working for address regions up to 0xA0000000 & problem is only with 0xA00... to0xC00..

  • 0 in reply to Ravikiran HV
    Intellectual 955 points
    Hi Ravikiran,

    I ran a test from 0x84000000 to 0xA0000000 and it works fine. However beyond 0xA0000000 it does not work.
    Also, Do you use a configuration which works for 2GB DDR and if so, Can you share it?

    Thanks,