particle-iot / spark-server

UNMAINTAINED - An API compatible open source server for interacting with devices speaking the spark-protocol
https://www.particle.io/
GNU Affero General Public License v3.0
442 stars 136 forks source link

DFU failing on raspberry pi #21

Open optikfluffel opened 10 years ago

optikfluffel commented 10 years ago

Hi, I followed your instructions for setting up spark-server on my raspberry pi. Now If I want to get the keys onto the core this happens:

pi@raspberrypi /spark/spark-server/js $ spark keys server default_key.pub.pem 192.168.8.14
Creating DER format file
running openssl rsa -in  default_key.pub.pem -pubin -pubout -outform DER -out default_key.pub.der
checking file  default_key.pub192_168_8_14.der
spawning dfu-util -d 1d50:607f -a 1 -i 0 -s 0x00001000 -D default_key.pub192_168_8_14.der
dfu-util 0.7

Filter on vendor = 0x1d50 product = 0x607f
Cannot open device
Opening DFU capable USB device... Make sure your core is in DFU mode (blinking yellow), and is connected to your computer
Error -

but the core is connected and the yellow LED is blinking + dfu-util -l gives me this:

Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=0, name="UNDEFINED"
Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=1, name="UNDEFINED"

Do you have an idea what's wrong here? Thanks.

kennethlimcp commented 10 years ago

It looks like the driver for the core might have some issue.

Do you have spark-cli on your laptop? You can attempt to copy out the pub.pem file and flash through your laptop

dmiddlecamp commented 10 years ago

Hi @optikfluffel ,

If you see name="UNDEFINED" I think that usually means you need to use "sudo" on your system to access the core via USB DFU. Can you try the command with sudo?

Thanks, David

schwiet commented 9 years ago

I can confirm that I was seeing the same issue and running with sudo solved the problem.

dmiddlecamp commented 9 years ago

Awesome, thanks! :)

Sent from my iPhone

On Dec 24, 2014, at 5:44 PM, schwiet notifications@github.com wrote:

I can confirm that I was seeing the same issue and running with sudo solved the problem.

— Reply to this email directly or view it on GitHub.

KarbonDallas commented 9 years ago

@optikfluffel @schwiet, I'm wondering if this might possibly be an issue with udev rules on linux.

Are either of you still experiencing this problem?