flashrom October 2013

flashrom@flashrom.org

22 participants
121 discussions

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by san 24 Oct '13

24 Oct '13

Not sure if it's FCC ID: FAB 02-0172-004 Rev A on the back side. On front side: 3c905B-TX Fast Etherlink XL PCI 03-0172-410 D EA=0050044B4FB9 SN=6TQ24B4FB9 2013/10/23 san <san(a)plusnet.pl> > W29EE011 does work with no problems. > > > 2013/10/23 san <san(a)plusnet.pl> > >> I have unsupported one, so i won't use it. >> >> PM29F002T is too big (256kB over 128kB). >> It does work at last for read. >> >> When erase it does work about 1/3 times. >> Once i suceed to write (after erase), and whole chip was programmed well! >> >> There is something wrong with erase function in nic3com, as i belive... >> >> Later i'll try to use W29EE011 (128kB). >> >> Regards! >> >> >> 2013/10/22 san <san(a)plusnet.pl> >> >>> Hi! >>> >>> I own: >>> 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX >>> [Boomerang] [10b7:9050] >>> >>> It's unsupported: >>> ---[code]--- >>> Error: No supported PCI device found. >>> Error: Programmer initialization failed. >>> ---[/code]--- >>> >>> I would love to help You to get it to work with flashrom. >>> Do You need it? >>> >>> Regards! >>> >>> -- >>> [ e-San.info | San(a)plusnet.pl ] >>> >> >> >> >> -- >> [ e-San.info | San(a)plusnet.pl ] >> > > > > -- > [ e-San.info | San(a)plusnet.pl ] > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Issues
by David Hendricks 23 Oct '13

23 Oct '13

On Tue, Oct 22, 2013 at 10:50 PM, Daniel Raburn <dandeaf1987(a)gmail.com>wrote: > Hi i have issue for IEC MARIO FISH 2330 CR-48 Insyde BIOS and somehow it > crash and it shutdown. and i decide to turn on boot... seem it damage > already not able to read my SSD (hard drive) but it able to read my USB > memory but the screen say Chrome OS is missing or damaged. Please Connect > a recovery device. and i did recovery and it works and install and whatever > is list is done. and it reboot and same issue . Any Suggest? > > Also i have backup for flash rom too. you can look on attach file. and > figure out how to force to flash it. > > Thanks > Daniel Raburn > Hi Daniel, Are you sure it's an issue with the BIOS? I suspect the issue is actually an SSD failure of some kind. SSDs are generally reliable, however the connection between it and the mainboard may have come loose. If you can open up the machine, check that cable is aligned with the connectors and fully inserted, and that the fastener clip on the mainboard connector is pushed in all the way. Here is a picture to help: http://goo.gl/KBjqlq -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

X8DT6-F
by Ryan VanRiper 23 Oct '13

23 Oct '13

