← Blog

Is it a firmware partner, or a body shop?

Twelve questions about the vendor, agency or contractor writing your firmware, or the one you are about to sign. It takes two minutes. You see the score and the risk points on this page, with or without your email.

  1. You own the repository during the project, and it lives in your own account.
  2. You hold the firmware signing keys, or the contract says how they are handed over.
  3. Every build runs in continuous integration, not only on someone's laptop.
  4. There is a hardware-in-the-loop (HIL) test rig for your board, and you get to keep it.
  5. The test plan is written into the statement of work.
  6. They told you which RTOS they would choose for this product, and what would change their mind.
  7. They have shown you a release they shipped with secure boot and rollback on A/B partitions.
  8. The contract states the notice period and how a ramp-down works in the middle of the project.
  9. The contract assigns you all the IP, including build scripts and test fixtures.
  10. Someone on their side talks to the certification lab, and has done FCC Part 15 or CE/RED before.
  11. The handover includes documentation and an SBOM.
  12. They committed to a time to first commit after signature.

0 of 12 answered

Ready to build with ByteNana?

Initialize your project →