Hi,
I tried programming Intel 28F001BN/BX-T on 3C905B-TXNM but it failed at
erase/write. I checked that chip's datasheet and it says PIN 1 and 30 must
be pulled to 12V to accept erase/write operation, but the card can only
offer 5V at PIN 1 and NC at PIN 30. So I wired 12V to the two pins and then
flashrom erased/wrote the chip successfully. Please check the attached
output files for the two attempts.
Lu
On Wed, 10 Dec 2014 21:24:27 +0400
Roman Lebedev <lebedev.ri(a)gmail.com> wrote:
> Invalid locking change 0xf8 requested at 0xb7323002! Please report a bug at
> flashrom(a)flashrom.org
Thanks for testing Roman!
Carl-Daniel, do you have any idea why we do the "new_bits & ~REG2_MASK"
in changelock_regspace2_block() in jedec.c at all?
It is essentially your code, c.f.
http://patchwork.coreboot.org/patch/3412/
I propose to use "(old ^ new) & ~REG2_MASK" instead, i.e. check if the
caller requests a change of bits not related to the write protection. I
guess that was your original intention anyway, is that correct?
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Various kernel options are known to interfere with flashrom's attempts to
access physical memory through /dev/mem. Some (like CONFIG_STRICT_DEVMEM)
are important security measures that cannot be disabled without recompiling
the kernel, and are likely to be used more widely over time.
However, complete access to physical memory is unnecessary for some use
cases. For example, the SPI interface on an Intel NIC can be accessed by
mmapping a BAR resource file in the PCI device directory in sysfs. Has
anyone considered implementing such an alternative access method for PCI
devices in flashrom?
--Ed
On Fri, 5 Dec 2014 18:26:46 +0100
Mathilde <allatoja(a)gmail.com> wrote:
> Hello,
>
> Being not an informatician, I need help for updating my BIOS Coreboot (on a
> Thinkpad X60), because of heat issues.
>
> I dowloaded the last release here http://libreboot.org/docs/release.html,
> and installed the build dependencies. Could you explain me step by step
> what to do now?
>
> I did'nt understand whether I am to compile flashrom or not. In advance
> thank you very much!
Hi,
you probably want to ask the libreboot guys not us ;)
Please see the contact information on http://libreboot.org at the
bottom.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
I finally managed to get the chip recognised by flashrom using the following circuit:
Chip --- Arduino
1 10
2 12
3 3.3V
4 GND
5 11
6 13
7 3.3V
8 3.3V
The problem now is with the reading. With the flag -VVVr I get the following:
Reading flash... serprog_spi_send_command, writecnt=4, readcnt=65536
serprog_spi_send_command, writecnt=4, readcnt=65536
serprog_spi_send_command, writecnt=4, readcnt=65536
serprog_spi_send_command, writecnt=4, readcnt=65536
serprog_spi_send_command, writecnt=4, readcnt=65536
serprog_spi_send_command, writecnt=4, readcnt=65536
It outputs a different number of lines each time but always stops. Any idea what the problem may be? Any help will be greatly appreciated.
Best regards,
Paulo Ribeiro
Hi,
I have successfully flashed a EN25Q64 that was rated untested. It was
for an 8MB version of openWRT.
My setup was a Raspberry Pi with flashrom 0.9.5.2-r1546 and Linux
3.12.22+. I made a little SMD adapter like shown in the picture that
plugs directly in the Pi header.
Regards
Markus
On Tue, 23 Sep 2014 20:29:55 +0330
Arman Khodabande <amal555(a)gmail.com> wrote:
> Hello
> As I checked Supported hardware on the Flashrom website the chip
> EN25F32 has unknown status. I wanted to inform you that successfully
> tested the Read and Write operations of this chip on a Rayer_spi
> programmer. The EN25F32 chip acts as the Bios in the Dell XPS L502
> Laptops. Here's the log with (-V):
>
> […]
>
> Perhaps the verification process failed which maybe because of
> programmer disconnection or fault. It may have been succeeded. So I'm
> unsure.
>
> Verifying flash... VERIFY FAILED at 0x00008134! Expected=0xed,
> Read=0xef, failed byte count from 0x00000000-0x003fffff: 0xbe54
> Your flash chip is in an unknown state.
> Get help on IRC at chat.freenode.net (channel #flashrom) or
> mail flashrom(a)flashrom.org with the subject "FAILED: "!
>
> I verified the chip with another program called SPIPGM and it showed
> no errors. so the READ and WRITE process was fine by flashrom.
Hello Arman,
thanks for your report! I'll pretend the verification errors never
happened, because the LPT-based programmers are usually to blame and
not flashrom itself. Thus I have marked the flash chip as fully tested
and will commit that later together with other small changes.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner