I am trying to put it all together, because I am not using the STM32F429i-disco with integrated TFT-LCD. But a ILI9431
Here I could find the Memory regions (also FMC and 3 memory regions [if I get it right...]) https://www.st.com/content/ccc/resource/technical/document/application_note/group0/25/ca/f9/b4/ae/fc/4e/1e/DM00287603/files/DM00287603.pdf/jcr:content/translations/en.DM00287603.pdf And this is my datasheet for the ILI9341 and its a QVGA (320 x 240) https://cdn-shop.adafruit.com/datasheets/ILI9341.pdf The display: https://www.ebay.com/itm/3-2-inch-LCD-TFT-With-Resistive-Touch-Screen-ILI9341-Display-Module-320-240-/183001025101 When the memory regions are not correct defined I do get that I get hardfaults... but I am struggling with these definitions. CONFIG_STM32_DMA2D_FB_BASE=0xD07B5000 CONFIG_STM32_DMA2D_FB_SIZE=150000 CONFIG_STM32_DMA2D_LAYER_PPLINE=240 CONFIG_STM32_DMA2D_NLAYERS=2 CONFIG_STM32_LTDC=y CONFIG_STM32_LTDC_FB_BASE=0xD076A000 CONFIG_STM32_LTDC_FB_SIZE=150000 CONFIG_HEAP2_BASE=0xD0000000 CONFIG_HEAP2_SIZE=150000 Op wo 1 jan. 2020 om 19:29 schreef Gregory Nutt <spudan...@gmail.com>: > Does that hardware support color mapping? Normally that is used with > 8-bit palette colors like old fashioned computers from the 80's. You > probably don't want it. > > On 1/1/2020 11:56 AM, Disruptive Solutions wrote: > > I am close, but looking in a loop? > > > > In ili9341_getvideoinfo the vinfo struct is filled correctly? > > fmt = 11 > > xres = 320 > > yres = 240 > > nplanes = 1 > > noverlays = 0 > > > > Is seems that the colormap is setting some problems in nxbe_colormap.c > > (lcd.h) > > /* Then set the color map */ > > > > ret = dev->putcmap(dev, &cmap); > > > > Disabling the colormap config (CONFIG_STM32_FB_CMAP) it gives a white > > screen (no text "Hello World"), but no hardfault... and if I start > nxhello > > for the second time I get: > > stm32_spi2select: devid: 262144 CS: assert > > > > stm32_ili93414ws_sendcmd: cmd=0029 > > > > stm32_spi2select: devid: 262144 CS: de-assert > > > > ili9341_getvideoinfo: fmt: 11 xres: 320 yres: 240 nplanes: 1 > > > > ili9341_getplaneinfo: planeno: 0 bpp: 16 > > > > > > * and if I start nxhello for the second time I get: * > > > > nsh> nxhello > > > > nxhello_initialize: nx_connect failed: 28 > > > > nxhello_main: NX handle=0 > > > > nxhello_main: Failed to get NX handle: 28 > > > > nsh> > > > > Somebody has an idea? > > > > Op wo 1 jan. 2020 om 13:06 schreef spudaneco <spudan...@gmail.com>: > > > >> Sent from Samsung tablet. > >> It seems strange that by not selecting CONFIG_NX_KBD it stil is trying > >> tocompile stuff that has relations with this > >> config?src/cnxwidget.cxx:691:65: error: 'class > NXWidgets::CWidgetControl' > >> has nomember named 'doubleClick' if (m_flags.doubleClickable && > >> hasFocus() &&m_widgetControl->doubleClick())DoubleClick has nothing to > do > >> with the ketboard. That is mouse codeAnd other problems. It seems I > have > >> to make changes in the NX side of Nuttxto get this going..?I don't > >> understand that. > > >
