flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 08 Nov '17

08 Nov '17

Hi Anders, On 07.11.2017 23:44, Anders Nelson wrote: > root@chrx:/home/chrx/Github/flashrom# make clean Doing such things as root is very discouraged. > 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...] Well, like Stefan said, this is the part that could have told me that libftdi is already installed. > > === > 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. I could have seen this earlier... you are not calling your self-built flashrom at all. You call the one pre-installed by GalliumOS. If you want to run a binary that is not in a directory in your $PATH envi- ronment variable, you have to prefix it with a path, e.g. `./flashrom -p ft2232_spi` if you want to run the flashrom in the current directory. Nico

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Stefan Tauner 08 Nov '17

08 Nov '17

Hi, you always leave out the important part of the logs. The build process shows which libraries it finds at the top. Details about reasons why it failed can be gathered from the build_details.txt file if need be. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 07 Nov '17

07 Nov '17

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

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 07 Nov '17

07 Nov '17

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? Thanks, -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Tue, Nov 7, 2017 at 8:07 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > Also am I correct in saying the help listing needs to be updated with more > --programmer options? I don't see the 2232H device in there. I'll Google it > in the meantime. > > It's really (really) nice to see such fast and comprehensive support for > an open source project. Many thanks. > > =] > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Tue, Nov 7, 2017 at 7:56 PM, Anders Nelson <anders.k.nelson(a)gmail.com> > wrote: > >> Hi guys, sorry for the delay again! >> >> TL;DR: I did "make clean CONFIG_INTERNAL=no" and it looks like it built >> successfully! Here's the email as I assembled it before doing the "make >> clean": >> >> === >> >> root@chrx:/home/chrx/Github/flashrom# git describe >> v0.9.9-86-ge1a960e >> >> === >> >> I've attached the output files you asked for to this message. >> >> I did not change the code at all and I pulled from the master branch here >> IIRC: https://github.com/flashrom/flashrom >> >> I tried to build using "make CONFIG_INTERNAL=no" early on but this was >> the error output: >> >> === >> >> cli_classic.o: In function `main': >> cli_classic.c:(.text.startup+0xaac): undefined reference to >> `force_boardmismatch' >> print.o: In function `print_supported_boards_helper': >> print.c:(.text+0x245): undefined reference to `board_matches' >> print.o: In function `print_supported': >> print.c:(.text+0xf11): undefined reference to `chipset_enables' >> print.c:(.text+0xff3): undefined reference to `chipset_enables' >> spi.o: In function `spi_get_valid_read_addr': >> spi.c:(.text+0x12c): undefined reference to `ichspi_bbar' >> collect2: error: ld returned 1 exit status >> Makefile:1018: recipe for target 'flashrom' failed >> make: *** [flashrom] Error 1 >> >> === >> >> Everything above that in the build process looked ok! >> >> >> -- >> Anders Nelson >> >> +1 (517) 775-6129 >> >> www.erogear.com >> >> On Sat, Nov 4, 2017 at 11:21 AM, Nico Huber <nico.h(a)gmx.de> wrote: >> >>> Hi Anders, >>> >>> On 03.11.2017 21:35, Anders Nelson wrote: >>> > Hi guys, >>> > >>> > Here's the error I get trying to apply the patch: >>> > >>> > "root@chrx:/home/chrx/Github/flashrom# git apply --check >>> > /home/chrx/Downloads/ich_descriptors-amd64.patch >>> > error: patch failed: ich_descriptors.c:1064 >>> > error: ich_descriptors.c: patch does not apply" >>> >>> sorry, I was looking at the wrong version of the code. Doesn't matter, >>> see below. >>> >>> > >>> > Derp? Here's my output from "cc -v": >>> > >>> > ... >>> > >>> > And here's the output from the second command you asked for: >>> > >>> > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null >>> > ... >>> > #define __x86_64__ 1 >>> > ... >>> > #define __amd64__ 1 >>> > ... >>> >>> Both are there that's fine. And I think now, that my original assumption >>> that this could be an issue was wrong: We do check for x86 not only in >>> the Makefile but also in ichspi.c too (pretty weird redundancy) and the >>> latter check is in sync with ich_descriptors.c. >>> >>> I've also tried to build flashrom on Ubuntu 16.04 with the same compiler >>> version... and it worked *shrug*. >>> >>> > >>> > Whaaatsa goin' onnn? Thanks for your help! >>> >>> No clue, actually. Did you already try to build with `make >>> CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall >>> your work. We are ofc very interested to understand and fix the >>> actual problem. >>> >>> Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` >>> of the failing build. >>> >>> Did you change anything in the code? or tried to build different >>> versions? switch branches? in case, you could try a `make clean` >>> (although, I can't imagine why it would be necessary). >>> >>> Oh, I nearly forgot: Please show us the output of `git describe` (I'm >>> loosing track of our branches atm). >>> >>> Nico >>> >> >> >

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 07 Nov '17

