flashrom

flashrom@flashrom.org

3 participants
9188 discussions

[PATCH] Add serprog to man page
by Carl-Daniel Hailfinger 18 Aug '09

18 Aug '09

Add serprog documentation to the manpage. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-serprog_manpage/flashrom.8 =================================================================== --- flashrom-serprog_manpage/flashrom.8 (Revision 686) +++ flashrom-serprog_manpage/flashrom.8 (Arbeitskopie) @@ -150,6 +150,8 @@ .sp .BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)" .sp +.BR "* serprog" " (for flash ROMs attached to Urja's AVR programmer)" +.sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the .B "flashrom -p dummy=type" @@ -182,16 +184,16 @@ .BR nic3com , .BR satasii . .sp -The it87spi has an optional parameter which will set the I/O base port of the -IT87* SPI controller interface to the port specified in the parameter. -For that you have to use the +The it87spi programmer has an optional parameter which will set the I/O base +port of the IT87* SPI controller interface to the port specified in the +parameter. For that you have to use the .B "flashrom -p it87spi=port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp -The ft2232spi has an optional parameter specifying the controller type and -interface/port it should support. For that you have to use the +The ft2232spi programmer has an optional parameter specifying the controller +type and interface/port it should support. For that you have to use the .B "flashrom -p ft2232spi=model,port=interface" syntax where .B model @@ -206,6 +208,19 @@ .B 4232H and the default interface is .BR B . +.sp +The serprog programmer has an optional parameter specifying either a serial +device/baud combination or an IP/port combination for communication with the +programmer. For serial, you have to use the +.B "flashrom -p serprog=/dev/device:baud" +syntax and for IP, you have to use +.B "flashrom -p serprog=ip:port" +instead. More information about serprog is available in serprog-protocol.txt in +the source distribution. +.sp +Support for some programmers can be disabled at compile time. +.B "flashrom -h" +lists all supported programmers. .TP .B "\-h, \-\-help" Show a help text and exit. -- http://www.hailfinger.org/

2 2

[commit] r689 - trunk
by svn＠flashrom.org 18 Aug '09

18 Aug '09

Author: hailfinger Date: 2009-08-19 01:51:22 +0200 (Wed, 19 Aug 2009) New Revision: 689 Modified: trunk/flashrom.8 Log: Add serprog documentation to the manpage. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/flashrom.8 =================================================================== --- trunk/flashrom.8 2009-08-18 23:50:14 UTC (rev 688) +++ trunk/flashrom.8 2009-08-18 23:51:22 UTC (rev 689) @@ -146,6 +146,8 @@ .sp .BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)" .sp +.BR "* serprog" " (for flash ROMs attached to Urja's AVR programmer)" +.sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the .B "flashrom -p dummy=type" @@ -178,16 +180,16 @@ .BR nic3com , .BR satasii . .sp -The it87spi has an optional parameter which will set the I/O base port of the -IT87* SPI controller interface to the port specified in the parameter. -For that you have to use the +The it87spi programmer has an optional parameter which will set the I/O base +port of the IT87* SPI controller interface to the port specified in the +parameter. For that you have to use the .B "flashrom -p it87spi=port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp -The ft2232spi has an optional parameter specifying the controller type and -interface/port it should support. For that you have to use the +The ft2232spi programmer has an optional parameter specifying the controller +type and interface/port it should support. For that you have to use the .B "flashrom -p ft2232spi=model,port=interface" syntax where .B model @@ -202,6 +204,19 @@ .B 4232H and the default interface is .BR B . +.sp +The serprog programmer has an optional parameter specifying either a serial +device/baud combination or an IP/port combination for communication with the +programmer. For serial, you have to use the +.B "flashrom -p serprog=/dev/device:baud" +syntax and for IP, you have to use +.B "flashrom -p serprog=ip:port" +instead. More information about serprog is available in serprog-protocol.txt in +the source distribution. +.sp +Support for some programmers can be disabled at compile time. +.B "flashrom -h" +lists all supported programmers. .TP .B "\-h, \-\-help" Show a help text and exit.

1 0

[PATCH] Tidy up docs before release
by Carl-Daniel Hailfinger 18 Aug '09

18 Aug '09

Tidy up docs before release. Don't mention coreboot.org without context. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-doc_cosmetics/flashrom.8 =================================================================== --- flashrom-doc_cosmetics/flashrom.8 (Revision 687) +++ flashrom-doc_cosmetics/flashrom.8 (Arbeitskopie) @@ -15,10 +15,6 @@ It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. -.PP -(see -.B http://coreboot.org -for details on coreboot) .SH OPTIONS Please note that the command line interface for flashrom will change before flashrom 1.0. Do not use flashrom in scripts or other automated tools without Index: flashrom-doc_cosmetics/README =================================================================== --- flashrom-doc_cosmetics/README (Revision 687) +++ flashrom-doc_cosmetics/README (Arbeitskopie) @@ -2,19 +2,16 @@ flashrom README ------------------------------------------------------------------------------- -flashrom is a utility for reading, writing, verifying and erasing flash ROM -chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system -using a supported mainboard, but it also supports flashing of network +flashrom is a utility for detecting, reading, writing, verifying and erasing +flash chips. It is often used to flash BIOS/EFI/coreboot/firmware images +in-system using a supported mainboard, but it also supports flashing of network cards (NICs), SATA controller cards, and other external devices which can program flash chips. -It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and -TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, -or SPI. +It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 +chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. -(see http://coreboot.org for details on coreboot) - Packaging --------- -- http://www.hailfinger.org/

2 2

[commit] r688 - trunk
by svn＠flashrom.org 18 Aug '09

18 Aug '09

Author: hailfinger Date: 2009-08-19 01:50:14 +0200 (Wed, 19 Aug 2009) New Revision: 688 Modified: trunk/README trunk/flashrom.8 Log: Tidy up docs before release. Don't mention coreboot.org without context. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/README =================================================================== --- trunk/README 2009-08-18 17:05:54 UTC (rev 687) +++ trunk/README 2009-08-18 23:50:14 UTC (rev 688) @@ -2,19 +2,16 @@ flashrom README ------------------------------------------------------------------------------- -flashrom is a utility for reading, writing, verifying and erasing flash ROM -chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system -using a supported mainboard, but it also supports flashing of network +flashrom is a utility for detecting, reading, writing, verifying and erasing +flash chips. It is often used to flash BIOS/EFI/coreboot/firmware images +in-system using a supported mainboard, but it also supports flashing of network cards (NICs), SATA controller cards, and other external devices which can program flash chips. -It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and -TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, -or SPI. +It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 +chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. -(see http://coreboot.org for details on coreboot) - Packaging --------- Modified: trunk/flashrom.8 =================================================================== --- trunk/flashrom.8 2009-08-18 17:05:54 UTC (rev 687) +++ trunk/flashrom.8 2009-08-18 23:50:14 UTC (rev 688) @@ -15,10 +15,6 @@ It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. -.PP -(see -.B http://coreboot.org -for details on coreboot) .SH OPTIONS Please note that the command line interface for flashrom will change before flashrom 1.0. Do not use flashrom in scripts or other automated tools without

1 0

[commit] r687 - tags
by svn＠flashrom.org 18 Aug '09

18 Aug '09

Author: hailfinger Date: 2009-08-18 19:05:54 +0200 (Tue, 18 Aug 2009) New Revision: 687 Added: tags/flashrom-0.9.1-rc1/ Log: flashrom 0.9.1-rc1 tag Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net>

1 0

new flashchip support for flashrom program information
by nanotonne＠free.fr 18 Aug '09

18 Aug '09

Hi, I send you a information for flashrom additionnal support (please) Flashrom program detect good my mainboard and chipset but don't detect chip flash rom I have tested to force reading with "similar" model" and it work mainboard : ASUS A7V133 chip flash memory : MOSEL V29C51002T (text writed on chip and reported by awflash utility) aparently this chip similar model as "SyncMOS S29C51002T" from your website because i can read fully with flashrom utility but i can't flash it. documentation mainboard is here : http://dlsvr02.asus.com/pub/ASUS/mb/socka/kt133a/a7v133/a7v133-105.pdf documentation chip rom is here : http://www.datasheetcatalog.org/datasheet/mosel/V29C51002T.pdf or here : http://pdf1.alldatasheet.co.kr/datasheet-pdf/view/2313/MOSEL/V29C51002T-90P… thank to add support of this chip , and too add option for flashrom program to force writing with a "similar chip" (know as compatible after research) when chip is manually defined. note : project coreboot is good, but support for usb disk for boot it and keyboard/mouse usb not supported is a big lack to "switch" to this alternative open firmware :-( ... Michael

2 1

flashrom v0.9.0-r670 works with an ASUS KFN4-D16
by Thomas Ward 18 Aug '09

18 Aug '09

I can report that flashrom v0.9.0-r670 works with an ASUS KFN4-D16 to reflash the mainboard bios chip I flashed an ASUS ROM (3.02) and halted the computer and rebooted, computer booted up as normal. next stop is to flash coreboot on this board, I hope to report back in about one month good luck with your project, Tom Ward

1 0

Success: Gigabyte GA-MA78GPM-DS2H
by Erik Haugen Bakke 17 Aug '09

17 Aug '09

Hi, all. Just wanted to confirm that the current SVN version of flashrom works on a Gigabyte GA-MA78GPM-DS2H board. The last time I tried this was about 2 months ago and the flashing failed back then, so this support would have added some time since then. The board was delivered with BIOS revision F3, and I have successfully flashed it with F4 and F5. This is my first success report, so please let me know if you need additional information on the board. Best regards -- Erik H. Bakke __________________________________________________________________________________ Find local businesses and services in your area with Yahoo!7 Local. Get started: http://local.yahoo.com.au

1 0

[PATCH] Fix compilation on Nexenta (Ubuntu/Solaris)
by Carl-Daniel Hailfinger 17 Aug '09

17 Aug '09

Fix compilation on Nexenta which is Ubuntu with a Solaris kernel. This is 0.9.1 material. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-nexenta/Makefile =================================================================== --- flashrom-nexenta/Makefile (Revision 684) +++ flashrom-nexenta/Makefile (Arbeitskopie) @@ -70,7 +70,10 @@ ifeq ($(CONFIG_SERPROG), yes) FEATURE_CFLAGS += -D'SERPROG_SUPPORT=1' OBJS += serprog.o +ifeq ($(OS_ARCH), SunOS) +LIBS += -lsocket endif +endif FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'FT2232_SPI_SUPPORT=1'") Index: flashrom-nexenta/README =================================================================== --- flashrom-nexenta/README (Revision 684) +++ flashrom-nexenta/README (Arbeitskopie) @@ -43,7 +43,7 @@ * pciutils * pciutils-devel / pciutils-dev / libpci-dev - * zlib-devel / zlib1g-dev + * zlib-devel / zlib1g-dev (only needed if libpci is static) On FreeBSD, you need the following ports: @@ -58,15 +58,18 @@ gmake +To compile on Nexenta, use: + + make + To compile on Solaris, use: - gmake LDFLAGS="-L$pathtolibpci -lpci -lz" CC="gcc -I$pathtopciheaders" \ - CFLAGS=-O2 + gmake LDFLAGS="-L$pathtolibpci" CC="gcc -I$pathtopciheaders" CFLAGS=-O2 To compile on DragonFly BSD, use: ln -s /usr/pkg/include/pciutils pci - gmake CFLAGS=-I. LDFLAGS="-L/usr/pkg/lib -lpci -lz" + gmake CFLAGS=-I. LDFLAGS="-L/usr/pkg/lib" To compile and run on Darwin/Mac OS X: -- http://www.hailfinger.org/

2 2

[commit] r686 - trunk
by svn＠flashrom.org 17 Aug '09

17 Aug '09

Author: hailfinger Date: 2009-08-17 18:30:53 +0200 (Mon, 17 Aug 2009) New Revision: 686 Modified: trunk/Makefile trunk/README Log: Fix compilation on Nexenta which is Ubuntu with a Solaris kernel. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/Makefile =================================================================== --- trunk/Makefile 2009-08-13 23:23:37 UTC (rev 685) +++ trunk/Makefile 2009-08-17 16:30:53 UTC (rev 686) @@ -70,7 +70,10 @@ ifeq ($(CONFIG_SERPROG), yes) FEATURE_CFLAGS += -D'SERPROG_SUPPORT=1' OBJS += serprog.o +ifeq ($(OS_ARCH), SunOS) +LIBS += -lsocket endif +endif FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'FT2232_SPI_SUPPORT=1'") Modified: trunk/README =================================================================== --- trunk/README 2009-08-13 23:23:37 UTC (rev 685) +++ trunk/README 2009-08-17 16:30:53 UTC (rev 686) @@ -43,7 +43,7 @@ * pciutils * pciutils-devel / pciutils-dev / libpci-dev - * zlib-devel / zlib1g-dev + * zlib-devel / zlib1g-dev (only needed if libpci is static) On FreeBSD, you need the following ports: @@ -58,15 +58,18 @@ gmake +To compile on Nexenta, use: + + make + To compile on Solaris, use: - gmake LDFLAGS="-L$pathtolibpci -lpci -lz" CC="gcc -I$pathtopciheaders" \ - CFLAGS=-O2 + gmake LDFLAGS="-L$pathtolibpci" CC="gcc -I$pathtopciheaders" CFLAGS=-O2 To compile on DragonFly BSD, use: ln -s /usr/pkg/include/pciutils pci - gmake CFLAGS=-I. LDFLAGS="-L/usr/pkg/lib -lpci -lz" + gmake CFLAGS=-I. LDFLAGS="-L/usr/pkg/lib" To compile and run on Darwin/Mac OS X:

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom