Hello
I'm trying to communicate with a ST7701 display controller.
Are some examples available? Can anyone share if possible?
I'm using an i.MX RT1170 board. In the SDK examples I found the drivers for the HX8394, RM68191 and RM68200 display controllers. I would like to find something similar for ST7701.
Can anyone help me please?
Thank you and kind regards,
Francesco Solito
Hi @SolitoFrancesco,
At the moment, we don't have any driver support in our SDKs for the ST7701 display controller. The integration with this controller would have to be done manually.
Good morning
I modified the files you mentioned, following the indications that I received from the display manufacturer and from the driver manufacturer. I'm able to write and read into the driver registers through MIPI. I can see the differential MIPI waveforms with oscilloscope (also after the "configuration" phase), but I'm still not able to see anything on the display. I'm using the demo example from NXP SDK called "mipi_dsi_compiance_test".
Can you please try to help more?
Thank you and kind regards,
Francesco Solito
Hi @SolitoFrancesco,
Have you been able to debug your code while running? Do you see any error message being printed? And what data patterns do you see on the data line? Do these patterns coincide with the expected ones described on the readme.md file?
BR,
Edwin.
Hello,
I have the same situation (same driver and resolution, and the base is a test example that worked on the devboard). The controller is configured, and I can also read the statuses (without any errors), and the data on the DSI lines is present, but the screen displays nothing.
Changing the videoMode in dsi_dpi_config from kDSI_DpiBurst to other modes also has no effect.
It looks like the screen isn't accepting the video stream?
Hello Francesco,
I managed to get the display working.
In the DisplayTFT_SetMipiDsiConfig function, add the line:
dsiConfig.enableNonContinuousHsClk = true;
for example, after these lines:
DSI_GetDefaultConfig(&dsiConfig);
dsiConfig.numLanes = DISPLAY_MIPI_DSI_LANE_NUM;
dsiConfig.autoInsertEoTp = true;
Assuming you have the display IC configured correctly (if necessary, I can share the configuration for my screen) and the display clock (my settings are around 26MHz).
Best regards, Chris
Hello,
the file was created based on other drivers in the SDK.
You can still change the delays to shorter ones.
This morning, I confirmed the configuration sequence and made a few changes as recommended by the display manufacturer, but there was no further improvement, so I started taking a closer look at the DSI configuration itself. I know the clocks were fine, and so was the video mode (burst mode), so the only options left were those for the DSI itself.
Familiarizing myself with (and other parts in docs):
https://docs.nxp.com/bundle/AN13573/page/topics/continuous_vs_non-continuous_clock.html
BR, Chris
Hello Rino
As promised, please find in attachment the settings comparison between yours and mine. I didn't go in details, but if me or you will find something interesting in the differences, please let's continue to write here.
Kind regards,
Francesco
Hello Francesco,
Sorry for the delay.
I looked through your comparison and noticed a lot of differences, partly due to the screens themselves (we have a glass/touch/screen sandwich, and there was a configuration fix for that – or at least that's what the supplier explained
Some settings, like power control, aren't required for startup, but for quality improvement (contrast/gamma settings).
And what's funny is that the whole "Sunlight Readable Enhancement" thing, I think they called it, is required, regardless of whether we're running it or not. Based on this data, it automatically sets optimal parameters. If they're incorrect or missing (default values), it takes a while to automatically set them -> hence the slow startup, as you've noticed.
The documentation itself can be quite irritating, many of the commands are undocumented, and without them, it's often impossible to fully start the screen. This isn't just with this model, I've encountered this with several other Sitronix models.
Kind regards,
Chris