NEQTO Docs
  • Languages iconEnglish
    • 日本語
  • Docs
  • API
  • FAQ

›Software Specifications

Getting Started

  • NEQTO Hello World!
  • Tutorial Step 1. NEQTO Console Setting
  • Tutorial Step 2. Device Settings & Launching Service (NEQTO Bridge)
  • Tutorial Step 2. Device Settings & Launching Service (STM32 Discovery)
  • Tutorial Step 2. Device Settings & Launching Service (SPRESENSE)
  • Tutorial Step 3. Application development using scripts

NEQTO

  • NEQTO Account Registration
  • Sub-accounts
  • API Usage
  • NEQTO CloudSync for GCP
  • NEQTO Engine Firmware List
  • Support Guidelines

NEQTO Console

  • Introduction
  • Fundamentals
  • Administrative Actions
  • Device Management
  • Linux-based Device Management
  • Batch Registration
  • Scripts
  • Actions and Contacts
  • View Data from the Console
  • NEQTO Apps

    • About NEQTO Apps
    • NEQTO Infinitypool
    • NEQTO Insights
    • NEQTO Custodia
    • NEQTO Flow
  • Machine Driver
  • Recommended Browsers
  • Billing Information

SPRESENSE

    Hardware Specifications

    • 01. About Spresense

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. Spresense Wi-Fi Initial Setup
    • 04. Spresense LTE-M Initial Setup
    • 05. Debug Log Acquisition
    • 06. System LED Indications
    • 07. Event Messages
    • 08. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. GPIO
    • 12. UART
    • 13. SPI
    • 14. I2C
    • 15. ADC
    • 16. GNSS
    • 17. Camera
    • 18. Utils
    • 19. nqSpresense
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte

STM32 Discovery

    Hardware Specifications

    • 01. About STM32 Discovery Kit (B-L4S5I-IOT01A)

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. STM32 Discovery Wi-Fi Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 18. Utils
    • 19. nqDiscovery
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi

NEQTO Bridge

    Hardware Specifications

    • 01. NEQTO Bridge Module
    • 02. NEQTO Bridge Wi-Fi Module
    • 03. NEQTO Bridge LTE-1 Module
    • 04. NEQTO Bridge LTE-M/NB Module
    • 05. NEQTO Bridge IO Board
    • 06. NEQTO Bridge Digital IO Board
    • 07. NEQTO Bridge Connector Board

    Software Specifications

    • 01. Operational Flow
    • 02. NEQTO Bridge Wi-Fi Module Initial Setup
    • 03. NEQTO Bridge LTE Module Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 17. BLE
    • 18. Utils
    • 19. nqBridge
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte
    • 25. nqLAN
    • 26. nqEx

Linux-based device

    Software Specifications

    • 01. System Requirements
    • 02. Installation
    • 03. Software Configurations
    • 04. Operational Flow
    • 05. Debug Log Acquisition
    • 06. Event Messages
    • 07. Updating Software

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. RTC
    • 10. UNIXSocket
    • 11. FileSystem
    • 12. SubProcess
    • 13. Utils
    • 14. nqLinux
    • 15. nqService
    • 16. nqMqtt
    • 17. nqFOTA
    • 18. nqLAN

neqto.js Libraries

  • About neqto.js Libraries
  • UART

    • GM65 Barcode Reader
    • SRF Ultrasonic Range Finder - Serial Mode

    I2C

    • HTS221 v2 Temperature and Humidity Sensor
    • LIS2DW12 v2 Accelerometer
    • SRF Ultrasonic Range Finder - I2C Mode
    • [Archive] HTS221 Temperature and Humidity Sensor
    • [Archive] LIS2DW12 Accelerometer

    Utils

    • RTC Alarm Synchronized Scheduler

    Integration

    • AWS S3 v2
    • AWS IoT Core v2
    • Azure IoT v2
    • GCP IoT Core
    • [Archive] AWS S3
    • [Archive] AWS IoT Core

neqto.js Snippets

  • About neqto.js Snippets
  • DataDog
  • Dropbox
  • Google Sheets
  • InfluxDB
  • Oracle Cloud Object Storage
  • Salesforce
  • SAP Cloud Platform Internet of Things
  • Splunk
  • Niagara

