Hi Vasile,

In 1.c, you say "prepare your mind as the product will be manufactured in
1000 pieces. In this way you'll avoid a lot of mistakes". Can you be more
explicit about classical/usual mistakes ? Maybe few examples, real-life ones
?

In 1.d, can you give pictures of good and bad PCB designs, regarding ground
& power nets, etc... ? (for the bad ones, you can use mine :))

In 1.e, can you tell me (us) more about testing points ? I have indeed
observed these points in big PCBs (DVD players, etc...), and was wondering
how they were used. I guess there's a testing specification document.

In steps you describe, you manufacture PCB before writing firmware.
Shouldn't a (prototype) firmware version be written before ? How do you test
your design ? If not entirely, at least some part of it ? You've now guessed
my question: how do you prototype your project ? Or, maybe, what can be
prototyped, and what shoudn't be prototyped because of some hardware issues
not compatible with a prototyping platform (PWM with breadboards, for
instance ?)

This actually makes me think about software development methodologies. What
you describe makes me think about the waterfall model: you build your
project as independent steps, when you finished one, you go to the next and
never come back to previous. As a hobbyst and beginner, it's important to
have a global overview, the "big picture", as soon as you can.
Test/experiment a schematic, an idea, from hardware to software, and
regurlarly iterate through this process 'til you reach a point where you're
quite confident moving to PCB manufacture is reasonably possible. It's
highly furstrating to produce smoke with a freshly made PCB you've spent
hours on...


Thanks for your advices
Cheers,
Seb



2010/4/5 vasile surducan <[email protected]>

> Hi all,
>
> I've wrote a short article with my ideas about designing an embedded
> project. Language may not be the best since English is not my native one,
> however take a look and tell me your comments.
>
> BTW, maybe Seb&Matt will find inside another jallib logo?
> :)
> Vasile
>
> --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<jallib%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/jallib?hl=en.
>



-- 
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to