Watchguard XTM 5 Series
-
This post is deleted! -
@747Builder:
I don't recall exactly which version it was I'm afraid. Unless it's noted somewhere here in thread already.
That's true though the earlier versions produced corrupted files which is why I ended up having to flash the chip via SPI directly a number of times.
Steve
Stephen10,
do you happen to still have the Pinouts you got from Lanner on the SPI port? also what software did you use with your home made SPI programmer?
in my world its called CYA and making sure mine works ahead of time before hacking on the bios.This diagram of pinouts is taken from the Lanner FW-7581W user manual
Grtz
DeLorean
 -
This post is deleted! -
Using the test clip directly is probably a better way to go.
I used flashrom which has a special driver for the parallel port "rayer_spi" programmer.
https://blogs.coreboot.org/blog/2010/08/17/rayer-spipgm-support-in-flashrom/Steve
-
@747Builder:
Thanks. i also found my soic8 test clip for my eprom burner too and it supports the SPI flash chip in the XTM 5.
I received my SOIC8 test clip today in the mail, but i'm not sure if my Nano USB Programmer can be used.
I gonna first try it on a old desktop motherboard.Which Eeprom programmer do you use ?
Grtz
DeLorean -
Okay, my Nano USB programmer has the ST M25P80 chip listed.
But when i look at the Bios chip of a XTM510 that i have here , it says MP25P80-VG.
A search on the internet doesnt give me any answer what the difference is between both nrs.Grtz
DeLorean
-
This post is deleted! -
@747Builder:
Bios chip is a Micron part you listed above (MP25P80-VG). Datasheet is here -> https://www.micron.com/~/media/Documents/Products/Data%20Sheet/NOR%20Flash/Serial%20NOR/M25P/M25P80.pdf
the ST M25P80 datasheet is here -> http://media.digikey.com/pdf/Data%20Sheets/ST%20Microelectronics%20PDFS/M25P80.pdf
The BIOS chip that i mentioned MP25P80-VG is also from ST (ST brand visible on the picture)
@747Builder:
NOTE: be VERY careful with programming eproms with software if your not 1000% sure they are compatible. especially on these boxes with no easy way to replace the bios chip without a SMD rework station.
That's why i'm carefull and not have tried updating the BIOS on a XTM5 untill now.
BIOS flashing with the SOIC8 test clip and programmer will eliminate this risk, or can it go wrong with this method also ?
I have used this programmer for BIOS flashing empty SST BIOS Chips for the X-E Core series,
and that worked like a charm.
A bad BIOS update is equal to a empty BIOS chip, are am i wrong ?Grtz
DeLorean -
This post is deleted! -
This post is deleted! -
@747Builder:
if anyone has a backup of the original rom before you flashed stephen10's rom , i deleted my copy by mistake and cant get it back. shoot me a PM, id like to get a copy.
im gonna update the CPU microcode plus a few other changes since im running a LGA771 CPU instead of the 775 CPU. but ill update Microcode for both 771 and 775 CPU's…
I will see tomorrow for providing a stock BIOS.
I have XTM505 , 510 and 525 available.Grtz
DeLorean -
@747Builder:
if anyone has a backup of the original rom before you flashed stephen10's rom…
I THINK I have it. I used flashrom to read the original one to a file called "current.rom" and then flashed it. But it is POSSIBLE that I overwrote it again with the new one.
Are the file sizes exactly the same? Is there a way I can tell, easily if it's the old one? -
This post is deleted! -
My Nano USB Programmer doesn't recognize the BIOS chip. :(
Grtz
DeLorean -
@747Builder:
you should be able to run a md5 on it and tell with "md5 nameofrom.bin"
if its stephen10's "pfsense 1.8 modded rom" the MD5 on it is MD5 e75bc93ca2db547a3facb8d611f0d441OK, then I DO have two different files.
MD5 (current.rom) = 2bd4ca666290306f8f9b63dee497acfa
MD5 (xtm5_83.rom) = e75bc93ca2db547a3facb8d611f0d441…
OK, Can't add .rom files. So try this and change the extension to .rom
(If putting that here was wrong, let me know and I'll try to remove it).
-
This post is deleted! -
This post is deleted! -
Doesn't look to be any of the files I have:
[2.4.0-BETA][root@ufw2.stevew.lan]/root: fetch https://sites.google.com/site/pfsensefirebox/home/xtm5.rom xtm5.rom 100% of 1024 kB 1424 kBps 00m01s [2.4.0-BETA][root@ufw2.stevew.lan]/root: md5 xtm5.rom MD5 (xtm5.rom) = 6fd0df1ef90335d5a4af2e9bea1a6958 [2.4.0-BETA][root@ufw2.stevew.lan]/root: fetch https://sites.google.com/site/pfsensefirebox/home/xtm5_83.rom xtm5_83.rom 100% of 1024 kB 1412 kBps 00m01s [2.4.0-BETA][root@ufw2.stevew.lan]/root: md5 xtm5_83.rom MD5 (xtm5_83.rom) = e75bc93ca2db547a3facb8d611f0d441 [2.4.0-BETA][root@ufw2.stevew.lan]/root: fetch https://sites.google.com/site/pfsensefirebox/home/xtm5_8.rom xtm5_8.rom 100% of 1024 kB 1488 kBps 00m00s [2.4.0-BETA][root@ufw2.stevew.lan]/root: md5 xtm5_8.rom MD5 (xtm5_8.rom) = b4e3e877b589b050f3e0dd52bc8fa2e4Steve
-
Doesn't look to be any of the files I have:
Steve
You said before that you thought the BIOS backup included dynamic data.
Ah, that's cool. :) Sorry for the delay replying.
You must use 3.51.
3.46 might corrupt the bios and there is no way to tell until the box doesn't boot.The bios you backed up up is not the same as my original backup:
steve@steve-Satellite-Pro-A300:~/Desktop$ md5sum OG-BIOS.ROM 6ce4e0811a16a61f98e051caee7d3bbb OG-BIOS.ROM steve@steve-Satellite-Pro-A300:~/Desktop$ md5sum xtm5.rom 6fd0df1ef90335d5a4af2e9bea1a6958 xtm5.romHowever I don't think that's necessarily a problem. When I have backed up the BIOS rom before and compared it they have always been different. I believe that the downloaded ROM file must contain some dynamic data which changes every time making comparison like that impossible.
Steve
Edit: typos
Anybody tired comparing this one:
EDIT2>>
Here's the OG-BIOS.ROM file. Can you verify that it matches your original BIOS so I know if I can just flash the modified BIOS you've provided?I have an XTM 510 that still has the original BIOS. Can extract in a few days if needed.
-
Did the one I attached not work? Or was it the wrong version?
