I had the same problem and I couldn't upload code anymore. I took out the board from the housing in order to get to the reset button and followed this procedure: https://www.youtube.com/watch?v=plCxXwiUK-w
I uploaded the Blink scetch which is easy to find. After the succesful upload of the Blink scetch I could upload the CBT firmware again.
@Derek I am running it on OSX Yosemite, npm version 2.7.5, node v0.12.2 and I cloned the latest code today. The problem is the node app starts up when I run: node index.js /dev/cu.usbmodem411
and it returns:
Socket bound: /tmp/cbtbus1
Socket bound: /tmp/cbtbus2
Socket bound: /tmp/cbtbus3
Logging enabled on all three busses
But then it exits, without any error message. It should stay running shouldn't it? The cbtbus1-3 files are created in /tmp.
Somehow, there is a problem in my environment :-/ I tried it with a friend on another OSX machine and it ran fine.
Hi Grayda, the path in of the serial device is not the problem. The node.js app runs and creates the pipe /tmp/cbtbus1 correctly. Also, when the path to the serial device is incorrect, the node.js app won't start, which it does. There seems to be some problem with the rights / access but haven't figured out what.
Derek, I tried Wireshark on Mac, I need to solve one last thing to get it working I thing, any ideas? My findings are described here: