Closed UniverGao closed 1 year ago
Hi @UniverGao, to help debug this it would be useful to have the logs from VS Code:
I did the test and the log is here: Best regrards.
Thanks for sharing. It looks like the first line is the cause of the problem:
workbench.desktop.main.js:89 [Extension Host] Core Tools process error Error: spawn c:\Users\%USERNAME%\.vscode\extensions\arm.cmsis-csolution-0.10.0\tools\cmsis-core-tools\cmsis.exe ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:478:16) at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
The CMSIS Core Tools is a binary the extension uses to understand the CMSIS ecosystem. Does the file exist at %HOME%\.vscode\extensions\arm.cmsis-csolution-0.10.0\tools\cmsis-core-tools\cmsis.exe
? If so, can you run it from the command line?
Also, what is the CPU architecture for your machine? Intel 64 bit, 32 bit or Arm?
@mcgordonite Sorry that the extention was not installed correctly. I reinstalled the extension, cmsis.exe could be run corrently, the error message 'Failed to load solution at...' was disappeared, but the 'Manage Software Components' interface of the CMSIS solution extention was still empty. PS:
The log shown below is about the status after the extension correctly re-installed: vscode-app-cmsis-win-v0.10.0.log
It looks like the issue is that csolution example includes components via layers. The preview Manage Components view doesn't support layers yet, although basic support is in the roadmap for the next few months. If you'd like to try out the component manager, you could use an example that doesn't use layers, e.g. https://github.com/Open-CMSIS-Pack/csolution-examples/.
Type: Bug Report
Describe the bug
Failed to load solution at c:\Practice\Demo_EW\Blinky\Blinky.csolution.yml
when the project folder was opened in vs code, and 'Manage Software Components' interface of the CMSIS solution extention was empty.
To Reproduce Steps to reproduce the behavior:
Expected behavior
No error pop-out and 'Manage Software Components' interface of the CMSIS solution extention shows the pack components existed.
Code sample and logs
csolution convert --load required -s c:\Practice\Demo_EW\Blinky\Blinky.csolution.yml --no-check-schema C:/Practice/Demo_EW/Blinky/Blinky.Debug+AVH_MPS3_Corstone-300.cprj - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Debug+B-U585I-IOT02A.cprj - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Release+AVH_MPS3_Corstone-300.cprj - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Release+B-U585I-IOT02A.cprj - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.cbuild-idx.yml - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Debug+AVH_MPS3_Corstone-300.cbuild.yml - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Debug+B-U585I-IOT02A.cbuild.yml - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Release+AVH_MPS3_Corstone-300.cbuild.yml - info csolution: file generated successfully C:/Practice/Demo_EW/Blinky/Blinky.Release+B-U585I-IOT02A.cbuild.yml - info csolution: file generated successfully
Screenshots
Additional context