Visual Studio 2019 Debugging Error / Colibri iMX6

ebongiovanni · January 20, 2021, 9:06pm

Hi,
I did step by step “Build and Run your First C Application”, an error appeared when I try to “Deploy and Debug Torizon Application”.
Target Device OS: Torizon
Development PC OS: Windows

Output msg:

Starting Torizon build...
Starting SDK container...
Setting connection info...
Torizon setup completed.
1>------ Build started: Project: FofitoFirstApp, Configuration: Debug_debian_arm32v7_bullseye x64 ------
1>Torizon Container Build
1>EXEC : API error : Error calling ApplicationsLoad: No es posible conectar con el servidor remoto
1>Description:
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Application Type\Linux\1.0\Linux.targets(604,5): error MSB3073: The command ""c:\program files (x86)\microsoft visual studio\2019\community\common7\ide\extensions\ujdmjqr5.hii\TorizonBuildContainer.exe" ".\appconfig_0" "debug" -sdk
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Application Type\Linux\1.0\Linux.targets(604,5): error MSB3073: :VCEnd" exited with code -1.
1>Done building project "FofitoFirstApp.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I tried to do everything.
I changed the SOM, restored it to the factory, reinstall the visual studio, etc.

Help me!.
Thanks!

ebongiovanni · January 21, 2021, 6:09pm

I attached a capture of the moses.exe console with msg when I try “Deploy and Debug Torizon Application” on Microsoft Visual Studio Community 2019 - Version 16.8.4

ebongiovanni · January 21, 2021, 9:14pm

Serving on http://kubernetes.docker.internal:8090
INFO:root:REST -> /api/eulas
INFO:root:REST <- /api/eulas - 200
INFO:root:REST -> /api/version/docker
INFO:root:REST <- /api/version/docker - 200
INFO:root:REST -> /api/platforms
INFO:root:REST <- /api/platforms - 200
INFO:root:REST -> /api/applications/create
archivo procesado: C:\Users\ebongiovanni\source\repos\TorizonAppABAJO\appconfig_0\id_rsa
Se procesaron correctamente 1 archivos; error al procesar 0 archivos
Se procesaron correctamente 0 archivos; error al procesar 0 archivos
archivo procesado: C:\Users\ebongiovanni\source\repos\TorizonAppABAJO\appconfig_0\id_rsa
Se procesaron correctamente 1 archivos; error al procesar 0 archivos
INFO:root:REST <- /api/applications/create - 200
INFO:root:REST -> /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69
WARNING:root:REST - Attempt to change value of property images
WARNING:root:REST - Attempt to change value of property sdkimages
INFO:root:REST <- /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69 - 200
INFO:root:REST -> /api/applications/load
INFO:root:REST <- /api/applications/load - 200
INFO:root:REST -> /api/platforms
INFO:root:REST <- /api/platforms - 200
INFO:root:REST -> /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run
ERROR:root:Error: 520 Container image not found on local host. Image torizonappabajo_arm32v7-debian_bullseye_debug_d8eb730e-6962-4f35-a268-c9aabcc4dd69_sdk_image is not available.
INFO:root:REST <- /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run - 520
INFO:root:REST -> /api/applications/load
INFO:root:REST <- /api/applications/load - 200
INFO:root:REST -> /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/container
ERROR:root:Error: 548 SDK container not found. SDK Container not found: 404 Client Error: Not Found ("No such container: torizonappabajo_arm32v7-debian_bullseye_debug_d8eb730e-6962-4f35-a268-c9aabcc4dd69_sdk")
ERROR:root:Exception: SDK Container not found: 404 Client Error: Not Found ("No such container: torizonappabajo_arm32v7-debian_bullseye_debug_d8eb730e-6962-4f35-a268-c9aabcc4dd69_sdk")
ERROR:root:404 Client Error: Not Found ("No such container: torizonappabajo_arm32v7-debian_bullseye_debug_d8eb730e-6962-4f35-a268-c9aabcc4dd69_sdk")
INFO:root:REST <- /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/container - 548
INFO:root:REST -> /api/applications/load
INFO:root:REST <- /api/applications/load - 200
INFO:root:REST -> /api/platforms
INFO:root:REST <- /api/platforms - 200
INFO:root:REST -> /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run
INFO:root:SDK - SDK image not found, building it.
INFO:root:REST <- /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run - 200
INFO:root:REST -> /api/applications/load
INFO:root:REST <- /api/applications/load - 200
INFO:root:REST -> /api/platforms
INFO:root:REST <- /api/platforms - 200
INFO:root:REST -> /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run
INFO:root:REST <- /api/applications/d8eb730e-6962-4f35-a268-c9aabcc4dd69/sdk/run - 200

