I found an interesting-sounding thread on ASML's software stack, below.
I suspect the sheer complexity of EUV devices and 40+ years of development at ASML is going to need a similarly elaborate supporting software stack. I also imagine ASML has some customer centric requirements driving their choices of stack documentation. That said, any company that has been around for decades will have opportunities to lean out their processes, so this thread has me a little curious what ASML's culture is like in this regard.
Disclaimer: I really like creating and/or learning engineering and change processes, I'm weird like that.
(Note the flow diagram below feels in line with (very) high level processes I've worked with, so perhaps "messy" and "insanely complex" is a bit overstated?)
From the thread: ASML, creator of lithography machines used by 90% of chipmakers, has a messy software stack.
Every TWINSCAN EUV ships with ~45 million lines of code (similar size to Win10!)
Bugfixes and features start out as *word documents* sent to a series of review boards.
..
Massive Jenkins farms compile 1500+ Maven and Make modules.
Full EUV image builds are run overnight. Small changes still take >1hr to compile.
Integration is mostly performed on virtual hardware (Simulink) as there are *literally* only 2 machines in the world to test on!
..
ASML’s software development lifecycle is insanely complex.
One university student wrote their Master's thesis on the EUV engineering change process!
Software work flows as word documents through multiple layers of risk management. All before a single line of code is written!
I suspect the sheer complexity of EUV devices and 40+ years of development at ASML is going to need a similarly elaborate supporting software stack. I also imagine ASML has some customer centric requirements driving their choices of stack documentation. That said, any company that has been around for decades will have opportunities to lean out their processes, so this thread has me a little curious what ASML's culture is like in this regard.
Disclaimer: I really like creating and/or learning engineering and change processes, I'm weird like that.
(Note the flow diagram below feels in line with (very) high level processes I've worked with, so perhaps "messy" and "insanely complex" is a bit overstated?)
From the thread: ASML, creator of lithography machines used by 90% of chipmakers, has a messy software stack.
Every TWINSCAN EUV ships with ~45 million lines of code (similar size to Win10!)
Bugfixes and features start out as *word documents* sent to a series of review boards.
..
Massive Jenkins farms compile 1500+ Maven and Make modules.
Full EUV image builds are run overnight. Small changes still take >1hr to compile.
Integration is mostly performed on virtual hardware (Simulink) as there are *literally* only 2 machines in the world to test on!
..
ASML’s software development lifecycle is insanely complex.
One university student wrote their Master's thesis on the EUV engineering change process!
Software work flows as word documents through multiple layers of risk management. All before a single line of code is written!