• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 325 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.

TDA4VM: Device tree - OSPI0 node properties for cypress device S28HS01GT-GA-B-H-B-01

Sankar Muthukrishnan
Intellectual 610 points
Part Number: TDA4VM

Hi Karan,

I found a SDK document link for the cypress flash part: S28HS512TGABHM010.

Link: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j7200/latest/exports/docs/j7200/linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI.html

If we are using Part no: S28HS01GT-GA-B-H-B-01. Can I reuse the ospi0 properties from the link.

 

Few queries:

  1. In the sdk ospi0 node found in following dts/dtsi files - k3-j721e-r5-common-proc-board.dts & k3-j721e-som-p0.dtsi. The properties seems to be different, which one is taken for EVM?.
  2. For cypress 256KB is reserved for “ospi.phypattern”. How is this decided between 128 KB (micron-512Mb) vs 256 KB(cypress - 512Mb).

Thanks & Regards,

Sankar M

  • 0
    Intellectual 610 points

    Hi Karan,

    Please ingore question 1. i got the answer and it is my misunderstanding

  • 0 in reply to Sankar Muthukrishnan
    TI__Guru* 77084 points

    Hi Sankar,

    The PHY tuning data needs to be flashed to the last sector of the flash. On the MT35XU512ABA1G12 flash the sector size is 128KB and hence the last sector starts at 0x3fe0000 whereas on the S28HS01GT-GA-B-H-B-01 the sector size is 256KB and hence the last sector starts at 0x3fc0000.

    The below parameter is also different, let me check on what needs to be the value for that for the flash you are using:

    cdns,read-delay

    Regards

    Karan

  • 0 in reply to Karan Saxena
    TI__Guru* 77084 points

    Hi Sankar,

    For now, lets use the OSPI node properties as mentioned in j7200 device tree as the part on your custom hw is similar to the one on j7200 EVM.

    Regards

    Karan