[SOLVED] Connect WiFi / Firmware Update - no go (Photon, Windows 10, Totolink)

Hello All,

I am new to the forum.
I am trying to get my Photon to connect to the cloud and claim it. I have checked through various searches on the forum but with no luck.

What I have tried:

  • iOS app setup - stucks at blincking green (WiFi connection)
  • CLI particle update - cannot get status error
  • CLI particle serial wifi - fast blinking cyan (Cloud connection) with occasional red / yellow blink
  • CLI particle setup - same as above
  • CLI particle cloud claim <my photon id> - some error mentioning Object object
  • CLI particle serial mac - ! serial: Error: Unable to find mac address in response
  • CLI particle identify - returns only id of the device - no firmware version

WiFi setup:
Router Totolink A2004NS
Channel 11 ( 2.462 GHz,Upper,40 MHz ) Region Europe
WPA2PSK + AES(CCMP)
WiFi password has 62 characters but I have also tried unencrypted version with the iOS app - result was the same.

I am out of ideas at the moment - please help. :smile:
First impression of the Photon / SDK / Setup is kind of frustrating…

Best Regards

Can you post the output?

To cure this you’d usually do the following in DFU Mode (yellow blinking)

particle keys server
particle keys doctor <yourDeviceID>

I have just tried to perform the particle update from my office mac. The output is the same:

Dariuszs-MacBook-Pro:StandUpSmart-Android dariuszseweryn$ particle update

> Your device is ready for a system update.
> This process should take about 30 seconds. Here goes!


! An error occurred while attempting to update the system firmware of your device:

dfu-util: Invalid DFU suffix signature

dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!

dfu-util: Error during download get_status


> Please visit our community forums for help with this error:
https://community.particle.io/

In the office when using direct serial connection (no CLI) I was able to get a quick blinking cyan without red / yellow blinks. Still no connection to the cloud.

When I have performed particle keys server - output:

Dariuszs-MacBook-Pro:StandUpSmart-Android dariuszseweryn$ particle keys server
Found DFU device 2b04:d006
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 2082 -D /usr/local/lib/node_modules/particle-cli/keys/rsa.pub.der
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

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 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "DCT Flash   "
Downloading to address = 0x00000822, size = 512
Download	[=========================] 100%          512 bytes
Download done.
File downloaded successfully
Okay!  New keys in place, your device will not restart.

After that I have used particle keys doctor 2b04:d006 (ID from the previous command) and I got the connection to the cloud and I was able to claim the device through the build.particle.io though the ID I specified was apparently not correct as it stated in the output:

Dariuszs-MacBook-Pro:StandUpSmart-Android dariuszseweryn$ particle keys doctor 2b04:d006
***************************************************************
   Warning! - device id was shorter than 24 characters - did you use something other than an id?
   use particle identify to find your device id
***************************************************************
Found DFU device 2b04:d006
Found DFU device 2b04:d006
New Key Created!
Found DFU device 2b04:d006
Found DFU device 2b04:d006
Unable to generate public key from the key downloaded from the device. This usually means you had a corrupt key on the device. Error:  { Error: Command failed: openssl rsa -in backup_rsa_2b04:d006_rsa_new.der -inform DER -pubout -out backup_rsa_2b04:d006_rsa_new.pub.pem
unable to load Private Key
57478:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/asn1_lib.c:153:
57478:error:0D068066:asn1 encoding routines:ASN1_CHECK_TLEN:bad object header:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/tasn_dec.c:1331:
57478:error:0D06C03A:asn1 encoding routines:ASN1_D2I_EX_PRIMITIVE:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/tasn_dec.c:831:
57478:error:0D094071:asn1 encoding routines:d2i_ASN1_SET:error parsing set element:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/a_set.c:218:address=140596941514608 offset=-1187063664
57478:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/tasn_dec.c:1344:
57478:error:0D06C03A:asn1 encoding routines:ASN1_D2I_EX_PRIMITIVE:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/tasn_dec.c:848:
57478:error:0D08303A:asn1 encoding routines:ASN1_TEMPLATE_NOEXP_D2I:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/tasn_dec.c:768:Field=dmq1, Type=RSA
57478:error:0D09A00D:asn1 encoding routines:d2i_PrivateKey:ASN1 lib:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-64.30.2/src/crypto/asn1/d2i_pr.c:99:

    at ChildProcess.exithandler (child_process.js:206:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:498:12)
  killed: false,
  code: 1,
  signal: null,
  cmd: 'openssl rsa -in backup_rsa_2b04:d006_rsa_new.der -inform DER -pubout -out backup_rsa_2b04:d006_rsa_new.pub.pem' }
Saved!
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 34:leave -D 2b04:d006_rsa_new.der
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

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 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "DCT Flash   "
Downloading to address = 0x00000022, size = 608
Download	[=========================] 100%          608 bytes
Download done.
File downloaded successfully
Saved!
attempting to add a new public key for device 2b04:d006
Error sending public key to server: Permission Denied
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - undefined

Bottomline - I have claimed the device though it may be that it may be not set up correctly. Should I perform particle keys doctor <my_actual_device_id> still?

That last bit is not your device ID. It’s the USB Vendor & Product ID.
You had found your device ID earlier already

Hence I didn’t see the need to explain how you’d get to it :wink:

But now where things should be clear

Absolutely!

@ScruffR Thank you very much for your support!

I am back home and now everything works here as well. I have generated new keys.

I wonder why the app setup did not work for me nor did the firmware update. Nevermind. Thank you again. :smile:

1 Like