Just tested it on MX25L6405 with v1.8.0 and everything is working fine. Unfortunately I do not have MX25L6473 at the moment, but read/erase/write procedures are the same for both - I checked it in datasheets:https://datasheetspdf.com/pdf-file/1259 ... 25L6473E/1https://datasheetspdf.com/pdf-file/6460 ... 25L6405D/1
Device ID is also the same for both (C2h 20h h17) and erasing/programming commands are the same.
There are BlockProtect (BP) bits in status register, but for both devices there in the same place and REVELPROG is disabling block protect (even if it is enabled) before erase and write. New devices should not be protected anyway, so this is not the case.
It's very strange - it should work. It seems too me that MOSI or WP are not contacting (effect will be the same), but.. W25Q64 is working (both pins in the same place) so this is not the case... What's more, ...6473 variant does not have WP pin.
But I have an idea.
I prepared you memory database file with "MX25L6473E-BE" - it is using Block Erase command instead of Chip Erase command. Please unzip file from attachment and replace it in "%appdata%/REVELPROG-IS". Then select MX25L6473E-BE (with "BE" at the end) and test it. Please let me know about results.
PS. There is also WPSEL bit in Security Register (page 52 in datasheet). It is OTP bit (one time programm) - when it was set to "1" then device is write protected by default (erase and write will not work).. but you have new devices so this is not the case.