I believe you are referring to this Code Example - GitHub - cypresssemiconductorco/mtb-example-psoc6-emwin-oled-freertos: This code example demonstrates displaying 2D grap…
Please correct me if I am wrong.
The code example uses an SSD1306 OLED display which is interfaced using I2C.
You do not see the pins enabled in Device Configurator because the pins/peripherals are initialized using Hardware Abstraction Layer (HAL) APIs which do not require Device Configurator. The pins are mentioned in the code itself. You can find the initialization code for the I2C peripheral and the display in oledTask.c
You can learn more about HAL drivers in this training - Session 2: Introduction to Digital Peripherals in ModusToolbox
You can also refer the discussions on these threads -
Hope this helps,
Thanks and Regards,
Rakshith M B
Rakshith, thank you for your reply.
I am looking at the PSoC6 WiFi-BT Pioneer Kit, part number CY8CKIT-062-WiFi-BT. I figured that the example code was going to match the TFT display included with the kit. It is based on the ST7789V display controller. The schematic for the LCD shows a parallel interface (4 control lines plus 8 data lines). I'll look for example code that communicates with the TFT Shield included with the kit.
Thank you again for your help. I'm digging through the projects you created in the other thread to understand how the libraries work in MTB. It may take a few days for me to get through it.
I thought I'd follow up to keep track of my own progress. Baby steps.
I was able to build the project today by using these steps:
- Switch the active BSP to CY8CKIT-062-WIFI-BT. That had the side-effect of removing the CY8CKIT-028-TFT and motion sensor libraries from the project. I figured that was ok because the mtb_st7789 library was still present. It is good that the CY8CKIT-028-TFT library was removed by the library manager because the library has support for other devices that are on the TFT shield that are not present on my breadboard.
- Remove the CY8CKIT-028-TFT include file from main.c.
- Hardcode the pin definitions in main.c to match my hardware setup as below.
After that, the project builds.
Next, I need to investigate whether port 8 is working as expected after the mtb_st7789v init code runs. I am using port 8 for TFT control signals and am concerned that port 8 is configured for capsense. If I don't find out what code is initializing the capsense pins quickly, I'll hook a scope up and try stepping through the TFT init code to see if the pins working as expected. If so, then it's time to hook up the TFT, check for smoke and step through the initialization to see if emWin can bring up the display.