Hi, I have a supermicro X8DT6-F/X8DTE-F board with a bricked IPMI bmc chip from a previous flash attempt. The techs at supermicro pointed me at a tool called yafukcs tool (in DOS) which claims to reflash it, but it fails with some odd errors they can't figure out. Since the yafukcs tool is not open source i'm a bit in the dark trying to understand what the errors mean. I'm not alone because the techs at supermicro did not comment and simply said RMA it. The errors are as follows: Error in SendTimedImbpRequest Error in Getting FMH info Error in FirmwareInfo I thought maybe flashrom could save the day over there tool and simply did the following just to get an idea of what was on the board. ./flashrom -V --programmer internal flashrom v0.9.7-r1711 on Linux 2.6.32-358.18.1.el6.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.10, GCC 4.4.7 20120313 (Red Hat 4.4.7-3), little endian Command line (3 args): ./flashrom -V --programmer internal Calibrating delay loop... OS timer resolution is 1 usecs, 1195M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1004 us, 10000 myus = 10005 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "X8DT6" DMI string system-version: "1234567890" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "X8DT6" DMI string baseboard-version: "1234567890" DMI string chassis-type: "Main Server Chassis" Found Winbond Super I/O, id 0x52 Found chipset "Intel ICH10R" with PCI ID 8086:3a16. 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 = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x2008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=0, FLOCKDN=0 Programming OPCODES... done 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0x004130 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=3, DBC=1, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Found Macronix flash chip "MX25L3205(A)" (4096 kB, SPI) at physical address 0xffc00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Found Macronix flash chip "MX25L3205D/MX25L3208D" (4096 kB, SPI) at physical address 0xffc00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address 0xffc00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Multiple flash chip definitions match the detected chip(s): "MX25L3205(A)", "MX25L3205D/MX25L3208D", "MX25L3206E" Please specify which chip definition to use with the -c <chipname> option. Restoring MMIO space at 0x7f754100c8a0 Restoring MMIO space at 0x7f754100c89c Restoring MMIO space at 0x7f754100c898 Restoring MMIO space at 0x7f754100c896 Restoring MMIO space at 0x7f754100c894 Restoring PCI config space for 00:1f:0 reg 0xdc The chip that runs the IPMI software is from a company called Nuvoton, the chip is a WPCM450RA0BX which also seems to be known as a winbond chip as well from some google searches. So, my question(s) are I don't see nuvoton mentioned in the detection / probing ? (maybe because it's bricked?) Has anyone ever tried to reflash just the IPMI portion of this board ? Supermicro went through the trouble of creating separate flash images (one for the bios, and one for IPMI). Any ideas on which programmer I would even use to attempt such a reflashing of this board ? Thanks for any comments or help R

1 0

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by Idwer Vollering 23 Oct '13

23 Oct '13

2013/10/23 san <san(a)plusnet.pl>: > W29EE011 does work with no problems. > > > 2013/10/23 san <san(a)plusnet.pl> >> >> I have unsupported one, so i won't use it. >> >> PM29F002T is too big (256kB over 128kB). >> It does work at last for read. >> >> When erase it does work about 1/3 times. >> Once i suceed to write (after erase), and whole chip was programmed well! >> >> There is something wrong with erase function in nic3com, as i belive... >> >> Later i'll try to use W29EE011 (128kB). >> >> Regards! What's the FCC ID of your 3Com (10b7:9050) NIC? Mine says DF63C905-TX and 'ASSY 03-0104-005', 'REV A'. Neither AT29C010, W29C011 or P28F001 was detected, over here. Idwer

1 0

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by san 23 Oct '13

23 Oct '13

W29EE011 does work with no problems. 2013/10/23 san <san(a)plusnet.pl> > I have unsupported one, so i won't use it. > > PM29F002T is too big (256kB over 128kB). > It does work at last for read. > > When erase it does work about 1/3 times. > Once i suceed to write (after erase), and whole chip was programmed well! > > There is something wrong with erase function in nic3com, as i belive... > > Later i'll try to use W29EE011 (128kB). > > Regards! > > > 2013/10/22 san <san(a)plusnet.pl> > >> Hi! >> >> I own: >> 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX >> [Boomerang] [10b7:9050] >> >> It's unsupported: >> ---[code]--- >> Error: No supported PCI device found. >> Error: Programmer initialization failed. >> ---[/code]--- >> >> I would love to help You to get it to work with flashrom. >> Do You need it? >> >> Regards! >> >> -- >> [ e-San.info | San(a)plusnet.pl ] >> > > > > -- > [ e-San.info | San(a)plusnet.pl ] > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by san 23 Oct '13

23 Oct '13

I have unsupported one, so i won't use it. PM29F002T is too big (256kB over 128kB). It does work at last for read. When erase it does work about 1/3 times. Once i suceed to write (after erase), and whole chip was programmed well! There is something wrong with erase function in nic3com, as i belive... Later i'll try to use W29EE011 (128kB). Regards! 2013/10/22 san <san(a)plusnet.pl> > Hi! > > I own: > 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX > [Boomerang] [10b7:9050] > > It's unsupported: > ---[code]--- > Error: No supported PCI device found. > Error: Programmer initialization failed. > ---[/code]--- > > I would love to help You to get it to work with flashrom. > Do You need it? > > Regards! > > -- > [ e-San.info | San(a)plusnet.pl ] > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Issues
by Daniel Raburn 22 Oct '13

22 Oct '13

Hi i have issue for IEC MARIO FISH 2330 CR-48 Insyde BIOS and somehow it crash and it shutdown. and i decide to turn on boot... seem it damage already not able to read my SSD (hard drive) but it able to read my USB memory but the screen say Chrome OS is missing or damaged. Please Connect a recovery device. and i did recovery and it works and install and whatever is list is done. and it reboot and same issue . Any Suggest? Also i have backup for flash rom too. you can look on attach file. and figure out how to force to flash it. Thanks Daniel Raburn A non-text attachment (backup.bin) has been stripped. It is available at http://paste.flashrom.org/view.php?id=1785

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

It propably has nothing to do with nVidia, since those chips are not listed on flashrom support page. ;) 2013/10/23 Donovan Lavinder <drmario2007(a)gmail.com> > Interesting. However, I know some ROM are locked for some reasons. (Namely > NVIDIA being 100% closed-source...) > On Oct 22, 2013 3:47 PM, "san" <san(a)plusnet.pl> wrote: > >> Both are OTP, but why they are not supported (for read)? >> >> >> 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> >> >>> I think some are OTP, others are flashable. You can check the datasheet >>> to be sure. >>> On Oct 22, 2013 1:08 PM, "san" <san(a)plusnet.pl> wrote: >>> >>>> Same here for Vanta (Atmel AT27LV512A). >>>> Or it is intentionally to not support those 27's chips which are >>>> One-Time-Programmable? >>>> >>>> Regards! >>>> >>>> >>>> 2013/10/22 san <san(a)plusnet.pl> >>>> >>>>> Thanks for the info. >>>>> I've found that it MIGHT be supported by flashrom. It does look for >>>>> memory (see log). >>>>> >>>>> I checked the chip and it's Holtek ht27c512 (it's 64k - good sign?) >>>>> which seems to be, simply, unsupported by flashrom. >>>>> Can You add its support? >>>>> >>>>> Best regards! >>>>> >>>>> >>>>> 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> >>>>> >>>>>> 32KB, I think. I do remember owning that card a long time ago. The >>>>>> BIOS image may be 16KB, however, due to very simple pipeline architecture. >>>>>> The only way to find out is to pull the BIOS copy and verify its size. >>>>>> On Oct 22, 2013 12:44 AM, "san" <san(a)plusnet.pl> wrote: >>>>>> >>>>>>> I ani going to buy riva to program some bioses with it. But first >>>>>>> i would like to know what chip sizes i can use. Parallel ofcourse. >>>>>>> >>>>>>> Regards! >>>>>>> >>>>>>> _______________________________________________ >>>>>>> flashrom mailing list >>>>>>> flashrom(a)flashrom.org >>>>>>> http://www.flashrom.org/mailman/listinfo/flashrom >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> [ e-San.info | San(a)plusnet.pl ] >>>>> >>>> >>>> >>>> >>>> -- >>>> [ e-San.info | San(a)plusnet.pl ] >>>> >>> >> >> >> -- >> [ e-San.info | San(a)plusnet.pl ] >> > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by Idwer Vollering 22 Oct '13

