Software Validation Questions - FPGA (Field Programmable Gate Array)

T

tomnmiami

#1
We have an electronic device which contains an FPGA (Field Programmable Gate Array). This is a semiconductor that is configured, to our specification, to perform a specific function. Our opinion is that the FPGA is hardware, even though it performs a function defined by us. We think of it the same way one would think of a transistor (which is also a semiconductor, usually used to amplify or switch and electronic signal). As such, we do not intend to perform software validation on the device.

Do any of you have experience with FPGA's and can confirm our position?

Thanks,
T
 
Elsmar Forum Sponsor

Marc

Hunkered Down for the Duration with a Mask on...
Staff member
Admin
#2
Does anyone here have any background in FPGA's (Field Programmable Gate Array) or similar who can help with this?
 
D

ddunn

#3
First some questions.
1. When is the FPGA programmed?
2. How is the FPGA programmed?
3. It there an initialization or boot program loaded?
4. Who developed the FPGA program?

If the FPGA is preprogrammed it is an assembly consisting of the blank part and the program. The loaded software is validated during functional test of the assembly.

If the FPGA is programmed during product use through the system software then the FPGA program is validated with the system software.
 
T

tomnmiami

#4
The binary code that tells the FPGA what to do is loaded onto the FPGA, from internal memory, when the system initialization starts (at power up). We created the code using a standard hardware description language, and it's loaded into the internal memory by the vendor who makes our circuit boards.

Does this change anything?

Thanks,
Tom
 
I

icare2much

#5
I think it is important to understand the underlying needs when talking about software validation, and whether it applies. If the software is very complex and cannot be fully verified - i.e. all the possible branches and error conditions are not feasible to test, then software validation considers the process of development as well to reduce the risk of bugs.

Apply this thought process to FPGAs - if your FPGA is relatively simple and can be 100% tested to verify its functionality - I agree it could fall into the hardware domain. However - if it is not feasible to test it fully (we have FPGAs that are extremely complex) then treat it as software.

Sorry, to summarize, I guess I'm saying "it depends"!! :notme:
 
F

fpgawiz

#6
Google for "NASA Assurance of Complex Electronics" and it will lead you to a NASA website with a very elaborated process for FPGA validation as compared to software IV&V..

but the previous answer is a very good point that summarizes it well.
 
J

John Mann

#7
In my opinion a FPGA is hardware. What do you use to "program" it with? - Hardware description language!

The FPGA should be verified in the same way as an electronic circuit using discrete components.

That said, my present employer does not permit me to be involved with FPGA design because "FPGAs are software - you program them":mad:
 
J

JSambrook

#8
I'm wondering if the thinking on this post has changed at all since it was last updated.

I believe FPGA development, unless it's almost trivial, is software development. Yes, it's a specialized kind of software, the programming model is a bit different, but (in the case of one of our clients) they have tens of thousands of lines of VHDL code, it's iterated almost constantly during development, testing finds defects, etc.

I'd appreciate it if anyone could relate what they are seeing in practice. Are your companies or clients developing FPGA code for a medical device and not striving to comply with standards such as IEC 62304?

Thanks in advance for any replies.
 
