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.

Does 3.02.00.03 SDK support DRA716 & DRA725?

Other Parts Discussed in Thread: DRA750, DRA714, DRA716, DRA725

We are using 3.02.00.03 SDK version to develop, and is already workable at DRA714 & DRA750(DRA750BJGABCR).

Now we'd like to change CPU to DRA716 & DRA725(DRA725BMGABCRQ1). Does 3.02.00.03 SDK support these two CPU type?

If it can, should i modify u-boot or kernel to deal with this change?

Regards,

Shawn

  • Shawn
    3.02 releases support DRA71x, DRA72x, DRA75x family of devices
  • Hi Sriram,

    Below are our CPU change info:

    1.DRA750BJGABCRQ1 -> DRA725BMGABCRQ1

    2.DRA755BLH3ABCRQ1 -> DRA750BJH3ABCRQ1

    3.DRA714BEGCBDRQ1 -> DRA716BGGCBDRQ1

    I have some questions,

    Q1.Should i modify u-boot or kernel to deal with this change?

           For example, DRA714 -> DRA716,  they are different in Arm MHz and DRAM speed(DRA714 is 600 Arm MHz DDR3-1066, DRA716 is

           800 Arm MHz DDR-1333).

    Q2.What's the different about the serial number mean? ex. DRA755BLH3ABCRQ1   V.S. DRA750BJH3ABCRQ1, i mark the different part as red color, should i modify code to deal with this different?

    Regards,

    Shawn

  • Hi Shawn,

    > Q2.What's the different about the serial number mean? ex. DRA755BLH3ABCRQ1 V.S. DRA750BJH3ABCRQ1, i mark the different part as red
    > color, should i modify code to deal with this different?

    You can check chapter "9.1.2 Device Naming Convention" of device Data Manual for explanation of device nomenclature description.
    In your case deference is in device speed and "L" stands for "Overdrive speed grade" and "J" for "Nominal speed grade".

    (Sriram will reply to the other questions)

    Regards,
    Yordan
  • Hi Sriram,

    Any update for my Q1 question?
    Q1: Should i modify u-boot or kernel to deal with this change?

    DRA714 -> DRA716, they are different in Arm MHz and DRAM speed(DRA714 is 600 Arm MHz DDR3-1066, DRA716 is

    800 Arm MHz DDR-1333). Currently, i can boot DRA714 successfully.

    Regards,
    Shawn
  • Shawn
    For devices that belong to the same product family, SDK will setup the frequencies based on OPP_NOM(in some cases HIGH) values for the super set part. For derivative parts that operate at lower speeds we will need to modify suitably in uboot
  • Hi Srirama,

    Srirama Govindarajan said:
    For devices that belong to the same product family, SDK will setup the frequencies based on OPP_NOM(in some cases HIGH) values for the super set part.

    Is this mean SDK will deal with Arm clock change(from 600MHz to 800Mhz) automatically without modify uboot code?

    Srirama Govindarajan said:
    For derivative parts that operate at lower speeds we will need to modify suitably in uboot

    What does "the derivative parts" mean? And where should i modify if needed?

    Although DDR clock change from DDR3-1066(DRA-714) to DDR3-1333(DRA-716), but i think DRA-716 still support DDR3-1066 speed, so may i still can use DDR3-1066 clock setting for DRA-716 to boot?  

    Regards,

    Shawn

  • Shawn
    For the ARM core alone DVFS is supported. This implies that the linux kernel includes a CPUFREQ governor and a driver that allows for the ARM CPU frequency to be modified dynamically (as chosen by the governor). The list of supported frequencies is dependent on the specific part and can be passed as input to the kernel

    For DDR, the configuration happens very early from the boot loader and is decided based on reading configuration information programmed in EEPROM
  • Shawn
    To clarify further, for ARM frequency supported is an enumerated list of supported frequencies and the max frequency that can we can be allowed to operate at is determined based on the part(efuse values). Need to check if 600, 800Mhz are covered as part of the current driver implementation - will revert back on this

    For DDR, the DDR size is determined based on the configuration value programmed in the EEPROM and the speed/clock currently is programmed based on the DeviceID . Bootloader can be suitably modified to pick the right setting based on the exact part number
  • Hi Srirama,

    Srirama Govindarajan said:
    Need to check if 600, 800Mhz are covered as part of the current driver implementation

    Where can i check at the driver?

    Srirama Govindarajan said:
    the DDR size is determined based on the configuration value programmed in the EEPROM and the speed/clock currently is programmed based on the DeviceID

    Currently, dra716 datasheet said it support DDR3-1333 & DDR3L-1333. I have 3 questions,

    1. This mean the maximum DDR clock speed supported by dra716, right?

    2. Does dra716 also support DDR3-1066 & DDR3L-1066 clock speed?

    3. Because our DDR chip support 1066 DDR clock speed and we use 1066 DDR timing parameter at u-boot to boot now, so we hope to use these timing parameter for dra716 to boot, is this ok?

    Regards,

    Shawn

  • Former Member
    0 Former Member in reply to shawn lin
    Hi Shawn,
    Apologize for the delay in response.
    I will try to get back to you in a couple of days.

    Regards,
    Somnath
  • Hi Shawn,

    1) Yes, the maximum DDR data rate for DRA716 is DDR3/L-1333.

    2) Yes, DRA716 also supports DDR3/L-1066 data rate.

    Best regards,
    Kevin

  • Former Member
    0 Former Member in reply to Kevin S
    Hi Shawn,
    In addition to Kevin's reply on DDR3 data rate, I also wanted to point to a relevant thread that should address your query on changing the ARM cpu speed. Please take a look at the thread here --> e2e.ti.com/.../2286496

    Regards,
    Somnath