Bios Version 2.2.8.0

[Rosetta Ockman]

You probably shouldn't update your BIOS, but sometimes you need to. Here's how to check what BIOS version your computer is using and flash that new BIOS version onto your motherboard as quickly and safely as possible.

Your computer's BIOS version is displayed in the BIOS setup menu itself, but you don't have to reboot to check this version number. There are several ways to see your BIOS version from within Windows, and they work the same on PCs with a traditional BIOS or a newer UEFI firmware.

If you purchased a pre-built computer instead of building your own, head to the computer manufacturer's website, look up the computer model, and look at its downloads page. You'll find any available BIOS updates there.

The archive may also contain a README or other text file that will walk you through updating to the new BIOS. You should check out this file for instructions that apply specifically to your hardware, but we'll try to cover the basics that work across all hardware here.

You'll need to choose one of several different types of BIOS-flashing tools, depending on your motherboard and what it supports. The BIOS update's included README file should recommend the ideal option for your hardware.

Some manufacturers offer a BIOS-flashing option directly in their BIOS, or as a special key-press option when you boot the computer. You copy the BIOS file to a USB drive, reboot your computer, and then enter the BIOS or UEFI screen. From there, you choose the BIOS-updating option, select the BIOS file you placed on the USB drive, and the BIOS updates to the new version.

The DOS-based flashing tool is often provided in the BIOS archive you download from the manufacturer's website, although you may have to download it separately. Look for a file with the .bat or .exe file extension.

Some manufacturers provide Windows-based flashing tools, which you run on the Windows desktop to flash your BIOS and then reboot. We don't recommend using these, and even many manufacturers who provide these tools caution against using them. For example, MSI "strongly recommends" using their BIOS-based menu option instead of their Windows-based utility in the README file of the sample BIOS update we downloaded.

The BIOS and compiler versions are stored as part of the project so this project would have originally been created with BIOS 5.40.02.22. Moving from BIOS 5.40 to 5.41 is not a big deal, no real migration steps involved other than changing the BIOS version associated with the project. Right click on your project and select build properties. In the dialog that opens select CCS build settings on the left. Now on the right hand side you should be able to change the version of BIOS set for the project.

Thanks, but as the image above shows, I have already done this. To be more clear, below the entire CCS Build config window. Note the use of 5.41.02.14 DSP/BIOS. Could there be something in the orginal project file (EZDSP_AudioFilter.pjt) that was packaged with the sample project?

This project was created using a version of DSP/BIOS tools that is not currently installed: 5.41.10.36. Please install the DSP/BIOS tools of this version, or migrate the project to one of the supported versions.
Build stopped.

Victor - Do you have a version of DSP/BIOS installed and recognized by your CCSv6 installation? If so, CCS should try to use it. Note that CCSv6 does not come with DSP/BIOS by default (you can get it from the App Center)

The information here includes both version and BIOS revision. If dmidecode does not include that data on your machine, I'm afraid you will have to reboot and actually look at the BIOS.

I am also have a MSA 2060 SAN connected via x2 16gb Fibre channel adaptors and I want to update to the latest firmware but want to ensure there will be no issues based on the current hosts bios version?

There should be no issue with upgrading the BIOS directly to the latest version. However, I would generally recommend updating it using the SPP on the servers in order to make sure everything is at supported revisions, instead of doing it piecemeal. That should also help to ensure that the MSA is also at versions that are supported with the other components in the server.

I believe that, technically, the last version with ESXi 6.7 support in the SPP is the 2022.03 SPP. The latest BIOS update should work fine with this version of ESXi. The VMware compatability guide does not list anything later than 2.72, even with ESXi 8.0:

This combination or just the old BIOS-Version is the reaoson why the laptop fans stays calm and silent while the CPU works with max 2,75 Ghz. The temperatures of the main components were 40-50 degree, while I updated the old laptop.

How can I fix that? Does a rollback fix it? Is it an hardware issue? Because all works, except that the white glowing led is a blue. Or is it a motherboard issue, because the "rollback-initializing" process which started by pressing WIN+B and Power-Button can't be finished/brough to an end?

