zyga64 wrote on 2025-06-08, 20:37:
DudeFace wrote on 2025-06-08, 13:06:
if you have another motherboard with the same bios socket you can hot swap the chip with uniflash, doesnt have to be the same chip, uniflash has an option to re-detect the chip before you flash.
I'm not 100% sure that the above sentence is always correct. Not only does the socket have to be the same - I think the flash chip pinout should match as well.
However, the author of the thread wrote that the BIOS chip on the board he tried to cross-flash was identical...
the chip i flashed was the same PM49FL004T, the board i flashed it with had a Winbond W39V040A both with 512kb bios, there may be some differences i haven't come across with the chips ive flashed so i may not be 100% correct on that.
martin778 wrote on 2025-06-08, 19:46:Ok, I got Uniflash 1.40 booted from FreeDOS USB, swapped the BIOS chip on the fly, detected again (even though they are all the […]
Show full quote
Ok, I got Uniflash 1.40 booted from FreeDOS USB, swapped the BIOS chip on the fly, detected again (even though they are all the same type) and after offering it the P4P81019.ROM file, it tried to flash but failed with FLASH DATA VERIFICATION ERROR. Tried 2 different chips of the same type but the result was identical.
Do I need a BIN file??
+++
Tried with a BIN for the A7n8x deluxe since the BIOS chips are the same - got the same error.
ive not come across that error before, since all the boards you have use a 512kb bios i would have thought it should work, though if you had the same error with both chips/bios it could be that the board you're using just wont do it,
ive got a few boards with the same socket bios but only 2 boards will flash chips, the ones that dont tell me the bios is write protected or detects the chip as unknown, the error you are getting is probably down to the motherboard, i forgot to mention it might not work on every board but it was at least worth a try.
as for the bios file i dont think it matters with uniflash what the extension is, though i usualy rename it to .rom