Hi Dialog Team,
SDK10.0.10.118
I am using emWin sample to as a base and adding a new SPI-4wire AMOLED display module and a I2C touch support,
//www.xmece.com/products/connectivity/bluetooth-low-energy/smartbond-reference-designs/emwin
By tracing lcdc adapter, and sample of DT280QV10CT, it seems even example are SPI LCD, I saw the phy type of DT280QV10CT is HW_LCDC_PHY_MIPI_SPI4.
However init command are all still LCDC_MIPI_CMD(xx), does it mean LCDC_MIPI_CMD are working with SPI interface display module?
I am a little cofused with LCDC_MIPI_CMD, becasue the real interface for those display should be SPI, right?
Are we able to use LCDC_MIPI_CMD directly or we need to implement a LCDC_SPI_CMD to suuport SPI interface display module? Thank you in advance.
Hi jerryjuan,
Thanks for posting on our public BLE forum. Please let me check this and I’ll get back to you.
Thanks, PM_Dialog
Hi jerryjuan,
We have taken this offline from the forum and will reach out to you directly.
Thanks, PM_Dialog
I didn't get response for now, could you help to let me know if any update?
Hi jerryjuan,
Thanks for the update. Let me check this again and let you know.
Thanks, PM_Dialog
Hi Dialog team,
Could you help to cofirm and reply it?
Why it used LCDC_MIPI_CMD, even interface is SPI4?
Hi jerryjuan,
The official terminology for the SPI3/4 is MIPI Type-C. The MIPI is referred to all the serial interfaces. Please check ad_lcdc_driver_conf_t – the HW is configured as HW_LCDC_PHY_MIPI_SPI4 . The SDK supports different macros for sending data and commands, that is, LCDC_MIPI_CMD , LCDC_MIPI_DATA (located in ad_lcdc.h file). From the LLD point of view, check the hw_lcdc_mipi_cmd API (located in hw_lcdc.h).
Thanks, PM_Dialog