Dear Ladies and Gentlemen,
I hope you had a good start into the new year. Since you have already successfully applied for the Thomas-Krenn-Award with your project Flashrom, I would like to draw your attention to this year's award.
Open source projects can again win server hardware with a total value of 6,500 Euros.
The submission of a project is very easy - you select three configurations (1500 €, 2000 € and 3000 € net value of goods) and send an e-mail to award(a)thomas-krenn.com with a description for what purpose the server would be used in the project.
All details can be found below:
We at Thomas-Krenn would be delighted if you and your project could participate in our award again. You can also forward the information to other developers in the open source community (one submission per project is possible. There is also no registered association required to submit the project.)
The registration deadline is 27.01.2019.
Tel: +49 8551 91 50 264
[Lassen Sie sich zu Windows Server 2019 beraten]<https://www.thomas-krenn.com/de/produkte/software/microsoft-software/wind...>
Thomas-Krenn.AG; Speltenbach-Steinäcker 1; 94078 Freyung; Sitz der Gesellschaft: Freyung | HRB 6790;
Vorstand: Ralf Hohmann, Christoph Maier; AR-Vorsitzender: Guido Bollue
[Xing]<https://www.xing.com/companies/thomas-krenn.ag> [Facebook] <https://www.facebook.com/thomaskrenn.ag> [Twitter] <https://twitter.com/thomaskrennag> [LinkedIn] <https://de.linkedin.com/company/thomas-krenn.ag>
I'm trying to flash an ENE KB9012QF A3 KBC on LA-8241P motherboard. The
problem is flashrom can't detect the internal SPI of it, fails with error.
flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.5.2, GCC 7.3.0, little endian
Command line (5 args): ./flashrom -p rayer_spi -c KB9012 (EDI) -V
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing rayer_spi programmer
Using address 0x378 as I/O base for parallel port access.
Using RayeR SPIPGM pinout.
The following protocols are supported: SPI.
Probing for ENE KB9012 (EDI), 128 kB: edi_chip_probe: reading hwversion
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
How to get it working? Thanks a lot for help!
I am using this patch for a while now and I did not encounter any problems. I
am not sure if this was/is not supported. Is there any reason why this is not
Thank you very much,
This patch adds support for the MCP2210 USB to SPI bridge as a
programmer. Since the MCP2210 is an HID device I have a working version
using both libusb and hidraw + udev for finding the device. I have
already made a github pull request with more details:
https://github.com/flashrom/flashrom/pull/68. But I am posting it here
I realized I mixed up the flash part status with the motherboard, so
figured I'd better make that clear. Sorry about that.
On 1/4/19, Branden Waldner <scruffy99(a)gmail.com> wrote:
> I got an asus p2b to go with my asus p2-99 for coreboot testing and it
> works with flashrom.
> Erase and write are reported as untested, so attached are logs of
> flashing from the award bios and from coreboot. It reports failure
> when trying erase function 0, but tries erase function 1 and works. It
> also requires the this_is_not_a_laptop option to work with the award
> I can do any further testing or supply logs if required.
Hi to the cool guys from Flashrom!
I'm trying to dump the contents of a Winbond W25Q16 using the command:
./flashrom -p ft2232_spi:type=232H,port=A -c W25Q16 -r dump.rom
I'm getting an error that:
This flash part has status NOT WORKING for operations...
However, when I do "flashrom -L" the W25Q16 chip, with the exact same ID
appears on the list.
Here's a verbose output:
I also tried reading the chip without specifying the exact chip.
I got an asus p2b to go with my asus p2-99 for coreboot testing and it
works with flashrom.
Erase and write are reported as untested, so attached are logs of
flashing from the award bios and from coreboot. It reports failure
when trying erase function 0, but tries erase function 1 and works. It
also requires the this_is_not_a_laptop option to work with the award
I can do any further testing or supply logs if required.