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

31.0.x/dev build: No messages in "Notifications" on first boot #611

Open
spiderkeys opened this issue Jan 6, 2017 · 2 comments
Open

31.0.x/dev build: No messages in "Notifications" on first boot #611

spiderkeys opened this issue Jan 6, 2017 · 2 comments
Labels

Comments

@spiderkeys
Copy link

Steps and observations:

  1. Burned latest dev image
  2. Waited for the first reboot (sysdetect installing dt overlays)
  3. SSH'd in
  4. Immediately ran top and saw that there was a firmware build in progress. This is proper.
  5. Opened cockpit a few minutes later after all of the firmware build/flash steps had been completed.
  6. No notification messages were waiting for me to indicate that a firmware build/flash had taken place
  7. Subsequent builds seemed to behave properly if I started them from the diagnostics window (all log messages came up, as well as notifications)
@BrianAdams
Copy link
Contributor

Is it possible that the system was only checking to see if firmware updates were needed? It won't trigger the update notifications unless the statemachine actually tries to build or push the firmware.

@spiderkeys
Copy link
Author

No, currently fresh images always build the firmware the first time they come up, as there is no existing build file (/opt/openrov/system/config/lastBuildHash) with a "last hash" to compare against. Also, I watched the compiler and avrdude running in top at first boot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants