You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to parse SVD file: Error: ENOENT: no such file or directory, open '/home/username/.vscode-insiders/extensions/marus25.cortex-debug-dp-stm32f4-1.0.0/data/STM32F40x.svd'
It's no big deal for me since I already had the STM32F407.svd, but I just wanted to see the changes in the 0.3.0 Cortex-Debug update changelog.
I commented out the "svdFile" line in my launch.json, for the moment, to see it in action.
Also for anyone else updating, for some reason after I updated Cortex-Debug and was reading through the changelog and saw the part about these additional extensions that could be found by searching for "cortex-debug" in the marketplace, no other extensions showed up besides the one from discotools.
I tried multiple times, and think they finally showed up in the search after I closed/reopened vscode. Updating cortex-debug did NOT require a restart.
EDIT0:
Heh, the 0.3.1 update came quickly. Don't know what's in that though.
The text was updated successfully, but these errors were encountered:
"device": "STM32F407VG"
extensions.ts
STM32F40x.svd doesn't seem to yet exist in https://github.com/Marus/cortex-debug-db-stm32f4/tree/master/data.
It's no big deal for me since I already had the STM32F407.svd, but I just wanted to see the changes in the 0.3.0 Cortex-Debug update changelog.
I commented out the "svdFile" line in my launch.json, for the moment, to see it in action.
Also for anyone else updating, for some reason after I updated Cortex-Debug and was reading through the changelog and saw the part about these additional extensions that could be found by searching for "cortex-debug" in the marketplace, no other extensions showed up besides the one from discotools.
I tried multiple times, and think they finally showed up in the search after I closed/reopened vscode. Updating cortex-debug did NOT require a restart.
EDIT0:
Heh, the 0.3.1 update came quickly. Don't know what's in that though.
The text was updated successfully, but these errors were encountered: