Basic Questions about using XGecu-T76 with pogo-tool to fix motherboards

[Tesla]

I was wondering if you more experienced technicians could help answer some basic questions I have ... and help me build a reliable work-flow for using my new XGecu-T76 Chip Programmer (running XgPro v13.17). I like being able to leave the chips soldered-in (when possible) and read/write them with pogo-tool.

As instructed, for more reliable operation with pogo-tool, I have backed the SPI-Clock Frequency down to 16-Mhz (and that seems to be working fine so far for reading/erasing/writing/verify).

So, let's say I have a MB that soft-bricked itself after a common BIOS-Firmware upgrade.

I disconnect the internal Li-Ion run-battery and CMOS coin-battery if it has one.
I dissipate the flea-power with main power-switch (a couple of times for safety) before removing a single screw.
After removing the MB, I identify the Video-BIOS chip (and don't touch it as previously instructed) and also locate the main-BIOS-chip.

Let's say the BIOS-chip has "Winbond 25R512JVEN" clearly marked on top of it.
- So, I select "W25R512JV @WSON8" in the XgPro software.

Question 1:
Where in the XgPro software does it show me what voltages it plans to use to erase and program the chip with?

Question 2:
It there a signal/voltage name associated with this voltage(s) ... like Vcc or other?

Question 3:
On the official datasheet for that chip:
https://datasheet.octopart.com/W25R5...-169682265.pdf

Where exactly does it show that same info?

With 38,000 chips for XGecu to keep track of, seems like there should be a way to at least verify that the two-sides are the same.

Generally, instead of hastily using my new chip-programmer tool, I would like to know exactly what it plans to do and how. Instead of just following some steps to get past them, I would like to have more of an understanding of what is going on. All this automation is great, but so it human oversight.

[m1ch43lzm]

1. That's auto selected when you choose the chip name; I wish they added manual Vcc selection, but as long as you select the correct chip it selects the appropriate voltage
The voltage is only applied when reading/writing
If the chip is not in the supported database (for SPI flash), you have some options
a. Find a similar chip (preferably same brand) that's same voltage and capacity, example: W25Q512JV instead of W25R128JV (it has same chip ID), check both datasheets first and compare them
b. When it has a slightly different chip ID, but same capacity, voltage and brand, example: MX77L25650F, you can select MX25L25673F and ignore chip ID in that case; it can also be added to the database (latest version already has MX77L25650F)
c. Wait for a software update
What can't/shouldn't be done, is selecting a 3.3V chip and trying to program a 1.8V chip, even if it's the same brand and capacity; example: W25Q256JV (3.3V) instead of W25Q256JW (1.8V)

2. Usually Vcc on the datasheet of the chip; whatever the engineers decided to name that net on the schematics of your board...
3. "Operating ranges" section on the datasheet..., page 84: 3.0 - 3.6V; 3.3V is right in the middle, and it's a "common" voltage: 1.2V, 1.8V, 3.3V, 5V, etc.

[Tesla]

1. That's auto selected when you choose the chip name;

2. Usually Vcc on the datasheet of the chip; whatever the engineers decided to name that net on the schematics of your board...
3. "Operating ranges" section on the datasheet..., page 84: 3.0 - 3.6V; 3.3V is right in the middle, and it's a "common" voltage: 1.2V, 1.8V, 3.3V, 5V, etc.

1. Acknowledged.

But you know they know the Vcc voltage they will use, so seems like they would show us. Actually, they could just let it appear in "IC Information" with the other details.

So, basically ... we have to just trust they got it correct from the Datasheet (when they coded it into the XgPro). It's just that it's not like before where you work with the same chips everyday. In this use-case ... seems like you could potentially be working with a different chip every day.

2. Acknowledged. That's what I was thinking but I thought better to just ask.

3. Acknowledged.

Thanks for the help.