m_m
April 3, 2019, 7:20pm
21
As far as I know everything is working as it should and I’ve learned some things. Thanks much!
hooray!
let's try one last round of checks just to be extra-sure. run the Particle: Launch Compiler Shell command and in the terminal that launches run:
which particle
that should return a path like /home/<you>/.vscode/extensions/particle.particle-vscode-core-1.3.0/src/cli/bin/linux/amd64/particle.
then run:
which arm-none-eabi-gdb
and that should return a path like: /home/<you>/.particle/toolchains/gcc-arm/5.3.1/bin/arm-none-eabi-gdb
if either command above it does not return the expected output, please post the screengrab and error text here.
I am not sure if I’ve left some confidential information in this thread
i didn't notice anything
johns
April 3, 2019, 7:45pm
22
which particle did not work See below.
john@john-Precision-M4600:~/ProjectsforParticleIO/WorkspacesLocal/BlinkLED$ which particle
m_m
April 3, 2019, 8:01pm
23
which particle did not work
run the Particle: Launch Compiler Shell command and in the terminal that launches run:
echo $PATH
and share the results
johns
April 3, 2019, 8:55pm
24
john@john-Precision-M4600:~/ProjectsforParticleIO/WorkspacesLocal/BlinkLED$ which particle
m_m
April 3, 2019, 9:08pm
25
how about:
echo $PARTICLE_MAKEFILE
again, for all of this you’ll need to be in the terminal instance spawned via Particle: Launch Compiler Shell
m_m
April 3, 2019, 9:42pm
26
actually, i forgot: changes to .bashrc often require a full reboot to take effect - couldn’t hurt to try that as well
johns
April 3, 2019, 10:07pm
27
Rebooted computer. Then launched the compiler shell followed by the additional steps you stated.
│ Available Targets
johns:
/usr/local/gcc-arm/bin
I'm no expert here, but would having this in your PATH conflict with gcc-arm used by Workbench?
Doesn't Workbench use?:
~/.particle/toolchains/gcc-arm/5.3.1/bin
m_m
April 3, 2019, 10:28pm
29
we prepend a number of locations to your $PATH when launching our tasks (Particle: Compile application (local), etc) and terminals (Particle: Launch Compiler Shell and Particle: Launch CLI) so our bins should take precedence.
i’m stumped as to why echo $PATH is not returning our locations in this case, unfortunately.
one last thing to try is run Particle: Launch CLI and then in that terminal, run echo $PATH - that should include something like /home/<you>/.vscode/extensions/particle.particle-vscode-core-1.3.0/src/cli/bin/linux/amd64
but if it does not all i can think is that there’s something odd about .bashrc (perhaps it’s sourcing another file which is messing w/ PATH) and the shell env in general. sorry!
johns
April 4, 2019, 2:42pm
30
m_m, it does return what you expect.
bash-4.4$ echo $PATH
m_m
April 4, 2019, 3:00pm
31
might have a fix to ship w/ the next update. thanks again!
johns
April 4, 2019, 3:21pm
32
How will I know when and how to update my platform? Will the update be part of the Particle Extensions?
m_m
April 4, 2019, 4:19pm
33
unless you’ve disabled it in your settings, VSCode will periodically check for extension updates and automatically download new versions when they’re available
glad we got you up and running and thanks again for working through the issues - very helpful as we evolve Particle Workbench 
hm. ok, then i think i might have a fix to ship w/ the next update. thanks again!