Joel Bodenmann

Hello David, Can you please give some more information about what your troubles are and what you already tried to do? ~ Tectu

Yes, that for sure, I also meant that you won't notice any visible color quality differences ~ Tectu

Well, it can be done with GPIO without any problem. Since he uses ChibiOS/RT it's fairly easy because it offers to build a bus structure out of several GPIO pins. However, I don't really see the reason to use this display in 18- instead of 16-bit mode too. I don't think that you'll notice any difference at all. ~ Tectu

Because the FSMC has per definition only a 16-bit data width. You'd have to bitbang your stuff using GPIO then. @ mobyfab: There are an awful lot of people having issues with the SSD1963 driver. Can you confirm that the driver itself is fine the way it is and that it's only a problem with the panel configuration? We have to find a solution for this. Maybe some more documentation will help there. ~ Tectu

One more issue fixed - excellent! I will try to come up with a better solution for custom initialization routines. When you want to use your display in 18-bit mode, you have to create a copy of the driver and modify it that it matches the 18-bit stuff. The current SSD1963 driver runs in RGB565 format. You have to make sure that you handle all the colors and data writing correctly inside the driver. You will also have to redefine the color_t type since it's a uint16_t by default. ~ Tectu

Hello David, Just leave it blank so your line would look like this: palSetPadMode(GPIOB, 12, PAL_MODE_OUTPUT_PUSHPULL Why exactly are you modifying the SPI config registers in your SPI struct? I cannot remember the default values provided by ChibiOS/RT but experience says that it will work for 99% sure if you leave it as it is. Just set a higher prescaler to be sure that your LCD controller can handle it. I know that distributors often write «SPI Freq = 10MHz» in their example codes but those are very often just copied and copied and copied and copied so the comments are not up to date. static const SPIConfig spi2cfg1 = { NULL, /* HW dependent part.*/ GPIOB, 12, SPI_CR1_BR_2 | SPI_CR1_BR_1 }; Furthermore I can see that you seem to directly access your registers in the board file. Why do you do this? I advice you to do everything through the SPI driver provided by the ChibiOS/RT HAL because the spiSend() command already handles the busy flag and so on. One more thing: How long are your wires? ~ Tectu

Good to hear that you got it working. The multicolor lines indicate that this part of the screen was not initialized properly. Please check your initialization code to make sure that the entire area gets initialized. ~ Tectu