We need to extract video from the Jetson Orin Nano to reach an FPD link III interface (Orin → … → FPD link III interface), since we have a proprietary external Display that works with FPD link III interface (external Display: DS90UB926 deserializer + 480x272 LCD with 10MHz pixel clock).
We have evaluated the option of using a Texas Instrument serializer that passes from the HDMI output of the Jeston Orin Nano to the FPD link III interface. But it is not valid, due to the minimum HDMI clock (TMDS clock/pixel) which is 25MHz, being higher than the clock allowed by our LCD (it only allows pixel clock in the range [8MHz, 12MHz]).
What other options can be done to get video from the Jetson Orin to reach an FPD link III interface?
*** Please note that this reply is generated by LLM automatically ***
To extract video from the Jetson Orin Nano and send it to an FPD-Link III interface, you have a few options to consider. Since the Texas Instrument serializer is not a viable option due to the minimum HDMI clock (TMDS clock/pixel) being higher than the clock allowed by your LCD, here are some alternative solutions:
FPD-Link III Bridge Chip: You can use a bridge chip specifically designed for FPD-Link III interfaces, such as the DS90UB953 or DS90UB954 from Texas Instruments. These chips can convert the HDMI output from the Jetson Orin Nano to an FPD-Link III interface. However, you will need to ensure that the bridge chip can handle the pixel clock range of your LCD (8-12 MHz).
HDMI to FPD-Link III Converter: Another option is to use a dedicated HDMI to FPD-Link III converter module, such as the ones from companies like THine Electronics or Inova Semiconductors. These modules can convert the HDMI output from the Jetson Orin Nano to an FPD-Link III interface, and some of them may support pixel clock ranges that are compatible with your LCD.
Custom FPGA-based Solution: If the above options are not feasible, you can consider designing a custom FPGA-based solution that can convert the HDMI output from the Jetson Orin Nano to an FPD-Link III interface. This approach would require significant development and testing efforts, but it can provide a customized solution that meets your specific requirements.
Jetson Orin NX Module with FPD-Link III Interface: If you are designing a custom carrier board for the Jetson Orin NX module, you can consider adding an FPD-Link III interface to the board. This would allow you to connect the Jetson Orin NX module directly to your external display without the need for any additional conversion or bridging.
In comparison, the FPD-Link III Bridge Chip and HDMI to FPD-Link III Converter options are more straightforward and may require less development effort. However, the custom FPGA-based solution and Jetson Orin NX Module with FPD-Link III Interface options may provide more flexibility and customization options, but they require more development and testing efforts.
It is essential to evaluate each option carefully and consider factors such as cost, development time, and compatibility with your LCD before making a final decision.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Thanks for responding to me so quickly!
I see that some of the options are designed for video capture, being the camera and the CSI interface. In my case I need it for the video output (display) of the Jetson Orin Nano, either: DP, eDP or HDMI. What options would I have?
If you require higher throughput in display output, it exceeds hardware capability and you may need to go other route, such as compress the video frame data and stream out through RTSP.
We actually have problems with the minimum clock (pixel clock/TMDS) of the HDMI output of the Jetson Orin Nano, since it seems to have a minimum of 25MHz. The bad thing is that our LCD only supports the range [8 MHz, 12 MHz], less than the minimum of the HDMI output of the Jetson Orin Nano.
We need to take the HDMI (or DP/eDP) output of the Jetson Orin to an FPD link III interface, necessary to finally lead to the LCD. We have tried it with several Texas Instruments serializers that receive DP/eDP/HDMI and output FDP link III, but in all of them the minimum clock (pixel) is 25 MHz, being higher than that supported by our LCD (range [8 MHz, 12 MHz]), and that is why this option is not suitable for us.
What other options can be made to bring the DP/eDP/HDMI output of the Jetson Orin Nano to an FPD Link III interface and that meet the clock restrictions of our LCD of [8MHz, 12MHz] as a pixel clock?
Hello!
Thank you for your option (use the common HDMI/DP resolutions), but it is not valid for our design, since we are forced to use LCD (480x272, pixel clock between 8MHz and 12MHz).
From what I have seen on the Internet, it seems viable to use DP or eDP to work with clocks around 10MHz, but not possible for HDMI since its minimum frequency is 25MHz.
Would it be possible to use the DP or eDP output of the Jetson Orin Nano to work with a size of 480x272 and with a pixel clock between 8MHz and 12MHz?
Thank you,
Daniel.
Which parts of your system are fixed (can’t be changed)
LCD (most likely a 4.3” parallel RGB display)
FPD Link?
?
Idea:
This is an external graphics controller that has support for these standard 480*272 Pixel TFT displays with parallel RGB interface. You can connect such a disply directly to this chip. This chip also handles touch if you need this.
This display controller does not use HDMI or DP but (Q)SPI. You should not have any problems connecting this chip to any Jetson board. SPI clock can go up to 30 MHz. If the distance between the Orin and your display is larger than a few cm you’ll need transceivers to LVDS, RS485 etc.
We do not have direct access to the Display, we can only reach the FPD link III interface, since we have a proprietary external display that works with the FPD link III interface (External display: DS90UB926 deserializer + 480x272 LCD with 10MHz pixel clock).
Does your display have an EDID rom? This chip needs one in order to supply the display properties to the DP and to the Jetson display controller. You would need the emulation function otherwise. You need a way to configure the chip via I2C before use.
I’m not sure if the DS90USB927 serializer is compatible. From the electrical data it should, but regarding the data format I don’t know if all bits are in the same position. DS90UB925 and DS90UB926 are a matching pair that is guaranteed to work.
+Do you mean the PTN3460I?
Yes, sorry, I meant PTN3460I.
+Does your display have an EDID rom?
Our display does not have EDID ROM. I have seen that the PTN3460I seems to be able to emulate the EDID without requiring the Display/LCD to have EDID ROM.
+I’m not sure if the DS90USB927 serializer is compatible.
In the old design we are using the DS90UB927 serializer with the DS90UB926 deserializer, so there should be no problems.
Could there be something else that makes the option of using “PTN3460I + DS90UB297” invalid?
I have some questions about whether the Jetson Orin Nano can output the LCD format required by 480 x 272, 50-60fps, with a pixel clock of around 10MHz via DP/eDP output in Jetson Orin Nano. Is this possible?
If it is, what do I need to do? Would using the emulated EDID of the PTN3460I work? Could I force this format on the DP/eDP output by modifying the device tree or drivers?
This is eactly why I suggested the Bridgetek BT817/818 Display controller. This is completely independent of the Jetson’s HDMI/DP outputs, and it can drive such displays directly without any HDMI/DP in between. Ok, you will have to write code specifically for this controller, but it will work.