Standalone project no BSP

Sysprogs forums › Forums › VisualGDB › Standalone project no BSP

Tagged: 

Log In Register Lost Password
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • July 18, 2017 at 22:34 #11750
    sidprice
    Participant

    I need to produce a project for STM32F411RE that does not use the ST HAL BSP. It just needs to have the startup code and vectors. Is there an easy way to do this?

    Sid

    July 19, 2017 at 05:05 #11754
    support
    Keymaster

    Hi,

    Normally, you can just remove the reference to “STM32 HAL” via the Embedded Frameworks page. This should leave the startup code, vectors and the linker script (you would need to change the main source file).

    July 19, 2017 at 17:07 #11762
    sidprice
    Participant

    Thank you, that almost got me there.

    The remaining issue is that Intellisense is still looking in the BSP for header files. The compiler does not and it follows the include file directories I have entered, however Intellisense does not. If I right click on an include file line to open that file the IDE opens the file in the BSP.

    How can I force Intellisense to reparse my project?

    Sid

    July 20, 2017 at 02:00 #11771
    support
    Keymaster

    Hi,

    The answer depends whether you are using GNU Make or MSBuild. Normally VisualGDB should update the include paths automatically. Perhaps they have been removed and then re-discovered by the automatic header discovery feature?

    July 21, 2017 at 17:36 #11781
    sidprice
    Participant

    This is an MSBuild project.

     

    I switched to MS Intellisense and my problem went away,

    Sid

    July 21, 2017 at 18:07 #11782
    support
    Keymaster

    Hi,

    MS IntelliSense does not support automatic header discovery, so it could be indeed related. You can also try disabling the header discovery via the IntelliSense Settings page of VisualGDB Project Properties.

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