Re: [SystemSafety] Development of code for ASICs under IEC 61508

From: Mike Ellims < >
Date: Wed, 3 Jul 2013 21:11:11 +0100

IMHO - yes. If the VHDL or Verilog it is not code, then what is it?

It's interesting to note that these language based systems have similar issues to languages such as C, e.g. non-deterministic behavior.  

However IEC61508 appears to require a less complete interpretation as given in Part 7 Annex E.  


From: systemsafety-bounces_at_xxxxxx [mailto:systemsafety-bounces_at_xxxxxx Lloyd
Sent: 02 July 2013 17:32
To: systemsafety_at_xxxxxx Subject: [SystemSafety] Development of code for ASICs under IEC 61508  

Dear Colleagues

I have a question about code developed for ASICs under IEC 61508:2010. IEC 61508-2 specifies that an ASIC development life cycle shall be used and notes the similarity between the software and ASIC life cycles ( Note 2). However, there is a concern that the standard's requirements for the ASIC life cycle appear to be less than those for software. For example, IEC 61508-3 specifies requirements for tools, including programming languages in para 7.4.4. On the other hand, IEC 61508-2 is less forthcoming on the issue of tools. It cross refers to para of IEC 61508-3 in 7.8 the section on modification (, and also mentions in Table B6 (normative) Use of tools that are proven in use (see 7.4.10) or validated; general computer aided development for all phases of the safety lifecycle.

Thus, should one interpret the standard along the lines that when one needs to certify an ASIC against IEC 61508-2, then it must also be the case that the ASIC code complies with IEC 61508-3 as well?

Kind regards
Martin Lloyd
Dr M H Lloyd CEng FIET
Tel: +44(0)118 941 2728
Mobile: +44(0)786 697 6840

_______________________________________________ The System Safety Mailing List systemsafety_at_xxxxxx
Received on Wed Jul 03 2013 - 22:11:30 CEST

This archive was generated by hypermail 2.3.0 : Tue Feb 19 2019 - 13:17:05 CET