07 Nov '17

Also am I correct in saying the help listing needs to be updated with more --programmer options? I don't see the 2232H device in there. I'll Google it in the meantime. It's really (really) nice to see such fast and comprehensive support for an open source project. Many thanks. =] -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Tue, Nov 7, 2017 at 7:56 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > Hi guys, sorry for the delay again! > > TL;DR: I did "make clean CONFIG_INTERNAL=no" and it looks like it built > successfully! Here's the email as I assembled it before doing the "make > clean": > > === > > root@chrx:/home/chrx/Github/flashrom# git describe > v0.9.9-86-ge1a960e > > === > > I've attached the output files you asked for to this message. > > I did not change the code at all and I pulled from the master branch here > IIRC: https://github.com/flashrom/flashrom > > I tried to build using "make CONFIG_INTERNAL=no" early on but this was the > error output: > > === > > cli_classic.o: In function `main': > cli_classic.c:(.text.startup+0xaac): undefined reference to > `force_boardmismatch' > print.o: In function `print_supported_boards_helper': > print.c:(.text+0x245): undefined reference to `board_matches' > print.o: In function `print_supported': > print.c:(.text+0xf11): undefined reference to `chipset_enables' > print.c:(.text+0xff3): undefined reference to `chipset_enables' > spi.o: In function `spi_get_valid_read_addr': > spi.c:(.text+0x12c): undefined reference to `ichspi_bbar' > collect2: error: ld returned 1 exit status > Makefile:1018: recipe for target 'flashrom' failed > make: *** [flashrom] Error 1 > > === > > Everything above that in the build process looked ok! > > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Sat, Nov 4, 2017 at 11:21 AM, Nico Huber <nico.h(a)gmx.de> wrote: > >> Hi Anders, >> >> On 03.11.2017 21:35, Anders Nelson wrote: >> > Hi guys, >> > >> > Here's the error I get trying to apply the patch: >> > >> > "root@chrx:/home/chrx/Github/flashrom# git apply --check >> > /home/chrx/Downloads/ich_descriptors-amd64.patch >> > error: patch failed: ich_descriptors.c:1064 >> > error: ich_descriptors.c: patch does not apply" >> >> sorry, I was looking at the wrong version of the code. Doesn't matter, >> see below. >> >> > >> > Derp? Here's my output from "cc -v": >> > >> > ... >> > >> > And here's the output from the second command you asked for: >> > >> > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null >> > ... >> > #define __x86_64__ 1 >> > ... >> > #define __amd64__ 1 >> > ... >> >> Both are there that's fine. And I think now, that my original assumption >> that this could be an issue was wrong: We do check for x86 not only in >> the Makefile but also in ichspi.c too (pretty weird redundancy) and the >> latter check is in sync with ich_descriptors.c. >> >> I've also tried to build flashrom on Ubuntu 16.04 with the same compiler >> version... and it worked *shrug*. >> >> > >> > Whaaatsa goin' onnn? Thanks for your help! >> >> No clue, actually. Did you already try to build with `make >> CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall >> your work. We are ofc very interested to understand and fix the >> actual problem. >> >> Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` >> of the failing build. >> >> Did you change anything in the code? or tried to build different >> versions? switch branches? in case, you could try a `make clean` >> (although, I can't imagine why it would be necessary). >> >> Oh, I nearly forgot: Please show us the output of `git describe` (I'm >> loosing track of our branches atm). >> >> Nico >> > >

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 07 Nov '17

07 Nov '17

Hi Anders, On 03.11.2017 21:35, Anders Nelson wrote: > Hi guys, > > Here's the error I get trying to apply the patch: > > "root@chrx:/home/chrx/Github/flashrom# git apply --check > /home/chrx/Downloads/ich_descriptors-amd64.patch > error: patch failed: ich_descriptors.c:1064 > error: ich_descriptors.c: patch does not apply" sorry, I was looking at the wrong version of the code. Doesn't matter, see below. > > Derp? Here's my output from "cc -v": > > ... > > And here's the output from the second command you asked for: > > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null > ... > #define __x86_64__ 1 > ... > #define __amd64__ 1 > ... Both are there that's fine. And I think now, that my original assumption that this could be an issue was wrong: We do check for x86 not only in the Makefile but also in ichspi.c too (pretty weird redundancy) and the latter check is in sync with ich_descriptors.c. I've also tried to build flashrom on Ubuntu 16.04 with the same compiler version... and it worked *shrug*. > > Whaaatsa goin' onnn? Thanks for your help! No clue, actually. Did you already try to build with `make CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall your work. We are ofc very interested to understand and fix the actual problem. Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` of the failing build. Did you change anything in the code? or tried to build different versions? switch branches? in case, you could try a `make clean` (although, I can't imagine why it would be necessary). Oh, I nearly forgot: Please show us the output of `git describe` (I'm loosing track of our branches atm). Nico

