flashrom August 2015

flashrom@flashrom.org

35 participants
53 discussions

Re: [flashrom] Proposed changes to flashrom hosting and workflow
by Carl-Daniel Hailfinger 11 Aug '15

11 Aug '15

On 10.08.2015 19:46, Patrick Georgi wrote: > I wanted to note that mercurial can use git servers in the backend: > http://hg-git.github.io/ Hm. That sounds promising, thanks. On 08.08.2015 15:04, Patrick Georgi wrote: > 2015-08-08 10:23 GMT+02:00 Carl-Daniel Hailfinger > <c-d.hailfinger.devel.2006(a)gmx.net > <mailto:c-d.hailfinger.devel.2006@gmx.net>>: > > If there really is a large demand for a non-svn hosting, I would > be open > to using mercurial (as master) because it at least has some sort of > usability and can provide (conceptually limited) version numbers. > I have > worked for a few years with mercurial and the version numbers are > extremely helpful even if they are per-branch and only semi-stable. > > mercurial's notion of a monotonic commit counter (that you're looking > for if I understand you correctly) has about the same quality as git > describe's commits-since-last-tag counter. > > For a global numbering scheme, you could just (automatically) tag > every single commit of a certain branch (master, release, ...) with a > monotonic counter. That's more or less what the svn-to-git translation > of tianocore is doing, for example (with tags following the scheme > svn18670). That way, those numbers are actually global, unlike what > mercurial is doing. > Assume that the scheme is to use $version-$number since release: git > describe would emit something like 0.9.9-40-5-gabcde, meaning that > your tree is based on the tag 0.9.9-40 (globally unique), is 5 local > commits away from that, with your current local commit id being abcde. The auto-tag of every commit sounds like an option I could agree with. It would preserve the convenience of the global strong svn commit ID even for git. However, I don't know if this would be acceptable for Stefan (especially from a merging perspective). Regards, Carl-Daniel

1 0

Re: [flashrom] Proposed changes to flashrom hosting and workflow
by Carl-Daniel Hailfinger 10 Aug '15

10 Aug '15

I would like to avoid git at all costs, even if it means I have to host something non-git as main repo myself and pay for the hosting. Cloning git into a local svn on my side is not an option because it combines the worst usability aspects of git hosting (no version numbers) and svn clients (no offline commits). If there really is a large demand for a non-svn hosting, I would be open to using mercurial (as master) because it at least has some sort of usability and can provide (conceptually limited) version numbers. I have worked for a few years with mercurial and the version numbers are extremely helpful even if they are per-branch and only semi-stable. About jenkins: Seems to be a good idea and would help detect patch bitrot. About gerrit: Last time I tried gerrit the usability was horrible: - needs registration (like a forum) - has no usable mail interface (like a forum) - you can't work on drafts for a review unless you keep the web browser window open (like a forum) If we really want to move to gerrit, we should close the mailing list as well and switch to a forum which has roughly the same usability as gerrit. I really mean it. We seriously should consider moving to a forum _if_ developers prefer forum interfaces to mail. Regards, Carl-Daniel On 07.08.2015 20:51, David Hendricks wrote: > For those who missed it on IRC, Stefan (Reinauer) has proposed > retiring SVN and patch work in favor of Git and (likely) Gerrit + > Jenkins. Maintaining SVN and Patchwork represents a surprisingly large > maintenance burden on top of Git and Gerrit that coreboot uses. > Additionally, many in the community work around SVN's limitations by > mirroring the project at places like Github anyway. > > Stefan put up a Doodle poll here to hear out comments/concerns: > http://doodle.com/p2dxtnksmsgwmzrq > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom <

3 3

Re: [flashrom] MX25L6445E erase and write failed!
by The Raven 10 Aug '15

10 Aug '15

Hi again I have now tryed with frser-duino from "Urja Rannikko". With other chips i have better results (for example with the M25P10, this chips is working now). But the MX25L6445E is still not working. After a long time flashrom trys other erase options, but all failed. Have a look here (cut from log): ...............-0x0f5fff:E, 0x0f6000-0x0f6fff:E, 0x0f7000-0x0f7fff:E, 0x0f8000-0x0f8fff:E, 0x0f9000-0x0f9fff:E, 0x0fa000-0x0fafff:E, 0x0fb000-0x0fbfff:E, 0x0fc000-0x0fcfff:E, 0x0fd000-0x0fdfff:E, 0x0fe000-0x0fefff:E, 0x0ff000-0x0fffff:E, 0x100000-0x100fff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, failed byte count from 0x00100000-0x00100fff: 0xfe5 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x007fff:S, 0x008000-0x00ffff:S, 0x010000-0x017fff:S, 0x018000-0x01ffff:S, 0x020000-0x027fff:S, 0x028000-0x02ffff:S, 0x030000-0x037fff:S, 0x038000-0x03ffff:S, 0x040000-0x047fff:S, 0x048000-0x04ffff:S, 0x050000-0x057fff:S, 0x058000-0x05ffff:S, 0x060000-0x067fff:S, 0x068000-0x06ffff:S, 0x070000-0x077fff:S, 0x078000-0x07ffff:S, 0x080000-0x087fff:S, 0x088000-0x08ffff:S, 0x090000-0x097fff:S, 0x098000-0x09ffff:S, 0x0a0000-0x0a7fff:S, 0x0a8000-0x0affff:S, 0x0b0000-0x0b7fff:S, 0x0b8000-0x0bffff:S, 0x0c0000-0x0c7fff:S, 0x0c8000-0x0cffff:S, 0x0d0000-0x0d7fff:S, 0x0d8000-0x0dffff:S, 0x0e0000-0x0e7fff:S, 0x0e8000-0x0effff:S, 0x0f0000-0x0f7fff:S, 0x0f8000-0x0fffff:S, 0x100000-0x107fff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, failed byte count from 0x00100000-0x00107fff: 0x7f69 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 2... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:S, 0x080000-0x08ffff:S, 0x090000-0x09ffff:S, 0x0a0000-0x0affff:S, 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:S, 0x0e0000-0x0effff:S, 0x0f0000-0x0fffff:S, 0x100000-0x10ffff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, failed byte count from 0x00100000-0x0010ffff: 0xfb20 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, failed byte count from 0x00000000-0x007fffff: 0x26be30 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, failed byte count from 0x00000000-0x007fffff: 0x26be30 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! As you can see it always fails at the same byte count. I am still not sure if this problem is related to serprog/frser-duino. It looks like the chip is write protected or something like that.

1 1

W836xx: HP Proliant DL385 G7: flashrom -V
by Александр Трубицын 08 Aug '15

08 Aug '15

Hi, Stefan! I can't reflash DL385 G7, but can try flashrom -p internal -V and flashrom -p internal -Vr on this server with new versions of flashrom. With best regards, Alexander Trubitsyn

1 0

Proposed changes to flashrom hosting and workflow
by David Hendricks 07 Aug '15

07 Aug '15

For those who missed it on IRC, Stefan (Reinauer) has proposed retiring SVN and patch work in favor of Git and (likely) Gerrit + Jenkins. Maintaining SVN and Patchwork represents a surprisingly large maintenance burden on top of Git and Gerrit that coreboot uses. Additionally, many in the community work around SVN's limitations by mirroring the project at places like Github anyway. Stefan put up a Doodle poll here to hear out comments/concerns: http://doodle.com/p2dxtnksmsgwmzrq -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

ease projects task 1.1 find chips without voltage data
by sven.waldecker＠mail.de 04 Aug '15

04 Aug '15

Hello Flashrom members, i want to support the Flashrom project i was reading the easy projects page and want to do Task 1.1 "Find chips without voltage data". Ive read the flashchips.c hello flashrom.org members, i complete the voltage ranges in flashchips.c at the moment the INTEL_28F002BL-T VCC is available in a 3.3 Volt and in a 3.3 Volt Version. should i create two structs one for the 3.3 Volt and the other one for 5 Volt type ? best regards Sven ------------------------------------------------------------------------------------------------- FreeMail powered by mail.de - MEHR SICHERHEIT, SERIOSITÄT UND KOMFORT

2 1

Re: [flashrom] dediprog: Use command 0x0B only on older SF100s
by David Woodhouse 04 Aug '15

04 Aug '15

On Tue, 2015-08-04 at 00:37 -0700, David Hendricks wrote: > > > On Mon, Aug 3, 2015 at 4:50 PM, David Woodhouse <dwmw2(a)infradead.org> > wrote: > > On Sun, 2015-08-02 at 15:09 -0700, David Hendricks wrote: > > > Tested with SF100 V:5.1.5 and SF600 V:7.1.4 (with subsequent > > patches) > > > > Where are these subsequent patches of which you speak? I have SF600 > > testers who would be happy to try them out... > I was just referring to the earlier patches that you and Stefan had > posted earlier (based off Simon Glass's work): > http://www.flashrom.org/pipermail/flashrom/2015-July/013759.html Hm. I could have sworn I'd tried simply disabling the call to dediprog_device_init(), and my SF600Plus tester (FW 7.1.1) still told me it wasn't working — or that it was working for reads but not erase/writes. Am I missing something more that your patch does? > <insert rant about SCM and code review process> Yeah. FWIW my set of patches is at http://git.infradead.org/users/dwmw2/flashrom.git — it's not *impossible* to work sanely, even if you are stuck with a project which for some reason is still stuck in the 20th century with Subversion. -- dwmw2

1 0

New programmer board "SPI_TT LPT" support - patch submission
by Max 04 Aug '15

04 Aug '15

Hello, everybody, involved into flashrom! I'd implemented support for well known in Russia SPI_TT LPT programmer. Basically, it's only Byteblaster clone with changed pinout. So, modifications was pretty straIghtforward. In attach - modified "rayer_spi.c" from trunk branch. Hope, it will be useful for someone. Best regards, Max Arephin.

1 0

Re: [flashrom] dediprog: Use command 0x0B only on older SF100s
by David Woodhouse 04 Aug '15

04 Aug '15

On Sun, 2015-08-02 at 15:09 -0700, David Hendricks wrote: > Tested with SF100 V:5.1.5 and SF600 V:7.1.4 (with subsequent patches) Where are these subsequent patches of which you speak? I have SF600 testers who would be happy to try them out... -- David Woodhouse Open Source Technology Centre David.Woodhouse(a)intel.com Intel Corporation

2 1

dediprog: Use command 0x0B only on older SF100s
by David Hendricks 03 Aug '15

03 Aug '15

As per e-mail with Dediprog, command 0x0B (which is not listed in the command spec) is used to set voltage level on older Dediprogs. SF100 V6.0.0 and newer as well as all SF600 programmers do not support it. This patch renames dediprog_device_init() to something more appropriate and adds comments for clarity, and only runs it conditionally if we cannot query the devicestring during init. Tested with SF100 V:5.1.5 and SF600 V:7.1.4 (with subsequent patches) Signed-off-by: David Hendricks <dhendrix(a)chromium.org> Index: dediprog.c =================================================================== --- dediprog.c (revision 1896) +++ dediprog.c (working copy) @@ -75,6 +75,7 @@ CMD_READ_PROG_INFO = 0x08, CMD_SET_VCC = 0x09, CMD_SET_STANDALONE = 0x0A, + CMD_SET_VOLTAGE = 0x0B, /* Only in firmware older than 6.0.0 */ CMD_GET_BUTTON = 0x11, CMD_GET_UID = 0x12, CMD_SET_CS = 0x14, @@ -579,13 +580,15 @@ return 0; } -static int dediprog_device_init(void) +/* Only use dediprog_set_voltage on SF100 programmers with firmware older + * than V6.0.0. Newer programmers (including all SF600s) do not support it. */ +static int dediprog_set_voltage(void) { int ret; char buf[0x1]; memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, REQTYPE_OTHER_IN, 0x0B, 0x0, 0x0, + ret = usb_control_msg(dediprog_handle, REQTYPE_OTHER_IN, CMD_SET_VOLTAGE, 0x0, 0x0, buf, 0x1, DEFAULT_TIMEOUT); if (ret < 0) { msg_perr("Command A failed (%s)!\n", usb_strerror()); @@ -595,6 +598,7 @@ msg_perr("Unexpected response to init!\n"); return 1; } + return 0; } @@ -853,11 +857,15 @@ if (register_shutdown(dediprog_shutdown, NULL)) return 1; - /* Perform basic setup. */ - if (dediprog_device_init()) - return 1; - if (dediprog_check_devicestring()) - return 1; + /* Try reading the devicestring. If that fails and the device is old + * (FW < 6.0.0) then we need to try the "set voltage" command and then + * attempt to read the devicestring again. */ + if (dediprog_check_devicestring()) { + if (dediprog_set_voltage()) + return 1; + if (dediprog_check_devicestring()) + return 1; + } /* Set all possible LEDs as soon as possible to indicate activity. * Because knowing the firmware version is required to set the LEDs correctly we need to this after

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom August 2015