DS320PR810RSCEVM: EEPROM not writing

Part Number: DS320PR810RSCEVM
Other Parts Discussed in Thread: USB2ANY, DS160PR810EVM-RSC

Hi ,
I have procured a DS320PR810RSCEVM and installed the required profile for that.
1)But when making the changes in the GUI( making few Equalization value changes to particular changes), and writing them to EEPROM , it is showing write successful .
But when connected the DS320PR810RSCEVM in my setup , and loading the values from EEPROM it is not showing the previous saved values which i did earlier by writing to EEPROM.
So it is acting as a intermediate card in my setup and the link is downgrading , if the changes which i made were successful then the link would have come for higher generations of PCIe.

2)And to add on, the card is not getting detected from USB2ANY, but it is being detected while using Aardvark .


  • Hi Vamsi,

    Please follow the setup in EVM user's guide section 2.11 Quick-Start Guide (SMBus Slave Mode). For step 1, place shunt on J1 L1 location (instead of L2 from the guide) to set devices in SMBus Master mode. 

    The auto-detect button should auto-populate the address shown in the screenshot below: 

    Please follow 3 EEPROM Programming page in the "How to Configure the DS320PR810 Using SigCon Architect" app note for EEPROM programming guidance. 

    Best,

    Charles

  • Hi Charles, i placed shunt on J1 L1 location, and still I am not able to detect the device using USB2ANY.
    with Ardvark connected i have downstream devices ( DS1(0x00, 0x01) show and it is blank in upsteam devices), and when I am writing to EEPROM  it is showing write successful but when I am clicking on Load from EEPROM it is not showing the values which I entered earlier.
    Attaching few screenshots of the errors encountered while USB2ANY is connected:

  • Hi Vamsi,

    Could you check if write protect is enabled on the EEPROM. Also, please check USB2ANY is connected correctly to the EVM: 

    Best,

    Charles

  • Hi charles, 
    We have already worked with TI Gen4 redriver DS160PR810EVM-RSC, and since we wanted to do more we procured this Gen 5 redriver, we have been using the GUI since then.


    On the DS320PR810EVM-RSC , the write protect is enabled( on J5 header, EEPROM write enable is tied to GND), and the USB2ANY interface is also connected correctly.
    attaching few images of the same.


  • Hi Vamsi,

    Thanks for sending pictures of the EVM. Your USB2ANY connection looks correct.

    Could you please double check that your SMBus address strap jumper settings (J15, J16, J22, J23) matches the ones below:

    Best,

    Charles

  • Hi Charles,
    Checked the  J15, J16, J22, J23 made them accordingly as in the image you shared, but still EEPROM write is not happening.
    I am attaching a video of the GUI, please check it. 
    Even though the device is connected , when I am selecting the device and clicking on Auto-detect is is showing no device, so i directly clicked on Apply button.
    In the EEPROM page i wrote some EQ values to device 0 and then clicked on write to EEPROM, later when I am clicking on Load from EEPROM , it is giving the default values.

  • Hi Vamsi,

    My jumper for J23 was incorrect (J15, J16, J22 remains the same). Please see revised image below: 

    On GUI side, ensure device address are configured before hitting "apply". Otherwise, no GUI changes will take affect. For pin settings shown above, please use configuration shown below: 

    Best,

    Charles

  • Hi Charles ,
    checked with the configuration of J23 header as well, it is still the same.

    In the GUI when I am clicking on Auto Detect is it telling "Device not found" and it is showing Downstream devices address (0x00, 0x01) but it is not showing any Upstream devices.
    Could the card itself be bad, I don't know , it has been many days since we started debugging this card.
    Could we connect over a call?

  • Hi Vamsi,

    Please try manually setting the addresses according to the jumper configuration by clicking "Edit Device Address". 

    Unfortunately, we do not support call over E2E queries. 

    Best,

    Charles