flashrom August 2016

flashrom@flashrom.org

26 participants
43 discussions

Unsupported Lenovo Thinkpad X200
by Alexander Waldmann 21 Aug '16

21 Aug '16

Basically what it says on the tin. One of my X200 systems works with flashrom's internal programmer, as expected, but a recently acquired one does not, I get the error about unsupported laptop. Using the laptop:force_I_want_a_brick option seems to work, I've used it to update a few times. Attached are the requested command outputs, dmidecode and lspci -nn. System is currently running Libreboot beta. Flashrom version tested was 0.9.9 on several distros. If there's any other info required feel free to request it. Thanks.

2 2

Skylake support
by Jason La Mont 20 Aug '16

20 Aug '16

Is there a plan or timeline on skylake support? Thanks, Lee Sent from my iPhone

1 0

Re: [flashrom] Windows Help
by Jason Jacobs 12 Aug '16

12 Aug '16

Urja, Thanks so much. I will give this a try. Thanks, Jason Jacobs -----Original Message----- From: Urja Rannikko [mailto:urjaman@gmail.com] Sent: Friday, August 12, 2016 11:31 AM To: Jason Jacobs <Jason.Jacobs(a)FIRSTSOLAR.COM> Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] Windows Help On Fri, Aug 12, 2016 at 6:09 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > The link on the flashrom page takes me to here: > http://ra.openbios.org/~idwer/flashrom/mingw/ > > The windows flashrom exe on that page is from 2014 so I assume that is very old. Where do I download version 0.9.9? > Oh the wiki should be fixed. I dunno in what direction, but atleast to mark that as obsolete. The entire windows page is kinda in need of updating. We dont have any official windows binary releases (thus I assumed you had cross-compiled yours from source on linux), but since the buildbot does test win32 and win64, I made a static build for windows: http://buildbot.flashrom.org/buildresults/flashrom-000478-pe5/win32/flashro… (or win64 http://buildbot.flashrom.org/buildresults/flashrom-000478-pe5/win64/flashro… ).

1 0

Re: [flashrom] Windows Help
by Urja Rannikko 12 Aug '16

12 Aug '16

On Fri, Aug 12, 2016 at 6:09 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > The link on the flashrom page takes me to here: http://ra.openbios.org/~idwer/flashrom/mingw/ > > The windows flashrom exe on that page is from 2014 so I assume that is very old. Where do I download version 0.9.9? > Oh the wiki should be fixed. I dunno in what direction, but atleast to mark that as obsolete. The entire windows page is kinda in need of updating. We dont have any official windows binary releases (thus I assumed you had cross-compiled yours from source on linux), but since the buildbot does test win32 and win64, I made a static build for windows: http://buildbot.flashrom.org/buildresults/flashrom-000478-pe5/win32/flashro… (or win64 http://buildbot.flashrom.org/buildresults/flashrom-000478-pe5/win64/flashro… ).

1 0

Re: [flashrom] Windows Help
by Jason Jacobs 12 Aug '16

12 Aug '16

Urja, The link on the flashrom page takes me to here: http://ra.openbios.org/~idwer/flashrom/mingw/ The windows flashrom exe on that page is from 2014 so I assume that is very old. Where do I download version 0.9.9? Thanks, Jason Jacobs -----Original Message----- From: Urja Rannikko [mailto:urjaman@gmail.com] Sent: Friday, August 12, 2016 11:05 AM To: Jason Jacobs <Jason.Jacobs(a)FIRSTSOLAR.COM> Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] Windows Help On Fri, Aug 12, 2016 at 5:56 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > Urja, > > Thanks for the response. The issue I am having is setting the baud in Windows to 20000000, it gets rounded down to 115200. I have been unsuccessful in all the attempts to get around this. There is a way to alias a baud in the FTDI drivers so that when you set the baud to 300 for instance, it is actually 2000000. I tried this, and it didn’t work in flashrom but I did verify that the port is actually being set to 2000000 and data is being send to the Arduino at 2000000. > > My question is, does flashrom do anything with the baud rate setting other than just set the port? Is it used for timing internally? If so, that would explain why flashrom doesn’t work with aliasing when I set the baud to 300 (which is actually 20000000). You should use the newest flashrom (0.9.9), flashrom has supported arbitrary baudrates (anything the driver supports) on windows since svn revision 1909... (it is then also possible to omit specifying the baudrate... IIRC the result is that the one selected in device manager would be used...). -- Urja Rannikko

1 0

Re: [flashrom] Windows Help
by Urja Rannikko 12 Aug '16

12 Aug '16

