flashrom

flashrom@flashrom.org

8 participants
9164 discussions

Re: [flashrom] I lost my backup image and now my pc doesn't start...!
by İlhan Kahraman 08 Jan '12

08 Jan '12

No, it didn't give any errors. And No, bupdater identifies the bios of m4a.... and gives an error mesage because it knows the board is not appropriate for the bios of m4a.... So I have to do it with flashrom. Yes I can do hot swap as I mention in prev. mail. Same protocol same voltages... The one thing that I totally confused that: *the flashing*. Is it just a " sudo flashrom -w any.rom " process or more complicated than that like: updating some part of the chip with -- layout or -- image options and leaving other parts of the chip whit its original contents (like boot block) or something like that? And I do not really know if this process can affect the amd chipset of my board or its only effective on the flash chip? İf its just a writing process of any .ROM file I thing I can try forcing it to writing operation with internal programer... Thanks for Luck :)) 8 Ocak 2012 19:37 tarihinde Marcos Felipe Rasia de Mello < marcosfrm(a)gmail.com> yazdı: > 2012/1/8 İlhan Kahraman <ilhan805(a)gmail.com> > > > > Hello there..., > > > > My name is ilhan and I have just started to use a linux > operating system, so I am new to all of these linux applications... > > While I am using this operating system, my self-confidence about diving > into more tough stuff like flashtom-0.9.4. , has pushed > > me a downgrade flashing attempt on my motherboard, Asus M4A88TD-V > EVO/USB3. > > > > Actually, I have tried a downgrade flashing whit my mobo's > official applications, such as asus update and bupdater, in both FreeDos > and > > Win7 environments but, this did not help me and kept saying that " you > are trying to load an old version of bios"... > > > > So, I downloaded flashrom-0.9.4 source, installed it according > to README file, read its manual > > (http://www.flashrom.org/trac/flashrom/browser/trunk/flashrom.8) and > finally I made a backup file. > > > > While playing around these linux applications and > procrastinating my bios flashing, days gone by... Then one day :)... I just > decided > > to flash my bios because of increased freezings and shutdowns in Win7, > without being aware of that I have lost my usb stick in which I > > backup my mobos image whit using: > > > > sudo flashrom -r m4a88tdbackup > > > > > > In other words; I, unconsciously, started the flashing whit out > having a backup file... > > > > I simbly downloaded my old bios to my desktop (M4A88TD-V EVO/USB3 BIOS > 1601) from: > > > http://support.asus.com/download/download_item_mkt.aspx?slanguage=en-us&mod… > > > > I named this file as m4a88tdnew.ROM > > > > and continue with ... > > > > ilhan@ubuntu:~/Desktop$ >> sudo flashrom -E > > ilhan@ubuntu:~/Desktop$ >> sudo flashrom -w m4a88tdnew.ROM > > > > After flashrom verified that the chip (winbond W25Q16) content > and the file content was same, I hit the re-start button and this was the > end of my computer :) > > It has not respond anything after that, not even any fan has cycled... I > have already tried the firmware CD and usb which both contains the > > m4a88tu3.rom ( I think its the equivalent of the amitool.rom in the > asus due to user guide instructions), have clear the cmos without its > battery and > > have un-plugged everything (expect cpu) in various combinations... All I > have now, at start, CD-rom trying to read the CDs but it gives up quickly > and > > the most important the cpu fan and the cpu ( I guess) does not work... > > > > Trying all of this with out any luck, I decided to buy a new but > cheaper mobo. I bought a Asus M4N68T-M ( with Nvidia MCP61 chipset > (un-tested) and Eon EN25F80 > > flash chip). I plugged everything on this mobo and it just working like > a charm. > > > > With this new card I continued my attempts to flash my old cards chip > but, I realized that I have no enough skills even making a simple > confirmation of that: did I succeed it, > > in a right way. I decided to go in short way, made a simple search on > the issue and found the yann's report ( > http://paste.flashrom.org/view.php?id=687) about my old card. > > I requested from him to send me his back up image file via e-mail and > he, kindly, said that he hadn't got any backup and directed me to the Asus > support site which I already tried. > > > > After all of this, as a last resort, I decided to stole your precious > time for my unimportant problem... Can you help me about it. Can I resque > my old card and how? > > I thought, if you can help me, in return of this help; I could > contribute by sending you a report about both my new and old mobos :) I > thing it is a good deal...:)) > > > > So How can I flash my old card's chip in my new card and verify its > flashed in a right way? > > > > I thank you very much by now for just reading this long. > > > > > > > > Have a good day.... > > > > > > -- > > İlhan KAHRAMAN > > Undergraduate Student at > > Materials Science & Engineering Department > > and > > Department of Industrial Design, > > Anadolu University, Eskisehir, > > Turkey > > e-mail: ilhan805(a)gmail.com > > > > > > Hi, > > Did "sudo flashrom -w m4a88tdnew.ROM" show any errors? If no, I can > only think this board requires some magic from the official update > tool to work... > > To restore your old chip contents using the new board you will need > hot swap. Before continuing see if both chips have the same protocol > and voltage. Power on your new board and load Linux. With the system > powered on, remove with care the flash chip and put the "dead" one in > place. Run flashrom -E and -w as usual. Power off and put each chip in > its original place. However I don't think it will help if your first > update attempt apparently was completed without errors. > > You can also use the DOS tool. Maybe it's the solution: > > UPDATE > bupdater /iBIOS.ROM /pc /g > > BACKUP > bupdater /oBKP.ROM > > The bios filename has *no* space after the "/i" and "/o" switches. > > Good luck. > > Marcos > -- İlhan KAHRAMAN Undergraduate Student at Materials Science & Engineering Department and Department of Industrial Design, Anadolu University, Eskisehir, Turkey e-mail: ilhan805(a)gmail.com

1 0

Re: [flashrom] I lost my backup image and now my pc doesn't start...!
by Marcos Felipe Rasia de Mello 08 Jan '12

08 Jan '12

2012/1/8 İlhan Kahraman <ilhan805(a)gmail.com> > > Hello there..., > > My name is ilhan and I have just started to use a linux operating system, so I am new to all of these linux applications... > While I am using this operating system, my self-confidence about diving into more tough stuff like flashtom-0.9.4. , has pushed > me a downgrade flashing attempt on my motherboard, Asus M4A88TD-V EVO/USB3. > > Actually, I have tried a downgrade flashing whit my mobo's official applications, such as asus update and bupdater, in both FreeDos and > Win7 environments but, this did not help me and kept saying that " you are trying to load an old version of bios"... > > So, I downloaded flashrom-0.9.4 source, installed it according to README file, read its manual > (http://www.flashrom.org/trac/flashrom/browser/trunk/flashrom.8) and finally I made a backup file. > > While playing around these linux applications and procrastinating my bios flashing, days gone by... Then one day :)... I just decided > to flash my bios because of increased freezings and shutdowns in Win7, without being aware of that I have lost my usb stick in which I > backup my mobos image whit using: > > sudo flashrom -r m4a88tdbackup > > > In other words; I, unconsciously, started the flashing whit out having a backup file... > > I simbly downloaded my old bios to my desktop (M4A88TD-V EVO/USB3 BIOS 1601) from: > http://support.asus.com/download/download_item_mkt.aspx?slanguage=en-us&mod… > > I named this file as m4a88tdnew.ROM > > and continue with ... > > ilhan@ubuntu:~/Desktop$ >> sudo flashrom -E > ilhan@ubuntu:~/Desktop$ >> sudo flashrom -w m4a88tdnew.ROM > > After flashrom verified that the chip (winbond W25Q16) content and the file content was same, I hit the re-start button and this was the end of my computer :) > It has not respond anything after that, not even any fan has cycled... I have already tried the firmware CD and usb which both contains the > m4a88tu3.rom ( I think its the equivalent of the amitool.rom in the asus due to user guide instructions), have clear the cmos without its battery and > have un-plugged everything (expect cpu) in various combinations... All I have now, at start, CD-rom trying to read the CDs but it gives up quickly and > the most important the cpu fan and the cpu ( I guess) does not work... > > Trying all of this with out any luck, I decided to buy a new but cheaper mobo. I bought a Asus M4N68T-M ( with Nvidia MCP61 chipset (un-tested) and Eon EN25F80 > flash chip). I plugged everything on this mobo and it just working like a charm. > > With this new card I continued my attempts to flash my old cards chip but, I realized that I have no enough skills even making a simple confirmation of that: did I succeed it, > in a right way. I decided to go in short way, made a simple search on the issue and found the yann's report (http://paste.flashrom.org/view.php?id=687) about my old card. > I requested from him to send me his back up image file via e-mail and he, kindly, said that he hadn't got any backup and directed me to the Asus support site which I already tried. > > After all of this, as a last resort, I decided to stole your precious time for my unimportant problem... Can you help me about it. Can I resque my old card and how? > I thought, if you can help me, in return of this help; I could contribute by sending you a report about both my new and old mobos :) I thing it is a good deal...:)) > > So How can I flash my old card's chip in my new card and verify its flashed in a right way? > > I thank you very much by now for just reading this long. > > > > Have a good day.... > > > -- > İlhan KAHRAMAN > Undergraduate Student at > Materials Science & Engineering Department > and > Department of Industrial Design, > Anadolu University, Eskisehir, > Turkey > e-mail: ilhan805(a)gmail.com > > Hi, Did "sudo flashrom -w m4a88tdnew.ROM" show any errors? If no, I can only think this board requires some magic from the official update tool to work... To restore your old chip contents using the new board you will need hot swap. Before continuing see if both chips have the same protocol and voltage. Power on your new board and load Linux. With the system powered on, remove with care the flash chip and put the "dead" one in place. Run flashrom -E and -w as usual. Power off and put each chip in its original place. However I don't think it will help if your first update attempt apparently was completed without errors. You can also use the DOS tool. Maybe it's the solution: UPDATE bupdater /iBIOS.ROM /pc /g BACKUP bupdater /oBKP.ROM The bios filename has *no* space after the "/i" and "/o" switches. Good luck. Marcos

1 0

I lost my backup image and now my pc doesn't start...!
by İlhan Kahraman 08 Jan '12

08 Jan '12

Hello there..., My name is ilhan and I have just started to use a linux operating system, so I am new to all of these linux applications... While I am using this operating system, my self-confidence about diving into more tough stuff like *flashtom-0.9.4. *, has pushed me a downgrade flashing attempt on my motherboard, *Asus M4A88TD-V EVO/USB3*. Actually, I have tried a downgrade flashing whit my mobo's official applications, such as *asus update and bupdater, *in both FreeDos and * *Win7 environments but, this did not help me and kept saying that " you are trying to load an old version of bios"... So, I downloaded flashrom-0.9.4 source, installed it according to README file, read its manual (http://www.flashrom.org/trac/flashrom/browser/trunk/flashrom.8) and finally *I made a backup file*. While playing around these linux applications and procrastinating my bios flashing, days gone by... Then one day :)... I just decided to flash my bios because of increased freezings and shutdowns in Win7, without being aware of that I have lost my usb stick in which I backup my mobos image whit using: sudo flashrom -r m4a88tdbackup In other words; I, unconsciously, started the flashing whit out having a backup file... I simbly downloaded my old bios to my desktop (M4A88TD-V EVO/USB3 BIOS 1601)from: http://support.asus.com/download/download_item_mkt.aspx?slanguage=en-us&mod… I named this file as m4a88tdnew.ROM and continue with ... ilhan@ubuntu:~/Desktop$ >> sudo flashrom -E ilhan@ubuntu:~/Desktop$ >> sudo flashrom -w m4a88tdnew.ROM After flashrom *verified that the chip (winbond W25Q16) content and the file content was same*, I hit the re-start button and this was the end of my computer :) It has not respond anything after that, not even any fan has cycled... I have already tried the firmware CD and usb which both contains the m4a88tu3.rom ( I think its the equivalent of the amitool.rom in the asus due to user guide instructions), have clear the cmos without its battery and have un-plugged everything (expect cpu) in various combinations... All I have now, at start, CD-rom trying to read the CDs but it gives up quickly and the most important the cpu fan and the cpu ( I guess) does not work... Trying all of this with out any luck, I decided to buy a new but cheaper mobo. I bought a Asus M4N68T-M ( *with Nvidia MCP61 chipset (un-tested) and Eon EN25F80 flash chip*). I plugged everything on this mobo and it just working like a charm. With this new card I continued my attempts to flash my old cards chip but, I realized that I have no enough skills even making a simple confirmation of that: did I succeed it, in a right way. I decided to go in short way, made a simple search on the issue and found the* yann's report *( http://paste.flashrom.org/view.php?id=687) about my old card. I requested from him to send me his back up image file via e-mail and he, kindly, said that he hadn't got any backup and directed me to the Asus support site which I already tried. *After all of this, as a last resort, I decided to stole your precious time for my unimportant problem... Can you help me about it. Can I resque my old card and how? I thought, if you can help me, in return of this help; I could contribute by sending you a report about both my new and old mobos :) I thing it is a good deal...:)) So How can I flash my old card's chip in my new card and verify its flashed in a right way? I thank you very much by now for just reading this long. * Have a good day.... -- İlhan KAHRAMAN Undergraduate Student at Materials Science & Engineering Department and Department of Industrial Design, Anadolu University, Eskisehir, Turkey e-mail: ilhan805(a)gmail.com

1 0

Problems flashing bios
by Feldi alias aXl 08 Jan '12

08 Jan '12

Hello all, i have problems flashing my bios with your utility. i have rented a small root-server in germany (http://www.hetzner.de/hosting/produkte_rootserver/x2) and wanted to update the bios. at the moment the hetzner rescue system is booted. infos: root@rescue ~ # uname -a Linux rescue 2.6.39.2 #1 SMP Mon Jul 25 18:36:18 CEST 2011 x86_64 GNU/Linux its a small debian system. flashrom is installed via apt: root@rescue ~ # flashrom --version flashrom v0.9.2-r1141 on Linux 2.6.39.2 (x86_64), built with libpci 3.1.7, GCC 4.4.5 20100728 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org hwinfo says this about my mainboard: root@rescue ~ # hwinfo --bios | grep "Board Info" -A 10 Board Info: #2 Manufacturer: "MICRO-STAR INTERNATIONAL CO., LTD" Product: "MS-7094" Version: "1.00" Chassis Info: #3 Type: 0x03 (Desktop) Bootup State: 0x02 (Unknown) Power Supply State: 0x02 (Unknown) Thermal State: 0x02 (Unknown) Security Status: 0x02 (Unknown) Processor Info: #4 so i entered "ms-7094" on the msi page and getted this site: http://www.msi-computer.de/product/mb/K8T-Neo2-F-V2-0.html#/?div=BIOS first i backuped the old bios with "flashrom --read bios.bak" and then tried to write the new bios with "flashrom --write W7094vms.360" .... then i get this error: root@rescue ~ # flashrom --write W7094vms.360 flashrom v0.9.2-r1141 on Linux 2.6.39.2 (x86_64), built with libpci 3.1.7, GCC 4.4.5 20100728 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Found chip "Winbond W39V040A" (512 KB, LPC) at physical address 0xfff80000. === This flash part has status UNTESTED for operations: ERASE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -Vw, -VE), and mention which mainboard or programmer you tested. Thanks for your help! === Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Erasing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0000ffff: 0x4c4 ERASE FAILED! ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x48ec4 ERASE FAILED! FAILED! ERASE FAILED! FAILED! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! what to do now? thanks for any help! p.s.: sorry for my bad english :) greetz from germany, axel

1 0

Re: [flashrom] Help: unable to upgrade bios
by David Hendricks 06 Jan '12

06 Jan '12

On Fri, Jan 6, 2012 at 5:12 AM, Raghuramchary Jallipalli < Raghuramchary.Jallipalli(a)lntinfotech.com> wrote: > The force option enable worked and we were able to program the AT25DF321A > flash. But the contents are wrong and the board was not able to come up. > Please see attached for the verbose output for both read and write. > There is a high likelihood that either the Management Engine (ME) or embedded controller (EC) is interfering with Flashrom operation. One concern is that flashrom does not appear to set the op.atomic field properly: 0x94: 0x0606 (PREOP) 0x96: 0x0be4 (OPTYPE) 0x98: 0x02030105 (OPMENU) 0x9C: 0xff9f3c20 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xD0: 0x00000000 (FPB) Reading OPCODES... done preop0=0x06, preop1=0x06 op[0]=0x05, 0, 0 op[1]=0x01, 1, 0 op[2]=0x03, 2, 0 op[3]=0x02, 3, 0 op[4]=0x20, 3, 0 op[5]=0x3c, 2, 0 op[6]=0x9f, 0, 0 op[7]=0xff, 0, 0 The third column shows that none of the opcodes are configured as atomic cycles. Thus, Flashrom does not know to set the SPIC_ACS bit ( http://flashrom.org/trac/flashrom/browser/trunk/ichspi.c#L782) when processing these opcodes. If the "atomic" field is not set properly, then it is possible for ME or EC to interfere with flashrom in between write enable (WREN) opcodes such as block erase and program page. On Fri, Jan 6, 2012 at 5:12 AM, Raghuramchary Jallipalli < Raghuramchary.Jallipalli(a)lntinfotech.com> wrote: > For your info, the board has two flashes(each 4MB) and the bios resides on > the second(we have a jumper option to select the flash device). We are > confused whether the flashrom selects the correct flash device and program > it. > Are both ROMs logically present? Or will the jumper only enable one ROM at a given time? If there are multiple ROMs present, then Flashrom use the "Hardware Sequencing" method of flashing when it detects the "Number of Components" (NC) > 0 in the flash descriptor region: http://flashrom.org/trac/flashrom/browser/trunk/ichspi.c#L1742 See FLMAP0 in the Intel documentation for more details, and ensure the NC field is programmed appropriately for your mainboard configuration. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

flashrom -V
by Vince S 06 Jan '12

06 Jan '12

probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50 Found SST flash chip "SST49LF040B" (512 kB, LPC). No operations were specified. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x90 Restoring PCI config space for 00:01:0 reg 0x8c Restoring PCI config space for 00:01:0 reg 0x88 Thanks for your work

1 0

Re: [flashrom] Help: unable to upgrade bios
by Stefan Tauner 06 Jan '12

06 Jan '12

On Tue, 3 Jan 2012 22:51:42 +0530 Raghuramchary Jallipalli <Raghuramchary.Jallipalli(a)lntinfotech.com> wrote: > Do you have any plans to support the laptops with QM67 chipset and AT25DF321A, AT25DF641A flashchips, to upgrade the bios gracefully? If yes, can you please give us the timeline. Hello Raghu! the AT25DF321A is already supported, but untested (usually SPI chips just work). The AT25DF641A is almost identical to the AT25DF641 and will (for now) be detected and used as such. The latter is supported, but as well untested. I dont see a problem regarding those chips. In the event that a problem is encountered we can probably fix it quite fast. The other part of the question is not that easily answered. First of all laptops have additional chips (embedded controllers) involved in accessing the flash device which we dont support in general at the moment. This is a long term goal without a timeline (you could depend on). The chipset itself is supported. It just have some features that - if enabled - prohibit accessing some portions of the flash. There is some work done on working around this, but do not expect this to arrive soon please. I could tell you at least a bit more, if you could post a verbose output of running flashrom (including the laptop-enabling parameter of course). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 2

2CHIPSET: Alix 6F2
by Philip Prindeville 04 Jan '12

04 Jan '12

# flashrom flashrom v0.9.3-r1205 on Linux 2.6.39.4 (i586), built with libpci 3.1.7, GCC 4.5.4 20110808 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. No coreboot table found. Found chipset "AMD CS5536", enabling flash write... OK. WARNING: unexpected second chipset match: "AMD CS5536" ignoring, please report lspci and board URL to flashrom(a)flashrom.org with 2CHIPSET: your board name in the subject line. This chipset supports the following protocols: Non-SPI. Found chip "AMIC A49LF040A" (512 KB, LPC) at physical address 0xfff80000. No operations were specified. #

3 6

GIGABYTE M61P-S3
by ekso 03 Jan '12

03 Jan '12

Hi This chipset is not really supported yet... Please view attached file.

2 1

[PATCH] Replace --mainboard with -p internal:mainboard
by Carl-Daniel Hailfinger 03 Jan '12

03 Jan '12

--mainboard is a relic from a time before external programmers and makes the CLI inconsistent. Use a programmer parameter instead and free up the short option -m. A nice side effect is that there is one less corner case we have to care about in the logging patch. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-kill_cli_mainboard_parameter/cli_classic.c =================================================================== --- flashrom-kill_cli_mainboard_parameter/cli_classic.c (Revision 1482) +++ flashrom-kill_cli_mainboard_parameter/cli_classic.c (Arbeitskopie) @@ -128,11 +128,6 @@ " -V | --verbose more verbose output\n" " -c | --chip <chipname> probe only for specified " "flash chip\n" -#if CONFIG_INTERNAL == 1 - /* FIXME: --mainboard should be a programmer parameter */ - " -m | --mainboard <[vendor:]part> override mainboard " - "detection\n" -#endif " -f | --force force specific operations " "(see man page)\n" " -n | --noverify don't auto-verify\n" @@ -190,7 +185,6 @@ {"verify", 1, NULL, 'v'}, {"noverify", 0, NULL, 'n'}, {"chip", 1, NULL, 'c'}, - {"mainboard", 1, NULL, 'm'}, {"verbose", 0, NULL, 'V'}, {"force", 0, NULL, 'f'}, {"layout", 1, NULL, 'l'}, @@ -275,17 +269,6 @@ } erase_it = 1; break; - case 'm': -#if CONFIG_INTERNAL == 1 - tempstr = strdup(optarg); - lb_vendor_dev_from_string(tempstr); -#else - fprintf(stderr, "Error: Internal programmer support " - "was not compiled in and --mainboard only\n" - "applies to the internal programmer. Aborting.\n"); - cli_classic_abort_usage(); -#endif - break; case 'f': force = 1; break; Index: flashrom-kill_cli_mainboard_parameter/internal.c =================================================================== --- flashrom-kill_cli_mainboard_parameter/internal.c (Revision 1482) +++ flashrom-kill_cli_mainboard_parameter/internal.c (Arbeitskopie) @@ -213,6 +213,16 @@ } free(arg); + arg = extract_programmer_param("mainboard"); + if (arg && strlen(arg)) { + lb_vendor_dev_from_string(arg); + } else if (arg && !strlen(arg)) { + msg_perr("Missing argument for mainboard.\n"); + free(arg); + return 1; + } + free(arg); + get_io_perms(); if (register_shutdown(internal_shutdown, NULL)) return 1; Index: flashrom-kill_cli_mainboard_parameter/cbtable.c =================================================================== --- flashrom-kill_cli_mainboard_parameter/cbtable.c (Revision 1482) +++ flashrom-kill_cli_mainboard_parameter/cbtable.c (Arbeitskopie) @@ -33,17 +33,19 @@ char *lb_part = NULL, *lb_vendor = NULL; int partvendor_from_cbtable = 0; -void lb_vendor_dev_from_string(char *boardstring) +void lb_vendor_dev_from_string(const char *boardstring) { + /* strtok may modify the original string. */ + char *tempstr = strdup(boardstring); char *tempstr2 = NULL; - strtok(boardstring, ":"); + strtok(tempstr, ":"); tempstr2 = strtok(NULL, ":"); if (tempstr2) { - lb_vendor = boardstring; + lb_vendor = tempstr; lb_part = tempstr2; } else { lb_vendor = NULL; - lb_part = boardstring; + lb_part = tempstr; } } Index: flashrom-kill_cli_mainboard_parameter/flashrom.8 =================================================================== --- flashrom-kill_cli_mainboard_parameter/flashrom.8 (Revision 1482) +++ flashrom-kill_cli_mainboard_parameter/flashrom.8 (Arbeitskopie) @@ -88,19 +88,6 @@ without the vendor name as parameter. Please note that the chip name is case sensitive. .TP -.B "\-m, \-\-mainboard" [<vendor>:]<board> -Override mainboard settings. -.sp -flashrom reads the coreboot table to determine the current mainboard. If no -coreboot table could be read or if you want to override these values, you can -specify \-m, e.g.: -.sp -.B " flashrom \-\-mainboard AGAMI:ARUMA \-w agami_aruma.rom" -.sp -See the 'Known boards' or 'Known laptops' section in the output -of 'flashrom \-L' for a list of boards which require the specification of -the board name, if no coreboot table is found. -.TP .B "\-f, \-\-force" Force one or more of the following actions: .sp @@ -245,11 +232,16 @@ running coreboot, the mainboard type is determined from the coreboot table. Otherwise, the mainboard is detected by examining the onboard PCI devices and possibly DMI info. If PCI and DMI do not contain information to uniquely -identify the mainboard (which is the exception), it might be necessary to -specify the mainboard using the -.B \-m -switch (see above). +identify the mainboard (which is the exception), or if you want to override +the detected mainboard model, you can specify the mainboard using the .sp +.B " flashrom \-p internal:mainboard=[<vendor>:]<board>" +syntax. +.sp +See the 'Known boards' or 'Known laptops' section in the output +of 'flashrom \-L' for a list of boards which require the specification of +the board name, if no coreboot table is found. +.sp Some of these board-specific flash enabling functions (called .BR "board enables" ) in flashrom have not yet been tested. If your mainboard is detected needing Index: flashrom-kill_cli_mainboard_parameter/programmer.h =================================================================== --- flashrom-kill_cli_mainboard_parameter/programmer.h (Revision 1482) +++ flashrom-kill_cli_mainboard_parameter/programmer.h (Arbeitskopie) @@ -264,7 +264,7 @@ void cleanup_cpu_msr(void); /* cbtable.c */ -void lb_vendor_dev_from_string(char *boardstring); +void lb_vendor_dev_from_string(const char *boardstring); int coreboot_init(void); extern char *lb_part, *lb_vendor; extern int partvendor_from_cbtable; -- http://www.hailfinger.org/

3 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom