flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Start a nNew thread

log Intel Q67
by Heijstek, J.W. 21 Aug '18

21 Aug '18

Hereby the -V of a Intel Q67 chip

1 0

Re: [flashrom] MX25L6473F Bios
by Nico Huber 20 Aug '18

20 Aug '18

Hello B., I guess you might have solved your problem by now, anyway: On 13.07.2018 15:56, B. Ford wrote: > I am trying to read a MX25L6473F bios chip, it is in your supported list > of chips. However when i read the chip (ch341a programmer) it asks to > specify the chip type using the -c command, but the MX25L6473F is not in > the selected ones, and therfore i cannot continue to read.. MX25L6473F was added rather late indeed. Though, it's one of those chips that share their ID with many others. For flashrom-0.9.9 this should work: -c MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E They are all compatible to the 73F as far as flashrom is concerned. Nico

1 0

Web Chat
by Milind Saraswala 16 Aug '18

16 Aug '18

I registered myself with username milindsaraswala(a)gmail.com and my real name Milind Please let me know how can I chat on http://webchat.freenode.net/?channels=flashrom&uio=d4 Regards, Milind Saraswala

1 0

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

15 Aug '18

Hi, On 14.08.2018 19:50, Владимир Амельянович wrote: > I would be nice to get the patch. I will check my board tomorrow. > I have 3 different boards. Would you like to get reports from all of them? it seems the issue is already mitigated by other changes in the core of flashrom (though, the actual bug is still there). For the moment, it would be nice if you could try flashrom-1.0 to see if the issue persists. Nico

1 0

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom