Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when flashing an invalid firmware binary (that the device ignores) it should post an event describing why the binary was not applied #1032

m-mcgowan opened this issue Jun 13, 2016 · 1 comment


Copy link

commented Jun 13, 2016

E.g. flashing system binaries in the wrong order, or flashing a binary with an invalid CRC.

The event will help provide some visibility into the system, and help troubleshoot cases when binaries are not being applied, and conversely for success cases, will provide confirmation that a flashed binary will be applied on next reboot.


  • Minimum test case added
  • Device, system and user firmware versions stated
  • Particle confirmed

@m-mcgowan m-mcgowan added this to the 0.7.x milestone Jun 13, 2016

@m-mcgowan m-mcgowan referenced this issue Jun 14, 2016
3 of 3 tasks complete

This comment has been minimized.

Copy link

commented Jul 21, 2016

Spec from a discussion we had about this issue:

  • publish an event when the system has rx'd an OTA image
    • success (include parseable module info of the OTA module updated)
    • failure (reason crc, module dependency (include parseable module info), wrong device type)
    • publish to cloud or reply to YMODEM host
  • add success/fail (with reason) to reset syndrome for when the system reboots and applies an OTA image
  • HELLO message contains OTA_FLASHED_Status_SysFlag, so theoretically the cloud already knows if an OTA update was applied, and can generate an event based on this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.