Watchguard XTM 5 Series

[A Former User]

This post is deleted!

[DeLorean]

@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

[dhoffman98]

@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?

[A Former User]

This post is deleted!

[DeLorean]

My Nano USB Programmer doesn't recognize the BIOS chip.  :(

Grtz
DeLorean

[dhoffman98]

@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 e75bc93ca2db547a3facb8d611f0d441

OK, 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).

xtm5_original.txt

[A Former User]

This post is deleted!

[A Former User]

This post is deleted!

[stephenw10]

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) = b4e3e877b589b050f3e0dd52bc8fa2e4

Steve

[dlucas46]

@stephenw10:

Doesn't look to be any of the files I have:

Steve

You said before that you thought the BIOS backup included dynamic data.

@stephenw10:

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.rom

However 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:

@John:

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.

[dhoffman98]

Did the one I attached not work? Or was it the wrong version?

[dhoffman98]

Does anyone have a good source for 4GB DDR2 240 Pin DIMMs PC2-6400, 800MHz, Non-ECC, unbuffered memory?
Looking to buy 2 sticks that won't end up costing me $95.

[A Former User]

This post is deleted!

[A Former User]

This post is deleted!

[dhoffman98]

@747Builder:

dont forget you need low density 4G sticks… apparently NON low density sticks dont work.

Right… Forgot to mention that was another requirement on my list.
NON ECC
Unbuffered
AND Low Density.

I'm finding them out there, but it's almost $50 per stick.

I'd like to set up Squid, but only have 2GB right now, and hear that would take more than 2GB.

[DeLorean]

@747Builder:

@DeLorean:

My Nano USB Programmer doesn't recognize the BIOS chip.  :(

Grtz
DeLorean

Delorean,
your sure you had the clip on the flash chip the right direction (YES ive made that stupid mistake of being on wrong) and power unplugged from the XTM?

747Builder,

Pin1 is marked with a red line on my clip, i have tried with powercord unplugged, plugged, with and without the CMOS battery.
Everytime same result.
Also used a 9pin USB header cable, with on each side a female connector, to connect to the SPI connector on the motherboard,
but this gave same result.

I have then looked further, and the seller advertised also a socalled "SPI Reverse Socket Kit" ,
which would be needed, for flashing soldered BIOS chips.
The explanation is that the Nano USB Programmer can't handle flashrom direct connected.
With the "SPI Reverse Socket Kit", the soldered BIOS chip can then be "isolated" to gain full access and to proceed with the BIOS flashing.

The full explanation is found here :
http://cafe.daum.net/tualatin/J11z/243

So it seems that i must order extra hardware to use my Nano USB Programmer  :(

Grtz
DeLorean

[A Former User]

This post is deleted!

[DeLorean]

@747Builder:

DeLorean,
do you have a link to the exact programmer you have?
and the soic8 test clip?

you may be able to just buy 8 jumper wires for your test clip and figure out the reverse wiring to the clip from the programmer.

let me know.

This is my programmer :
http://www.ebay.com/itm/NANO-USB-Programmer-for-PC-M-B-BIOS-repairing-with-Economic-shipping-/271313593344?hash=item3f2b8ce400:g:B6QAAMXQrNtR0sQZ

And this is the SOIC8 test clip that i have :
http://www.ebay.com/itm/CTYRZCH-SOIC8-SOP8-Flash-Chip-IC-Test-Clips-Socket-Adpter-Programmer-/122481188471?hash=item1c84729e77:g:rsUAAOSw-3FZDMxE

If have also used internal USB cable from a old case, like this for connecting my programmer to the SPI connector on the motherboard :
http://www.ebay.com/itm/Internal-Mainboard-motherboard-USB-2-0-9pin-female-to-female-extension-Cable/142057029855?_trksid=p2045573.c100642.m3226&_trkparms=aid%3D555017%26algo%3DPL.CASSINI%26ao%3D1%26asc%3D41375%26meid%3D7b69eab2420547cab591541b188cc098%26pid%3D100642%26rk%3D1%26rkt%3D1%26

But i gives me same result each time, device ID : 0XEEEE (see attached screenshot)

So i think for this programmer to work correctly, i have to use the SPI Reverse kit.

Grtz
DeLorean


[uknownme123]

WGbiosV1_2.bin
MD5: 35F34C44D4418550278CBEC29D351753

OGxtm5BIOS.bin
MD5: 6CE4E0811A16A61F98E051CAEE7D3BBB

xtm505.bin
MD5: 2FDD6851B32AE931637D4845C037B550

WG_Bios_1_2.rom
MD5: C94B1E6AF6DB5CB3A1F37A33F6BAF494

WGbiosV1_2.bin.txt
OGxtm5BIOS.bin.txt
xtm505.bin.txt
WG_Bios_1_2.rom.txt

[A Former User]

This post is deleted!