[We]

We encountered almost the same problem a few months ago, solved by cleaning all local cache directories like .vs .visualgdb.

[We]

Figured it out:

Vitis(or say Vivado) requires its own “Microsoft Visual C++ 2017 Redistributable(x64)“.

I installed a software packed with its own MSVC++ 2015-2019 package and overwrite the 2017 version, problem should be exposed when trying to start Vivado and pop out with a “VCOMP140.DLL not found” error window.

It happened on my laptop so I fixed it partially, but not happened on my desktop because of TortoiseSVN on my desktop(TortoiseSVN directory contains lots of dll and add them to Path).

TortoiseSVN path is not included in VS prompt environment variables, so xsct.bat exited immediately.

I reinstalled MSVC++ 2017 and visualgdb Xilinx project works.

Thanks!

[We]

It maybe about some MSVC redistribute package dll, I will give a further exploration.

[We]

Ridiculous

Attachments:

You must be logged in to view attached files.

[We]

Hi, it’s deep night in my time region, I will try it later.

But I can give more info:

since the command prompt looks more like windows cmd other than xsct prompt, I tried running …\xsct.bat as you mentioned yesterday, no echo and nothing changed, I’m still in the windows prompt.

So the problem left is all about the path, hope to get it fixed before the weekend 🙂

[We]

cmdline complained xsdbserver not found as a cmd/executable/bat.I print all env variables in screenshot 1 if needed.

telnet not found, too.

Attachments:

You must be logged in to view attached files.

[We]

Connected successfully when launch from pre-build step in a .Net project.

I also tried VS Tools>Cmdline>Developer Cmdline and connected successfully.

[We]

Hi,

telnet connected successfully, it displays a blank window titled telnet localhost, I don’t know how to operate it and no response to any key.

The screenshot shows the echo before connecting

Attachments:

You must be logged in to view attached files.

[We]

Here is the log, I had shut down windows defender and the internet firewall when testing(actually firewall doesn’t affect log)

[00:00:06.4660783] C:\Program Files (x86)\Sysprogs\VisualGDB\vgagent.exe cmd.exe /c “C:\Xilinx\Vitis\2021.1\bin\xsct.bat” -n -interactive

[00:00:06.5250860] …. xsdbserver start -host localhost -port 51958 ; puts done-d4bf66b4-aeac-48b8-8f4d-9ee904fc9abb

[00:00:53.8287477] C:\Program Files (x86)\Sysprogs\VisualGDB\vgagent.exe cmd.exe /c “C:\Xilinx\Vitis\2021.1\bin\xsct.bat” -n -interactive

[00:00:53.8307220] …. xsdbserver start -host localhost -port 51970 ; puts done-1e35497c-ea4b-4399-b914-e82d385d4837

[00:00:55.7359018] C:\Program Files (x86)\Sysprogs\VisualGDB\vgagent.exe cmd.exe /c “C:\Xilinx\Vitis\2021.1\bin\xsct.bat” -n -interactive

[00:00:55.7396576] …. xsdbserver start -host localhost -port 51971 ; puts done-b94d29f8-ead1-4873-b45a-629100933d4f

Every time I choose a Xilinx platform *.xsa, it put 2 lines, no more.

[We]

I checked “Extensions to delete on clean” of main app project,it’s already $(TargetName).bin since using the newest demo project.

However,generated bin doesn’t include bootloader no matter rebuild or clean then rebuild,Bug not fixed,:(

If I clean Bootloader.bin20.rsp|*.bootldr-0|*.bootldr-rename.rsp manually(clean project won’t delete these 3 files),then build sln,generated bin is all right.

Maybe you should config to delete these middlewares after merging.Could it be done in .props?

 

[We]

Thanks a lot.I cancelled stack validatation but I just forgot that stack decend from the end of RAM,so the MCU stuck somewhere 🙁 .

Finally I copied the linker script and changed memory size configuration and it works!

By the way,when will a new mbed support package come out?The Official version is now 5.12.2  while VisualGDB still offers an old 5.9.2.The new mbed project wizard takes a lot of time download files while creating new solution and compiling the whole solution is also very very slow compared to use old mbed toolchain inside.

[We]

I have renewed my license,let’s start.

[Author]

Posts