flashrom August 2018

flashrom@flashrom.org

17 participants
30 discussions

Re: [flashrom] join IRC
by Nico Huber 14 Aug '18

14 Aug '18

On 14.08.2018 10:53, Владимир Амельянович wrote: > I made 3) > 3) verify image - flashrom -p > internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -v boxpc899_0.rom > > And result is VERIFIED. Heh, I missed this (your other mail went into another folder). So you can ignore my other mail, I guess. Though, if you want to try a patch for the error you've seen before, let me know :) Nico

1 0

Re: [flashrom] join IRC
by Nico Huber 14 Aug '18

14 Aug '18

Hi Владимир, On 14.08.2018 09:46, Владимир Амельянович wrote: > I have tried to write saved image finally. And got the following message: > > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... Reading 8388608 bytes starting at > 0x000000. > done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! > ------------------------------------------------------------------------------- > DO NOT REBOOT OR POWEROFF! > Restoring MMIO space at 0x7fb5896f08a0 > Restoring PCI config space for 00:1f:0 reg 0xdc > > -V output attached. > > What should i do next? PC is power on. Try to verify (flashrom -v) the image you just wrote. I hope it just succeeded but run into an error afterwards. >From your log: >> 0x805000-0x805fff:E >> Request to erase some inaccessible memory address(es) (addr=0x805000, len=4096). Not erasing anything. This is already beyond your actual flash chip (0x800000), so it al- ready wrote the image. I also found the cause for flashrom running off, your firmware descriptor seems misconfigured which triggered a bug in flashrom: >> 0xD0: 0xffffffff (FPB) This register is supposed to be 0 instead *shrug*. But there's obviously something to fix in flashrom to handle wrong values more gracefully. So, hope your board is fine, Nico

1 0

Re: [flashrom] join IRC
by Владимир Амельянович 14 Aug '18

14 Aug '18

I made 3) 3) verify image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -v boxpc899_0.rom And result is VERIFIED. 2018-08-14 10:46 GMT+03:00 Владимир Амельянович < amelyanovich.vladimir(a)gmail.com>: > Hello, > > 1) save image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -r boxpc899_0.rom > 2) write image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -w boxpc899_0.rom -V -o /lib/live/mount/medium/ > > I have tried to write saved image finally. And got the following message: > > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... Reading 8388608 bytes starting at > 0x000000. > done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! > ------------------------------------------------------------ > ------------------- > DO NOT REBOOT OR POWEROFF! > Restoring MMIO space at 0x7fb5896f08a0 > Restoring PCI config space for 00:1f:0 reg 0xdc > > -V output attached. > > What should i do next? PC is power on. > > > 2018-08-09 23:16 GMT+03:00 Владимир Амельянович < > amelyanovich.vladimir(a)gmail.com>: > >> Hello Nico, >> >> Thank you very much for your information. >> >> Does the image of SPI chip which i get with -r key contain BIOS firmware >> or BIOS settings or both? >> My goal is to create BIOS master image which i can write to 10,20,100 >> devices with same hardware. >> >> Regards, >> Vladimir >> >> >> 2018-08-09 22:11 GMT+03:00 Nico Huber <nico.h(a)gmx.de>: >> >>> Hi Владимир, >>> >>> On 08.08.2018 10:07, Владимир Амельянович wrote: >>> >>>> flashrom -p internal:laptop=this_is_not_a_laptop didn't change >>>> anything >>>> >>> >>> yes, because your BIOS claims that it's a laptop: `DMI string >>> chassis-type: "Notebook"`. >>> >>> flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs >>>> with >>>> different V number are attached. >>>> Please could you please tell me if i can use flashrom in my case? >>>> >>> >>> You already did. If you let it probe with the above force option, >>> it can already harm some laptops. But in your case (SPI chip directly >>> attached) it's safe. You can go ahead (if you have a valid image to >>> flash). In either case of success of failure, please always keep >>> logs (best use the -o option) and report back. >>> >>> Please note that your message got filtered from the mailing list (there >>> is a 256KiB limit for the mail size). So I'll attach your least verbose >>> log for reference. >>> >>> Regards, >>> Nico >>> >> >> >

1 0

Re: [flashrom] join IRC
by Владимир Амельянович 14 Aug '18

14 Aug '18

Hello, 1) save image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -r boxpc899_0.rom 2) write image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -w boxpc899_0.rom -V -o /lib/live/mount/medium/ I have tried to write saved image finally. And got the following message: FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... Reading 8388608 bytes starting at 0x000000. done. Apparently at least some data has changed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Restoring MMIO space at 0x7fb5896f08a0 Restoring PCI config space for 00:1f:0 reg 0xdc -V output attached. What should i do next? PC is power on. 2018-08-09 23:16 GMT+03:00 Владимир Амельянович < amelyanovich.vladimir(a)gmail.com>: > Hello Nico, > > Thank you very much for your information. > > Does the image of SPI chip which i get with -r key contain BIOS firmware > or BIOS settings or both? > My goal is to create BIOS master image which i can write to 10,20,100 > devices with same hardware. > > Regards, > Vladimir > > > 2018-08-09 22:11 GMT+03:00 Nico Huber <nico.h(a)gmx.de>: > >> Hi Владимир, >> >> On 08.08.2018 10:07, Владимир Амельянович wrote: >> >>> flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything >>> >> >> yes, because your BIOS claims that it's a laptop: `DMI string >> chassis-type: "Notebook"`. >> >> flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs >>> with >>> different V number are attached. >>> Please could you please tell me if i can use flashrom in my case? >>> >> >> You already did. If you let it probe with the above force option, >> it can already harm some laptops. But in your case (SPI chip directly >> attached) it's safe. You can go ahead (if you have a valid image to >> flash). In either case of success of failure, please always keep >> logs (best use the -o option) and report back. >> >> Please note that your message got filtered from the mailing list (there >> is a 256KiB limit for the mail size). So I'll attach your least verbose >> log for reference. >> >> Regards, >> Nico >> > >

