On Mon, 9 May 2016 20:46:18 -0700
David Hendricks <dhendrix(a)google.com> wrote:
> Hi Victor,
> From Flashrom's software perspective all chips with the same ID are
> indistinguishable.
>
> Part number often includes characteristics such as package and thermal
> tolerance which do not affect software compatibility.
However, we will add the new names to the in-program (and hence
wiki) database so that this new information becomes public. Thanks for
the heads up, Victor.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Hi,
we're hitting the 80 column limit in our code in ways which actually
reduce readability for the code. Examples are various multiline messages
and complicated nested code where refactoring to a separate function
doesn't make sense.
Keeping the old 80 column limit is not really an option anymore.
Standard terminal sizes have one of 80, 100 or 132 columns.
Given the monitor resolutions many people have nowadays, I think it is
safe to say that you can fit two xterms with 100 columns horizonally
next to each other. 100 columns should also be sufficient for a msg_p*
of roughly 80 columns of text.
132 columns provide more leeway, but IMHO that would be too wide for
good readability (and my screen can't fit two xterms side-by-side anymore).
Of course some files have sections where any column limit is not
acceptable (board lists etc.), but the column limit violations should be
limited to the affected file sections, not whole files.
Comments?
I'd like to get this decided today or tomorrow so we know where we need
line breaks in Stefan Tauner's new struct flashchip patch.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
A Hardware Enablement devroom will be taking place at FOSDEM this year,
on Sunday 10 December 2017. This newly-created devroom is the result of
3 proposals that were merged together. It is co-organized by several
individuals.
The devroom covers all aspects related to hardware enablement and
support with free software, including aspects related to boot software,
firmwares, drivers and userspace tools and adaptation.
Proposals for talks related to these topics are welcome and can be
submitted until Sunday 26 November 2017 via the pentabarf interface.
Short talks are encouraged over longer ones in order to cover a wide
range of topics.
The announcement for the devroom, that contains all the useful
information, was published at:
https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html
Cheers and see you at FOSDEM!
--
Paul Kocialkowski, developer of free digital technology and hardware
support
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/https://git.code.paulk.fr/
Hello dear,
I've try to program an SPI flash from Macronix MX25V1635F and receive
the following mensage from flashrom:
Calibrating delay loop... OK.
Found Macronix flash chip "unknown Macronix SPI chip" (0 kB, SPI) on
ft2232_spi.
===
This flash part has status NOT WORKING for operations: PROBE READ ERASE
WRITE
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom(a)flashrom.org if any of the above
operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-VE, -Vw), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
Read is not working on this chip. Aborting.
Can you help with this?
Thank you very much,
Best regards
Emiliano
Hi everyone,
I have spent the past few days implementing support for the AMD
Am79C971, in the family of AMD Lance network controllers. Please see
attached source code.
So far, testing with SST39SF020A memory has shown positive results for
reading flash memory. However, erasure and writing fails now and then,
often with just one or two bytes being erroneous. Sometimes it fails
with “magic data” being written, sometimes with random data at random
locations. Please see the attached log for a full example failure.
"Verifying flash... FAILED at 0x00005555! Expected=0xef, Found=0xaa,
failed byte count from 0x00000000-0x0003ffff: 0x1"
"Verifying flash... FAILED at 0x000008b9! Expected=0x00, Found=0xb9,
failed byte count from 0x00000000-0x0003ffff: 0x1"
"Verifying flash... FAILED at 0x0001fd86! Expected=0x86, Found=0x85,
failed byte count from 0x00000000-0x0003ffff: 0x1"
I have never worked with PCI devices nor flash memory before, and I
would really appreciate some ideas of where to start poking around to
fix the erasure and writing issues. Also, comments on the code is highly
appreciated!
The datasheet for the network controller can be found here:
https://datasheet.octopart.com/AM79C971AKC-W-AMD-datasheet-5389196.pdf
Kind regards,
Alexander Lundén
Good Morning,
I have a few blank ROM chips that I am trying to program. I keep receiving errors whenever I try to write to them. Can I not write to a blank chip with flashrom?
The chip is a Winbond W25X40.
Thank you,
Kaitlin Key
CACI - Sterling, US
(805) 236-8555
Hi,
I'm not sure where this should be reported, but I've tested the
stable v1.0-1-g6b9e934 version, which supports a few new chips, and I
can successfully PROBE, READ, and WRITE with the following chips:
MX25U12835F
W25Q128.W
This is on two different Gigabyte AB350N Gaming WiFi motherboards,
flashrom compiled and running as so:
|$ ./flashrom -R||
||flashrom v1.0-1-g6b9e934 on Linux 4.8.17-tinycore64 (x86_64)||
||flashrom is free software, get the source code at https://flashrom.org|
I have not had occasion to test ERASE on either, so I cannot comment.
What is the proper place to report this information?
--
David Martinka
Engineering & Support
MediaVue Systems
+1 781.926.0676
mediavuesystems.com <http://www.mediavuesystems.com/>
Your Vision Enabled
> but when I type "make" I get this error:
>
>
>
> The following features require libusb-0.1/libusb-compat: CONFIG_PICKIT2_SPI.
>
> Please install libusb-0.1 headers or libusb-compat headers or disable all
> features
>
> mentioned above by specifying make CONFIG_ENABLE_LIBUSB0_PROGRAMMERS=no
>
>
>
> What can be done to solve that error? Thank you.
>
make CONFIG_ENABLE_LIBUSB0_PROGRAMMERS=no
This will disable the support for the programmers depending on the libusb 0.1 library (pickit2 for e.g.)
--
Best regards,
Miklos Marton
Hi, I´m trying to install flashrom on windows following these steps:
https://www.flashrom.org/Windows
but when I type "make" I get this error:
The following features require libusb-0.1/libusb-compat: CONFIG_PICKIT2_SPI.
Please install libusb-0.1 headers or libusb-compat headers or disable all
features
mentioned above by specifying make CONFIG_ENABLE_LIBUSB0_PROGRAMMERS=no
What can be done to solve that error? Thank you.