Hi Anders,
On 07.11.2017 21:31, Anders Nelson wrote:
Argh:
===
root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) flashrom is free software, get the source code at https://flashrom.org
Error: Unknown programmer "ft2232_spi". Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. Please run "flashrom --help" for usage info.
===
"ft2232_spi" is what I see in the source code, should I be using another option to use my FTDI 2232H board as a programmer?
no, that's the right one. But the `make` failed you again. It checks if libftdi is available and silently ignores ft2232_spi if not (even if explicitly asked to build ft2232_spi support in, pretty weird). Anyway, the solution is simple, install libftdi along with it's development package. Under Ubuntu this would be `apt-get install libftdi-dev`. Then run the same `make` command again.
Hope that (finally) helps, Nico
Hi Nico,
I thought I had installed the libftdi-dev package when I started so I repeated that process:
===
root@chrx:/home/chrx/Github/flashrom# apt-get install libftdi-dev Reading package lists... Done Building dependency tree Reading state information... Done libftdi-dev is already the newest version (0.20-4build1). 0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
===
root@chrx:/home/chrx/Github/flashrom# apt-get install libftdi1 Reading package lists... Done Building dependency tree Reading state information... Done libftdi1 is already the newest version (0.20-4build1). libftdi1 set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
===
root@chrx:/home/chrx/Github/flashrom# make clean Replacing all version templates with v0.9.9-86-ge1a960e. rm -f flashrom flashrom.exe libflashrom.a *.o *.d flashrom.8 flashrom.8.html build_details.txt make[1]: Entering directory '/home/chrx/Github/flashrom/util/ich_descriptors_tool' rm -f ich_descriptors_tool ich_descriptors_tool.exe rm -rf .dep .obj make[1]: Leaving directory '/home/chrx/Github/flashrom/util/ich_descriptors_tool'
===
[...build completes without error...]
===
root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) flashrom is free software, get the source code at https://flashrom.org
Error: Unknown programmer "ft2232_spi". Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. Please run "flashrom --help" for usage info.
===
The fuuuu?
-- Anders Nelson
+1 (517) 775-6129
www.erogear.com
On Tue, Nov 7, 2017 at 10:10 PM, Nico Huber nico.h@gmx.de wrote:
Hi Anders,
On 07.11.2017 21:31, Anders Nelson wrote:
Argh:
===
root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) flashrom is free software, get the source code at https://flashrom.org
Error: Unknown programmer "ft2232_spi". Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii,
atavia,
it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. Please run "flashrom --help" for usage info.
===
"ft2232_spi" is what I see in the source code, should I be using another option to use my FTDI 2232H board as a programmer?
no, that's the right one. But the `make` failed you again. It checks if libftdi is available and silently ignores ft2232_spi if not (even if explicitly asked to build ft2232_spi support in, pretty weird). Anyway, the solution is simple, install libftdi along with it's development package. Under Ubuntu this would be `apt-get install libftdi-dev`. Then run the same `make` command again.
Hope that (finally) helps, Nico