One of Altima's rookie engineers, the chief, had finished his work and was dozing off on the train...
While my consciousness was flying, I was thinking about the production practice, and there was one thing I wanted to confirm.

"Is the FPGA I/O standard 3.3 V LVTTL?"
The other day, when the three newcomers were talking, it was a topic that came up. At that time, I believe... I came to the conclusion that I needed to check the Fitter Report...

The next day, I checked some pinouts and I/O Standards of the designs created in the production practice by going to Fitter Report → Pin-Out File. Then...

Oh! In this design, only I/O Bank 1 has an I/O Voltage of 2.5 V!
"I didn't set it to 2.5 V..." I wonder why...

! ? Is it the other way around? Isn't it just not set to a voltage other than 2.5 V!? "not set"
Oh, I was told the other day that this happened because I didn't change the default setting of I/O Standard in "Device and Pin Options"!

Only one VCCIO voltage level can be set per I/O bank. In other words, when the I/O standard of User I/O to be used is decided, the VCCIO in the bank is decided. For example, VCCIO = 1.8 V for the bank to which the pin with SSTL-18 and 1.8 V settings belongs.

This time, Banks 2-8 use User I/O, and I set the I/O Standard to 3.3 V LVTTL in the Pin Planner, so Quartus® II automatically recognizes that the VCCIO in these banks is 3.3 V. bottom.
However, since User I/O is not used in Bank 1, the voltage level of VCCIO cannot be determined from the I/O Standard of User I/O.
In this case, Quartus® II applies the default setting value to VCCIO. Normally, if you haven't changed the settings, the default setting is "2.5 V".
Therefore, when I changed the default setting value to 3.3 V LVTTL in "Device and Pin Options" Voltage → Default I/O Standard, the change was reflected in the Fitter Report.

Bank 1's standard and its voltage, which was left at 2.5 V by the default I/O Standard setting, is also the same. Changed to 3.3 V LVTTL as expected.

Even if you make detailed settings in Assignment Editor, Pin Planner, etc. before compiling, there are places where option settings for the entire device are reflected.
For that reason, there is a Fitter Report to check if the settings are as specified!

In this way, the head of the new engineer got into the habit of always checking the standards, etc. with the "Pin-Out" of the "Fitter Report" after compiling.