Bug 839179 - flashrom is built without USB programmer support (FT2232, FT4232, etc)
Summary: flashrom is built without USB programmer support (FT2232, FT4232, etc)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: flashrom
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-11 07:19 UTC by Alex G.
Modified: 2012-07-20 01:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-20 01:53:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alex G. 2012-07-11 07:19:00 UTC
Description of problem:
Flashrom is built without support for USB programmers. When trying to use FT4232H with an SPI ROM, flashrom returns an error.

Version-Release number of selected component (if applicable):
NA

How reproducible:
Always

Steps to Reproduce:
1. Connect FTDI-based programmer (FT4234H for example)
2. Invoke flashrom to use the FTDI-based programmer
3.
  
Actual results:
$ flashrom -p ft2232_spi:type=4232H,port=A -w coreboot.rom --noverify
[...]
Error: Unknown programmer ft2232_spi:type=4232H,port=A.
Please run "flashrom --help" for usage info.


Expected results:
$ ./flashrom -p ft2232_spi:type=4232H,port=A -w coreboot.rom --noverify
flashrom v0.9.5.2-r1547 on Linux 3.4.4-3.fc17.x86_64 (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Found ST flash chip "M25P40" (512 kB, SPI) on ft2232_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.

Additional info:
Clean flashrom build from svn works without a problem, so this looks to me like a Fedora specific problem.

Comment 1 Peter Lemenkov 2012-07-11 07:39:53 UTC
Thanks for the report. I'll fix this asap. Unfortunately I don't have any "external" programmers so I can't really test it - that's why I missed this issue.

Comment 2 Alex G. 2012-07-11 07:46:03 UTC
Thanks for responding on such short notice. Even if you don't have an external programmer, you can tell if flashrom was built with support for it.

I can test the Fedora build once it hits updates-testing.

When no programmer is connected:

$ ./flashrom -p ft2232_spi:type=4232H,port=A -w coreboot.rom --noverify
flashrom v0.9.5.2-r1547 on Linux 3.4.4-3.fc17.x86_64 (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Unable to open FTDI device: -3 (device not found)
Error: Programmer initialization failed.

Comment 3 Fedora Update System 2012-07-11 09:34:00 UTC
flashrom-0.9.5.2-4.svn1547.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/flashrom-0.9.5.2-4.svn1547.fc16

Comment 4 Fedora Update System 2012-07-11 09:34:09 UTC
flashrom-0.9.5.2-4.svn1547.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/flashrom-0.9.5.2-4.svn1547.fc17

Comment 5 Alex G. 2012-07-11 20:51:15 UTC
The new rpm works with USB-based FT4232.
Thanks!

Comment 6 Fedora Update System 2012-07-11 23:50:56 UTC
Package flashrom-0.9.5.2-4.svn1547.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing flashrom-0.9.5.2-4.svn1547.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-10520/flashrom-0.9.5.2-4.svn1547.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-07-20 01:53:00 UTC
flashrom-0.9.5.2-4.svn1547.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2012-07-20 01:58:00 UTC
flashrom-0.9.5.2-4.svn1547.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.