I have been researching a problem I had with a CurieNano I bought from DFRobotics to find I have the same problem with a Genuino 101 I bought from LittleBirdBigE.
In fact, I note all sorts of people are having the same problem.
Problem being it seems there are batches Curie chips, assuming they have firmware pre-installed, are not talking to the Arduino IDE.
So, you can have the problem on Windows 10 and fix it by going to Windows 7. You can have it on Windows 7 and on Windows 10. It pops up when you are using Linux. It matters not if you are using a CurieNano or a Genuino 101. OR one person reports it won’t work on one Genuino board and will on another!!!
Driver disable then re-enable fixes the problem for some, for others it does not.
Manual driver re-install was fix offered by DFRobot but that does not fix the problem for everyone.
Curiously, the problem is the board will fail to upload a file BUT will happily respond to a Board ID request. The Port happily reports Genuino 101 etc. So IDE will talk to board to get board ID but will not upload files.
Reported problem on the console is:
Arduino: 1.6.12 (Windows 10), Board: "Arduino/Genuino 101" Sketch uses 17,628 bytes (11%) of program storage space. Maximum is 155,648 bytes. Starting download script... Flashing is taking longer than expected Try pressing MASTER_RESET button ERROR: Timed out waiting for Arduino 101 on COM11 ERROR: Timed out waiting for Arduino 101 on COM11
So that is, brand new CurieNano from DFRobotics and a Genuino 101 from LBE, straight out of the box, fresh install of Arduino IDE, add curie core, open blink.ino and kaput. Various usb 2.0 ports that work fine with other arduino boards (with same cables) do not work with the curie based devices. I tried a different windows 10 computer, same problem for the CurieNano (still to try the Genuino).
Yes, for the brainiacs who have to ask, reset button was pushed - so what - doesn’t help me nor any other person so not sure why the prompt offers it as a fix.
The salient point is it should work out of the box and doesn’t.
No, no effort has been made to re-bomb the firmware as that would break the warrantee I suspect and won’t guarantee fixing the problem - not to mention that you have to build a ubuntu machine before you can do that and there goes another wasted weekend.
So, Intel or someone needs to come clean.
There is enough evidence this is happening to enough people to be able to factor out the usual complaints.
Has anyone really solved this problem? Not convinced.