Thread starter Similar threads Forum Replies Date
H Software Validation for FFS Packaging Machine Qualification and Validation (including 21 CFR Part 11) 1
Q ISO 13485 7.5.6 Validation - Off the shelf Software ISO 13485:2016 - Medical Device Quality Management Systems 3
M ERP / QMS related software standards for Validation IEC 62304 - Medical Device Software Life Cycle Processes 6
D Software validation team Misc. Quality Assurance and Business Systems Related Topics 3
silentmonkey Rationalising the level of effort and depth of software validation based on risk ISO 13485:2016 - Medical Device Quality Management Systems 10
E 13485:2016, Sections 4.1.6, 7.5.6 and 7.6 - Validation of Software - Need some Advice please ISO 13485:2016 - Medical Device Quality Management Systems 3
K Software Validation for Measurement Tools used in Process Validation ISO 13485:2016 - Medical Device Quality Management Systems 2
S SOP for ISO 13485:2016 Quality related Software validation ISO 13485:2016 - Medical Device Quality Management Systems 9
K ERP System Software Validation - ISO13485 2016 4.1.6 Design and Development of Products and Processes 8
D Software validation in Medical Equipment Other Medical Device and Orthopedic Related Topics 20
C Looking for simple Software Validation IQ templates. Qualification and Validation (including 21 CFR Part 11) 4
C Software validation - Off The Shelf Software - Web hosted ISO 13485:2016 - Medical Device Quality Management Systems 6
R Validation of Medical Device Hardware containing Software - How many to Validate ISO 13485:2016 - Medical Device Quality Management Systems 1
F 21 CFR Part 11 - Implicit requirements - Validation plan for a Software as a Service Other US Medical Device Regulations 1
R ISO 13485 Software validation procedure and Quality Objectives Monitoring wanted Document Control Systems, Procedures, Forms and Templates 1
S Validation of COTS Equipment plus Software Qualification and Validation (including 21 CFR Part 11) 12
D Software Validation - Contract manufacturer of Components (PCBA's) Qualification and Validation (including 21 CFR Part 11) 7
Pmarszal Software Validation Training Course - Recommendations Training - Internal, External, Online and Distance Learning 3
T Software Validation Certificate (ISO 13485:2016) ISO 13485:2016 - Medical Device Quality Management Systems 19
R FDA Requirements - Printing Equipment Software Validation Qualification and Validation (including 21 CFR Part 11) 1
G Windows 10 OS build Software Validation US Food and Drug Administration (FDA) 1
S Where to keep Enterprise Resource Planning software (ERP) Validation Records ISO 13485:2016 - Medical Device Quality Management Systems 1
C Software validation (4.1.6 ISO 13485:2016) ISO 13485:2016 - Medical Device Quality Management Systems 20
M Software Validation Guidance Suggestions Various Other Specifications, Standards, and related Requirements 6
S QMS software validation - Documentation ISO 13485:2016 - Medical Device Quality Management Systems 5
A SOP for software validation of software in medical device IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 5
R CNC Software Validation requirements as per ISO 13485:2016 Other ISO and International Standards and European Regulations 8
R Software validation - off the shelf X-Ray Software Quality Assurance 3
S What is the clause in ISO 13485 for SAP Software Validation? ISO 13485:2016 - Medical Device Quality Management Systems 3
P Software validation of Data Exporter ISO 13485:2016 - Medical Device Quality Management Systems 3
A Process Validation of QMS Software ISO 13485: 2016 Cl. 4.1.6 ISO 13485:2016 - Medical Device Quality Management Systems 26
P Software Validation for Equipment - Question ISO 13485:2016 - Medical Device Quality Management Systems 5
D Medical Device Software Tool Validation - Compilers! IEC 62304 - Medical Device Software Life Cycle Processes 7
N When is Medical Device Software Validation required? ISO 13485:2016 - Medical Device Quality Management Systems 6
O Process Mapping prior to Validation and Software to use to Map Process Maps, Process Mapping and Turtle Diagrams 12
S Software Validation – Clause 4.1.6 of ISO 13485:2016 ISO 13485:2016 - Medical Device Quality Management Systems 12
B Could I combine IQ, OQ and PQ for Minitab Software Validation ? Software Quality Assurance 3
R Document Management Software : Validation and other requirements Medical Information Technology, Medical Software and Health Informatics 8
E Software Validation - Clinical Trials US Food and Drug Administration (FDA) 3
K What are the minimum requirements for Process Validation (Software)? ISO 13485:2016 - Medical Device Quality Management Systems 5
R ISO - Clause 7.5.1.3 - CMM Software Program Validation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2
I Validation Software Experience? (Valgenesis, etc.) Quality Assurance and Compliance Software Tools and Solutions 1
M Injection Molding Machine Software Validation Calibration and Metrology Software and Hardware 2
E FDA Requirements for Implantable Medical Device Software Validation ISO 13485:2016 - Medical Device Quality Management Systems 5
C Change Control Forms Post Software Validation Medical Information Technology, Medical Software and Health Informatics 2
C Thoughts on validation of Legacy Systems for Medical Device Software EU Medical Device Regulations 2
C Cement Mixing Software Validation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
Y OTS (Off The Shelf) Software Validation for 510k Traditional 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
V Validation of macro - scripts - programs used in statistical software (Minitab-SAS... Qualification and Validation (including 21 CFR Part 11) 5
R ISO 13485 Software Validation Requirements - Help needed ISO 13485:2016 - Medical Device Quality Management Systems 4

Similar threads

Top Bottom