[peini7]

Thank you so much. This helped me finding the problem.

I have used PC14+PC15 as output pins which is not allowed.
As soon as they have been initialized, i was loosing the OCD connection.

• This reply was modified 1 year, 9 months ago by peini7.

[peini7]

Ah… thank you. That is the missing piece in the puzzle..
I’ve installed VC++ “after” installing VisaulGDB.

Maybe the installer can check the required workloads too, but this is just a suggestion.

I really love what you’re providing with VisualGDB. Keep on the great work 🙂
I think i will buy it after the evaluation phase…

[peini7]

Here are the two screens. Sorry for the error message beeing in german.
Copying over the VisualGDB folder from v160 to v170 helps and everything is working fine.
It looks like the installer is copying it to the wrong directory.

I had VS2019 installed on this machine earlier, but when i’ve installed VisualGDB only VS2022 was installed.
Also the installer has detected VS2022 correctly.

Attachments:

You must be logged in to view attached files.

[peini7]

It seems that this still exists in the latest version.
I’am using the final RTM version of VS2022 and the latest VisualGDB version 5.6r2 but i also needed to copy the files from v16 to v17.

[peini7]

Ah.. Solved it.

For everyone having the same problem.. Running the installer from an adminstrator command promt did the trick, because there is no “Run as administrator”-button on msi-files.

[Author]

Posts