DS320PR822: Download profiles for DS320PR822 in SigConArchitect tool

Hi David,

The customer used USB2ANY tool to connect DS320PR822 but was unable to connect.

This is the register F1 of DS3200PR822 that can be read and written normally using other I2C tools. The register is the ID of the chip (the ID of DS3200PR822 is read as 29)

Do GUI tools require any other configuration operations?

This toggle LED can control the LED lights on USB2ANY,right?

Hi David,

By the way, The customer cannot connect to the GUI of CDCE6214 even with USB2ANY.

Do USB2ANY need to be configured when using different GUI tools

Hi Vayne, 

Due to the US Christmas and New Year holiday, the response to your question will be delayed. Sorry for the wait and any inconvenience it may cause.

Thanks,

David

:Hi Vayne,

For the DS320PR822 question, are you only trying to connect to one DS320PR822 device? Or, are you trying to connect to multiple DS320PR822 devices? I suspect that if you are only trying to connect to one DS320PR822 device, that the GUI will be looking for all SMBus addresses entered in the "Downstream" and "Upstream" address fields.

• If you are trying to connect to only one device, please use the "DS320PR822EVM-SMA" EVM Model and select the device's Slave Address
  
• If you are trying to connect to more than one DS320PR822 devices at the same time, please select the "DS320PR822EVM-CUSTOM" EVM Model and enter each of the device's slave addresses using the "Edit Device Addresses" button and menu.
  

Please let me know if this helps to resolve the DS320PR822 SMBus connectivity issue with the SigCon Architect GUI.

Regarding the CDCE6214 question, I will re-assign the thread to the appropriate product line so that they can help assist. I am unsure if the TICS PRO software uses a different driver version for the USB2ANY. Please excuse any delay in response due to the US Christmas and New Year holiday. Sorry for the wait and any inconvenience it may cause.

Best,
David

Hi David,

Thank you for your reply,

At present, they are using two ICs to form a 4-lane PCIe for switching, one connected to RX and the other connected to TX.

Even with the configuration above, it still doesn't work.

Below is the error message

7.7204729000,65,0x30,W
7.7205499000,66,0x31,R
7.7354775000,67,0x34,W
7.7355545000,68,0x35,R
7.7414768500,69,0x38,W
7.7415538500,70,0x39,R
7.7564814000,71,0x3C,W
7.7565584000,72,0x3D,R
7.7614729500,73,0x40,W
7.7615499500,74,0x41,R
7.7654789500,75,0x44,W
7.7655559500,76,0x45,R
7.7814776000,77,0x48,W
7.7815546000,78,0x49,R
7.7974816500,79,0x4C,W
7.7975586500,80,0x4D,R
7.8034785500,81,0x50,W
7.8035555500,82,0x51,R
7.8184813500,83,0x54,W
7.8185583500,84,0x55,R
7.8234793500,85,0x58,W
7.8235563500,86,0x59,R
7.8274750500,87,0x5C,W
7.8275520500,88,0x5D,R
7.8314804000,89,0x60,W
7.8315574000,90,0x61,R
7.8364810000,91,0x64,W
7.8365580000,92,0x65,R
7.8504799000,93,0x68,W
7.8505569000,94,0x69,R
7.8644812500,95,0x6C,W
7.8645582500,96,0x6D,R

The above is the data captured by the customer using a logic analyzer after automatic detection of USB2ANY points.

The device IDs of 822 on the board are 0x1e, 0x1f, 0x30, and 0x31, respectively.

Vayne,

Is this the latest web version of the TICS Pro software for the CDCE6214? Can you try the I2C scan in the USB Communications > Interface menu?

Is this issue with the CDCE6214-Q1 evaluation module?

Thanks,
Kadeem

Hi Kadeem,

The version is as follows

The customer has tried I2C scan in the USB Communications, but there are still issues

Vayne,

The connection mode "Device Not Connected" means that the USB2ANY connected to the PC is not being detected. It is possible that the handle is being held by another instance of TICS Pro, that the USB2ANY is not connected to the PC, or that the firmware on the USB2ANY needs to be updated. I expect that the second option is the most likely, as your previous screenshot shows the USB2ANY connected.

Are you using the evaluation module for this device, or is this on a custom board?

Thanks,
Kadeem

Hi Vayne,

Could you please select the "DS320PR822" device under the Device Model drop-down menu before editing the SMBus addresses, then try to connect? Its odd that the other I2C tool is working, so I'm thinking there may be some sort of address issue or the GUI is looking for a different device ID.

If you could attach a schematic of the device SMBus address strapping and I2C connection so that I could take a look, this would be helpful as well.

Best,
David