3 ms·
> But these chiplet chips can only be properly tested when all the chiplets have been assembled into a package Why is that, though? Could you have a physical t
by thebean11 5y ago
> But these chiplet chips can only be properly tested when all the chiplets have been assembled into a package
Why is that, though? Could you have a physical test harness for a chiplet that mocks out the others, sends input to your chiplet, and make sure it's operating correctly? Maybe that's harder than it sounds, I'm coming at this from a software perspective.
- jleahy 5y agoIt’s very easy, this kind of testing is crucial for hardware (in a way that it is not for software). At the most basic level this is done through scan, which allows you to test every single wire in the design for several faults (stuck at 0 and stuck at 1 being the most important). This covers the vast majority of failures (for example missing vias and missing contacts). For memory other techniques are needed (reading and writing fixed patterns) and various ‘repairs’ can be done by blowing fuses to translate faulty addresses. So for example you might do scan test (the first one) at the wafer before the dies are even cut, then assume that the majority of dies will have repairable (rather than irreparable) memory errors and only test those after packaging.
- pwr-electronics 5y agoNever made a chiplet, but as a general observation in hardware ... Digital hardware acts predictably only when everything is electrically matched and connected properly. And the integration processes can introduce new defects. It's probably still an analog and materials problem at that point.