• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 986
  • Last Modified:

Trouble performing BIOS flash via PXE.

Hello all,

I have a need to be able to flash a BIOS via a PXE boot. My PXE boot image is a standard MS DOS 6.22 disk with the flash util and binary on it. I will apologize for the length but I thought being thorough would be best:

The PXE boot image is the same image that I use via floppy. If I boot the floppy image and perform the BIOS uprade it works fine. As soon as I use the image delivered via PXE the BIOS upgrade fails, wiping out the BIOS in the process.

When booting from the floppy and flashing the BIOS, the last 8 blocks never get overwritten (3FE000 and higher), stating that there is no update. This seems to be normal for the operation and the BIOS updates successfully to the newer version.
When performing the same process via PXE, it overwrites those last 8 blocks. After this happens the unit is unbootable and I am prompted by the Award BootBlock notice stating that there is a BIOS ROM Checksum error. This doesnt make any sense since I am using the identical image as the floppy.

I am using the award 823b flash utility (awfl823b.exe) which is suggested by the manufacturer of the motherboard (Via).
I believe the issue centers around memory management. Here are the contents of my config.sys and autoexec.bat files:

config.sys:
FILES=20
BUFFERS=10
DEVICE=a:\HIMEM.SYS /TESTMEM:OFF
DEVICE=a:\EMM386.EXE NOEMS
DOS=HIGH,UMB
shell=a:\command.com /E:512 /P
lastdrive=z

autoexec.bat:
@echo off
path=a:\
a:\awfl823b.exe i010010f.bin
prompt=$p$g

I understand that EMM386 is bad when performing BIOS flashes, but this is something that predates me at this company and it has worked successfully in the past.

Here is what I have tried:
1) removing the autoexec.bat and config.sys files - This would perform the BIOS upgrade but list 4 blocks as "write failed" and so it would not perform the update
2) removing EMM386 from config.sys - same results as #1
3) removing himem.sys and emm386 from congig.sys - same results as #1
4) I have tried flashing the BIOS with the switch that prevents writing the boot block. No change. If emm386 and himem are loaded it wipes out the BIOS, if not then it gives the same results as #1

I have to admit I am stumped. Any suggestions from you gurus out there that might have run into this? I am currently looking into a different DOS as well as a different flashing utility but so far I haven't met with any success (I haven't spent much time on it to be fair).

Any help would be appreciated.

Michael

0
mweyant_marlin
Asked:
mweyant_marlin
1 Solution
 
mweyant_marlinAuthor Commented:
I have since tried tried this process using PC DOS instead of MS DOS with the same results. Any thoughts?
0
 
_Commented:
Other than using a "clean boot disk" (no autuexec, config, etc) which you tryed, I have no idea.

I had one that wouldn't Flash from the floppy, but if I booted from the floppy and changed to the HD and ran the flash from there, it worked flawlessly.  Ain't hardware fun...
0
 
rindiCommented:
Have you tried different settings in the BIOS itself, like trying the flash using "failsafe" settings, or shutting off all the shadowing, maybe setting the "memory hole" option, disabling cache etc?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
mweyant_marlinAuthor Commented:
I havent tried anything in the BIOS itself. I will look into the shadowing possibility.
0
 
mweyant_marlinAuthor Commented:
Well as a quick update I still have no idea what was causing this issue. I have circumvented this by unloading himem.sys and including ramdrive.sys. Once the ramdrive is loaded I copy the bios binary and flash utility to the ramdrive and run the update from there. This seemed to be a work around but I would love to know what the actual cause was..
0
 
_Commented:
Glad you got it working.

As to what the problem is, I have no idea. I got tired of messing with mine, and just chalked it up to "one of those things". Maybe one of these days I will come across some info that will explain it.
0
 
_Commented:
PAQ - Refund

Original question has No Known Answer, but he came up with an interesting work around.
0
 
ee_ai_constructCommented:
PAQ / Refund
ee ai construct, community support moderator
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now