22 Oct '13

2013/10/22 san <san(a)plusnet.pl>: > Hi! > > I own: > 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX > [Boomerang] [10b7:9050] > > It's unsupported: > ---[code]--- > Error: No supported PCI device found. > Error: Programmer initialization failed. > ---[/code]--- > > I would love to help You to get it to work with flashrom. > Do You need it? > > Regards! Yes, we would appreciate some testing. Do you have a parallel DIP32 chip that you can insert into its socket? Either SST39SF512, CAT28F125 or AT29C512 should work: http://www.ebay.com/sch/i.html?_nkw=SST39SF512 http://www.ebay.com/sch/i.html?_nkw=CAT28F512 http://www.ebay.com/sch/i.html?_nkw=AT29C512 When you have that set up, apply this patch: Index: nic3com.c =================================================================== --- nic3com.c (revision 1760) +++ nic3com.c (working copy) @@ -37,6 +37,9 @@ static uint16_t id; const struct dev_entry nics_3com[] = { + /* 3C905 */ + {0x10b7, 0x9050, NT, "3COM", "3c905: Fast EtherLink XL PCI (3c905-TX)"}, + /* 3C90xB */ {0x10b7, 0x9055, OK, "3COM", "3C90xB: PCI 10/100 Mbps; shared 10BASE-T/100BASE-TX"}, {0x10b7, 0x9001, NT, "3COM", "3C90xB: PCI 10/100 Mbps; shared 10BASE-T/100BASE-T4" },

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

Both are OTP, but why they are not supported (for read)? 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> > I think some are OTP, others are flashable. You can check the datasheet to > be sure. > On Oct 22, 2013 1:08 PM, "san" <san(a)plusnet.pl> wrote: > >> Same here for Vanta (Atmel AT27LV512A). >> Or it is intentionally to not support those 27's chips which are >> One-Time-Programmable? >> >> Regards! >> >> >> 2013/10/22 san <san(a)plusnet.pl> >> >>> Thanks for the info. >>> I've found that it MIGHT be supported by flashrom. It does look for >>> memory (see log). >>> >>> I checked the chip and it's Holtek ht27c512 (it's 64k - good sign?) >>> which seems to be, simply, unsupported by flashrom. >>> Can You add its support? >>> >>> Best regards! >>> >>> >>> 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> >>> >>>> 32KB, I think. I do remember owning that card a long time ago. The BIOS >>>> image may be 16KB, however, due to very simple pipeline architecture. The >>>> only way to find out is to pull the BIOS copy and verify its size. >>>> On Oct 22, 2013 12:44 AM, "san" <san(a)plusnet.pl> wrote: >>>> >>>>> I ani going to buy riva to program some bioses with it. But first i >>>>> would like to know what chip sizes i can use. Parallel ofcourse. >>>>> >>>>> Regards! >>>>> >>>>> _______________________________________________ >>>>> flashrom mailing list >>>>> flashrom(a)flashrom.org >>>>> http://www.flashrom.org/mailman/listinfo/flashrom >>>>> >>>> >>> >>> >>> -- >>> [ e-San.info | San(a)plusnet.pl ] >>> >> >> >> >> -- >> [ e-San.info | San(a)plusnet.pl ] >> > -- [ e-San.info | San(a)plusnet.pl ]

1 0

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom October 2013