Hi,
OK - so - bashing my head against a brick wall once again.
Made the mistake of running running NPM upgrade - when particle list refused to list 3 'variables' for one of my photons.
upgrade failed, install now fails and I am back to (pre) stage 1 again - no CLI at all.
Might be a 'red herring' BUT in hindsight its possibly because of a windows driver clash. I have a Python-based 3D printer program (pronterface) which was originally set up to use an FTDI driver on Com3. Seems that this was trashed when I installed the CLI some weeks/months back and it grabbed Com3.
Then I needed to use the printer again (a couple of weeks back) - and had to re-install the FTDI driver - which looks like it trashed the CLI driver settings - such that CLI now refuses to install again. I ended up then in changing CLI to use Com5 and 'most' of it worked - except for the Serial port in Dev - so I just stopped using it and reverted to RealTerm instead - which seems perfectly happy to talk to a photon
I 'assume' that I now need to uninstall everything and then re-install, and I guess I will have to do this every time I need to use my 3D printer.
What I fail to understand is WHY the CLI stuff insists on having its own USB drivers installed - when the FTDI ones do a GREAT job, and don't clash with anything else. Basically it seems to have insisted on taking over Com3 (which had the FTDI driver) and stomping on the drivers in there ???? - why ??. They should really be able to live side-by-side....
So I give up for tonight. Re-ran the zadig app found my photon in DFU mode and installed libusb as directed :-O. Just the same set of errors installing SerialPort 2.0.4 ???
Rebooted and its still just the same.....
Running out of ideas now - this is all way too much of a 'black art'
Any help most welcome - in the morning now though. Basically all photon development grinds to a halt now until I can get this talking again.....
Graham
In case it helps screen is as below.....
C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-cli\node_modules\seria
lport>if not defined npm_config_node_gyp (node "C:\Program Files (x86)\nodejs\no
de_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" co
nfigure --fallback-to-build --module=C:\Users\Graham\AppData\Roaming\npm\node_mo
dules\particle-cli\node_modules\serialport\build\Release\node-v14-win32-ia32\ser
ialport.node --module_name=serialport --module_path=C:\Users\Graham\AppData\Roam
ing\npm\node_modules\particle-cli\node_modules\serialport\build\Release\node-v14
-win32-ia32 ) else (node configure --fallback-to-build --module=C:\Users\Graha
m\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\build\Re
lease\node-v14-win32-ia32\serialport.node --module_name=serialport --module_path
=C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-cli\node_modules\seri
alport\build\Release\node-v14-win32-ia32 )
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack at failNoPython (C:\Program Files (x86)\nodejs\node_modules\n
pm\node_modules\node-gyp\lib\configure.js:114:14)
gyp ERR! stack at C:\Program Files (x86)\nodejs\node_modules\npm\node_module
s\node-gyp\lib\configure.js:69:11
gyp ERR! stack at FSReqWrap.oncomplete (evalmachine.:95:15)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "node" "C:\Program Files (x86)\nodejs\node_modules\npm\nod
e_modules\node-gyp\bin\node-gyp.js" "configure" "--fallback-to-build" "--modu
le=C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-cli\node_mo
dules\serialport\build\Release\node-v14-win32-ia32\serialport.node" "--modu
le_name=serialport" "--module_path=C:\Users\Graham\AppData\Roaming\npm\nod
e_modules\particle-cli\node_modules\serialport\build\Release\node-v14-win3
2-ia32"
gyp ERR! cwd C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-cli\node_
modules\serialport
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd configure --fallb
ack-to-build --module=C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-
cli\node_modules\serialport\build\Release\node-v14-win32-ia32\serialport.node --
module_name=serialport --module_path=C:\Users\Graham\AppData\Roaming\npm\node_mo
dules\particle-cli\node_modules\serialport\build\Release\node-v14-win32-ia32' (1
)
node-pre-gyp ERR! stack at ChildProcess. (C:\Users\Graham\AppData
\Roaming\npm\node_modules\particle-cli\node_modules\serialport\node_modules\node
-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:110:17)
node-pre-gyp ERR! stack at maybeClose (child_process.js:1015:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (child_proces
s.js:1087:5)
node-pre-gyp ERR! System Windows_NT 6.3.9600
node-pre-gyp ERR! command "node" "C:\Users\Graham\AppData\Roaming\npm\node
_modules\particle-cli\node_modules\serialport\node_modules\node-pre-gyp\bi
n\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-
cli\node_modules\serialport
node-pre-gyp ERR! node -v v0.12.7
node-pre-gyp ERR! node-pre-gyp -v v0.6.13
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=C:\Users
Graham\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\bui
ld\Release\node-v14-win32-ia32\serialport.node --module_name=serialport --module
_path=C:\Users\Graham\AppData\Roaming\npm\node_modules\particle-cli\node_modules
\serialport\build\Release\node-v14-win32-ia32' (1)
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files (x86)\nodejs\\node.exe" "C:\Program Files (
x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "particle-cli"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! serialport@2.0.4 install:
node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the serialport@2.0.4 install script 'node-pre-gyp install --f
allback-to-build'.
npm ERR! This is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR! npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Windows\system32\npm-debug.log
C:\Windows\system32>