When I read all of the previous BIOS' version release notes, I don't see any of them that indicate 'you cannot roll back to a previous version' message, so you should be able to install any of the previous versions you want.

The update process was executed in DOS environment using the command "iflash2 /pf TC0048P.bio". The system restarted and initiated the update process. It was taking too long though (more than 10 minutes). Having no other choice, I left it to its guns to (hopefully) complete the update, and went away to do something else. Upon returning, a good 30 minutes later, the system's fans were running and the screen was black. At that point no amount of resetting, turning it on/off, clearing the CMOS, etc. could get it to boot.

There are ways to recover but these did not work. I prepared a USB drive with only the BIOS file on it, removed the jumper from the motherboard to initiate recovery process but to no avail. The other option would be flashing the BIOS externally. The problem is that the BIOS chip (MX25L6445E) is 8 megabytes whilst the bios file is near 10 megabytes. I was still able to flash (with a warning) using the CH341a programming tool but, again, that didn't work.

First, let me say that other than swapping out or otherwise upgrading drives and memory cards, I am NOT an expert hardware guy. I have on occasion run the F7 BIOS updates many years ago, but on the whole I've "let sleeping dogs lay".

The problem prompting my post here is that a DVD optical drive recently connected to the SATA 2 port (SSD & HDD in ports 0 and 1) while showing in the BIOS and Device Manager fails to appear along with the drives in Windows Explorer. To the best of my knowledge, the Optical drive is functioning properly, at least Device Manager reports it as such.

So, given all the above, it would seem the first order of business ought to be to get the BIOS up-to-date? If so, will the "TC00P48.bio" file take my current version 37 BIOS through the series of updates in one swoop, or does one have to obtain the intervening updates and do them one at a time? OR, do you recognize the "WE no show" issue and there's a simple solution that doesn't involve the BIOS at all?

Sounds like your issue is a Windows problem. Maybe try assigning a new drive letter to the DVD drive in Windows Drive Management? Failing that you could perform a DISM / SFC or even a re-install of Windows.

That said BIOS updates are fun, and easy. My hobby is buying old computers and seeing if I can turn them into something usable. Once I get something running the next step is BIOS update. It was pretty easy on this Intel board so I recommended it. My most recent purchase was a M83 Lenovo and it actually made me write an ISO to CD and connect a physical optical drive to it before it got going.

.BIN files are not provided for desktop boards because you are basically stealing the identity of another board. Those .BIN files that you do find are from someone who as copied the bios from one board, and sells the .BIN file to people, like you. Now, if you have a damaged board, and copy the bios in .BIN format, that is "acceptible". But, most that you find are clones from good boards and should not be used. Consider, for example, you will have the same MAC address as another board.

By professional I mean someone who has experience with these boards. I have been using Intel desktop boards for a VERY long time. And, Scott has been using them longer than me. I have updated the bios on desktop boards probably three times a year for the past 30 years or so. Do the math. And, I have seen a good number of guys with a chip burner make mistakes and roach/brick their boards, and try to blame it on Intel. And, you could have come this forum BEFORE you tried anything and asked questions.

You are actually mistaken about the working BIOS files. To put matters into perspective, I have a Lenovo Ideacentre Y900 of which the BIOS was password-protected from the previous owner. There was no way to unlock it and used the serial number of that system to download a working BIOS file directly from Lenovo that I used to successfully flash the BIOS on that system, with my external flasher, in order to remove the password. Of course more work was needed later to also add details like serial number UUID, MAC address etc but, the bottomline is, it worked!

About the procedure now for the Intel board now. If you followed this thread closely, you would have read that I followed the conventional procedure first, before resorting to the flasher, and it FAILED. Is that my fault too? Would your 30 years of experience have predicted that by following the standard procedure to update the BIOS would result to a failed BIOS update? I don't think so.

Lenovo's bios belongs to lenovo and they can do what they want. Not relevent here because this is an intel bios and board. So, it is your mistake to assume they are the same. And, to help you further, dell's bios belongs to dell, asus bios belongs to asus, msi bios belongs to msi, etc., etc., etc. They may or may not have the same restrictions as Intel.

c80f0f1006