Hi again,
I'd test again with other chips, but it is still not possible to flash
with flashrom on my Jetway NC96FL Board.
Could somebody help me?
Outputs of flashrom -V and so on are attached.
Thanks, Hans-Martin
2014-02-12 13:34 GMT+01:00 Arun Chandran <achandran(a)mvista.com>:
> Hi,
>
> I am using the latest flashrom. I am unable to flashBIOS using dediprog sf
> 100 programmer.
>
> The log is pasted below. Please help.
> ###################################################################
>
> arun@arun-OptiPlex-9010:~/work/vview/flashrom$ sudo flashrom -p internal -w
> BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V
When you run flashrom like that, you will tell it to write
'BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin' to
your optiplex' mainboard flash chip, not to the flash chip connected
to your dediprog. (hint: change the target programmer after reading
the comment below)
Most, if not all, distributions package without compiling in dediprog
support. If this is the case, this means that you must compile
flashrom with dediprog support yourself.
Instructions are found here:
http://flashrom.org/Downloads#Installation_from_source
Hi,
I am using the latest flashrom. I am unable to flashBIOS using dediprog sf
100 programmer.
The log is pasted below. Please help.
###################################################################
arun@arun-OptiPlex-9010:~/work/vview/flashrom$ sudo flashrom -p internal -w
BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V
flashrom v0.9.7-r1764 on Linux 3.5.0-45-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.1.8, GCC 4.6.3, little endian
Command line (5 args): flashrom -p internal -w
BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V
Calibrating delay loop... OS timer resolution is 1 usecs, 3881M loops per
second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 999 us, 10000 myus =
10006 us, 4 myus = 5 us, OK.
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Mini Tower"
DMI string system-manufacturer: "Dell Inc."
DMI string system-product-name: "OptiPlex 9010"
DMI string system-version: "01"
DMI string baseboard-manufacturer: "Dell Inc."
DMI string baseboard-product-name: "0M9KCM"
DMI string baseboard-version: "A02"
Found chipset "Intel Q77" with PCI ID 8086:1e47.
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with
it,
then please email a report to flashrom(a)flashrom.org including a verbose
(-V) log.
Thank you!
Enabling flash write... Root Complex Register Block address = 0xfed1c000
GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI)
Top Swap : not enabled
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 enabled
0xff600000/0xff200000 FWH decode enabled
0xff500000/0xff100000 FWH decode enabled
0xff400000/0xff000000 FWH decode enabled
Maximum FWH chip size: 0x100000 bytesSPI Read Configuration: prefetching
enabled, caching enabled,
BIOS_CNTL = 0x0a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled
Warning: Setting Bios Control at 0xdc from 0x0a to 0x09 failed.
New value is 0x0a.
SPIBAR = 0x00007f669c2d9000 + 0x3800
0x04: 0xe008 (HSFS)
HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1
Warning: SPI Configuration Lockdown activated.
Reading OPCODES... done
0x06: 0x3f00 (HSFC)
HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0
0x50: 0x00000a0b (FRAP)
BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b
0x54: 0x00000000 FREG0: Warning: Flash Descriptor region
(0x00000000-0x00000fff) is read-only.
0x58: 0x0bff0600 FREG1: BIOS region (0x00600000-0x00bfffff) is read-write.
0x5C: 0x05ff0005 FREG2: Warning: Management Engine region
(0x00005000-0x005fffff) is locked.
0x60: 0x00040001 FREG3: Gigabit Ethernet region (0x00001000-0x00004fff) is
read-write.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see http://flashrom.org/ME for details.
Writes have been disabled for safety reasons. You can enforce write
support with the ich_spi_force programmer option, but you will most likely
harm your hardware! If you force flashrom you will get no support if
something breaks. On a few mainboards it is possible to enable write
access by setting a jumper (see its documentation or the board itself).
0x90: 0xc0 (SSFS)
SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0
0x91: 0xf84030 (SSFC)
SSFC: SCGO=0, ACS=0, SPOP=0, COP=3, DBC=0, SME=0, SCF=0
0x94: 0x0006 (PREOP)
0x96: 0x043b (OPTYPE)
0x98: 0x05200302 (OPMENU)
0x9C: 0x0000019f (OPMENU+4)
0xA0: 0x00000000 (BBAR)
0xC4: 0x00802005 (LVSCC)
LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1
0xC8: 0x00002005 (UVSCC)
UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0
0xD0: 0x00000800 (FPB)
Enabling hardware sequencing due to multiple flash chips detected.
PROBLEMS, continuing anyway
The following protocols are supported: FWH, Programmer-specific.
Probing for Programmer Opaque flash chip, 0 kB: Found 2 attached SPI flash
chips with a combined density of 12288 kB.
The flash address space (0x000000 - 0xbfffff) is divided at address
0x800000 in two partitions.
The first partition ranges from 0x000000 to 0x7fffff.
In that range are 2048 erase blocks with 4096 B each.
The second partition ranges from 0x800000 to 0xbfffff.
In that range are 1024 erase blocks with 4096 B each.
Found Programmer flash chip "Opaque flash chip" (12288 kB,
Programmer-specific) at physical address 0x0.
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1
is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1
is normal flash content, id2 is normal flash content
Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xea, id2
0xd0, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0,
id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than
supported size 1024 kB of chipset/board/programmer for FWH interface,
probe/read/erase/write may fail. 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 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1
is normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1
is normal flash content, id2 is normal flash content
Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than
supported size 1024 kB of chipset/board/programmer for FWH interface,
probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is
normal flash content, id2 is normal flash content
Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xea, id2
0xd0, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1
0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Found Programmer flash chip "Opaque flash chip" (12288 kB,
Programmer-specific).
Write/erase is not working yet on your programmer in its current
configuration.
Aborting.
Restoring MMIO space at 0x7f669c2dc8a0
Restoring PCI config space for 00:1f:0 reg 0xdc
##############################################################
Regards,
Arun C
ping?
On Mon, Dec 2, 2013 at 4:45 PM, Ricardo Ribalda Delgado <
ricardo.ribalda(a)gmail.com> wrote:
> Hello
>
> Is there any status change here? There are other people using this patch.
>
> http://www.projectosx.com/forum/index.php?showtopic=2485&st=20&start=20
>
> Thanks!
>
>
> On Thu, Sep 12, 2013 at 1:26 PM, Ricardo Ribalda Delgado
> <ricardo.ribalda(a)gmail.com> wrote:
> > Hello Stefan
> >
> > On Thu, Sep 12, 2013 at 12:08 PM, Stefan Tauner
> > <stefan.tauner(a)student.tuwien.ac.at> wrote:
> >> On Thu, 12 Sep 2013 11:25:39 +0200
> >> Ricardo Ribalda Delgado <ricardo.ribalda(a)gmail.com> wrote:
> >>
> >>> ping?
> >>
> >> Hi Ricardo,
> >>
> >> I would have hoped for a more generic patch that adds some
> >> eeprom-specific infrastructure, but your approach seems to be legit
> >> when implementing this with the current infrastructure in flashrom.
> >> Sorry for not mentioning the opaque API before, that is of course the
> >> easiest way to get such things to work.
> >
> > I thought about it, but I soon realized that it was probably not the
> > best option.
> >
> > The intel cards supports a limited ammount of chips, and the
> > read/write is not very standard. They are read by the card firmware,
> > but written with something spi_alike, but no jedec or anything to find
> > out the model of the eeprom.
> >
> >>
> >> Would it be even possible to probe for IDs of the EEPROMs with the
> >> interface on the Intel NICs? What EEPROM model(s) do see on your boards?
> >
> > You can ask the network card for the size of the eeprom. That is done
> > in nicintel_ee_probe
> >
> > According to the doc this eeproms can be used:
> >
> > 128 AT25128AN-10SI-2.7 M95128WMN6T CAT25CS128-TE13
> > 256 AT25256AN-10SI-2.7 M95256WMN6T
> >
> > All of them have the same instruction set. And unfortunately there is
> > no id instruction
> >
> > So, if the board is an intel card and it says that the size is 128
> > kbits, then it is a chip from the first row, otherwise it is from the
> > second
> >
> >>
> >> I have not reviewed your patch in detail yet. There are probably a few
> >> coding style issues etc., but we can fix that ourselves if we have to.
> >
> > I could not find a coding style, so I tried to stick to the kernel one.
> >
> >> The bigger question is if we want to add something like it at all. I
> >> don't see good reason why we should not, but I need to discuss this
> >> with my colleague(s) (and that usually takes more time than one would
> >> expect). In any case your code is out there and can be used even if it
> >> does not get merged into vanilla flashrom eventually and your work is
> >> much appreciated, thank you.
> >
> > That was the whole point, that this could be reused by somebody else.
> > And the program more standard up to date is yours :)
> >
> > Thaks!
> >
> >
> >> --
> >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner
> >
> >
> >
> > --
> > Ricardo Ribalda
>
>
>
> --
> Ricardo Ribalda
>
--
Ricardo Ribalda
On Wed, Feb 5, 2014 at 10:59 PM, Daniel Lenski <dlenski(a)gmail.com> wrote:
> Hello,
> I have a Flashrom NT-510 nettop (Intel Atom D510, ICH7/NM10 chipset).
> Flashrom doesn't find any chip while probing. Complete output of
> sensors-detect and flashrom -V here:
> http://paste.flashrom.org/view.php?id=1966
A little more info... According to the BIOS docs I found on Foxconn's
site, it's an AMI BIOS with an 8 MB SPI flash chip. The part on the
motherboard is a square surface-mount IC labeled "AMI BIOS" etc but
with no part information labeled that I can see.
Hello,
I have a Flashrom NT-510 nettop (Intel Atom D510, ICH7/NM10 chipset).
Flashrom doesn't find any chip while probing. Complete output of
sensors-detect and flashrom -V here:
http://paste.flashrom.org/view.php?id=1966
When running sensors-detect to find thermal/fan/etc., it appears to find an
EEPROM chip while probing I2C/SMBus adapters, however I think this is just
an EEPROM that gives information about the RAM module, rather than a
BIOS/firmware Flash chip:
SMBus I801 adapter at 0400 (i2c-6)
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Does anyone else have experience with this system and might know how to
probe and read the BIOS EEPROM?
Thanks,
Dan