juppeck

I had seen that some vector rotations are implemented now - just a few years later. Sometimes it's just need time, not more. :-) In this time, i had never tested µGFX on an STM32F7 plateform, but i had seen some nice presetation videos on youtube.

In emBitz you can point to an discret installed arm-toolchain. You are not limited to the included arm toolchain. It's very easy to switch between them.

Tectu: Yepp, i had used this Display in combination with Keil RTX and emWIN 5.24h and a STM32F4Discovery board. I had finaly used a PCB as an Adapter board to get the wires short and the length of the equal as possible. All this makes i possible the FSMC-Timing as fast as possible. The Limits of the SSD1963 seems to be quite close. I had noticed, that the design of the TFT-Displays Controller board; especially the routing layout, seems to be available in different qualities. I payed less the $60.- for a 5" Touchpanel with 800x480 Pixel Resolution with Controllers for TFT (SSD1963), a resistiv touch controller and an on-board SD-CARD Slot and finaly the voltage Generation and a backlight regulator that can be switched between PWM, continiously on and just ON/OFF by a port-pin. The Panel Looks great, but the Setup of the SSD1963 Register was difficult at start time. The Touchpanel seems to be in poor Quality. I use a Stylus and get a couple of different positions that's not quite near at the touch point. It looks like a starfield instead a point. I sample actually 16 times and sort them to find out the real touched Position. It's just a cheap touch panel. If i will use them laster - well, i am unsure. I will taste the Gfx Lib at the Weekend. I did'nt found a function that place and move a polygone by just an angle. This is very helpful if you wanna move the pointers of a watch or analoge messuring device.

Hello, i would like to add some lines to the FSMC and Display connectivity. At first, i wondering why the GCC Compiler is prefered to use in combination of the worst IDE like "Eclipse" and their commons. To get the IDE works with the JTAG and the Environment Setup is done, a couple of hours could be passed. For a beginner in Cortex-M programming, the homogene IDE like µVision from Keil make the start easier. The next Point, same reason is the use of the CMSIS-Library and Std-Library instead Manipulation the bits directy. You must beware about the huge amount of available Registers and their names. A good example that demonstrate what i mean is the FSMC init Structure that Needs to be filled with valid Parameters. Every Screw thats required to be turn should be self described by a regular name. This example do a part of the FSMC Setup by using a structure to map the FSMC lines. Looks very understandable, or not ? GPIO_PinAFConfig ( GPIOD, GPIO_PinSource9, GPIO_AF_FSMC ); // D14 // GPIO-PortD Pin9 will used as FSMC GPIO_PinAFConfig ( GPIOD, GPIO_PinSource10, GPIO_AF_FSMC ); // D15 GPIO_PinAFConfig ( GPIOD, GPIO_PinSource11, GPIO_AF_FSMC ); // A16 // use Address A16 as /RS of Display GPIO_PinAFConfig ( GPIOD, GPIO_PinSource14, GPIO_AF_FSMC ); // D0 GPIO_PinAFConfig ( GPIOD, GPIO_PinSource15, GPIO_AF_FSMC ); // D1 GPIO_InitStructure.GPIO_Pin = GPIO_Pin_0 | GPIO_Pin_1 | GPIO_Pin_4 | GPIO_Pin_5 | GPIO_Pin_7 | GPIO_Pin_8 | GPIO_Pin_9 |GPIO_Pin_10 | GPIO_Pin_11 | GPIO_Pin_14 | GPIO_Pin_15; // i will use this PortPins to setup GPIO_InitStructure.GPIO_Mode = GPIO_Mode_AF; // use the alterative pin function GPIO_InitStructure.GPIO_Speed = GPIO_Speed_100MHz; // 100Mhz Clock of I/O Flip-Flop GPIO_InitStructure.GPIO_OType = GPIO_OType_PP; // I/O Output will be Push-Pulled GPIO_InitStructure.GPIO_PuPd = GPIO_PuPd_NOPULL; // no Pull-up or Pull-Down Resistor used GPIO_Init ( GPIOD , &GPIO_InitStructure ); // and finaly i will init the GPIO-Port D with my setup structure. i don't understand why many programmers prefere to use the old school bit names and their maniplation like this: FSMC_Bank1->BTCR[FSMC_Bank + 1] = (FSMC_BTR1_ADDSET_2 | FSMC_BTR1_ADDSET_1) | (FSMC_BTR1_DATAST_2 | FSMC_BTR1_DATAST_1) | FSMC_BTR1_BUSTURN_0; Is line this understandable without a Manual, that further describe the register Function and bit Position. Understand me right - there is nothing wrong to do like this - the final result of the preprocessor of both methodes looks equal. The code result would be similar because both are just preprocessor definitions and declarations. So, it's easier to understand what you had programmed and finaly set, if the CMSIS Lib is used instead direct bit Manipulation.

I guess that he want to know somting about the tuning issues of an SSD1963 driven TFT Display, that's linked to an STM32Fxxx MPU by the external system bus Interface called FSMC (Flexible Static Memory Controller). The 8 Frames per Second are not the fast possible value. How this can be raised was the question. Well, my experiences with the 5" Type of this kinda TFT/SSD1963 with 800x480 Pixel Resolution works nice with about 28 FPS in combination with emWIN-5.24.2, an STM32F4-Discovery board. The main Problem is, that the Controller SSD1963 maps just one Register into the mpu address range instead direct access to the displays data memory. I never taste the functionality to move the Memory to Register copy by using the STM's DMA. This should gives the Display Output more performance, but Needs more Attention and custom driver design for every different MPU and Display variants. It's near impossible to done a common usage of code for different MPU and Display variants.