Potential bug when importing STMCubeMX projects

Sysprogs forums › Forums › VisualGDB › Potential bug when importing STMCubeMX projects

Tagged: 

Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • September 27, 2019 at 15:37 #25941
    MrZANE
    Participant

    Hi.

    After importing an STL32l4xx project created in STM32CubeMX I get an error when compiling.

    Severity Code Description
    Error C:/work/<projectpath>/Drivers/CMSIS/Device/ST/STM32L4xx/Source/Templates/system_stm32l4xx.c: No such file or directory

    This seems to be because the file system_stm32l4xx.c was added to the project with the wrong path settings.
    The file accualy exists in <projectpath>\Core\Src

     

    I don’t know the function of the stm32.xml but the same error is in there for system_stm32l4xx.c

     

    Sw. versions:
    Visual GDB 5.4R12 (Build 3242)
    STM Devices 2019.06
    Visual studio 2017 15.9.16
    STM32CubeMX 5.3

    Thanks in advance..

     

    Ps. Edited for clarity and to remove customer name etc.

     

    • This topic was modified 5 years, 1 month ago by MrZANE.
    • This topic was modified 5 years, 1 month ago by MrZANE.
    September 27, 2019 at 21:10 #25946
    support
    Keymaster

    Hi,

    Sorry, unfortunately the recent versions of STM32CubeMX are somewhat buggy and often include incorrect paths in the generated GPDSC files.

    VisualGDB works around the known instances of this, but it looks like you have discovered another one. If you could reproduce it on a freshly created STM32CubeMX project and share it with us (along with the generated GPDSC file), we should be able to add a workaround rule.

    If the problem is specific to a project that cannot be shared, please consider cloning our STM32CubeMX importing plugin from Github and adding logic similar to the ApplyFreeRTOSFixes() method that works around known STM32CubeMX bugs.

  • Author
    Posts
Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.