[Sherlock]

Hi, thanks this is helpful, for my immediate purposes I’m using MSBuild projects and nothing more.

I created a new repo and used the Github Visual Studio ignore, then added this:

# VisualGDB MSBuild Projects
.vs/
.visualgdb/
VisualGDB/

 

Does this seem OK? might there be anything additional to consider?

Thanks

 

 

 

 

 

 

 

[Sherlock]

Beautiful !

All good, thanks for a prompt and precise response, much appreciated.

 

 

[Sherlock]

OK installing now…

[Sherlock]

Interestingly that when I choose “Program and Start Without Debugging” this succeeds, I see the “The device has been programmed successfully” dialog and the board seems to reset and the code gets loaded (I can see expected activity on my DSO).

 

 

 

[Sherlock]

I can’t see the “Edit” option here any more so I can’t add to my original post.

Anyway I just ran a repair of Visual GDB but this seems to have had no effect on this behavior.

 

[Sherlock]

If I try to start without debugging (from VS debug menu) I see a console window that soon vanishes, no app seems to load into the board and VS doesn’t crash, here’s what I captured from the console window:

 

Attachments:

You must be logged in to view attached files.

[Sherlock]

Hi, OK that helps me actually, so the contents of Device-specific files folders are never intended to be manipulated by the developer.

So there’s never a situation where I’d need to include some additional STM32 header in my source file and that include file would not already be present in the Device-specific files header section?

Every include file I’d ever need to leverage any aspect of HAL should already be present in the Device-specific folders?

Thanks

 

[Sherlock]

This is resolved, it was caused by me assuming I could freely leverage the std periph library within a project initially created for HAL.

[Sherlock]

OK understood, I have now posted this as a question on the STM forum site along with details of a public GitHub repo that contains the (unbuildable) project.

https://community.st.com/s/group/0F90X000000AXsASAW/stm32-mcus

Thanks.

 

• This reply was modified 5 years, 3 months ago by Sherlock.

[Sherlock]

But I though my purchase included support? I just paid for the Custom Edition last week!

Thanks,

Hugh

 

 

[Sherlock]

But surely this is something you understand? what would you do to resolve this kind of issue?

[Sherlock]

Hi, OK I’ve done as you suggested and started discussing this on the STM32 site.

However I wonder if I’m doing something wrong here.

In order to call RCC_GetClocksFreq I searched the web for info to get the name of the .h file that declares this function.

I found that it was in stm32f4xx_rcc.h and simply embedded the include for that into my source – but was that wrong?

Should I add these files and their sources into the solution explorer?

I can see that the project (as created when I created the new VisualGDB project) has solution explorer folders like Device-specific files and LL and so on, should I be adding files to the project by adding them to solution explorer?

How would one typically go about adding a call to a function that’s not defined in any of the headers currently being included in my mainapp.c file?

Is there any documentation about how to do these kinds of project tasks with VisualGDB?

Thanks

 

 

 

 

• This reply was modified 5 years, 3 months ago by Sherlock.
• This reply was modified 5 years, 3 months ago by Sherlock.
• This reply was modified 5 years, 3 months ago by Sherlock.
• This reply was modified 5 years, 3 months ago by Sherlock.

[Author]

Posts