Search Results

Hi, Just found the new STM32F3xx CPU support package will generate an incorrect memory map of the chip. When I select STM32F334R8 as the target, the auto generated example "Hello world" code will always cause a hard fault when debugging on hardware but runs fine in simulation. I finally found out it's the STM32F334R8Tx_MemoryMap.xml file doesn't give a correct memory map. It has the content: Source Code (5 lines) while an old project created by an older version of SES has the STM32F334R_MemoryMa…

Hi guys, Thanks for viewing. I've found the problem and solved the problem. Hope this could also help you. The reason for what was happening is emWin need the calibration function to be called before you can use the touch screen, even if you still don't have the calibration data! Segger never mentioned this in the manual and I thought I would run the calibrate code to get the values for the calibration and then add the calibration to the code, but the truth is if you don't call the GUI_TOUCH_Cal…

Hi I'm using STemWin 5.22, got stuck at the touch driver. It's a 3.2" LCD with analog touch screen, the touch screen controller is XPT2046. I've already written the 4 hardware routines GUI_TOUCH_X_ActivateX(), GUI_TOUCH_X_ActivateY(), GUI_TOUCH_X_MeasureX(), and GUI_TOUCH_X_MeasureY(), and I've called the GUI_TOUCH_Exec() every 10ms from an interrupt. When I tried to run the TOUCH_Calibrate.c in the Win32 simulator's /sample/tutorial folder, the code was stuck at the welcome screen because it co…