A7V600-X Won't POST; UNIFLASH write errors; NFORCE Chipset;

Hot-swapping and Boot-Block flash & Boot block flash and floppy support
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

Hi there,

My Asus A7V600-X board died last weekend:
  • Booted up..
    BIOS Messages font is corrupted
    Shutdown
    Reseat GPU, CPU Ram etc.
    Boot up,
    No POST.
    Beep pattern of 1 second ON, 1 second OFF continuously
I've tried to hot flash on a couple of different boards with the following results:

on 2 Intel PIII boards:

If I try to detect Chip type, "I'm told that Write protect may be disabled".
If I force type 9D6D (PM49fl002t) then I can flash the bootblock, but not the main BIOS file.

My only other machine to try this out is a Biostar with an nForce2 chipset, which according to UNIFLASH website might not work.
On Biostar, UNIFLASH can't read from floppy, so I use USB, which it can read but can't flash without verification errors.

Needless to say the Asus utility AFLASH is useless, because it won't let me hot flash on another board.

I could really do with getting this board working again, or at least confirming that the bios is NOT the issue :-)

Any suggestions warmly received.

alasdair
Last edited by alasdair on Tue Mar 25, 2008 1:47 am, edited 1 time in total.
edwin
The Hardware Archivist
Posts: 6286
Joined: Wed Mar 20, 2002 7:11 pm
Location: Netherlands
Contact:

checked for bad capacitors?
http://www.badcaps.net
edwin/evasive

Do not assume anything

System error, strike any user to continue...
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

Hi

Yes, I've given the board a thorough visual inspection, there is no sign of damage anywhere, no leaking caps, nothing seems wrong.

I just booted the board with the PLCC from the Biostar, obviously the board doesn't post, but there is no beeping noise either.

Despite searching like crazy, I can't find out what my beeping pattern actually signifies, apart from a vague reference to "memory problems".

Because of the strange corruption to the characters on screen I'm sure that Bios corruption is not the only issue, however I'd like to rule that out.

Asus arn't making my life any easier by telling me how to flash this bios on another computer, pretty terrible support from them.

Alasdair
edwin
The Hardware Archivist
Posts: 6286
Joined: Wed Mar 20, 2002 7:11 pm
Location: Netherlands
Contact:

which it can read but can't flash without verification errors.
sound to me like a fried bios chip.
edwin/evasive

Do not assume anything

System error, strike any user to continue...
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

I'm not sure, I think it's to do with the Asus write protection.

you see I can use this flash chip in the biostar board, flashing it works fine, however neither uniflash, the asus aflash, nor a whole bunch of awdflash will let me flash either chip with the asus bios.

Only uniflash even tries, and it fails with verification errors.

Is there a way to fake the chipset ID so that I can use the Asus flasher on my biostar board?
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

a clarification:

Both flash chips are identical, both can be flashed by the biostar built-in flasher with any of the biostar bioses.

Neither Biostar or Asus bios can be flashed successfully by Uniflash.

Asus's Aflash won't run on Biostar board as it's looking for an Asus bios id.
Denniss
BIOS Guru
Posts: 3153
Joined: Thu Mar 21, 2002 8:16 pm
Location: Near Hannover (CEBIT) Germany
Contact:

Try an AMI flashprog - it's often useable with other Bios as well.
Search for Aminf342.exe

This is a commandline flasher to be used within DOS. Make sure you always use the parameter -r to prevent a reboot with the other Bios still installed.

Aminf342 newbios.bin -r
-> To be sure what to use type Aminf342 /? or -? to see the optional commands.
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

Hi Denniss,
thanks for the advice.

I have tried using Aminf342 just now, however I get the some sort of exception handler:
PMODE/W: ABORT : 00
EXCEPTION 6

etc etc

I tried with
aminf342 latest.bin -r
aminf342 latest.bin -r /b /n
aminf342 latest.bin -r /b /n /i

maybe there's a combination that works with ASUS bios files, I just haven't found it yet.

I also have access to a very large collection of bios flashers/utilities, and could try some of those flashers, if you had specific recommendations for ASUS bioses hot flashed on non ASUS boards.

Isn't there a program that just flashes what ever you throw at it?
i.e No checking of BIOS ID/ SYSTEM ID.

Or are there modified aflash.exe that bypass Asus Hook test?
Denniss
BIOS Guru
Posts: 3153
Joined: Thu Mar 21, 2002 8:16 pm
Location: Near Hannover (CEBIT) Germany
Contact:

Did you use a Floppy that has received a fresh and full format ? Best would be the DR-DOS Bootdisk for biosflashing - search for drdflash.exe
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

hi dennis,

I'm trying the full formatted drdos floppy right now. is there a particular set of command switches I should be using for a total flash including bootblock?

I was interested in the /i switch but to be honest the explanation on the output of aminf342 -h didn't amount to much
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

full formatted floppy didnt make any difference, and uniflash doesn't read from floppies on my nforce board.

I'm currently considering building a flash programmer, as I'm not going to pass more money to Asus for a replacement bios.

Will take a look at Uniflash source and see if there's any comments on error 152, or nforce chipsets.
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

It strikes me that perhaps it possible to only update the bootblock, then use the internal boot block recovery on the Asus board itself.

That should be fine as I can successfully flash a bootblock onto either chip, however I do not have the Asus boot block to flash :-) I do not know why Uniflash will not correctly flash the rest of the bios, however I'm still seeing those verification errors, that are also mentioned here:
http://www.wimsbios.com/phpBB2/topic7200.html

If someone could run uniflash and save the bootblock to a file for an asus Kt600 board and PM it to me I'd be grateful.

OR can I use acbrom to pull it from a rom myself?
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

Well, it's been a bit of time now, and I'm pretty surprised about the lack of any suggestions other than checking for bad caps and having a properly formatted disk! I don't know if I was asking these questions in the wrong place, or if it's just quiet round here these days?

I'm going to build myself a Willem eeprom flasher and have a crack at flashing it with that. The flasher will be used for other projects too, not just buying it for this K8 board ;-).

Will report back to this thread once I have more results.

Alasdair
cp
BIOS Guru
Posts: 1914
Joined: Mon Oct 21, 2002 9:07 pm
Location: Germany

my suggestions would have been:

- get another version of uniflash (there are/were some more recent versions on rom.by)
- get another version of amiflash
- get another board to flash the chip on
- build an eeprom programmer (ct'flash, ideflash, willem)

these suggestions are more or less the ones already given here.
If you email me include [WIMSBIOS] in the subject.
alasdair
New visitors - please read the rules.
Posts: 11
Joined: Tue Mar 25, 2008 12:37 am

cp wrote:my suggestions would have been:

- get another version of uniflash (there are/were some more recent versions on rom.by)
- get another version of amiflash
- get another board to flash the chip on
- build an eeprom programmer (ct'flash, ideflash, willem)

these suggestions are more or less the ones already given here.
Hi cp,

Thanks for the suggestions. That there's newer versions of Uniflash available than the ones on uniflash.org comes as a bit of a surprise. (But not a total surprise as with the source available I should have guessed somebody would have updated it between 2005 and now :-) )

Should have some time tomorrow to search rom.by, if I find a version that is more successful with roms for this board I'll report back.

I suppose this will teach me not to buy from a manufacturer that uses non standard flashers... :cry:
Post Reply