flashrom

flashrom@flashrom.org

3 participants
9189 discussions

wiki patches 6.0?
by Stefan Tauner 07 Mar '13

07 Mar '13

This is actually not about the wiki, but about the programmers. now that we have combined usb and pci device entries and put them together in a union with a char *note, i wonder why we have the union at all. the note might be very handy for normal programmers too (e.g. nvidia does not support writing, but this is not documented prominently...). It would also get rid of the annoying non-anonymous union... :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 2

[PATCH] Add pinout for ByteBlaster to rayer_spi.c.
by mmcx＠mail.ru 05 Mar '13

05 Mar '13

Add pinout for ByteBlaster to rayer_spi.c. Signed-off-by: Maksim Kuleshov <mmcx(a)mail.ru> --- rayer_spi.c | 91 +++++++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 61 insertions(+), 30 deletions(-) diff --git a/rayer_spi.c b/rayer_spi.c index b312610..488b555 100644 --- a/rayer_spi.c +++ b/rayer_spi.c @@ -35,13 +35,28 @@ #include <string.h> #include "flash.h" #include "programmer.h" #include "hwaccess.h" -enum rayer_type { - TYPE_RAYER, - TYPE_XILINX_DLC5, + +static void rayer_byteblaster_preinit(void *); +static int rayer_byteblaster_shutdown(void *); + +static struct s_rayer_pinout { + const char * name; + const char * description; + int cs_bit; + int sck_bit; + int mosi_bit; + int miso_bit; + void (*preinit)(void *); + int (*shutdown)(void *); +} rayer_pinouts [] = { + {"rayer","RayeR SPIPGM",5,6,7,6}, + {"xilinx","Xilinx Parallel Cable III (DLC 5)",2,1,0,4}, + {"byteblaster","Altera ByteBlaster",1,0,6,7,rayer_byteblaster_preinit,rayer_byteblaster_shutdown}, + {0}, }; /* We have two sets of pins, out and in. The numbers for both sets are * independent and are bitshift values, not real pin numbers. * Default settings are for the RayeR hardware. @@ -81,11 +96,11 @@ static void rayer_bitbang_set_mosi(int val) static int rayer_bitbang_get_miso(void) { uint8_t tmp; - tmp = INB(lpt_iobase + 1); + tmp = INB(lpt_iobase + 1) ^ 0x80;//bit.7 inverted tmp = (tmp >> rayer_miso_bit) & 0x1; return tmp; } static const struct bitbang_spi_master bitbang_spi_master_rayer = { @@ -95,14 +110,17 @@ static const struct bitbang_spi_master bitbang_spi_master_rayer = { .set_mosi = rayer_bitbang_set_mosi, .get_miso = rayer_bitbang_get_miso, .half_period = 0, }; + +static void (*rayer_preinit)(void*) =NULL; +static void * rayer_preinit_data=NULL; + int rayer_spi_init(void) { char *arg = NULL; - enum rayer_type rayer_type = TYPE_RAYER; /* Non-default port requested? */ arg = extract_programmer_param("iobase"); if (arg) { char *endptr = NULL; @@ -136,51 +154,64 @@ int rayer_spi_init(void) msg_pdbg("Using address 0x%x as I/O base for parallel port access.\n", lpt_iobase); arg = extract_programmer_param("type"); if (arg) { - if (!strcasecmp(arg, "rayer")) { - rayer_type = TYPE_RAYER; - } else if (!strcasecmp(arg, "xilinx")) { - rayer_type = TYPE_XILINX_DLC5; - } else { + struct s_rayer_pinout *p = rayer_pinouts; + for (; p->name; ++p) { + if (! strcasecmp (arg, p->name)) { + break; + } + } + if(! p->name) { msg_perr("Error: Invalid device type specified.\n"); free(arg); return 1; } - } - free(arg); - switch (rayer_type) { - case TYPE_RAYER: - msg_pdbg("Using RayeR SPIPGM pinout.\n"); - /* Bits for master->slave direction */ - rayer_cs_bit = 5; - rayer_sck_bit = 6; - rayer_mosi_bit = 7; - /* Bits for slave->master direction */ - rayer_miso_bit = 6; - break; - case TYPE_XILINX_DLC5: - msg_pdbg("Using Xilinx Parallel Cable III (DLC 5) pinout.\n"); - /* Bits for master->slave direction */ - rayer_cs_bit = 2; - rayer_sck_bit = 1; - rayer_mosi_bit = 0; - /* Bits for slave->master direction */ - rayer_miso_bit = 4; + msg_pinfo("Using %s pinout.\n", p->description); + rayer_cs_bit = p->cs_bit; + rayer_sck_bit = p->sck_bit; + rayer_mosi_bit = p->mosi_bit; + rayer_miso_bit = p->miso_bit; + + if(p -> preinit){ + rayer_preinit = p -> preinit; + rayer_preinit_data = p; + } + + if(p -> shutdown){ + register_shutdown(p -> shutdown, (void*)p); + } + + free(arg); } if (rget_io_perms()) return 1; /* Get the initial value before writing to any line. */ lpt_outbyte = INB(lpt_iobase); + if(rayer_preinit){ + rayer_preinit(rayer_preinit_data); + } + if (bitbang_spi_init(&bitbang_spi_master_rayer)) return 1; return 0; } +static void rayer_byteblaster_preinit(void * data){ + msg_pdbg("byteblaster_init\n"); + OUTB(2, lpt_iobase + 2 );//clear #EN signal +} + +static int rayer_byteblaster_shutdown(void * data){ + msg_pdbg("byteblaster_shutdown\n"); + OUTB(0, lpt_iobase + 2 );//set #EN signal + return 0; +} + #else #error PCI port I/O access is not supported on this architecture yet. #endif -- 1.7.10.4