Release Notes

  • NEQTO Console Updates
  • NEQTO Firmware (Bridge Wi-Fi/LTE Module) Releases
  • NEQTO Firmware (STM32 Discovery Wi-Fi) Releases
  • NEQTO Firmware (Spresense Wi-Fi/LTE-M) Releases
  • NEQTO Engine for Linux Releases

08. Updating Firmware

The SPRESENSE (hereafter "device") firmware can be updated by executing a command from the NEQTO Console.
The process of firmware update (called "FOTA") is as follows:


1. Node Settings

Check the settings of the target node for FOTA.

Select the "Nodes" tab in NEQTO Console's navigation menu.

Select the Settings icon in the row of the node that you wish to perform a FOTA on.

Note the template assigned to the node.



2. Template Settings

Specify the firmware to be applied in the template.

Select the "Templates" tab in NEQTO Console's navigation menu.

On the templated you noted earlier, click the Settings icon.

Make sure the Firmware Type setting is correct. Then, select the desired firmware version from the "Firmware Version" dropdown. Hit "Save" to save your changes.



3. Sending a FOTA

From the yellow control center menu, select the FOTA command.

IMPORTANT

When performing a FOTA execution, please note that the FOTA execution may fail, or the FOTA execution may cause your device to fail.

It takes approximately 3-5 minutes for a FOTA command execution to begin and complete, assuming a stable connection and environment.
Depending on factors such as connection strength or stability, this time may be shorter or longer.
It is recommended that FOTA be performed for devices in areas with strong, stable Internet connections.

  • Be careful not to touch the power cord during FOTA execution.

  • Do not turn off the device until the FOTA is complete.

  • If your device is being powered by a battery, it is recommended to only perform FOTA after the battery has been fully charged.

  • The device will restart during FOTA execution. If you are using User Console mode, it will not restart in User Console mode.

3.1 About the Different FOTA Commands

There are two types of FOTA commands: "FOTA" and "FOTA on Next Boot".

  • The FOTA command interrupts the program running on the device, and begins the FOTA execution immediately.

  • The FOTA on Next Boot command queues the FOTA command to be run the next time that the device restarts.

3.2 Node FOTA and Template FOTA

The FOTA command can be dispatched to all nodes attached to a template, or to any individual node.

  • If the FOTA command is executed on a template, all nodes using the same template will be updated to the template's selected firmware version.

  • If the FOTA command is executed on a node, just that node will be updated.



4. FOTA Execution

The progress of the FOTA command execution can be monitored from the "Recent Events" area on NEQTO Console, and by watching the device's LED patterns.

4.1 Recent Events

Check the "Recent Events" area on a node's page. Click on the name of the desired node on the Nodes page.

Immediately after the FOTA command is received by the device, it sends the "Running FOTA..." message.

After that, there are several FOTA-related messages that will be sent.
For more details, refer to the Event Messages page.

When the FOTA command execution has completed, the device will send the "FOTA OK (version xx.xx.xx)" message, and it will show up in the log.
After this, the device will restart, and resume normal operation.

4.2 System LEDs

The progress of the FOTA command can also be tracked by watching the LEDs on the device.

When a FOTA begins, the blue LED (LED2) blinks rapidly.
After that, they will follow the patterns seen on the System LED page.

When the FOTA command execution has completed, the device will restart and resume normal operation.



Updated: 2021-08-13
← 07. Event Messages01. About neqto.js →
  • 1. Node Settings
  • 2. Template Settings
  • 3. Sending a FOTA
    • 3.1 About the Different FOTA Commands
    • 3.2 Node FOTA and Template FOTA
  • 4. FOTA Execution
    • 4.1 Recent Events
    • 4.2 System LEDs
AboutNewsProductsFAQPrivacy Policy}
NEQTO Console
IntroductionFundamentalsAdministrative ActionsDevice Management NEQTO Apps
NEQTO Bridge
NEQTO Bridge ModuleNEQTO Bridge Wi-Fi ModuleNEQTO Bridge LTE-1 ModuleError Logging Event Messages
API Documentation
API UsageGlobal APIRegional APIAPI Terms of Service
Jigsaw, Inc.
© 2023 JIG-SAW INC.