DP159RSBEVM: The EVM is not working

Hi, Danilo

Why are they burning the EEPROM on the board?

Are they connected to a DP++ or DP source? The DP158 can only work with a DP++ source.

Thanks

David

Hello David,

I was not getting the reading on the EyeScan tool and I followed the user manual of the EyeScan tool which suggested to program the firmware. 

I am not sure what are the differences between the DP and DP++, I will attach a photo of our connector on the board but it seems to be DP.

Also, we are using DP159 if that is any different from DP158.

Is there a way to reverse the burning? or how should I proceed from here?

Hi,

You can download the firmware from TUSB3410 product page and re-burn the EEPROM, https://www.ti.com/product/TUSB3410?keyMatch=TUSB3410&tisearch=search-everything&usecase=GPN#software-development.

The firmware enables the TUSB3410 to act as a USB to I2C bridge and let the EyeScan SW controls the DP158/159 through the I2C interface.

But you still need to make sure your source is DP++, and not DP. DP158/159 will only work with a DP++ source. If the source is DP, then you would need an active protocol converter.

Thanks

David 

Hi,

Thank you for the quick response David.

I am trying to re-burn ;however, the device is not detected now and I cannot move on. Can you please guide me on this?

Thank you!

Rosti

Rosti

Can you try to manually install the TUSB3410 driver? Please see this app note, section 4 for manually installing the driver and see if it helps, https://www.ti.com/lit/ug/sllu205/sllu205.pdf.

Thanks

David 

Hi David,

I re-installed both the driver and the Burner and I still cannot detect the device. Everything is updated and the USB is recognized on COM3 but I cannot see TUSB3410 on the burner

Thanks,

Rosti

Rosti:

     Can you uninstall all EEPROM burner , USB to I2C bridge and eyescan tool first , then install only EEPROM burner ? Maybe the Burner can't find the right firmware.

Regards

Brian

Hello Brian, 

I uninstalled everything as you suggested and then installed only the burner. I still have the same issue:

Is there anything else I can do?

Thank you!

Rosti

Maybe something got bad on that board, I will check here and let you know.

Regards

Brian

Hi Brian, 

I just got a confirmation from the manufacturer of the carrier board that the source supports DP only and not DP++. Earlier in the messages, David mentioned that I can use a protocol converter. 

Are there any efficient solutions for conversion that you can suggest me? Or does TI has any ICs that supports DP?

Although, I found out that that the carrier supports DP only, the burner should have recognized the firmware anyway, am I correct?

Thank you!

Rosti

Rosti:

     We should have DP re-driver, I will let David back to you.

     Burner should recognized the firmware anyway, but re-driver don't have eye-scan  too.

Regards

Brian

Hi, Rosti

We do not have an active DP to HDMI protocol converter solution. Parade PS196 is one solution that can support this function, https://www.paradetech.com/products/ps196/.

But as Brian pointed out, you should still able to get the TUSB3410 burner to work as it is a separate function.

Thanks
David

Hello David,

Thank you for the clarification.

After multiple attempts I still cannot get the burner to work, it does not recognize the firmware. Maybe something is bad with the board.

Would you be able to suggest me potential DP-redrivers as well please?

Best regards,

Rosti

Rosti

For DP redriver, please use SN65DP141 or TDP142. DP Redriver is DP input and DP output. 

Thanks

David

Hi David,

After speaking with our board manufacturer, the engineers actually confirmed that this specific board does support DP++. 

However, we are still unable to recognize the board. Is there any way to force the firmware into the EEPROM? Could it be that the EEPROM has a bad firmware on it?

Rosti

Can you work with Danilo and send the board back to me? I will check the board out to make sure there is no issue.

Thanks

David

Hello David,

Thank you for the support. We just checked the EVM using a display docking station and it worked well. 

At this point, I think the issue comes from the carrier board that we have, and we are trying to solve the issue with the manufacturer.

Thanks again,

Rosti

Rosti

Thanks for the update. Please feel free to send me the board for the TUSB3410 repair if there is ever a need.

David