2014-03-31 08:47 AM
I have a project, developed by Segger, for the STM32F429i-Disco board. I have the project working, and wanted to replace the trial emWin files that Segger uses with the STemWin files ST provides. When I swap out the Segger binary library with the STemWin binary library, the micro goes into the GUI_Init function, and never comes out. Anyone out there run into this? Any recommendations on how to understand what it is that's creating this situation? All insight appreciated.
#stemwin #stm32f429i-discovery2014-03-31 10:09 AM
Add
/* Enable CRC clock */ RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_CRC, ENABLE); Prior to calling the function. [DEAD LINK /public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/STemWin%20GUI_Init%28%29%20crashed&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=762]https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2Fcortex_mx_stm32%2FSTemWin%20GUI_Init%28%29%20crashed&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=7622014-03-31 10:56 AM
That was it! I''m assuming that call was in the Segger version of GUI_Init?
2014-03-31 11:08 AM
No, rather there is a test in the ST licensed release that ties it to STM32 hardware.