2 3

Re: [flashrom] flashrom ignores layout file?
by Stefan Tauner 05 Mar '13

05 Mar '13

On Tue, 5 Mar 2013 12:57:39 -0700 Ross Amans <ross.amans(a)sanmina.com> wrote: > Thanks, but server is down. > oh, well. server relocation which apparently did not work out as expected... external cache of the mentioned mail: http://article.gmane.org/gmane.linux.bios.flashrom/1950 -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] flashrom ignores layout file?
by Stefan Tauner 05 Mar '13

05 Mar '13

On Mon, 4 Mar 2013 16:49:36 -0700 Ross Amans <ross.amans(a)sanmina.com> wrote: > I can run flashrom under linux for read, but not yet write. > Sandy Bridge / Patsburg C602 > When I attempt to use a layout file, it likes it, but ignores it. No > complaints, but instead of doing the 4 MB bios, it does the whole flash > (8MB). Hi Ross, please take a look at http://www.flashrom.org/pipermail/flashrom/2013-February/010500.html This will be changed in the next weeks. If you can not wait that long please use the patches. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] M29W512B write operation verified on 3C905C/TX
by Stefan Tauner 05 Mar '13

05 Mar '13

On Tue, 5 Mar 2013 07:40:25 +0800 Lu Xie <lxie1(a)andrew.cmu.edu> wrote: > Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:S > Erase/write done. > Verifying flash... VERIFIED. Hi and thanks for your report! The ":S" after the address range means that flashrom has detected that the data on the chip was already equal to the image you provided. I presume that you actually did write exactly that image to the chip already previously. Can you confirm that the contents of the chip really have changed? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

flashrom ignores layout file?
by Ross Amans 05 Mar '13

05 Mar '13

I can run flashrom under linux for read, but not yet write. Sandy Bridge / Patsburg C602 When I attempt to use a layout file, it likes it, but ignores it. No complaints, but instead of doing the 4 MB bios, it does the whole flash (8MB). command line: ./flashrom -r fll-19-w-bios.bin -c W25Q64 -p internal:laptop=this_is_not_a_laptop -i bios -l layout.flash -o fl-bios.log layout.flash: 00000000:0000ffff desc 00010000:003fffff me 00400000:007fffff bios fl-bios.log: flashrom v0.9.6.1-r1653 on Linux 3.7.5-201.fc18.x86_64 (x86_64) flashrom was built with libpci 3.1.10, GCC 4.7.2 20121109 (Red Hat 4.7.2-8), little endian Command line (12 args): ./flashroml -r fll-19-w-bios.bin -c W25Q64 -p internal:laptop=this_is_not_a_laptop -i bios -l layout.flash -o fl-bios.log romlayout 00000000 - 0000ffff named desc romlayout 00010000 - 003fffff named me romlayout 00400000 - 007fffff named bios Using region: "bios". Calibrating delay loop... OS timer resolution is 1 usecs, 1781M loops per second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 1004 us, 10000 myus = 9992 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "To be filled by O.E.M." DMI string system-product-name: "To be filled by O.E.M." DMI string system-version: "To be filled by O.E.M." DMI string baseboard-manufacturer: "To be filled by O.E.M." DMI string baseboard-product-name: "To be filled by O.E.M." DMI string baseboard-version: "To be filled by O.E.M." DMI string chassis-type: "Desktop" Found chipset "Intel X79" with PCI ID 8086:1d41. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled Root Complex Register Block address = 0xfed1c000 GCS = 0xc20: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x6008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... program_opcodes: preop=5006 optype=463b opmenu=05d80302c79f0190 done OP Type Pre-OP op[0]: 0x02, write w/ addr, none op[1]: 0x03, read w/ addr, none op[2]: 0xd8, write w/ addr, none op[3]: 0x05, read w/o addr, none op[4]: 0x90, read w/ addr, none op[5]: 0x01, write w/o addr, none op[6]: 0x9f, read w/o addr, none op[7]: 0xc7, write w/o addr, none Pre-OP 0: 0x06, Pre-OP 1: 0x50 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x007fffc0 (FADDR) 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x000f0000 FREG0: Flash Descriptor region (0x00000000-0x0000ffff) is read-write. 0x58: 0x07ff0400 FREG1: BIOS region (0x00400000-0x007fffff) is read-write. 0x5C: 0x03ff0010 FREG2: Management Engine region (0x00010000-0x003fffff) is read-write. 0x60: 0x00001fff FREG3: Gigabit Ethernet region is unused. 0x64: 0x00001fff FREG4: Platform Data region is unused. 0x74: 0x00000000 (PR0 is unused) 0x78: 0x00000000 (PR1 is unused) 0x7C: 0x00000000 (PR2 is unused) 0x80: 0x00000000 (PR3 is unused) 0x84: 0x00000000 (PR4 is unused) 0x90: 0x84 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf87f10 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00002005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) Reading flash descriptors mapped by the chipset via FDOC/FDOD... done. === Content Section === FLVALSIG 0x0ff0a55a FLMAP0 0x02040003 FLMAP1 0x12100206 FLMAP2 0x00210020 --- Details --- NR (Number of Regions): 3 FRBA (Flash Region Base Address): 0x040 NC (Number of Components): 1 FCBA (Flash Component Base Address): 0x030 ISL (ICH/PCH Strap Length): 18 FISBA/FPSBA (Flash ICH/PCH Strap Base Address): 0x100 NM (Number of Masters): 3 FMBA (Flash Master Base Address): 0x060 MSL/PSL (MCH/PROC Strap Length): 0 FMSBA (Flash MCH/PROC Strap Base Address): 0x200 === Component Section === FLCOMP 0x00100024 FLILL 0x00000000 --- Details --- Component 1 density: 8 MB Component 2 is not used. Read Clock Frequency: 20 MHz Read ID and Status Clock Freq.: 20 MHz Write and Erase Clock Freq.: 20 MHz Fast Read is supported. Fast Read Clock Frequency: 20 MHz No forbidden opcodes. === Region Section === FLREG0 0x000f0000 FLREG1 0x07ff0400 FLREG2 0x03ff0010 FLREG3 0x00001fff --- Details --- Region 0 (Descr.) 0x00000000 - 0x0000ffff Region 1 (BIOS ) 0x00400000 - 0x007fffff Region 2 (ME ) 0x00010000 - 0x003fffff Region 3 (GbE ) is unused. === Master Section === FLMSTR1 0xffff0000 FLMSTR2 0xffff0000 FLMSTR3 0xffff0118 --- Details --- Descr. BIOS ME GbE Platf. BIOS rw rw rw rw rw ME rw rw rw rw rw GbE rw rw rw rw rw SPI Read Configuration: prefetching enabled, caching enabled, OK. The following protocols are supported: FWH, SPI. Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Found Winbond flash chip "W25Q64" (8192 kB, SPI) at physical address 0xff800000. Chip status register is 0x00. This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Block protection is disabled. Reading flash... done. Restoring MMIO space at 0x7f6ced1e68a0 Restoring MMIO space at 0x7f6ced1e689c Restoring MMIO space at 0x7f6ced1e6898 Restoring MMIO space at 0x7f6ced1e6896 Restoring MMIO space at 0x7f6ced1e6894 Restoring PCI config space for 00:1f:0 reg 0xdc -- Ross Amans Systems Engineer Newisys div of Sanmina 5385 Mark Dabling blvd Colorado Springs, CO 80918 719-884-8714 (work) 719-287-4446 (cell) CONFIDENTIALITY This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof. ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina Corporation (or any of its subsidiaries), or any other person or entity.

1 0

M29W512B write operation verified on 3C905C/TX
by Lu Xie 05 Mar '13

05 Mar '13

Hi, Thanks for the wonderful tool. The verification is attached as requested. Lu

1 0

Re: [flashrom] Rayer_SPI and xilinx buffered dlc5 cable
by Kyösti Mälkki 04 Mar '13

04 Mar '13

On Tue, 2013-02-26 at 11:55 +1100, Andrew Tarabaras wrote: > Hi, > > Just a heads up that the rayer_spi module wont work with a buffered xilinx > DLC cable. There is a pull down buffer in the MISO ( Data In ) line which > is enabled when pin 6 of the parallel port is pulled low. > > I dont have time to be submitting patches, fix it or not I dont mind. > Thanks. So this is for the "Xilinx DLC-5" with following schematic? http://dev.ivanov.eu/uploads/images/dlc5/dlc5_schematic3.png There is another pending rayer_spi patch, I'll handle both. Regards, Kyösti