1 0

Re: [flashrom] join IRC
by Nico Huber 09 Aug '18

09 Aug '18

Hi Владимир, On 08.08.2018 10:07, Владимир Амельянович wrote: > flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything yes, because your BIOS claims that it's a laptop: `DMI string chassis-type: "Notebook"`. > flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs with > different V number are attached. > Please could you please tell me if i can use flashrom in my case? You already did. If you let it probe with the above force option, it can already harm some laptops. But in your case (SPI chip directly attached) it's safe. You can go ahead (if you have a valid image to flash). In either case of success of failure, please always keep logs (best use the -o option) and report back. Please note that your message got filtered from the mailing list (there is a 256KiB limit for the mail size). So I'll attach your least verbose log for reference. Regards, Nico

2 1

Re: [flashrom] Failed flashing
by Nico Huber 09 Aug '18

09 Aug '18

Hello Paweł, sorry for the late reaction, your message was filtered due to its excessive size (we have a 256KiB limit). On 30.06.2018 10:33, Paweł wrote: > Thanks for answer. Check photo of my setup in attachment. It is workin > correctly. To check I also pulled W25Q32.V from working Asus P8B WS and was > able to correctly read bios several times with spispeed 1000,10000,20000. > Checksum was correct. Generally you'd want shorter connections. As you use a breadboard, you shouldn't need all the long wires, only those from the RPi to the bread- board. That it works with one chip is no proof that the signals are good enough. Also, not clearly visible in your picture, it doesn't look like you connect all input pins of the flash chip. If that is the case: You should always connect all of them, they need a defined state, no matter if you use their function (if in doubt, pull them high to VCC). Hope that helps (or you succeeded already), Nico

1 0

S25FL512S Chip Support
by Mitchell Johnston 08 Aug '18

08 Aug '18

Hi guys, Does flashrom currently support the S25FL512S/Sf25FS512S? I don't see it on your supported devices list but see many similar spansion chips. Thanks for your help, Mitchell Johnston | Electronic Design Engineer 3500 Deer Creek Road | Palo Alto, CA 94304 p 628 219 2633| e mjohnston(a)tesla.com<mailto:mjohnston@tesla.com> [cid:image001.gif@01CFFE65.0CC0FD00]<http://www.teslamotors.com/> The content of this message is the proprietary and confidential property of Tesla, and should be treated as such. If you are not the intended recipient and have received this message in error, please delete this message from your computer system and notify me immediately by reply e-mail. Any unauthorized use or distribution of the content of this message is prohibited. Thank you. [cid:image002.png@01CFFE65.0CC0FD00]<http://www.facebook.com/tesla> [cid:image003.png@01CFFE65.0CC0FD00] <http://twitter.com/teslamotors> [cid:image004.png@01CFFE65.0CC0FD00] <http://www.youtube.com/teslamotors> Please consider the environment before printing this email.

1 0

HP WX9400 Workstation Mainboard flash
by Joel I. Oelsner 08 Aug '18

08 Aug '18

Hello, I've bought a HP wx9400 workstationboard - In acutallity it's a Tyan S2915-E. So my problem is: HP have flashed a special hp bios and pflash from Phoenix does not allow you to flash the vanilla tyan bios. The board has a SST49LF080A chip, so in theory flashrom should work - would be my guess. So my question is: do I just rom flashrom -p internal -w s2915.rom?, or is there anything else I have to do before flashing a phoenix bios(except a backup). furthermore I don't think the mainboard chipset is not supported - the chipset is a NVIDIA NFP3600 / NFP3050 . best regards

1 0

MX25L6473E
by Emmanuel Cardona 08 Aug '18

08 Aug '18

Hi, I'm French guy and i have a problem with my motherboard. After MAJ bios failed on my MSI-Z87-G45, i have search to the web for solution and i've find : CH341A With Flashrom. I buy CH341A Black Edition with Cable Clip SOIC 8, In order not to have to desolder the chip. Check Ubuntu 18.04 on Laptop = ok Check install flashrom (sudo apt-get install flasrom) = ok Check install https://github.com/gschorcht/spi-ch341-usb = ok Then, in general didn't work > Flashrom can never write if the flash chip isn't found automatically. But it worked twice and here is the message : Calibrating delay loop ... OK. Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE ...bla bla bla .... Read is not working on this chip. Abording Ok now, that is my chip : MXIC MX25L6473E M2I-10G 3P261900 L13511S Something missing on my linux distribution? (drivers configuration ...) I need your help or advices. Thanks Emmanuel PS : Sorry, my English so bad.

1 0

Re: [flashrom] join IRC
by Nico Huber 07 Aug '18

07 Aug '18

Hello Владимир, On 07.08.2018 11:14, Владимир Амельянович wrote: > Thank you for information. > One more question. > I have industrial PC, manufacturer didn't provide any BIOS tool. > When i run flashrom i get the warning about problems with unsupported > laptops BIOSes and the following message: > "Aborting. > Error: Programmer initialization failed" > I use command "flashrom -p internal" > How could i fix it? whether or not flashing is safe despite this message depends on your board. If you provide a verbose log for this board, we might be able to tell you more. For instance, newer systems with the BIOS flash con- nected through SPI to the southbridge or almost always safe to flash (you can see in the manpage how to tell flashrom that your board is not a laptop, or that it should flash anyway). Hope that helps, Nico

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom August 2018