[GeneM]

As happens so often, I figured out the solution 30 seconds after posting this question.  The sample file used main.c and I needed to rename is main.cpp.  Sorry for the distraction.

[GeneM]

That fixed it, thanks.

[GeneM]

I understand about what you can and can’t do on this forum, no worries.  Once I get a little farther along, I’ll definitely be looking for a consultant to move us up the learn curve effectively.  Do you have something that describes your consulting services and expertise?

[GeneM]

I think I found the magic Google search secret.  If I preface my search with GCC, I can find stuff that actually works in VisualGDB.  I found string.h and that seems to have most of the functionality I’m looking for.  Thanks again.

[GeneM]

Live mode in the memory window worked really well and I’m assuming with much less overhead than adding printf statements.  One more newbie question if you don’t mind.  Are there any low overhead functions to do things like strchr, strncmp, strtok, etc?

[GeneM]

If it’s the “Step into new instance (F10) steps in: entry point or main() function” then I found it (see attached).

Thanks

 

Attachments:

You must be logged in to view attached files.

[GeneM]

Great, that explains a lot.  And BTW, I’ve been able to build up the app for scratch with a lot more success.  Now I have to figure out how to replace the standard VisualGDB and STM32 SysTic_handler with the QP framework one.  I’m still working on that but I do have another question that I’ll ask in a new post.

Thanks for the help

 

[GeneM]

I’ve been trying a different path.  I built the basic VSgdb blinky program and am adding the QP features one at a time.  I’m still working on it but so far so good.  I do have one confusing issues.  I’m building up a QP folder inside my main project directory that will eventually have all the QP files I need for the app.  So far I’ve put all the header files in there that I need to get the app to compile without errors.  When I add the QP folder path to the Project Properties>Configuration Properties>C/C++>General/ Additional Include Directories option, everything compiles fine.  When I add the QP folder to the Solution Explorer>Header Files folder and remove the path in the Additional Include Directories I get lots of of errors; as if the compiler didn’t see any of the files in the QP folder in the Solution Explorer.  Seems like it would be nice to have all the QP .h, .hpp and .cpp files visible in the Solution Explorer.  What do I have to do to make a folder I added to the Header Files folder visible to the compiler.  I attached a .zip file of the project minus the very large .vs and VisualGDB folders.

• This reply was modified 5 years ago by GeneM.
• This reply was modified 5 years ago by GeneM.

Attachments:

You must be logged in to view attached files.

[GeneM]

By the way, that project is an example from the QP framework.  QP is an incredibly effective and well written framework for state machine based embedded apps.  It may be something you may be interested in supporting with VisualGDB.  Here’s the website: https://www.state-machine.com/

[GeneM]

That didn’t seem to work, hopefully this will

Attachments:

You must be logged in to view attached files.

[GeneM]

Here they are.

[GeneM]

That was the answer, for sure.  I was already trying to clone one of the SMM32 SKD examples and, now that I know where to look, VisualGDB does it for me and in a way where I can find most (maybe all) of the required include .c and .h files.  Thanks for the help.

[GeneM]

Thanks again for the help, that got me past the first step in the learning curve.  Next question: I’m starting to add the code I need to use the SD card and this code

FATFS SDFatFs; /* File system object for SD card logical drive */
FIL MyFile; /* File object */

Gives this error

1 [Clang IntelliSense] Error: unknown type name ‘FATFS’ C:\Users\gene\Documents\VisualGDB\EmbeddedProject1\EmbeddedProject1\EmbeddedProject1.cpp 10 1 EmbeddedProject1″

and a similar error for the “FIL” type. FATFS and FIL are structures defined in ff.h which is included in my solution as shown in the attached file. What do I need to do so the compiler can find FATFS and FIL?

Like I said earlier, I’m moving to C from C#.  I have a decent amount of experience with Visual Studio and I know where to look to get help with C programming but I’m struggling with how to set up an embedded C project using VisualGDB.  My current workflow is to start with an example from the STM32 firmware library.  I can look at it using the STM32CubeIDE and am trying to recreate the example in VisualGDB. The problem is the CubeIDE examples are really complicated and all the library and header files are scattered/hidden in dozens of different places.  Is there a  book, tutorial, website or whatever where I can get up to speed on issues like this one?  VisualGDB looks like a great solution for me if I can get past these initial learning curve hurdles but I wish I didn’t have to take up everyone’s time with my newbie questions.

And 1 more related question.  Does it make sense to start a project with STMCubeMX and then import that into VisualGDB?

Thanks

 

 

 

 

 

 

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

Attachments:

You must be logged in to view attached files.

[GeneM]

Thanks for the quick response, I’ll give those suggestions a try and get back to you if I need more help.

[Author]

Posts