DS320PR1601RSCEVM: The problem with DS320PR1601 32-CHANNEL PCIE 5.0 DS320PR1601 Re-Driver Interface Evaluation Board

Hi technical support team!
Could you please tell me when I can expect comments?
Thank you!

Hi Milosh,

We apologize for the delay. I will look over this and will get back to you this week.

Best regards,

Greg

Texas Instruments SigCon Architect EVM GUI v3 Setup with RTE.zip

Please install this version of SigCon and let us know if the issue still occurs.

Hello, thank you!
Could you please provide the latest version of the library that is compatible with this version of SigCon?

Hi Milosh,

It is possible that the version from the above .zip is mismatched with the version of the device profile. In the folder https://www.ti.com/secureresources/PCIE5-REDRIVERS-DESIGN,  please download TI_SigConGUI_DS320PR1601-Updated.zip. This should be the latest version of both the GUI and the device profile. 

Best regards,

Greg

Dear Support!

In our previous request, we sent you a description of issues with the current version of SigCon Architect 3.2 in conjunction with the current version of the DS320PR1601.exe library.

The files are dated March 27, 2023.

With these library and software versions for the DS320PR1601 chip on the DS320PR1601RSC-EVM debug board, the redriver is not detected in SigCon Architect (the device is not found).

I2C logs and a photo of the board with the jumpers set according to the manual were also attached.

In response to this request, we were sent an older version of the SigCon Architect 3.0 software (May 6, 2020).

The DS320PR1601.exe library, designed for SigCon Architect 3.2, doesn't work with this SigCon Architect 3.0.

Please send me the DS320PR1601.exe file that will work with SigCon Architect 3.0.

Thank you!

Hi Milosh,

Thank you for the clarification. I will check internally for this earlier version of the device file and will get back to you by tomorrow.

Best regards,

Greg

Hi Gregory,

could you please let me know if there is any new information regarding my case?

Thank you in advance.

Milosh

HI Milosh,

This updater profile looks to be the only version for this device. I am not sure what could be causing the issue on the GUI side, so I can set this up in the lab and verify which version works on my end. 

Best regards,

Greg

Hi Greg,

I would be very grateful if you could check this in the lab.

Thank you!

Milosh

Hi Milosh, 

I am setting up in the lab now. If you probe the SCL/SDA pins on connector P4 of the EVM when the I2C bus is idle, what voltage do you read?

Best regards,

Greg

Hi Greg,

In standby mode on I2C lines SDA and SCL 3.3 Voltage

If you mean the state of the line without the adapter connected, then the voltage is 3.3 V.

With the adapter connected to the debug board, for some reason the voltage on SDA line drops to 2 V.

On the board we designed, the voltage level is independent of the adapter connection and remains at 3.3 V.

Hi Milosh,

That may cause issues preventing the GUI from connecting to the evaluation board. I will check if we have seen this before or if a certain jumper configuration results in a lower voltage on SDA/SCL.

Best regards,

Greg

Hi Milosh,

I am just noticing that in your photo of the EVM configuration, it looks like the I2C Adapter Select header it set to "2-3: Aardvark Controller". If you are indeed using a TI USB2ANY Controller, the jumper should be set to pins 1-2. Have you tried this already?

Best regards,

Greg

Hi Greg,

Yes, we tried switching the jumper. We use a jumper on pins 2-3 with Aardwark.

The messages above also contain an I2C trace, which shows that the Re-Driver is responding to the adapter's polls (there is an ACK).

Hi Milosh,

When you are using an Aardvark, do you select "Aardvark" in the Interface drop-down menu? I also set up the EVM with Aardvark on my end with the same jumper configuration as you, and was able to successfully complete reads/writes. Are you able to complete I2C writes in Control Center with the Aardvark, or is this also not working like SigCon GUI?

Best regards,

Greg