[TerryR]

Thanks again.

I still had some issues after deleting the entire .pico-sdk directory and re-installing 2.2.0 and 2.3.0. I  did a “Clean” and “Reload CMake Project”. The errors were…

CMake Error at …/.pico-sdk/sdk/2.3.0/src/CMakeLists.txt:37 (add_subdirectory):
add_subdirectory not given a binary directory but the given source
directory “…/.pico-sdk/sdk/2.2.0/src/rp2040/pico_platform” is
not a subdirectory of “…/.pico-sdk/sdk/2.3.0/src”. When
specifying an out-of-tree source a binary directory must be explicitly
specified.

This 2.2.0 reference  made me think something is cached somewhere, so I deleted the .visualGDB subdirectory in the project directory, leaving only the CMakeLists.txt and the .vgdbprog file.  After doing that, I am now able to switch between 2.2.0 and 2.3.0 after just a simple “Clean”.

So, everything’s AOK.  Problem solved!

[TerryR]

Hi,

Thanks for your reply.

Actually I don’t really want to use VS Code; I prefer the Visual Studio layout that I’m used to. I only loaded VS Code to see if it would function without an Internet connection.

So, using my nightly back-ups, I restored my system drive (C:) to its state on the evening before I installed VS Code; it’s gone, kaput, finito!  There’s no  ….\pico-sdk\sdk\2.3.0 sub-directory.

Now, I used VisualGDB properties page to select a pico sdk. I don’t even see 2.3.0 unless I click on “show all github tags”; it only goes up to 2.2.0 otherwise.  I selected 2.30. and it seemed to do a successful install, but when I reload cmake for the project, I get the exact same “System.NullReferenceException”.

So, is 2.3.0 supported yet? Maybe I shouldn’t use anything that needs “all github tabs” selected?????

 

 

[TerryR]

Hi,

Thanks for your response. Sorry about the email confusion; I never use the email that I use for banking and financial transactions on this kind of public forum; just paranoid.

O.K. so VisualGDB V6.1R3(build 5547).  Pico SDK choices are 2.2.0 and 2.3.0; both located in c:\Users\me\.pico-sdk\sdk. The selected toolkit is in the same directory tree.

I had selected and have been using 2.2.0 for some time now. The 2.3.0 was added earlier today when I was evaluating VS Code with the Pico extension.  So at the time of the Internet outage, only 2.2.0 would have been available.

I just did a test by unplugging the Ethernet cable, and the entire solution compiled O.K.  Maybe during my installation of VS Code + Pico extension, it loaded something that was missing before?

In any case, since I can no longer reproduce the problem, I would say don’t spend any time on this; we can say “solved”.

Thanks again.

 

 

 

[TerryR]

Just an update..

It worked perfectly!  It wasn’t a lot of effort to reorganize the directory structure and chop up the multiple target CMakeLists.txt into multiple single target files. I like the pull-down combo box in the editor; I can use it to change the project, and immediately see the inactive and active code sections update.

After over a year of frustration with this, I’m glad I finally have it resolved.

So, thank you very much!

[TerryR]

Thank you for your response. Not quite the answer I had hoped for, but I’m willing to try anything.

I think my least worse option is to convert the current single project with multiple targets into multiple projects, each with a single target –  if that will make the advanced IntelliSense features work!

I think this might need a common source directory with separate sub-directories for each of the CMakeLists.txt and ./build subdirectories.

I’ll give it a try ( after backing up my entire hard drive ).

Thanks again.

[Author]

Posts