Board Testing HOWTO - Revision history

Icon: "nico.h@gmx.de: Rename => Supported Hardware"

2023-12-03T17:46:58Z

"nico.h@gmx.de: Rename => Supported *H*ardware"

← Older revision		Revision as of 17:46, 3 December 2023
Line 20:		Line 20:
	* Please tell us about your results by sending the output of '''flashprog -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashprog [[Contact#Mailing_List\|mailing list]].		* Please tell us about your results by sending the output of '''flashprog -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashprog [[Contact#Mailing_List\|mailing list]].

	If flashprog finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported ~~hardware~~#Supported_mainboards\|list of boards supported by flashprog]] accordingly (whether it works or does not work on your board).		If flashprog finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported Hardware#Supported_mainboards\|list of boards supported by flashprog]] accordingly (whether it works or does not work on your board).

	== Updating the wiki ==		== Updating the wiki ==

	We try to collect the status for every supported mainboard/card/device on [[Supported ~~hardware~~\|our autogenerated list of supported hardware]].		We try to collect the status for every supported mainboard/card/device on [[Supported Hardware\|our autogenerated list of supported hardware]].
	If you test something we should know about please send a mail to the [[Contact#Mailing_List\|mailing list]].		If you test something we should know about please send a mail to the [[Contact#Mailing_List\|mailing list]].

Icon: "nico.h@gmx.de: Update for flashprog"

2023-12-03T17:46:40Z

"nico.h@gmx.de: Update for flashprog"

Nico@flashrom.org/: "Nico@flashrom.org/: Empty MediaWiki Message"

2023-12-03T17:46:40Z

"Nico@flashrom.org/: *Empty MediaWiki Message*"

← Older revision		Revision as of 17:46, 3 December 2023
Line 18:		Line 18:
	*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase or even read doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.		*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase or even read doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.
	*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.		*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.
	* Please tell us about your results by sending the output of '''flashrom -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[~~Mailinglist~~\|mailing list]].		* Please tell us about your results by sending the output of '''flashrom -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Contact#Mailing_List\|mailing list]].

	If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported hardware#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).		If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported hardware#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).
Line 25:		Line 25:

	We try to collect the status for every supported mainboard/card/device on [[Supported hardware\|our autogenerated list of supported hardware]].		We try to collect the status for every supported mainboard/card/device on [[Supported hardware\|our autogenerated list of supported hardware]].
	If you test something we should know about please send a mail to the [[~~Mailinglist~~\|mailing list]].		If you test something we should know about please send a mail to the [[Contact#Mailing_List\|mailing list]].

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: /* Updating the wiki */"

2023-12-03T17:46:40Z

"Stefanct@flashrom.org/: Updating the wiki: "

← Older revision		Revision as of 17:46, 3 December 2023
Line 24:		Line 24:
	== Updating the wiki ==		== Updating the wiki ==

	We try to collect the status for every supported mainboard/card/device on [[Supported hardware\|our list of supported hardware]].		We try to collect the status for every supported mainboard/card/device on [[Supported hardware\|our autogenerated list of supported hardware]].
	If you test something we should know about please send a mail to the [[Mailinglist\|mailing list]].		If you test something we should know about please send a mail to the [[Mailinglist\|mailing list]].

	~~=== Implementation details ===~~
	~~The status table is implemented using the [[Template:Flashrom supported chips and devices\|status template]] in this wiki which has to be created by running~~

	~~$ '''flashrom --print-supported-wiki'''~~

Icon: "nico.h@gmx.de: Use lighter orange instead of red"

2023-12-03T17:46:40Z

"nico.h@gmx.de: Use lighter orange instead of red"

← Older revision		Revision as of 17:46, 3 December 2023
Line 3:		Line 3:
	== Important information ==		== Important information ==

	* <div style="color:~~red~~">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>		* <div style="color:cb4b16">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>
	* If you have a pre-2012 laptop/notebook/netbook, please do '''NOT''' try flashprog because interactions with the EC on these machines might crash your machine during flashing. Flashprog tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.		* If you have a pre-2012 laptop/notebook/netbook, please do '''NOT''' try flashprog because interactions with the EC on these machines might crash your machine during flashing. Flashprog tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.
	* To check whether flashprog knows about your chipset and ROM chip, run '''flashprog -p internal'''.		* To check whether flashprog knows about your chipset and ROM chip, run '''flashprog -p internal'''.

Uwe@flashrom.org/: "Uwe@flashrom.org/: Empty MediaWiki Message"

2023-12-03T17:46:39Z

"Uwe@flashrom.org/: *Empty MediaWiki Message*"

← Older revision		Revision as of 17:46, 3 December 2023
Line 1:		Line 1:
	This page gives you hints on how to test flashrom support for your mainboard ~~or your~~ graphics card ~~or your~~ network card ~~or your sata~~ card ~~or your~~ external programmer device.		This page gives you hints on how to test flashrom support for your mainboard / graphics card / network card / SATA card / external programmer device.

	==Important information==		== Important information ==

	* <div style="color:red">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>		* <div style="color:red">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>
	* If you have a laptop/notebook/netbook, please do NOT try flashrom because interactions with the EC on these machines might crash your machine during flashing. flashrom tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.		* If you have a laptop/notebook/netbook, please do '''NOT''' try flashrom because interactions with the EC on these machines might crash your machine during flashing. flashrom tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.
	* To check whether [[flashrom]] knows about your chipset and ROM chip, run '''flashrom'''.		* To check whether flashrom knows about your chipset and ROM chip, run '''flashrom'''.
	* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.		* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.
	* To check if you can read the existing BIOS image from the chip, run '''flashrom -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image. (~~Some~~ chipsets will return 0xff for large areas of flash without any error messages.)		* To check if you can read the existing BIOS image from the chip, run '''flashrom -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image (some chipsets will return 0xff for large areas of flash without any error messages).
	* Now the really important part, checking if ''writing'' an image on the chip works:		* Now the really important part, checking if ''writing'' an image on the chip works:
	** First make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe.		** First make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe.
	** Try inserting a ROM chip which you can safely overwrite (e.g. an empty one you bought). Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -w new.bin'''. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.		** Try inserting a ROM chip which you can safely overwrite (e.g. an empty one you bought). Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -w new.bin'''. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.
	** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS CMOS menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom ~~<tt>~~--mainboard~~</tt>~~ switch for some boards.		** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS CMOS menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom '''--mainboard''' switch for some boards.
	** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.		** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.
	** If you can't risk a write on a given chip and if the chip is SPI, the following guidelines may help:		** If you can't risk a write on a given chip and if the chip is SPI, the following guidelines may help:
Line 17:		Line 17:
	*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.		*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.
	*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.		*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.
	* Please tell us about your results by sending the output of		* Please tell us about your results by sending the output of '''flashrom -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].
	flashrom -V
	lspci -nnvvxxx
	superiotool -deV
	and the exact manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].
	If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well.

			If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported hardware#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).

			== Updating the wiki ==

	~~and we'll check~~/~~update~~ the [[~~Supported hardware#Supported_mainboards~~\|~~list of boards supported by flashrom~~]] ~~accordingly (whether it works or does not work on your board)~~.		We try to collect the status for every supported mainboard/card/device. The status table is implemented using the [[Template:Flashrom supported chips and devices\|status template]] in this wiki. The status table is designed to be created by running

	~~== Updating the wiki ==~~		$ '''flashrom --print-supported-wiki'''
	We try to collect the status for every supported mainboard/card/device. The status table is implemented using the [[Template:Flashrom supported chips and devices\|status template]] in this wiki. The status table is designed to be created by running
	flashrom --print-supported-wiki

	Write access to the wiki is only available to regular flashrom contributors. It doesn't hurt to ask on [[IRC]] if you want to change a few things on the wiki. Either someone will change the wiki for you, or you get write access (if you want to change lots of stuff and have demonstrated that you're not trying to vandalize the wiki).		Write access to the wiki is only available to regular flashrom contributors. It doesn't hurt to ask on [[IRC]] if you want to change a few things on the wiki. Either someone will change the wiki for you, or you get write access (if you want to change lots of stuff and have demonstrated that you're not trying to vandalize the wiki).

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: -p internal"

2023-12-03T17:46:39Z

"Stefanct@flashrom.org/: -p internal"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: Empty MediaWiki Message"

2023-12-03T17:46:39Z

"Stefanct@flashrom.org/: *Empty MediaWiki Message*"

← Older revision		Revision as of 17:46, 3 December 2023
Line 1:		Line 1:
	This page gives you hints on how to test flashrom support for ~~your mainboard /~~ graphics ~~card~~ / network ~~card~~ / SATA ~~card /~~ external programmer ~~device~~.		This page gives you mainly hints on how to test flashrom support on mainboards. Testing for graphics / network / SATA cards and external programmer devices is similar but less dangerous.

	== Important information ==		== Important information ==
Line 23:		Line 23:
	== Updating the wiki ==		== Updating the wiki ==

	We try to collect the status for every supported mainboard/card/device. The status table is implemented using the [[Template:Flashrom supported chips and devices\|status template]] in this wiki~~. The status table is designed~~ to be created by running		We try to collect the status for every supported mainboard/card/device on [[Supported hardware\|our list of supported hardware]].
			If you test something we should know about please send a mail to the [[Mailinglist\|mailing list]].

			=== Implementation details ===
			The status table is implemented using the [[Template:Flashrom supported chips and devices\|status template]] in this wiki which has to be created by running

	$ '''flashrom --print-supported-wiki'''		$ '''flashrom --print-supported-wiki'''

	Write access to the wiki is only available to regular flashrom contributors. It doesn't hurt to ask on [[IRC]] if you want to change a few things on the wiki. Either someone will change the wiki for you, or you get write access (if you want to change lots of stuff and have demonstrated that you're not trying to vandalize the wiki).

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: /* Important information */"

2023-12-03T17:46:39Z

"Stefanct@flashrom.org/: Important information: "

Hailfinger@flashrom.org/: "Hailfinger@flashrom.org/: remove useless template"

2023-12-03T17:46:38Z

"Hailfinger@flashrom.org/: remove useless template"

← Older revision		Revision as of 17:46, 3 December 2023
Line 20:		Line 20:
	*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom had a generic block protection checker, we'd be able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.		*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom had a generic block protection checker, we'd be able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.
	* Please tell us about your results by mailing flashrom@flashrom.org and we'll check/update the [[Flashrom#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).		* Please tell us about your results by mailing flashrom@flashrom.org and we'll check/update the [[Flashrom#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).


	~~{{GPL}}~~

← Older revision		Revision as of 17:46, 3 December 2023
Line 20:		Line 20:
	* Please tell us about your results by sending the output of '''flashprog -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashprog [[Contact#Mailing_List\|mailing list]].		* Please tell us about your results by sending the output of '''flashprog -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashprog [[Contact#Mailing_List\|mailing list]].

	If flashprog finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported ~~hardware~~#Supported_mainboards\|list of boards supported by flashprog]] accordingly (whether it works or does not work on your board).		If flashprog finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported Hardware#Supported_mainboards\|list of boards supported by flashprog]] accordingly (whether it works or does not work on your board).

	== Updating the wiki ==		== Updating the wiki ==

	We try to collect the status for every supported mainboard/card/device on [[Supported ~~hardware~~\|our autogenerated list of supported hardware]].		We try to collect the status for every supported mainboard/card/device on [[Supported Hardware\|our autogenerated list of supported hardware]].
	If you test something we should know about please send a mail to the [[Contact#Mailing_List\|mailing list]].		If you test something we should know about please send a mail to the [[Contact#Mailing_List\|mailing list]].

← Older revision		Revision as of 17:46, 3 December 2023
Line 7:		Line 7:
	* To check whether flashrom knows about your chipset and ROM chip, run '''flashrom'''.		* To check whether flashrom knows about your chipset and ROM chip, run '''flashrom'''.
	* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.		* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.
	* To check if you can read the existing BIOS image from the chip, run '''flashrom -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image (some chipsets will return 0xff for large areas of flash without any error messages).		* To check if you can read the existing BIOS image from the chip, run '''flashrom -p internal -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image (some chipsets will return 0xff for large areas of flash without any error messages).
	* Now the really important part, checking if ''writing'' an image on the chip works:		* Now the really important part, checking if ''writing'' an image on the chip works:
	** First make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe.		** First make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe.
	** Try inserting a ROM chip which you can safely overwrite (e.g. an empty one you bought). Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -w new.bin'''. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.		** Try inserting a ROM chip which you can safely overwrite (e.g. an empty one you bought). Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -p internal -w new.bin'''. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.
	** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS CMOS menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom '''--mainboard''' switch for some boards.		** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS CMOS menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom '''--mainboard''' switch for some boards.
	** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.		** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.
Line 17:		Line 17:
	*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.		*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.
	*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.		*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.
	* Please tell us about your results by sending the output of '''flashrom -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].		* Please tell us about your results by sending the output of '''flashrom -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].

	If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported hardware#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).		If flashrom finds your flash chip and everything works, we'd like to hear about it. If your flash chip is found, but not all operations work, we'd like to hear about it. If your flash chip or your chipset is not found, we'd like to hear about it as well, and we'll check/update the [[Supported hardware#Supported_mainboards\|list of boards supported by flashrom]] accordingly (whether it works or does not work on your board).

← Older revision		Revision as of 17:46, 3 December 2023
Line 5:		Line 5:
	* <div style="color:red">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>		* <div style="color:red">DO NOT ATTEMPT TO FOLLOW THESE INSTRUCTIONS UNLESS YOU KNOW WHAT YOU ARE DOING! THIS CAN RENDER YOUR MAINBOARD TOTALLY UNUSABLE! YOU HAVE BEEN WARNED!</div>
	* If you have a laptop/notebook/netbook, please do '''NOT''' try flashrom because interactions with the EC on these machines might crash your machine during flashing. flashrom tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.		* If you have a laptop/notebook/netbook, please do '''NOT''' try flashrom because interactions with the EC on these machines might crash your machine during flashing. flashrom tries to detect if a machine is a laptop, but not all laptops follow the standard, so this is not 100% reliable.
	* To check whether flashrom knows about your chipset and ROM chip, run '''flashrom'''.		* To check whether flashrom knows about your chipset and ROM chip, run '''flashrom -p internal'''.
	* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.		* If it says "Found chipset CHIPSETNAME..." and "CHIPNAME found at..." that's a good first sign.
	* To check if you can read the existing BIOS image from the chip, run '''flashrom -p internal -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image (some chipsets will return 0xff for large areas of flash without any error messages).		* To check if you can read the existing BIOS image from the chip, run '''flashrom -p internal -r backup.bin'''. Make sure that '''backup.bin''' contains a useful BIOS image (some chipsets will return 0xff for large areas of flash without any error messages, but there might be actually large areas of 0xff in the original image as well).
	* Now the really important part, checking if ''writing'' an image on the chip works:		* Now the really important part, checking if ''writing'' an image on the chip works:
	** First make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe.		** First, if the board has a flash socket and you have spare chips, make sure you have a backup chip containing the original BIOS. Also, you should have verified that it actually boots your system successfully. Put away that backup chip somewhere safe and insert a chip which you can safely overwrite (e.g. an empty one you bought).
	** Try inserting a ~~ROM~~ chip which you can safely overwrite (e.g. an empty one you bought). Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -p internal -w new.bin'''. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.		** If that is not possible make sure you have some other way for complete recovery, e.g. an external programmer that can do [[ISP\|in-circuit programming]] on the board in question.
	** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS ~~CMOS~~ menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom '''--mainboard''' switch for some boards.		** Then write an image onto the chip, which is ''different'' from what's on the chip right now: '''flashrom -p internal -w new.bin'''. If the image is equal you will get a notice since r1680. If this works and flashrom reports "VERIFIED" your board is supported by flashrom.
			** If not, you might try to enable the "Enable BIOS Update" or "Write-protect BIOS" or similar options in your BIOS menu first, or set a jumper on your board (this is highly board-dependent). Also, you might have to use the flashrom '''--mainboard''' switch for some boards.
	** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.		** If none of the above helps (but flashrom still ''does'' detect your chipset and ROM chip), there's quite likely a board-specific initialization required in flashrom, which is non-trivial to add (e.g. toggling certain custom GPIO lines etc). In that case, contact us as we may be able to help.
	** If you can't risk a write on a given chip and if the chip is SPI, the following guidelines may help:		** If you can't risk a write on a given chip and if the chip is SPI, the following guidelines may help:
	*** Try probing.		*** Try probing.
	*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.		*** For ICH/VIA SPI, lockdown can mean probe works, but write/erase or even read doesn't. It can also mean that probe does not work, but write/read/erase (or any subset thereof) would work. For all other SPI chipsets, there is no such lockdown, so you can issue any erase/write/read command.
	*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.		*** However, some SPI chips have a WP# pin which causes the block protection bits to become readonly. Now if flashrom has a generic block protection checker for your chip, we're able to figure out if write/erase is possible. Basically, you can check if you need a board enable by setting all block protection bits, then unsetting them. If either of the operations fail, you need a board enable. If they succeed, erase and write are guaranteed to work.
	* Please tell us about your results by sending the output of '''flashrom -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].		* Please tell us about your results by sending the output of '''flashrom -p internal -V''', '''lspci -nnvvxxx''', '''superiotool -deV''' and the exact board manufacturer and model name and all of your observations and test results to the flashrom [[Mailinglist\|mailing list]].

Board Testing HOWTO - Revision history

Icon: "nico.h@gmx.de: Rename => Supported *H*ardware"

Icon: "nico.h@gmx.de: Update for flashprog"

Nico@flashrom.org/: "Nico@flashrom.org/: *Empty MediaWiki Message*"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: /* Updating the wiki */"

Icon: "nico.h@gmx.de: Use lighter orange instead of red"

Uwe@flashrom.org/: "Uwe@flashrom.org/: *Empty MediaWiki Message*"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: -p internal"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: *Empty MediaWiki Message*"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: /* Important information */"

Hailfinger@flashrom.org/: "Hailfinger@flashrom.org/: remove useless template"

Icon: "nico.h@gmx.de: Rename => Supported Hardware"

Nico@flashrom.org/: "Nico@flashrom.org/: Empty MediaWiki Message"

Uwe@flashrom.org/: "Uwe@flashrom.org/: Empty MediaWiki Message"

Stefanct@flashrom.org/: "Stefanct@flashrom.org/: Empty MediaWiki Message"