Who is responsible for board bring-up in your company? Who is guilty if nothing works as expected? How easy is it to understand if it is a board design issue or a manufacturing defect? FPGA IP misconfiguration or a test program error?

 

In one of our previous blog articles, we looked at typical ways of testing FPGA boards for production defects. In many cases, common test techniques like ICT, Boundary Scan, or Flying Probe cannot cover high-speed interfaces and components due to their technical limitations. The lack of dedicated technologies in the market forces product managers to make a simple decision: converting the mission-mode application firmware developed for the final product into a test firmware. 

 

This approach is not error-prone. In this article, we have studied what kind of problems may arise with it:

https://testonica.com/blog/challenges-of-testing-fpga-boards-in-production