Greetings from Norway,
I had my Spark v2 running for some year and working ok. It was then flashed with “Controller firmware: baa3a201 (2022-01-21)”. After a year off brewing I tryed to apt-get update/upgrade and brewblox update.
Both apt-get and update works fine, but no luck with brewblox-ctl flash. It stopped with “No compatible USB devices found”.
I change the cables and it also seems that it been found in the commands I found in this forum.
What could be wrong/next step for search?
I just pushed a fix today to increase the timeout waiting for the DFU trigger after helping someone else resolve this.
We trigger DFU mode, but after that, the particle CLI hangs. As a workaround, we killed the process after 3 seconds. I increased this to 10 now.
If it still doesn’t work after updating, try this:
brewblox-ctl particle
This opens a bash shell in a container with the particle cli.
particle usb dfu
Wait for your spark to go into DFU mode (screen goes white, led blinks orange). Press ctrl-c and type exit to leave the container.
The run brewblox-ctl flash
Hi Elco, and this was magic!
It did the commands and a new flash, and have now the new “Controller firmware: 87cb8c22 (2024-10-07)” successfully.
Thank you for fast reply, awesome ! 
And thank you again for the solution. Now I can prepare a brew for x-mas…
Hi there,
I am having a similar issue. Current setup is a Raspberry Pi 4, running off of a SATA SSD (recent upgrade - as I got tired of SD issues).
Did a fresh install (fully updated, etc.) of brewblox on an out of the box SSD and the flash is failing for my Spark V2 as follows:
I even tried the suggested: brewblox-ctl particle → particle usb dfu and as you can see it timed out, I’ve done it now a few times same result.
The spark screen shows the last program I had on it from months ago, still running it, nothing changed.
You can also trigger DFU mode by holding the setup button during reset until the led blinks yellow. Then try running brewblox-ctl flash again.
Okay, thanks for the quick reply. Originally, I wasn’t sure what you meant, but searched a bit and I figured it out.
Okay, I just got the device to flash properly now, but after that, it had the blinking blue led.
I proceeded to run the “brewblox-ctl particle -c flash-bootloader” command since it kept blinking blue and it failed with the following:
INFO Starting Particle image …
INFO Type ‘exit’ and press enter to exit the shell
edge: Pulling from brewblox/brewblox-firmware-flasher
Digest: sha256:4432cefaf63d6d5a2684edd2271c9e361d9d0837761d19f3b87ae327b663aec0
Status: Image is up to date for Package brewblox-firmware-flasher · GitHub
Flashing Photon bootloader…
:::: NOTICE:
:::: Your first flash may take up to 10m to complete - during
:::: this time, your device may regularly change LED states
:::: as Device OS upgrades are applied.
NOTE: particle flash serial has been replaced by particle flash --local.
Please use that command going forward.
Error listing serial ports: spawn udevadm ENOENT
ERROR CalledProcessError(Command ‘docker run -it --rm --privileged -v /dev:/dev --pull always Package brewblox-firmware-flasher · GitHub flash-bootloader’ returned non-zero exit status 1.)
ERROR
Ok, I don’t know the exact cause for the failure above, but I did manage to resolve the issue and comeplete the setup. I got to the point where the bootloader needed updated, but it was failing in the, CLI as shown above.
I realized I might never have setup the wifi for my Photon, or at a minimum, my wifi network name has changed (at least once) since I set this thing up initially years ago. I found that the Particle app is still up on the iOS store, so I setup the wifi with that, then I completed the setup and added the new service, etc.
Ran a few tests and all is working now. Thanks!
Awesome, sorry that I forgot to reply.
If the photon has wifi, it will download the system update from the particle cloud.
