Tough one! The problem lies in the determination of "worst case". While
it would be easy to presume that having all of the hardware populated is
worst case, it overlooks the effects of un-terminated stubs and other SI
related issues. In addition, with the world of firmware based PLL
clocks and memory traffic, it is a tough thing to determine. My opinion
would be to preform the simplest pre-scan on each configuration and base
the final, rigorous certification based on that knowledge.
Brent Dewitt
Milford, MA
On 4/5/2024 6:47 PM, Lfresearch wrote:
Hi folks,
I would like to advise a client at where to draw the line on what needs
testing. I would like to solicit opinions besides my own. Otherwise it’s the
fox urging the chicken coop…
So a manufacturer that makes a product of which there will be several variants.
All use the same board, but have different sections of circuits populated. This
may require slightly different code to run on the same uP in each case.
So.. The burning question is can we perform and analysis that postulates a
worse case hardware/software combination and test just one configuration? Or,
do we have to do every combination?
Or, are there some guidelines about where we draw the line of what to test and
what can be claimed as similarity?
Off list responses are welcome too.
Thanks,
Derek Walton
LFResearch/SSCLabs.
-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc
discussion list. To post a message to the list, send your e-mail to
EMC-PSTC@LISTSERV.IEEE.ORG
All emc-pstc postings are archived and searchable on the web at:
https://www.mail-archive.com/emc-pstc@listserv.ieee.org/
Website: https://ewh.ieee.org/soc/pses/
Instructions: https://ewh.ieee.org/soc/pses/list.html (including how to
unsubscribe)
List rules: https://ewh.ieee.org/soc/pses/listrules.html
For help, send mail to the list administrators:
Mike Sherman at: msherma...@comcast.net
Rick Linford at: linf...@ieee.org
For policy questions, send mail to:
Jim Bacher: <j.bac...@ieee.org>
_________________________________________________
To unsubscribe from the EMC-PSTC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=EMC-PSTC&A=1
-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc
discussion list. To post a message to the list, send your e-mail to
EMC-PSTC@LISTSERV.IEEE.ORG
All emc-pstc postings are archived and searchable on the web at:
https://www.mail-archive.com/emc-pstc@listserv.ieee.org/
Website: https://ewh.ieee.org/soc/pses/
Instructions: https://ewh.ieee.org/soc/pses/list.html (including how to
unsubscribe)
List rules: https://ewh.ieee.org/soc/pses/listrules.html
For help, send mail to the list administrators:
Mike Sherman at: msherma...@comcast.net
Rick Linford at: linf...@ieee.org
For policy questions, send mail to:
Jim Bacher: <j.bac...@ieee.org>
_________________________________________________
To unsubscribe from the EMC-PSTC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=EMC-PSTC&A=1
