Eric Weddington at Hardware Innovation Summit 2013


Published on

The 1-1/2 day event kicks off with a VC panel, "Pitch Your Prototype," and "Getting Started, case studies of maker pros with early stage products. The Innovation Showcase follows, a unique opportunity to casually engage with over two dozen makers who have their cutting-edge products and devices on display. Creating an almost magical atmosphere where hardware innovation and creative genius generates spirited ideation, the Innovation Showcase is not to be missed.

Wednesday was an all-star lineup with over 30 speakers representing leading entrepreneurs and thought leaders at the forefront of the maker movement. Investors, industrial designers, product development teams - anyone looking for insight into the early stage companies with the potential to change the global business landscape - should attend.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Introduction Confession / secret
  • Story about Embedded Systems Meetup group in Colorado Springs: Making a camera trigger to photograph lightning.
  • Compiler switches: GCC has switches to control just about everything Coding tips and tricks: Examples, counting down in a for loop, switch statements Computer language & data structures: coding up a menu on a display will make you learn to code an array of structures with pointers to functions. Or how to use the bitwise operators in C to efficiently set up registers.
  • Obligatory disclaimer: IANAL
  • General guidelines.
  • Eric Weddington at Hardware Innovation Summit 2013

    1. 1. Eric WeddingtonMarketing Manager,Open Source & CommunityAtmel@eric_weddingtonBoard Building
    2. 2. Firmware: Prototype to ProductEric WeddingtonMarketing Manager, Open Source & Community
    3. 3. Complementary Disciplines
    4. 4. Prototype Stage“Premature optimization is the root of all evil.”– Donald Knuth, Professor Emeritus of the Art of Computer Programming at StanfordUniversity
    5. 5. When should I optimize my code?• To meet system requirements and constraints…–Time–Space–Quality• Or, for a possible economic benefit…
    6. 6. Think Scale
    7. 7. 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.
    8. 8. 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
    9. 9. 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, orcustomer, when I distribute my product?• Answers depends on intent of project / product.
    10. 10. Firmware: Prototype to Product1. Don’t optimize too soon2. Optimize when needed– To meet system requirements– Possible economic benefits1. Know your tools2. Software licenses matter