I am about to purchase a PRO edition of embedded wizard.
I have set up my custom board correctly and Hello World example is working partially.
When i run from atollic studio / STM32CUBEIDE debug mode, the touch handler runs, when programming the Hex directly this does not,
The touch handler does work in both situation where i build the Charts Demo.
My problem is the following:
I think i do not have correct functionality of my target specific graphics part because of the following situation:
The lines chart is also corrupt, the dots show correctly, but the dynamic non rectangle parts will fail.
maybe its caused by SDRAM? or any suggestions please,
when everything works smooth i will be ready to purchase the PRO edition!
Thank you in advance!
looking at some other screen tearing question on this website:https://ask.embedded-wizard.de/4660/flickering-while-using-doublebuffering?show=4663#c4663
i get 43 frames but no tearing, if i make this 60 frames it will solve the tearing problem?
How do i make this 60 frames..?
Tearing only happens when glyps or dynamic elements are changing, after touch events
Also when i am using the screenOrientation example, the bouncing balls will cause tearing, and
very noticable that the tearing have red and green colors, maybe i need to make seperate layers for these?
Dear Manfred, The custom board i am working with originated from an STM32-F756-EVAL, it has adapted to go from 640x480 screen to 800x480 screen.Is there a way of instead decreasing memory bus load, to increase memory bus bandwidth? different STM32 MCU?currently using STM32F767BI
i see the my SDRAM size is set to 8MB, instead of 256MB. 256MB is not working, maybe this can help this issue, how can i get the 256MB size working? the chip is the same as on the EVAL board, which is 256MB.
i am trying your suggestion on https://ask.embedded-wizard.de/2474/sdram-memory-test
the program crash at attempt of 64MB, 32MB works. but not 256MB. it does not give 'Error at Adress' but goes into 'HardFault_Handler'.
i think maybe the screen flikker could be related also to the 25FPS, that is low enough to be able to see changes in the LCD maybe?
Yes. at 60FPS there is screen tearing on movement, but no flikkering.
concerning the flickering/tearing effects, let me refer to this question/answer - there you will find a simple test application that is useful to detect flickering/tearing effects. Let me know the results.
Of course, you can use a framebuffer with color format RGB565 and a display that is connected with 6 or 8 bits per color channel (= 18 bits or 24 bits RGB). The LTDC of the STM32 hardware is able to convert the color accordingly.
Concerning the memory test: Please make sure that the MPU settings are adapted to match the start address and size of your SDRAM.
Btw: Is your SDRAM connected with 16bit or with 32 bit? This has a big impact to the available memory bandwidth.
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!