I think it was because in my video tutorial I selected the NX Graphics.
CONFIG_NX_LCDDRIVER" from stm32_ssd1306.c.
I will submit a new patch to fix it.
Post by ***@yahoo.com [nuttx]
That is not true.
There are two (mostly) independent configuration settings
./drivers/lcd/Kconfig: select NX_UPDATE if NX
./graphics/vnc/server/Kconfig: select NX_UPDATE
CONFIG_LCD_UPDATE is the only one that matters. CONFIG_NX_UPDATE is only
for backward compatibility.
Notice that if CONFIG_ NX enabled, they are kept in lock step. However, if
CONFIG_NX is not enabled, the CONFIG_LCD_UPDATE can be enabled or disabled
independently without :CONFIG_NX being enabled.
There are several configurations that do this. There are several
configurations using the framebuffer driver and none of them set NX (except
Of those, only configs/stm3240g-eval/fb uses CONFIG_LCD_FRAMEBUFFEr
$ find configs -name fb | xargs grep -r CONFIG_LCD_FRAMEBUFFER
NOTE that CONFIG_NX is not set and CONFIG_NX_UPDATE is not set.
CONFIG_LCD_UPDATE is not set in the configuration either, but that is
because it is the default when CONFIG_LCD_FRAMEBUFFER=y; it will reappear
when the configuration is refreshed.
33 config LCD_FRAMEBUFFER
34 bool "LCD framebuffer front end"
35 default n
36 select LCD_UPDATE