TF55001A-V0 Display for DragonBoard 410C



We have a DragonBoard 410C, and would like to combine it with a TF55001A-V0 display (with a Raydium RM69071 driver ic) and we are wondering if this is possible.

Our electrical engineers have developed a pcb to convert the 60-pin mipi-dsi to the correct 40-pin mipi-dsi, but we can’t find corresponding files as mentioned in the display porting guide.

Any help would be much appreciated!


Hi @DLeijen

The first question is “Which Operating system are you using?” Android, Linux. or Win10?

Full disclosure: I am an employee of Qualcomm Canada, any opinions I may have expressed in this or any other post may not reflect the opinions of my employer.


Hey @ljking,

Sorry for the late reply, busy weekend.

Preference would be android, so our app developer can handle software side of the DragonBoard, but linux would also be fine for us.

End goal is to have our own pcb, which can be powered by supercaps to play locally cached video for at least 3 minutes before needing to be charged again, meaning we have a 5V 0.7mA power budget. If OS has major impact on the power usage, we would like to know that too.


Is there anybody else with a suggestion how to use either this display or another display that works with the DragonBoard 410C, is fullHD, amoled, and connected through mipi-DSI?


Attaching any display to any of the 96Boards is a two part problem:

  1. The first part of the problem is the electrical connections. The MIPI-DSI standard describes the electrical signals that flow between the host SOC (the APQ8016 in this case) and the display controller chip (The RM69071 chip in the display module in this case). The MIPI-DSI standard does not specify a ‘standard’ physical connector for MIPI-DSI displays, in fact you will find that every model of display has a different physical connector, and a different pin-out order. The 96Boards standard does specify a standard connector for the MIPI-DSI signals and all of the compliant 96Boards products will match this connector and pin-out (the High-Speed connector on the board). In order to use a specific display module you will need to create a custom mezzanine PCB that has the correct mating connectors and electrical connections.

  2. The second part of the problem is the software drivers for the panel. Even this part of the problem has two sub-problems, the first is the driver for the display, and the second is the driver for the touch screen controller.
    2a) The display driver must set up the MIPI-DSI display controller in the SOC with the correct timing and data formats. For the 410c there is an app note that will help you get started. You also need to initialize the display controller on the display module to accept the timing signals and to drive OLED array. We do publish some guidelines on how to set-up the display controller for Android in the Application Note: Some display controllers are initialized over I2C, ad some are initialized over the MIPI-DSI virtual command channel.Setting up the controller on the display module is different for each controller and OLED matrix, you will need to get documentation form the display module manufacturer, and the display controller manufacturer to determine how the program the controller.
    2b) The Touchscreen controller usually communicates with the host SOC over I2C, however I have seen some that communicate over SPI. Again you will need datasheets and programming guides for the touch screen controller manufacturer in order to set this up.

Without a PCB or the programming guides for the display, display controller, and the touch screen controller we will not be able to give you much more help than this. Hopefully this post will give you some guidance on what information you need and what you need to do to interface the display module with the 410c.

Full disclosure: I am an employee of Qualcomm Canada, any opinions I may have expressed in this or any other post may not reflect the opinions of my employer.