Core with solid purple

[Wildfire]

Hi all,
After 6 months being busy with other stuff, I thought of a new idea for a particle core project. After a factory reset and connection to the iphone app, the core went into solid purple. I found some others having the same problem and I tried to follow the solutions given, but that didnt help. Think that might be caused by the fact that I dont know what the solution actually is.

I understand that the core is loaded with old firmware and needs to be updated, but this is not possible over wifi and therefore needs to be done via the usb. For this I understand I need the CLI connection.

I followed the instructions on https://docs.particle.io/guide/getting-started/connect/core/#opening-the-command-prompt

BTW, I have a windows 10 64 bit computer.

After giving the command npm install -g particle-cli
I get the following error message:

C:\>npm install -g particle-cli
\
> serialport@2.0.1 install C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport
> node-pre-gyp install --fallback-to-build

(node) child_process: options.customFds option is deprecated. Use options.stdio instead.

C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild --name=serialport --configuration=Release --module_name=serialport --version=2.0.1 --major=2 --patch=1 --runtime=node --node_abi=node-v46 --platform=win32 --target_platform=win32 --arch=x64 --target_arch=x64 --module_main=./serialport --host=https://node-serialport.s3.amazonaws.com/ --module_path=C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\build\serialport\v2.0.1\Release\node-v46-win32-x64 --remote_path=./serialport/v2.0.1/Release/ --package_name=node-v46-win32-x64.tar.gz --staged_tarball=build\stage\serialport\v2.0.1\Release\node-v46-win32-x64.tar.gz --hosted_path=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/ --hosted_tarball=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/node-v46-win32-x64.tar.gz )  else (node  rebuild --name=serialport --configuration=Release --module_name=serialport --version=2.0.1 --major=2 --patch=1 --runtime=node --node_abi=node-v46 --platform=win32 --target_platform=win32 --arch=x64 --target_arch=x64 --module_main=./serialport --host=https://node-serialport.s3.amazonaws.com/ --module_path=C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\build\serialport\v2.0.1\Release\node-v46-win32-x64 --remote_path=./serialport/v2.0.1/Release/ --package_name=node-v46-win32-x64.tar.gz --staged_tarball=build\stage\serialport\v2.0.1\Release\node-v46-win32-x64.tar.gz --hosted_path=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/ --hosted_tarball=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/node-v46-win32-x64.tar.gz )
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:116:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:71:11
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:82:15)
gyp ERR! System Windows_NT 10.0.10240
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--name=serialport" "--configuration=Release" "--module_name=serialport" "--version=2.0.1" "--major=2" "--patch=1" "--runtime=node" "--node_abi=node-v46" "--platform=win32" "--target_platform=win32" "--arch=x64" "--target_arch=x64" "--module_main=./serialport" "--host=https://node-serialport.s3.amazonaws.com/" "--module_path=C:\\Users\\Rutger\\AppData\\Roaming\\npm\\node_modules\\particle-cli\\node_modules\\serialport\\build\\serialport\\v2.0.1\\Release\\node-v46-win32-x64" "--remote_path=./serialport/v2.0.1/Release/" "--package_name=node-v46-win32-x64.tar.gz" "--staged_tarball=build\\stage\\serialport\\v2.0.1\\Release\\node-v46-win32-x64.tar.gz" "--hosted_path=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/" "--hosted_tarball=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/node-v46-win32-x64.tar.gz"
gyp ERR! cwd C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport
gyp ERR! node -v v4.2.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd rebuild --name=serialport --configuration=Release --module_name=serialport --version=2.0.1 --major=2 --patch=1 --runtime=node --node_abi=node-v46 --platform=win32 --target_platform=win32 --arch=x64 --target_arch=x64 --module_main=./serialport --host=https://node-serialport.s3.amazonaws.com/ --module_path=C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\build\serialport\v2.0.1\Release\node-v46-win32-x64 --remote_path=./serialport/v2.0.1/Release/ --package_name=node-v46-win32-x64.tar.gz --staged_tarball=build\stage\serialport\v2.0.1\Release\node-v46-win32-x64.tar.gz --hosted_path=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/ --hosted_tarball=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/node-v46-win32-x64.tar.gz' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\node_modules\node-pre-gyp\lib\util\compile.js:76:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:818:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Windows_NT 10.0.10240
node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Rutger\\AppData\\Roaming\\npm\\node_modules\\particle-cli\\node_modules\\serialport\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport
node-pre-gyp ERR! node -v v4.2.1
node-pre-gyp ERR! node-pre-gyp -v v0.5.19
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd rebuild --name=serialport --configuration=Release --module_name=serialport --version=2.0.1 --major=2 --patch=1 --runtime=node --node_abi=node-v46 --platform=win32 --target_platform=win32 --arch=x64 --target_arch=x64 --module_main=./serialport --host=https://node-serialport.s3.amazonaws.com/ --module_path=C:\Users\Rutger\AppData\Roaming\npm\node_modules\particle-cli\node_modules\serialport\build\serialport\v2.0.1\Release\node-v46-win32-x64 --remote_path=./serialport/v2.0.1/Release/ --package_name=node-v46-win32-x64.tar.gz --staged_tarball=build\stage\serialport\v2.0.1\Release\node-v46-win32-x64.tar.gz --hosted_path=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/ --hosted_tarball=https://node-serialport.s3.amazonaws.com/serialport/v2.0.1/Release/node-v46-win32-x64.tar.gz' (1)
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "particle-cli"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE

npm ERR! serialport@2.0.1 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the serialport@2.0.1 install script 'node-pre-gyp install --fallback-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! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "particle-cli"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! path C:\npm-debug.log.9a36bc39fe7ad6b146be022710be59e4
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall open

npm ERR! Error: EPERM: operation not permitted, open 'C:\npm-debug.log.9a36bc39fe7ad6b146be022710be59e4'
npm ERR!     at Error (native)
npm ERR!  { [Error: EPERM: operation not permitted, open 'C:\npm-debug.log.9a36bc39fe7ad6b146be022710be59e4']
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'open',
npm ERR!   path: 'C:\\npm-debug.log.9a36bc39fe7ad6b146be022710be59e4' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\npm-debug.log

[kennethlimcp]

Try running the command prompt as administrator and install CLI again.

Once that is completed you can do:

• place the core in DFU mode
• particle flash --usb cc3000
• core will blink magenta and eventually revert to magenta
• particle flash --factory tinker
• particle flash --usb tinker
• particle serial wifi

[Moors7]

It seems as if you're missing some dependencies (Python for example). If you'd like to try an easier way to install the CLI, I'd recommend this awesome installer. I'm using it on Windows 10, and it works great for me:

Toolchain for Windows Installer

So, in an effort to make local building easier for people, I put together a basic installer for the Toolchain for Windows. It should download and install GCC Arm, GNU make, and the necessary components of the MinGW toolkit, and add them appropriately to the path. I generally followed @kennethlimcp’s guide here. I tested it on Win 7, so if something doesn’t work, let me know and I’ll try to fix it! This should decrease the number of steps necessary to get up and running with building locally…

[Wildfire]

Unfortunately still stuck
First tried kenneths suggestion but still got the same comment.
Then used the Toolchain. Installed the particle firmware in C:\partic
Then went to C:\partic\ and run make clean all.

I got a lot of text and I dont know what happend or what to do next. My particle
core is unfortunately still purple.