1 0

Assist in the development of SPI protocol.
by Сергей Бараненков 04 Mar '13

04 Mar '13

Hello, please help in the development of the protocol SPI, I would like to implement a simple program to program MX25L3205. In this case, it is possible to program it with the Raspberry Pi, but you just want to understand. If you are not hard to help in your endeavors, if not difficult to specify where you can read and see the source code. I work in the Borland C + + 6.0. Thanks again -- Sincerely Sergey Baranenkov Engineer Grade 1 Interregional Center of ICT in the Bank of Russia (Central Bank)

1 0

Re: [flashrom] [coreboot] IMC on persimmon (was: Flashrom erase failure)
by Racine, Michel 04 Mar '13

04 Mar '13

Hello Wolfgang, I cannot do the commit to flashrom.org; I'm not a contributor, just a user. However, if you have a patch file I could apply it to the code on my system, and rebuild flashrom. That would get me out of the problem I have, and be able to reboot. Cheers, Michel. -----Original Message----- From: Wolfgang Kamp - datakamp [mailto:wmkamp@datakamp.de] Sent: Monday, March 04, 2013 1:43 AM To: flashrom(a)flashrom.org Cc: Stefan Tauner; Racine, Michel Subject: AW: [coreboot] IMC on persimmon (was: Flashrom erase failure) Hi, recently I had the same problems to get Flashrom working on an embedded platform with AMD G-series processor similar to Persimmon. I did all the patches to get Flashrom working but actually I'm not able to commit to flashrom.org. If there is interest I would send the necessary files to someone who can do that for me. Regards, Wolfgang -----Ursprüngliche Nachricht----- Von: coreboot-bounces(a)coreboot.org [mailto:coreboot-bounces@coreboot.org] Im Auftrag von Stefan Tauner Gesendet: Freitag, 1. März 2013 22:04 An: Racine, Michel Cc: flashrom(a)flashrom.org; coreboot(a)coreboot.org Betreff: [coreboot] IMC on persimmon (was: Flashrom erase failure) On Fri, 1 Mar 2013 20:48:48 +0000 "Racine, Michel" <michel.racine(a)hp.com> wrote: > Thank you for the quick reply. > > I have upgraded flashrom. I did a verify, and flashrom indicated a difference. I tried to re-flash coreboot, but I think I'm missing something: > > root@debian:~/flashrom/flashrom-0.9.6.1# ./flashrom -p internal -w > ~/coreboot.rom flashrom v0.9.6.1-r1564 on Linux 2.6.32-5-686 (i686) > flashrom is free software, get the source code at > http://www.flashrom.org > > Calibrating delay loop... OK. > coreboot table found at 0xc717d000. > Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... The SB700 IMC is active and may interfere with SPI commands. Disabling write. > OK. > Found SST flash chip "SST25VF032B" (4096 kB, SPI) at physical address 0xffc00000. > Write/erase is not working yet on your programmer in its current configuration. > Aborting > > > Thoughts? I have added the coreboot mailing list because I ham not familiar with the board or chipset and I am quite certain someone there knows how to handle this correctly. The new version of flashrom detects that the embedded controller on the board (IMC) accesses the SPI bus concurrently with flashrom. We disable writes for safety reasons in that case (your old version did not...). Apparently there is no way to force writing other than changing the source code (sb600.c). I don't think that is wisely though... Apart from repeating the warning to *NOT* reboot/reset/shutdown the machine (unless you have a known-working external flash programmer), I can not help you further ATM. > -----Original Message----- > From: Stefan Tauner [mailto:stefan.tauner@student.tuwien.ac.at] > Sent: Friday, March 01, 2013 12:09 PM > To: Racine, Michel > Cc: flashrom(a)flashrom.org > Subject: Re: [flashrom] Flashrom erase failure > > On Fri, 1 Mar 2013 17:19:46 +0000 > "Racine, Michel" <michel.racine(a)hp.com> wrote: > > > Greetings, > > > > I have an AMD Persimmon dev board. I built coreboot and flashed it successfully; the board was operational. > > I have attempted to flash the original rom (obtained before flashing coreboot with flashrom -r). > > When I attempted to flash the original rom, I get the output below. > > > > Hi, > > you are trying to write the original image while running coreboot, right? > > You are using a very old version of flashrom. Please verify that the content of the flash is untouched (by using the -v option with the image you have written successfully last). If it was modified try to rewrite that image. If that still does not work, please report back, else update and retry. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner -- coreboot mailing list: coreboot(a)coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom