Incompatibilities with Spark CLI 1.2.0

[nebrius]

When running Spark CLI 1.2.0, the only version that worked for us at JSConf, we had to flash voodoo spark with spark flash [id] voodoo, which is an older version of VoodooSpark. Our installation instructions are at https://github.com/opheliasdaisies/nodeboats-jsconf2015.

When we flash the latest version straight from GitHub, we would get a 404 error very quickly (less than a second after startup). This error came from the call that spark-io makes to get the device info (not from a voodoospark call).

This doesn't really make sense, but it's what we observed ¯_(ツ)_/¯.

This issue is mostly to track the problems we ran into that wasn't purely Spark Core based.

[nebrius]

cc @Resseguie

[rwaldron]

Thanks for the report!

[blackjk3]

@bryan-m-hughes I also noticed this issue. I have a Photon which needs a newer version of the cli for "particle setup" to work. It looks like an issue with voodospark and the "endpoint" action results in a 404. I saw some people suggest that I flash with the lastest version of voodospark but that ended in a trail of errors. I would love to help out but i'm not really sure where to proceed from here.

[nebrius]

@rwaldron do you have a photon yet? I don't, and without one in hand, I couldn't test and say what's going on.

On an unrelated note: here's why we had to use an old version of the Spark CLI: particle-iot/particle-cli@a5ae0db

[rwaldron]

I do, but when I first got it there was no cli that worked for it yet and I didn't have time resources to try and figure it out out. I just tried flashing voodoospark to the photon that I have and it doesn't work:

$ particle flash 53ff71066667574841202467 firmware-latest.bin
Including:
    firmware-latest.bin
attempting to flash firmware to your device 53ff71066667574841202467
flash device said  {"ok":false,"errors":[{"error":"Timed out."}]}

And...

$ particle flash --usb firmware-latest.bin
Apparently I didn't find a DFU device? util said  dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Deducing device DFU version from functional descriptor length
Found Runtime: [05ac:8286] ver=0148, devnum=6, cfg=1, intf=3, alt=0, name="UNKNOWN", serial="UNKNOWN"

Error writing firmware... no dfu device found.

I see Photon-E5AF in my wifi networks and the particle setup claims to have completed successfully. I have no idea what's going on.

On an unrelated note: here's why we had to use an old version of the Spark CLI: particle-iot/particle-cli@a5ae0db

I don't quite understand what that change means for Spark CLI...?

[nebrius]

The cli command setup first queries to see what devices are available. They forgot to rename the device in this one single place when they renamed the company (it's technically the Particle Spark Core, not Particle Core), so the CLI basically said I have no idea what "Core" is. It isn't "Spark Core", "Photon", or "Electron", and just gave up immediately.

[nebrius]

Oh, so the DFU thing...you have to hold down the reset and mode button, then release the reset button, and wait until it's flashing yellow (not flashing white) to put it in DFU mode (takes many seconds). Then that command should find it.

[rwaldron]

so the CLI basically said I have no idea what "Core" is. It isn't "Spark Core", "Photon", or "Electron", and just gave up immediately.

Wow.

Oh, so the DFU thing...you have to hold down the reset and mode button, then release the reset button, and wait until it's flashing yellow (not flashing white) to put it in DFU mode (takes many seconds). Then that command should find it.

$ particle flash --usb firmware/voodoospark.cpp
Found DFU device 1d50:607f
Apparently I didn't find a DFU device? util said  dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Deducing device DFU version from functional descriptor length
Found Runtime: [05ac:8286] ver=0148, devnum=6, cfg=1, intf=3, alt=0, name="UNKNOWN", serial="UNKNOWN"
Found DFU: [1d50:607f] ver=0200, devnum=13, cfg=1, intf=0, alt=1, name="@DCT Flash   /0x00000000/01*016Kg", serial="00000000010C"
Found DFU: [1d50:607f] ver=0200, devnum=13, cfg=1, intf=0, alt=0, name="@Internal Flash   /0x08000000/03*016Ka,01*016Kg,01*064Kg,07*128Kg", serial="00000000010C"

checking file  firmware/voodoospark.cpp
spawning dfu-util -d 1d50:607f -a 0 -i 0 -s 0x08005000:leave -D firmware/voodoospark.cpp
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 1d50:607f
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "Internal Flash   "
Downloading to address = 0x08005000, size = 20502
dfu-util: Last page at 0x0800a015 is not writeable
Error writing firmware...

I can't spend any more time on this tonight. It's 8 o'clock and I have to start dinner for my wife and I soon

[nebrius]

You and your silly eastern time zone ;-) Enjoy dinner!

[blackjk3]

@rwaldron haha, yeah I had to make dinner for my wife and 3 year old as well. Anyway, originally I flashed it successfully with $ particle flash device_id voodoo which worked. (At least flashed magenta, then breathing cyan) But then when I tried running anything it's a 404 error. Until jsconf, I had always flashed code written in C/C++ so I apologize for not really knowing what i'm doing :)

[Resseguie]

@bryan-m-hughes with that "Core" -> "Spark Core" fix in on the CLI, the latest works with the Spark Core now?

But something still not right with Photon? Am I tracking correctly?

Hopefully I'll get my Photon soon so I can help test.

[nebrius]

@Resseguie that is my understanding, but admittedly I have not tested since the cli fix I referenced was landed, so I can't say with any confidence.

[blackjk3]

@bryan-m-hughes confirmed! The core works with the cli fix referenced above.

However, the Photon throws this error right away.

★  node bot-start.js
Device(s) spark-io
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: Unable to connect to spark cloud.: code: 404
    at IncomingMessage.<anonymous> (/node-rolling-spider/node_modules/particle-io/node_modules/spark-io/lib/spark.js:282:19)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickDomainCallback (node.js:381:11)

[blackjk3]

Ok, I got it to work! The issue was voodoospark and the setup() method. It worked on the core but bombed on the photon. With this patch I got it to work on both. I tested 2 cores and 2 photons. voodootikigod/voodoospark#45