The document discusses considerations when taking a firmware prototype to a product. It recommends: 1) Not optimizing code too soon, but only when needed to meet requirements or for economic benefits. 2) Knowing tools like compilers, assembly code, and optimization techniques. 3) Considering software licensing for open source code used in commercial products.

1. Eric Weddington
Marketing Manager,
Open Source & Community
Atmel
@eric_weddington
Board Building

2. Firmware: Prototype to Product
Eric Weddington
Marketing Manager, Open Source & Community

5. Complementary Disciplines

6. Prototype Stage
“Premature optimization is the root of all evil.”
– Donald Knuth, Professor Emeritus of the Art of Computer Programming at Stanford
University

7. When should I optimize my code?
• To meet system requirements and constraints…
–Time
–Space
–Quality
• Or, for a possible economic benefit…

8. Think Scale

9. Why think about Scale? Do the math…
• Spend $100,000 on engineers and tools…
• To save 100 bytes of code space…
• To go to a smaller chip, with less memory…
• That costs 10 cents less.
• But, if you sell 10 million units…
• You just saved $1,000,000…
• Minus engineering/tool costs: $900,000.

10. Know Your Tools
• Compiler toolchain is very good, but not perfect…
• Learn to inspect the assembly code
• Compiler switches
• Coding tips and tricks
• Knowing your computer language
• Knowing data structures / algorithms
• White papers available
• User forums available

11. Open Source Software Licensing
• Using Open Source Software in commercial products
• Do I want my code to be open to every one?
• Can I use this code without burdens on myself, or
customer, when I distribute my product?
• Answers depends on intent of project / product.

12. Firmware: Prototype to Product
1. Don’t optimize too soon
2. Optimize when needed
– To meet system requirements
– Possible economic benefits
1. Know your tools
2. Software licenses matter