On Fri, Aug 12, 2016 at 5:56 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > Urja, > > Thanks for the response. The issue I am having is setting the baud in Windows to 20000000, it gets rounded down to 115200. I have been unsuccessful in all the attempts to get around this. There is a way to alias a baud in the FTDI drivers so that when you set the baud to 300 for instance, it is actually 2000000. I tried this, and it didn’t work in flashrom but I did verify that the port is actually being set to 2000000 and data is being send to the Arduino at 2000000. > > My question is, does flashrom do anything with the baud rate setting other than just set the port? Is it used for timing internally? If so, that would explain why flashrom doesn’t work with aliasing when I set the baud to 300 (which is actually 20000000). You should use the newest flashrom (0.9.9), flashrom has supported arbitrary baudrates (anything the driver supports) on windows since svn revision 1909... (it is then also possible to omit specifying the baudrate... IIRC the result is that the one selected in device manager would be used...). -- Urja Rannikko

1 0

Re: [flashrom] Windows Help
by Jason Jacobs 12 Aug '16

12 Aug '16

Urja, Thanks for the response. The issue I am having is setting the baud in Windows to 20000000, it gets rounded down to 115200. I have been unsuccessful in all the attempts to get around this. There is a way to alias a baud in the FTDI drivers so that when you set the baud to 300 for instance, it is actually 2000000. I tried this, and it didn’t work in flashrom but I did verify that the port is actually being set to 2000000 and data is being send to the Arduino at 2000000. My question is, does flashrom do anything with the baud rate setting other than just set the port? Is it used for timing internally? If so, that would explain why flashrom doesn’t work with aliasing when I set the baud to 300 (which is actually 20000000). Thanks Jason -----Original Message----- From: Urja Rannikko [mailto:urjaman@gmail.com] Sent: Friday, August 12, 2016 10:23 AM To: Jason Jacobs <Jason.Jacobs(a)FIRSTSOLAR.COM> Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] Windows Help Hi, On Thu, Aug 11, 2016 at 4:41 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > Hello, > > > > First, thanks for the awesome software and all the time you put into this. > I am trying to use it on windows with serprog. I installed libusb and > setup my device with libusb and installed the driver. How do I tell > flashrom to use my libusb device now? I tried > serprog:dev=<devicenameindevicemanager>:2000000 but it didn’t work. I > have been searching a ton on how to do this but can’t figure it out. For serprog, you shouldnt be installing a libusb driver for the device, but just a normal serial port driver (an .ini is needed for CDC ACM ports before win10, or an FTDI provided driver for ftdi devices, etc) , then use -p serprog:dev=COMx:2000000 where x is the COM port number in device manager for the serial port. (Also, be aware that this all works better on linux since thats where most of the developer resources are.)

1 0

Re: [flashrom] Windows Help
by Urja Rannikko 12 Aug '16

12 Aug '16

Hi, On Thu, Aug 11, 2016 at 4:41 PM, Jason Jacobs <Jason.Jacobs(a)firstsolar.com> wrote: > Hello, > > > > First, thanks for the awesome software and all the time you put into this. > I am trying to use it on windows with serprog. I installed libusb and setup > my device with libusb and installed the driver. How do I tell flashrom to > use my libusb device now? I tried > serprog:dev=<devicenameindevicemanager>:2000000 but it didn’t work. I have > been searching a ton on how to do this but can’t figure it out. For serprog, you shouldnt be installing a libusb driver for the device, but just a normal serial port driver (an .ini is needed for CDC ACM ports before win10, or an FTDI provided driver for ftdi devices, etc) , then use -p serprog:dev=COMx:2000000 where x is the COM port number in device manager for the serial port. (Also, be aware that this all works better on linux since thats where most of the developer resources are.)

1 0

Windows Help
by Jason Jacobs 11 Aug '16

11 Aug '16

Hello, First, thanks for the awesome software and all the time you put into this. I am trying to use it on windows with serprog. I installed libusb and setup my device with libusb and installed the driver. How do I tell flashrom to use my libusb device now? I tried serprog:dev=<devicenameindevicemanager>:2000000 but it didn't work. I have been searching a ton on how to do this but can't figure it out. Thanks Jason

1 0

Release numbering and branches
by Nico Huber 11 Aug '16

11 Aug '16

Hi folks, now that we have a git repository [1] ready (thanks Stefan!), I've visited again the flashrom development guidelines [2]. I stumbled there over a very long, exemplary version number: "0.9.10.1". IMHO, two things are wrong here: 1st there are too many dots for my taste, and 2nd the former two numbers are meaningless. To avert that, I call for naming the next release "1.0". If necessary it would get point releases "1.0.1", "1.0.2" etc, of course. Regarding the naming of release tags and branches, I really like what the Linux people do. In their naming scheme the tag for "1.0" would be named `v1.0` and the branch `flashrom-1.0.y`. With different pre- fixes for tags/branches it's always obvious what is referred to, and with a wildcard (here the `y`) in the branch name the ongoing develop- ment is emphasized. Opinions? other proposals? Nico [1] https://www.flashrom.org/git/flashrom.git/ [2] https://www.flashrom.org/Development_Guidelines

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom August 2016