I downgraded because i was tired of windows 10. Run the toolchain installer. now what?
If you ran the installer, you should have CLI installed - what more are you expecting?
if it did, then where do i do particle setup?
You should now be able to open a
cmd and enter
particle and see this
Welcome to the Particle Command line utility! Version 1.8.16 https://github.com/spark/particle-cli Usage: particle <command_name> <arguments> Common Commands: setup, list, call, get, device, identify, flash, subscribe compile, monitor, login, logout, help Less Common Commands: token, cloud, config, function, keys, serial, udp, update variable, webhook, wireless For more information Run: particle help <command_name>
Can you check your
You should at least have these entries in there
And the respective directories should exist
What do you get when you enter
that doesnt exist
This is my path text: C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\binaries\php\php_runningversion;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Java\jdk1.8.0_60\bin;C:\Python27;C:\Program Files\nodejs;C:\Particle\Tools\Git\cmd;C:\Particle\Tools\NodeJS;C:\Particle\Tools\DFU-util;
Ah, sorry, that path you can’t find is actually only connected to Particle Dev, so you won’t need it.
But these parts of your
PATH might be a clue for your problem.
You have got
C:\Program Files\nodejs and
Any reason why you’ve got two sets of
And I can’t see the
%appdata%\Roaming\npm in your
PATH, can you check if it exists?
This directory should actually contain the
If this directory exists, try adding it to your
PATH manually (and remove the second
NodeJS from it).
npm version report (maybe executed from within both of your directories)?
two node js because i had installed it and forgot to take it off of the toolkit installation. and npm version outputs: http://prntscr.com/8yt413. and particle-cli is in the npm-cache.
Have you actually got the full module in npm-cache or rather only the packed
This is how it looks on mine (although I’m still sticking with Node v0.12.4)
And there is a
particle.cmd file in
Its just the package.tgz
The installation of CLI is driving me nuts
npm uninstall -g particle-cli and a subsequent
npm install -g particle-cli another try.
If this doesn’t work, remove all instances of NodeJS and try the installer afresh.
particle-cli installation fails no matter what. even if i install it after all of the stuff ive been told to do.
i have a skype if someone wants to call me and go from there…
I’ve run out of ideas, but I’ve asked some of the more brilliant people to have a look into your problem.
I had thought of offering a TeamViewer session to just play through what I’d do if my machine would not work (providing you’d trust me enough to let me fiddle on your machine).
But let’s wait first if someone has got the right idea.
My timezone is UTC+1.
I FINALLY GOT IT TO WORK. I connected to it using putty with a serial.
Huh? Got what working?
How would PuTTY help installing CLI?
Or do you mean you got around the need for CLI by using another aporach - e.g. for setting WiFi credentials?
If that, then asking the correct question would have safed you a lot of trouble
i didnt know what to ask… but yeah
I recently had problems reinstalling particle-cli (failure at serialport) but then I found these posts:
I followed the suggestion to do the npm install from the Visual Studio Command Prompt:
Try running the npm install commands from a MSVS command prompt. Find it at Start menu > Microsoft Visual Studio 201X > Visual Studio Tools > Open Visual Studio 201X Tools Command Prompt or run the <Program Files>\<VS dir>\Common7\Tools\VsDevCmd.bat from a command prompt.
and the installation proceeded flawlessly.