tree: 3438f1adcc30c980952e8cc2ab26939717f89db3 [path history] [tgz]
  1. OWNERS
  2. README.md
  3. curve25519.c
  4. curve25519.h
  5. curve25519_unittest.cc
  6. dbus/
  7. dbus_wrapper.cc
  8. dbus_wrapper.h
  9. docs/
  10. fmap_utils.cc
  11. fmap_utils.h
  12. hammer_updater.cc
  13. hammer_updater.h
  14. hammer_updater_unittest.cc
  15. hammerd.gyp
  16. hammerd_api.cc
  17. hammerd_api.h
  18. hammerd_api_wrapper.py
  19. init/
  20. main.cc
  21. mock_dbus_wrapper.h
  22. mock_fmap_utils.h
  23. mock_pair_utils.h
  24. mock_update_fw.h
  25. mock_usb_utils.h
  26. pack_firmware.sh
  27. pair_utils.cc
  28. pair_utils.h
  29. pair_utils_unittest.cc
  30. process_lock.cc
  31. process_lock.h
  32. udev/
  33. uma_metric_names.h
  34. update_fw.cc
  35. update_fw.h
  36. update_fw_unittest.cc
  37. usb_utils.cc
  38. usb_utils.h
hammerd/README.md

hammerd: A daemon to update hammer

Summary

hammer is the base of detachable, connected via USB over pogo pins. hammer runs its own upgradable firmware (base EC, running EC codebase on STM32F072), is attached to a touchpad (with its own upgradable FW), and is able to pair with the detachable.

We need a userspace daemon, running on the AP, that does the following things related to hammer:

  • Waits for a base to be attached on detachable's pogo pins port, and then performs the following tasks as required.
    • Base EC FW update
    • Base touchpad FW update
    • Base pairing
    • Tell base to increment its rollback counter (if necessary)
    • Interaction with Chrome:
      • Shows notification during update (EC+touchpad)
      • Shows notification that a new base is connected (pairing)