[GeneM]

Thanks for the quick response.  I’ve been using VGDB quite happily for a couple of years now but almost entirely with MSBuild projects that I start from scratch or from the ST examples provided in VGDB or the excellent VGDB tutorials.  That works great.  Now that I’m moving outside my experience base, I’m trying to come up with an efficient work flow.  My next attempt will be importing a STM32CubeMX (or STM32CubeIDE) project into a VGDB project that sits in the same folder as the original CubeMX folder so all the necessary files are in the same place. thanks again.

[GeneM]

Thanks for the clues, this is almost for sure related to the fact this is a CMake project set up by somebody else.  I did build a really simple MSBuild project in VGDB with the same code shown in that snip I attached.  It worked just fine with no red error underscores.  I think we’re good for now.  Thanks again.

[GeneM]

No problem, I thought it might be a VisualGDB setup problem.

[GeneM]

I was afraid of that too.  But I had what turned out to be a good idea.  I used STM32CubeIDE to run the same STM LPTIMER example on the “failed” Nucelo board and it worked.  I tried my original LPTIMER example using VisualGDB and it works too.  So does the main project I’ve been working on. It may be related to me powering down the Nucleo board while the program was in the low power state and VGDB not being able to wake it up but that is way beyond my skill set.  Thanks for the quick response.

[GeneM]

In that case, I’m guessing that it’s git making the changes.  I’ll run a test in the near future to see what’s happening.

[GeneM]

I thought I’d try again to see if there was someone interested in a consulting job to help get us started with a VisualGDB project running on a standard STM Nucleo H7A3ZI-Q board.  I’ve made some progress talking to various peripherals starting with the STM examples on this and other Nucleo boards.  However, I could definitely use some help getting a basic VisualGDB project working on this Nucleo board that talks to a UART using DMA and also implements a FatFS on a SD card with timers that run at the correct rate.  If I got that going, it would be a huge help but there’s plenty of work after that if you’re still interested.

Thanks – Gene Massion

 

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

[GeneM]

You are correct, I created the project in a way that put the source code somewhere different than I expected.  Thanks for pointing out my dumb mistake.

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

[GeneM]

Actually something a little weird happened.  I thought the C Library type and Implementations for _sbrk(), etc. were set as I described above.  But they seem to have been reset under the hood to Newlib-nano and Minimal (no semihosting).  Same issue though, printf works in main but not in the interrupt callback.

[GeneM]

Exactly right. Thanks for the clarification.

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

[GeneM]

That worked perfectly.  Thanks.

[GeneM]

Thanks for the quick response.  I’m using STM32CubeIDE version 1.6.1 which is think the newest or pretty close to it.  My previous attempts to import a CubeIDE project into VGDB were pretty straight forward but definitely with previous versions of both IDEs.  I can see several lines in the current .cproject file with the suspect option in them but I can’t tell what might be wrong so I attached a .zip.

Thanks again

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

Attachments:

You must be logged in to view attached files.

[GeneM]

And I should have mentioned, I did try adding all the required header files one at a time and eventually go to memoryfwd.h which starts like this

#ifndef _MEMORYFWD_H
#define _MEMORYFWD_H 1

#pragma GCC system_header

//#include <bits/c++config.h>
#include <c++config.h>

namespace std _GLIBCXX_VISIBILITY(default)

And I get this error: “unknown type ‘namespace”.  I can make a copy of memoryfwd.h and rename it memoryfwd.hpp but I need to change whatever files are including memoryfwd.h to include memoryfwd.hpp.  But I can’t find any files in my solution that have the term “memoryfwd.h”.

There really has to be something fundamental I don’t understand.  I have several C/C++ books that I actually refer to, I’ve done a bunch of the VisualGDB tutorials and I spend a lot of time Googling for answers before I post a question.  If someone can point me at some tutorial that would help, that would be great.

Thanks again.

 

 

[GeneM]

This project has come up and again and I’d like to ask the question a different way.  It looks like I can access the JTAG pins on the SAM9X35 part and the Segger J-Link EDU module does support this device.  But I haven’t found a SAM9X35 or ARM926EJ-S in the list of MPUs in the VisualGDB New Embedded Project -> Device Selection table.  There are some part numbers that come close but nothing exact.  Does VisualGDB support this device?

[GeneM]

That looks like it fixed the issue.  And it compiles and downloads.  Next step, making it do something useful.  Thanks for the quick and effective support on a Saturday.

[GeneM]

Thanks for the quick response. Is the issue that the G400S is a niche or that Atmel’s SAM-BA is a niche or the combination of the two?

• This reply was modified 4 years, 8 months ago by GeneM.

[Author]

Posts