jeremias.tx · January 21, 2021, 9:12pm

Greetings @ebongiovanni,

I’m unable to reproduce this issue on my end.

Just to confirm what version of the Extension are you using?

Based on the moses console you provided there doesn’t appear to be any errors thrown. Can you provide the full moses log from the start to finish when going through the steps of “Build and Run your First C Application”.

It seems like the process specifically bugs out during the build step. Can you confirm that Docker Desktop is running properly and that it’s running the WSL 2 backend.

Finally if I understand you correctly it sounds like you can reproduce this reliably, correct?

Best Regards,
Jeremias

jeremias.tx · January 21, 2021, 10:45pm

We’re still theorizing as to what could be causing the error you are seeing.

However one of our IDE developers has an idea. Perhaps the extension backend “moses” is dying/being interrupted mid process. Does the moses window crash or close when the error happens? Or is there any other indication that moses may not be running the entire time you’re using the extension?

Furthermore can you confirm that in your project files there is a config.yaml file inside of the appconfig_0 folder.

Best Regards,
Jeremias

ebongiovanni · January 22, 2021, 12:19pm

Hi Jeremias, nice to meet you!
I answer your question below:

The version of the extension is:
1.3.0
- I have early access too, with version: 1.4.55
- No error throws me the moses console.
- Docker Desktop and WSL2 is running correctly. (or so I think) When I run VS2019, the output console throws: “Backend service and docker are up and running, enabling Torizon features.”
- Yes, I can reproduce this reliably. I restarted my PC and the same error was appear.
- I put “Show backend console” in true and never being interrupted or so I think, at least is never closed or crashed, and when it stops compilation the moses console was still open
- yes, there is a config.yaml file inside of the appconfig_0 folder.

I can’t make it work yet.

Best regards,
Esteban

ebongiovanni · January 22, 2021, 12:23pm

Hi Jeremias, nice to meet you!

I answer your question below:

The version of the extension is: 1.3.0
I have early access too, with version: 1.4.55
No error throws me the moses console.
Docker Desktop and WSL2 is running correctly. (or so I think) When I run VS2019, the output console throws: “Backend service and docker are up and running, enabling Torizon features.”
Yes, I can reproduce this reliably. I restarted my PC and the same error was appear.
I put “Show backend console” in true and never being interrupted or so I think, at least is never closed or crashed, and when it stops compilation the moses console was still open
Yes, there is a config.yaml file inside of the appconfig_0 folder.

I can’t make it work yet.

Best regards,
Esteban

jeremias.tx · January 22, 2021, 7:41pm

Thank you for the feedback so nothing seems wrong there then. By the way since you mentioned the early access version does the issue still happen when using this version?

Next another thing I would like for you to check is the following. When our extension starts the build process moses.exe spawns another process called TorizonBuildContainer.exe for the building. Can you check to make sure this secondary process isn’t being blocked by any firewall, anti-virus, or some other program possibly?

Just to explain the only way we’ve been able to reproduce your logs was by terminating moses.exe mid build process. Which is why our current theory is that the process is somehow “dying” or maybe being interrupted during the build.

Best Regards,
Jeremias

valter.tx · January 25, 2021, 9:38am

You mentioned having also the early access version.
Please notice that you can’t have stable and early access versions installed at the same time. If that’s the case, please uninstall one of them and reinstall the other.

rpannet · March 1, 2021, 10:25am

Hello,

I have the same issue. I try with only one Torizon extension installed.
Did you find a solution?

Best Regards

jeremias.tx · March 1, 2021, 7:03pm

Unfortunately we never got to the bottom of this issue and it’s still an unknown.

valter.tx · March 2, 2021, 7:45am

Sorry, I just noticed that your backend application seem to be running on port 8090 instead of the default one (5000), did you change that in the configuration? May you try to run it on port 5000 to understand if this makes a difference?

valter.tx · March 2, 2021, 7:46am

Also no communication with the server?
Did you change the default port (5000)? You can see that in the backend console, it’s the first message.

valter.tx · March 2, 2021, 1:42pm

If you change the default port you need to edit also the Pre-build event, adding -port to the command line.
ex for debug configuration and using port 8090, current command line:

"$(TorizonExtPath)\TorizonBuildContainer.exe" "$(torizon_configpath)" "$(torizon_configtype)" -sdk

becomes:

"$(TorizonExtPath)\TorizonBuildContainer.exe" "$(torizon_configpath)" "$(torizon_configtype)" -sdk -port 8090

rpannet · March 3, 2021, 7:51am

Hello,

I had changed the port during my try to solve the issue. I set back port 5000 an now it works.

Thanks a lot for your efficient support.

Best regards.

jeremias.tx · March 3, 2021, 6:15pm

Glad you were able to resolve this.