Title says most.
The installation may be a bit messy, as I installed beta 3.21.19 for a while to get SWD support. I then discovered that a workspace I'd been using successfully to do production testing on my EExplorer failed to load.
I downgraded to 3.21.3 where the issue remained, then fully uninstalled (using Digilent Software uninstaller), then installed 3.20.1 where the issue remained ( and additionally, where StaticIO doesn't work on EExplorer) and am now at 3.21.2.
Trying to open Script crashes the app whether I:
* Open a workspace that contains Script
* Open Script from the Welcome menu
* Regardless of if I use a physical or demo device
* Regardless of which Demo device is selected
Weirdly enough, I did get the Script window to open sometimes (feels like a 10% chance) and it worked fine, but I've yet to find any rhyme in what steps of flailing around result in a functional Script window.
Another potential hint is that the SWD tab has remained available in the Protocol window, and the app seems to remember my "recently used workspaces". So it would seem the uninstall was not as thorough as one might hope.
Of course, this first manifested when I was trying to teach production how to use the test rig, but that's just life.
Question
jostikas
Hi!
Title says most.
The installation may be a bit messy, as I installed beta 3.21.19 for a while to get SWD support. I then discovered that a workspace I'd been using successfully to do production testing on my EExplorer failed to load.
I downgraded to 3.21.3 where the issue remained, then fully uninstalled (using Digilent Software uninstaller), then installed 3.20.1 where the issue remained ( and additionally, where StaticIO doesn't work on EExplorer) and am now at 3.21.2.
Trying to open Script crashes the app whether I:
* Open a workspace that contains Script
* Open Script from the Welcome menu
* Regardless of if I use a physical or demo device
* Regardless of which Demo device is selected
Weirdly enough, I did get the Script window to open sometimes (feels like a 10% chance) and it worked fine, but I've yet to find any rhyme in what steps of flailing around result in a functional Script window.
Another potential hint is that the SWD tab has remained available in the Protocol window, and the app seems to remember my "recently used workspaces". So it would seem the uninstall was not as thorough as one might hope.
Of course, this first manifested when I was trying to teach production how to use the test rig, but that's just life.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now