Peslap

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: VisualGDB on Visual studio 2013 #6452
    Peslap
    Participant

    see http://visualgdb.com/download/

    System Requirements

    Microsoft Windows (incl. x64) 8.1/8/7/2008/Vista/2003/XP
    Visual Studio 2015, 2013, 2012, 2010, 2008 or 2005
    If you don’t have Visual Studio, try the free VS Community Edition

     

    in reply to: STM32CubeMx Project with VisualGDB? #6451
    Peslap
    Participant

    From the Visual Studio Project I excluded all files from Appdata/../com.sysprogs.arm.stm32/…
    except <AppData>\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\STM32F4xxxx-HAL\startup_stm32f4xx.c

    The Keil compiler use C99. For gcc append  –std=c99 in VDGB Property, Makefile settings, CFLAGS.

    So I can develop & debug in Visual Studio & Resharper C++ & VisualGDB, which is more comfortable as the Keil IDE.
    The release I build with the Keil compiler. A project based on the  CubeMX UDP_Echo_Server  result in FLASH size ( release build, in Keil -O3:)
    gcc: 70 kB: .text=66kB .data=3048
    Keil V5.04: Program Size: Code=34172 RO-data=732 RW-data=964 ZI-data=28060

     

    in reply to: STM32CubeMx Project with VisualGDB? #6446
    Peslap
    Participant

    Now it works:

    in the debug.mak I add  all the above includes (replaced “-I..\” by “”) after after INCLUDE_DIRS :=.

    Add all c files to the solution. There is an conflict between the hal files in the Project (copied by CubeMX) and the files in folder Appdata/../com.sysprogs.arm.stm32/… So I removed this hal files from the project.

    That’s all 🙂

    in reply to: STM32CubeMx Project with VisualGDB? #6445
    Peslap
    Participant

    This is not a legacy ARM device. It is a STM32F4 which is directly supported from VDGB.

    It would be very useful if there is an option to import a Keil Project.

    Lagacy tutorial :

    Where should I find some Compiler flags? Is it the ‘Compiler Control String’ from the Target Options Dialog, Tab C/C++? It is:

    -c –cpu Cortex-M4 -D__MICROLIB -g -O0 –apcs=interwork –split_sections -I..\Inc -I..\User -I..\Drivers\STM32F4xx_HAL_Driver\Inc -I..\Drivers\STM32F4xx_HAL_Driver\Inc\Legacy -I..\Drivers\CMSIS\Include -I..\Drivers\CMSIS\Device\ST\STM32F4xx\Include -I..\Middlewares\Third_Party\LwIP\system -I..\Middlewares\Third_Party\LwIP\src\include -I..\Middlewares\Third_Party\LwIP\src\include\ipv4 -I..\Middlewares\Third_Party\LwIP\system\arch -I..\Middlewares\Third_Party\LwIP\src\include\ipv4\lwip -I..\Middlewares\Third_Party\LwIP\src\include\lwip -I..\Middlewares\Third_Party\LwIP\src\include\netif -I..\Middlewares\Third_Party\LwIP\src\include\posix -I..\Middlewares\Third_Party\LwIP\src\include\posix\sys -I..\Middlewares\Third_Party\LwIP\src\netif\ppp –C99
    -I..\MDK-ARM\RTE -I C:\Keil_v5\ARM\PACK\Keil\STM32F4xx_DFP\2.3.0\Drivers\CMSIS\Device\ST\STM32F4xx\Include
    -I C:\Keil_v5\ARM\CMSIS\Include
    -DSTM32F407xx -DUSE_HAL_DRIVER -o “E407 Configuration\*.o” –omf_browse “E407 Configuration\*.crf” –depend “E407 Configuration\*.d”

     

     

Viewing 4 posts - 1 through 4 (of 4 total)