We are in the early stages of planning a design using the C5165 SOM in a product that will be using a larger display that is likely to have an LVDS interface. We have identified two candidate translators to go from DSI to LVDS - the TI SN65DSI84 and the Lattice CrossLink LIF-MD6000. The TI chip requires I2C configuration on every boot, so we are concerned that it could pose a barrier to presenting content on the display shortly after power-on (i.e., splash screen). The LIF-MD6000 is a non-volatile FPGA based solution that would circumvent that concern, but costs more. If we can be assured that the QRB5165 will boot to the point of being able to configure the TI chip (presumably within the kernel?) in a timely manner, then we would be comfortable designing for the TI chip. So a few questions:
- How much time does it take in the QRB5165 boot process before a splash screen can be presented on the display? Where in the boot process can this first occur?
- How much time does it take in the QRB5165 boot process before peripheral drivers are loaded in the kernel?
- Alternatively, is there any possibility of incorporating custom I2C accesses into the boot loaders?
- Is there any known prior experience using a non-DSI display with the QRB5165 that could be informative?
Thanks in advance.
Hi trothlisberger,
Our team is reviewing the query and will get back to you soon!
Thanks for waiting!
Mita
Hi trothlisberger,
With respect to first 3 quesries will need boot up logs , please connect the uart and capture boot up logs
Thanks
Hi Trothlisberger
In regards to query 3) and 4) , please check comments
3)Alternatively, is there any possibility of incorporating custom I2C accesses into the boot loaders?
Ans : Yes, we can do some I2C config on the xbl display side
4)Is there any known prior experience using a non-DSI display with the QRB5165 that could be informative?
Ans:We used MIPI -> HDMI IC like lt9611, not used MIPI-LVDS IC before, lt9611 also need configured by I2C
Thanks,
Mita
Hi Mita,
Thank you for the answers. Sorry for my slow response. We didn't have an RB5 when I first posted this but received one a couple days ago and I was hoping to get an answer by observation, but it won't turn on. I'm working on that through a separate channel.
Can you provide some more information on what we would need to do to customize the boot loader to include the I2C configuration of the bridge chip? Thanks.
Hi Mita,
I'm still looking for information on what is required to add the I2C configuration to the bootloader. Please advise where I can find more information on that. Thanks.
Hi trothlisberger,
Bootloader source code is not open to custoemr, hence can not be modify from customer side. To get further support please reach out to our sales team [email protected]
Thanks,
Mita