Spark V3 not working out the box

Hi,

Have just received my new v3 but when booting it up for the first time it has a black screen and a constant flashing blue light. from my understanding it should boot up in test mode. is this a firmware issue?

Thanks!!

Maybe we accidentally shipped it without programming it first.

If you follow the BrewBlox install guide at brewblox.netlify.com you will flash it yourself just like we should have done already.

After the flash, you probably also have to run “brewblox-ctl bootloader” before it will start normally.

WiFi can be configured from the web interface on the spark page while it is still connected with USB.

thanks for the quick reply

will give it a go

Thanks!!

have flashed the unit and now the blue light is flashing at a slower pace and i have 6 unassigned boxes on the screen.
have tried running the bootloader but seems to be failing

error is showing
Command ‘docker run -it --rm --privileged -v /dev:/dev brewblox/firmware-flasher:edge flash-bootloader’ returned non-zero exit status 1.

thanks

Power cycle the spark (unplug, plug), then run the following commands:

brewblox-ctl particle
particle usb safe-mode
bash ./flash-bootloader
exit

This will put the Spark in safe mode before flashing the bootloader.

still seem to be having the same issue.

this is what i am getting

pi@raspberrypi:~/brewblox $ brewblox-ctl particle
Please press ENTER when your Spark is connected over USB
INFO Pulling flasher image…
edge: Pulling from brewblox/firmware-flasher
Digest: sha256:ac8c5180d4f4cb9adbe39587b39caf1df99ed1e5b13341225ded750866c244c2
Status: Image is up to date for brewblox/firmware-flasher:edge
docker.io/brewblox/firmware-flasher:edge
INFO Stopping services…
Removing network brewblox_default
WARNING: Network brewblox_default not found.
INFO Starting Particle image…
INFO Type ‘exit’ and press enter to exit the shell
bash-5.0# exit
exit
pi@raspberrypi:~/brewblox $ brewblox-ctl bootloader
Please press ENTER when your Spark is connected over USB
INFO Pulling flasher image…
edge: Pulling from brewblox/firmware-flasher
Digest: sha256:ac8c5180d4f4cb9adbe39587b39caf1df99ed1e5b13341225ded750866c244c2
Status: Image is up to date for brewblox/firmware-flasher:edge
docker.io/brewblox/firmware-flasher:edge
INFO Stopping services…
Removing network brewblox_default
WARNING: Network brewblox_default not found.
INFO Flashing bootloader…
Request timeout
Command ‘docker run -it --rm --privileged -v /dev:/dev brewblox/firmware-flasher:edge flash-bootloader’ returned non-zero exit status 1.

You seem to immediately exit the Particle container.
The idea is to start it - it will then display the prompt that you can exit by typing exit. Don’t do that immediately.
In the Particle container, run

particle usb safe-mode
bash ./flash-bootloader

After that is done, exit by typing exit and pressing enter.

thanks

still seems to be timing out.

pi@raspberrypi:~/brewblox $ brewblox-ctl particle
Please press ENTER when your Spark is connected over USB
INFO Pulling flasher image…
edge: Pulling from brewblox/firmware-flasher
Digest: sha256:ac8c5180d4f4cb9adbe39587b39caf1df99ed1e5b13341225ded750866c244c2
Status: Image is up to date for brewblox/firmware-flasher:edge
docker.io/brewblox/firmware-flasher:edge
INFO Stopping services…
Removing network brewblox_default
WARNING: Network brewblox_default not found.
INFO Starting Particle image…
INFO Type ‘exit’ and press enter to exit the shell
bash-5.0# particle usb safe-mode
Request timeout

am i doing this correctly?

Yes. You’re just running into an issue with the underlying system libraries. We’ll be releasing a fix for it in the next few days, but until then it’s rather annoying.

You can manually put the system in safe mode:

  • Do not exit the particle image.
  • Get two tooth picks (or something else slim and pointy)
  • There are two buttons sunk into the right side of the spark. Top right is SETUP, and bottom right is RESET.
  • Hold down both buttons, then release RESET while still holding down SETUP.
  • When the led blinks magenta, also release SETUP. The led should now turn to solid magenta.
  • Now run bash ./flash-bootloader in the particle image.

i have released SETUP while flashing magenta but now it is flashing blue. what shall i do?

If you saw those 6 boxes, it is already running.
You don’t need the bootloader update.

@bob, bootloader fail is because of the listening mode bug that I just reported at particle. But it only occurs when the app is already running and a bootloader flash is not needed.

Just proceed with the guide. Skip WiFi setup and do that from the UI later.

ok… so what shall i do now? i have now lost the the boxes and have a fast flashing blue light

After power cycle you’ll be back at slow blue. That’s just no WiFi configured. It will work over USB. Set up WiFi later from the browser.

If needed, run brewblox-ctl flash again, in case you wiped the Brewblox app with a factory reset.

ok now back to 6 boxes and slow blue light. should it now be in test mode? how do i get to the browser, when typing in the ip address of the pi it takes me to a brewpi setup page, is this correct?

Test mode was something in BrewPi, not Brewblox.

You should not follow a BrewPi install guide, but the Brewblox guide on netlify.

If you followed the BrewPi guide, I would start fresh putting raspbian on the pi and follow the getting started guide for BrewBlox.

After the getting started guide you can use the one of the wizards in the web interface to configure the spark for your process.

ok thanks will start again and follow the Brewblox guide, when does the BrewPi firmware come in to play?

Never. Brewblox fully replaces BrewPi, including the firmware. We will change our branding soon and will officially release Brewblox as a platform.

thanks all working now

1 Like