Hi NXP.
I would like to use the LCD for Raspberry Pi with GUI Guider1.81, MIMRT1170-EVKB, and the RASPI_7INCH option.
However, at the moment, even if I write the GUI Guider sample project, it does not work properly and the screen remains black.
The project on the site below has a working RaspberryPi LCD (probably a project created with GUI Guider).
https://github.com/nxp-appcodehub/dm-lvgl_cluster_rt1170_evkb_rpi
After checking the differences and porting the necessary parts of the source code from github above to the source code output by GUI Guider,
I was able to display the LCD screen.
-Ported display_support.c
--left Github src / right gui guider output src
--I guess GPIO control via PCA6416 IO expander is required
-Ported pca6416.c/h, pca9530.c/h, rpi.c/h
-Ported the contents of the talk_to_raspi() function from lvgl_guider.c to rpi.c
--github src lvgl_guider.c
-- I think this initialization function is necessary,
but I think it would be better to have it in rpi.c/fsl_rpi.c rather than lvgl_guider.c where the main function is located.
-Deleted fsl_rpi.c/h
However, this is an inconvenient situation,
so I hope that they will fix it so that RASPI_7INCH can run as is with the source code output by GUI Guider.
Hi zongchunyu.
I shared a project I created with GUI Guider 1.81.
It has been split due to file size limitations.
This project simply loaded a sample program with the default settings,
without any special customization.
This project can be build and written to the board successfully using GUI Guider.
However,the display remains black and nothing can be displayed.
Similarly, the project can be build and written to the board successfully using MCU Xpresso.
However, the display remains black and nothing can be displayed.
The hardware and connections for the Raspberry Pi Display conform to the sample below,
and are working properly.
https://github.com/nxp-appcodehub/dm-lvgl_cluster_rt1170_evkb_rpi
This is not the case in my environment,
but does this mean that the source code output by GUI Guider 1.81 will work properly as is?
Best Regards.
Hi zongchunyu.
Thanks for testing. I did some testing and identified the cause.
In the source code output from GUIGuider,
I could see that the I2C communication was stuck at a certain point.
It is repeating reading 0x82 to 0x10 of device 0x45 forever.
This is the POWERON wait part of fsl_rpi.c.
Indeed, this code will not proceed to the next step unless 0x*1 is read.
I tried commenting out this section and the display worked fine.
I don't have detailed information about the display,
but I think that the GUI Guider team's display and my display are probably different types, revisions, etc.
If possible, I would be happy if the code output by the tool can run on my own display without any modifications.
For reference, I have posted a photo of the display I have.
