Where can we find the factory reset firmware? Like i know there's V1 and V2 right now and how often are they changed during production?
I would like to use it to test out the factory reset firmware during a factory reset of my core and other stuff like WEP configuration and stuff to catch more bugs
I went down that same route one day like ⌠where is it??? But then realized the only way it works is because itâs in the bootloader:
For factory firmware, the highest number here wins:
However, I would probably go with the latest from compile-server2 bin because the spark_2 build has a really slow OTA process, compared to newer code. Could also try master repo but not all things will be perfect in master.
I downloaded the factory-firmware to the wrong location and ended up at the private key location after missing a 0 in the address. haha!
Now my core goes rapidly blinking yellow.
I tried the CLI 'spark keys doctor core_id' but it says no dfu device found. (i placed the core in dfu mode already)
It's fun when some stuff that I always wanted to try messing around became a real problem that i need to resolve
EDIT:
I did "spark keys new" and spark keys send and it was successful.
BUT im unable to update my private key using
e:\dfu>dfu-util -d 1d50:607f -a 1 -s 0x2000 -v -D core.pem
error is:
Downloading to address = 0x00002000, size = 609
Poll timeout 50 ms
Download from image offset 00000000 to memory 00002000-00002260, size 609
Poll timeout 30 ms
Error during download get_status
Failed to write whole chunk: -7 of 609 bytes
It's fun to mess around with this but well..i'l get some sleep and check your inputs in the morning
Just got the email about this from the forums, not to worry! Itâs the â.derâ file that needs to be copied onto your core, you can do this with the CLI:
spark keys load core.der
The Coreâs dfu interaction has a quirk where the files need to be an even number of bytes, the CLI will pad the key with an extra byte to workaround that. If the CLI isnât finding the core, which would be weird if it shows up with dfu-util -l, try running spark keys new until there is a âderâ file with an even number of bytes, then send and load that key.
Hmm⌠I only have two public keys for your core, the factory key, and one that you uploaded. Didnât you say earlier that you also uploaded one then?
The API wonât insert duplicate keys, so it would be a question of if you had sent different keys multiple times, etc. Glad you got it back up and running! CLI success (sorta)
Thanks! Much appreciated. Which issue on spark-cli should I be looking at, I think the only one updated recently is the âserial wifiâ backwards compatibility issue?