Before posting on this section, take a look at the following troubleshooting infos that may save you some struggling.
[WIN] Cannot upload ("…arduino101load": CreateProcess error=2, The system cannot find the file specified)
Some antivirus recognize arduino101load utility as a virus. This is clearly a false positive and you shouldn’t worry about it (all files are signed and any compromised binary would be stopped by the IDE). To avoid this, check your AV quarantine folder and give grants to arduino101load utility. If your AV doesn’t automatically restore the file in its previous location, uninstall and reinstall the Curie core from Board Manager to restore the functionality
[OSX/LINUX] Error 74 on dfu-utils upload
If arduino101load is unable to upload due to “error 74”, please replace “arduino101load” binary (you can get the location by turning on “Verbose upload”) with this file. This is useful also for users on OSX 10.8 or older, because golang dropped the support for that OS. Remember to mark the script as executable after copying it in the correct location.
[ALL OS] CurieBLE, CurieBle, BLE libraries confusion
Some examples you could find on the web still use CurieBle API conventions. while very similar to official CurieBLE ones; porting is pretty easy and most of the times you obnly need to modify the “#include” so it uses the “capital” version. BLE library is instead the ongoing effort to add Central role APIs. No instruction or official APi will be published before the actual release of the updated library to avoid confusion (so if you track Github master you’ll probabily need to rewrite consistent parts of your sketch)
[WIN] Drivers installation issues
If the driver installation fails (ARDUINO 101/GENUINO 101 with a red cross), please install the root certificate for the drivers using this instructions.
The problem should only appear on a fresh Windows7 (or if Windows updates are disabled)
[WIN XP] Drivers are not automatically installed
- Open a command prompt (Win key + R, the type cmd) and go to “C:\Documents and Settings<username>\Local Settings\Application Data\Arduino15\packages\Intel\tools\arduino101load\1.6.4+1.18\drivers”
Once there, run
[b]dpinst-x86.exe /lm /sa /sw /se /f /path [/b]
- If the hardware Wizard comes up, have it “install from a specific location”:
C:\Documents and Settings<username>\Local Settings\Application Data\Arduino15\packages\Intel\tools\arduino101load\1.6.4+1.18\drivers
Reset the board using MASTER_RESET button to make sure Windows loads the drivers the remaining drivers - you may have to go through Hardware Wizard one more time.
[WIN] Uploading issue: Cannot open DFU device 8087:0aba
If the board stucks during upload and this message is displayed, please execute the following steps
- connect the board to another USB port (USB3 ports has been reported to behave more reliably)
- connect the board and press MASTER_RESET; keep pressing it once every 3 seconds until the drivers get installed correctly. From now on the upload will work as expected
[WIN] Upload fails with FINDSTR: cannot open
The current uploader for 101 has a bug for paths with spaces in them. Intel has already fixed it but they haven’t released an updated core.
To fix manually, go into
C:\Users\yourUsername\AppData\Local\Arduino15\packages\Intel\tools\sketchUploader\1.6.4+1.14/clupload/ and replace
cluploadArduino101_win.sh content with this one
Solved with core 1.0.5
[OSX] Uploading issue: Cannot open DFU device 8087:0aba
It seems that this problem is originated by a faulty driver for the internal Bluetooth adapter you can find in some Macbook. To solve it, download this file , extract it and then copy
This method is still in testing so please report if it works in your environment
[Linux] Uploading issue: Cannot open DFU device 8087:0aba
If you see this, you probably miss an udev rule to access the 101 without being root. Execute
sudo ~/.arduino15/packages/Intel/hardware/arc32/2.0.2/scripts/create_dfu_udev_rule, log out and login again to get the correct permissions