Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Via the Cloud Dashboard

Make sure your hardware is connected to the Cloud and is online. Steps on how set up your device to connect to the cloud server can be found here:
https://deeplocal.atlassian.net/wiki/spaces/GS/pages/37617673/Hardware+Getting+Started+Guide#Creating-Credentials

  1. Log into your Gumband Cloud dashboard (i.e. http://app.gumband.com ) and navigate to your hardware.

  2. Open the “Firmware” tab. Here you can upload and store firmware for your hardware device.


    The “Firmware” page is broken into two sections:

    • The Gumband Firmware section is for the Gumband Core firmware (.gbm0 file types). This will not be frequently used unless migrating to a newer version, or for smaller security and API updates.

    • The User Firmware section is for your code (.gbm4 file types). This is the one you will be interacting with the most!

  3. In the User Firmware section, click Upload then choose the .gbm4 firmware file from your computer/file-system you want to add to the Cloud dashboard. You can assign it a name and file version.

    Note: this “Firmware Version” is only for file management. It does not represent nor affect the User Firmware Version in the the hardware overview, which is set by the device using gumbandSetUserFirmwareVer() in the code.

  4. To update your device with this firmware, select it with the check-box and click Update. This will trigger a firmware update to begin on your device.

  5. Your device’s status LED will pulse green while receiving the updated firmware before restarting to run the new firmware. Uploading the firmware this way will also show up in the Change History with a timestamp.


Via the Gumband Loader

  1. Using the serial configuration interface run the command firmware to have the device get ready for an OTA update. If successful, the device status LED will pulse green and there will be a response from the device.

  2. Using the gumband_loader tool, run the

  • No labels