2 1

Flashrom and Bus Pirate issue on cFeon EN25F16
by biagiodemaio 07 Nov '17

07 Nov '17

root@Aspire-5742:~# flashrom -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=1M flashrom v0.9.9-r1954 on Linux 4.13.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on buspirate_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 chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! I am using a Bus Pirate v3 (version 3.6 on chart) This are Bus Pirate actual dates : Bus Pirate v3.5 Community Firmware v7.1 - goo.gl/gCzQnW [HiZ 1-WIRE UART I2C SPI 2WIRE 3WIRE KE5 DEVID:0x0447 REVID:0x3046 (24FJ64GA00 2 B8) http://dangerousprototypes.com Trying to read a Eeprom chip cFeon EN25F16 and got this issue. Looking for Bus Pirate I found other users to manifest prooblems with Flashrom e Bus Pirate about cFeon ! I tried to read a Macronix chip and It did good. Then I used an CH341A programmer whit Flashrom an It reads well the EN25F16 ... so I don't know if problem is on Bus Pirate or on Flashrom compatibility with cFeon chips. Many thanks Biagio De Maio

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Stefan Tauner 03 Nov '17

03 Nov '17

On Tue, 31 Oct 2017 00:18:58 +0000 Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > I'm trying to compile the latest stable source on my Ubuntu-based GalliumOS > system running on a recent x86_64 Chromebook. > > I get the error: > > ichspi.o: In function `ich_init_spi': > ichspi.c:(.text+0x26b2): undefined reference to > `read_ich_descriptors_via_fdo' Hi, can you please post more details about your build environment? E.g., the output of cc -v cc -dM -E - < /dev/null The latter should output all preprocessor defines, excluding/including the culprit 64b macros. According the best source I am aware of (https://sourceforge.net/p/predef/wiki/Architectures/) both, __amd64__ and __x86_64__ should be equivalently available in all systems we care about. But as Nico stated we have used both (and some additional variations) in various places which makes such breakage possible. Maybe we should use a similar approach as for discerning OSes with a central header file defining our own macros... I have once started such a thing in hwaccess.c. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Patch to flashrom for Macronix M25U12835F flash support and write protection bug fix
by David Hendricks 03 Nov '17

03 Nov '17

Hello Alex, Thank you for this patch and your friendly nudge in the other thread. I have uploaded it to chromium.org so that they can review, test, and merge it: https://chromium-review.googlesource.com/c/chromiumos/third_party/flashrom/… On Mon, Sep 4, 2017 at 8:47 PM, <alexlu6(a)mxic.com.tw> wrote: > Dear Sir, > > I am from Macronix (Taiwan), here I send you the source patch that > could > fix the write protection error on Chromebook project which came form > Quatun Computer. > I hope you can help patching into the Flashrom project (branch: master). > Thanks a lot ! > > Alex Lu > Macronix , FAE Dept. > > > CONFIDENTIALITY NOTE: > > This e-mail and any attachments may contain confidential information > and/or personal data, which is protected by applicable laws. Please be > reminded that duplication, disclosure, distribution, or use of this e-mail > (and/or its attachments) or any part thereof is prohibited. If you receive > this e-mail in error, please notify us immediately and delete this mail as > well as its attachment(s) from your system. In addition, please be informed > that collection, processing, and/or use of personal data is prohibited > unless expressly permitted by personal data protection laws. Thank you for > your attention and cooperation. > > Macronix International Co., Ltd. > > ===================================================================== > > > CONFIDENTIALITY NOTE: > > This e-mail and any attachments may contain confidential information > and/or personal data, which is protected by applicable laws. Please be > reminded that duplication, disclosure, distribution, or use of this e-mail > (and/or its attachments) or any part thereof is prohibited. If you receive > this e-mail in error, please notify us immediately and delete this mail as > well as its attachment(s) from your system. In addition, please be informed > that collection, processing, and/or use of personal data is prohibited > unless expressly permitted by personal data protection laws. Thank you for > your attention and cooperation. > > Macronix International Co., Ltd. > > ===================================================================== > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

working board - elitegroup P6STMT
by Branden Waldner 02 Nov '17

02 Nov '17

I've been using this board for chips in testing coreboot on a asus p2-99. Chips are correctly identified when hot swapped and do not get corrupted on power down. Flashrom does _not_ work on the asus p2-99. It fails to find the flash chip. The p2-99 seems to be very similiar to the asus p2b, just with 440ZX instead of a 440BX northbridge and one less ram slot.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom