If I understand correctly, DisplayPort began working after installing the EEPROM U17..? The same one that the Product Design Guide states it is not needed in custom design..?
Just to clarify. You need to figure out what kind of question you are asking here
“Display port begins to work” is a very unclear target here.
For example, if your board is not able to boot, then won’t have monitor shown.
If you forget to power on the board, then won’t have any monitor shown.
If your hardware design on displayport itself is wrong, then won’t have any monitor shown either.
There are too many kind of reasons that could lead to “display not able to work”. You should dump log from UART log to clarify what kind of error you hit here first.
Taking a EEPROM question to us and ask about Displayport sounds more like a boot issue to me. Nothing related to display.
I’ve just came across this thread and saw that @keyma305 had a problem with the DisplayPort in his custom carrier board (when connected the display to DevKit - no problem observed).
What triggered my question us that he indicated that the problem was solved once the EEPROM was installed.
The discussion on that post has nothing valuable .
The logic we just told here is the correct direction. You need to understand what you are doing here.
Adding a EEPROM would affect the boot, but it won’t affect the display directly.
But if your system does not boot, you won’t have display either.
The result are all “display not work” but the reason behind is totally different.
So you need to clarify whether your board is able to boot or not first..
If your device already booted up, then dig into EEPROM could be a waste of time.
Hope you understand what we are talking about here. This has nothing to do with Jetson. This is basic sense when using a computer.
If you just want to ask whether you need to add ID EEPROM on the board, then it is not. You don’t need that.