Dear Sir
If I have SAS3 Mux requirement ,Could I use HD3SS3412 to do that ?
Thanks
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.
Dear Sir
If I have SAS3 Mux requirement ,Could I use HD3SS3412 to do that ?
Thanks
Hi Kai,
I am unable to offer much commentary on the HD3SS3412 for SAS3 applications, but from a lookthrough of the datasheet, I was unable to find indication of support for link-training or OOB burst signaling.
For SAS3 mux, the DS125MB203 may also be worth looking at. It is a mux/buffer equipped with EQ, VOD gain, and de-emphasis to provide additional signal conditioning if desired, and was designed to be used in applications requiring link-training.
Thanks,
Michael
Hi Kai,
Thanks for pointing this out. You are correct. Though the DS125MB203 can support data rates up to 12.5 Gbps, validation would need to be performed on the customer side to ensure correct operation for SAS-3.
After looking further at the HD3SS3412, I believe since it is a generic passive switch that does not perform any equalization or signals the output to be mute/active, the HD3SS3412 can be used to Mux different SAS-3 devices. I think if you require additional signal conditioning features, you may want to add a repeater with the HD3SS3412, such as the DS125BR111 (1-lane) or DS125BR401A (4-lane). This will make a solution that is similar to the DS125MB203, but with SAS-3 support.
I'd like to point a few things I spotted regarding the HD3SS3412 switch. The HD3SS3412 is that it is only spec'd from 0 - 70C as of the Nov. 2013 revision. You will also need to AC couple on both sides if the common mode bias voltage on either side of the switch is >2.0 V. This is particularly important if you use the DS125BR111, where the input is biased to 2.5 V on VDD.
Thanks,
Michael
Hi Kai,
As of now, I am not aware of any demo boards with the HD3SS3412. I will reach out to my TI counterpart in our Consumer & Computing Interface group to comment.
Thanks,
Michael